The Low Codes Solutions team offers 2 different platforms on which UW-Madison staff can build web applications:
- Kuali Build
- Betty Blocks
For speed and ease of use, an application should be built in Kuali Build (Kuali) unless it is beyond the capabilities of the Kuali platform. The following table outlines what Kuali can do then moves into the additional functionality of Betty Blocks.
The following table outlines what types of features and development work are feasible using Kuali.
Betty Blocks is suited for developing applications of medium complexity. Development in Betty Blocks requires greater expertise and development time. The following table outlines what additional features and development are feasible in Betty Blocks beyond the capabilities of Kuali.
If it seems like one of these tools will meet the needs of your development project, or you are unsure or have questions about tool capabilities please fill out the customer support form.
If this tool does not meet your needs, we recommend that your fill out the University IT Project Intake form.
- Kuali Build's features
- Betty Blocks' additional features
- Service Team assistance required
- Not capable
Kuali Build expertise: These features would require some tech-savvy experience in permissions, data and process flow, and form and field manipulation.
- Gather form data
- Store form data
- Secure/NetID login
- Display public data without a required login
- Collect qualitative and quantitative data
- Upload images
- Upload documents
- Customize help text in-form
- Customize form text
- Conditionally make fields required/perform validation based on prior criteria
- Import/use live campus data via API
- Export form data to another campus database via API or another Kuali application
- Automatic email notifications based on triggers
- Auto-fill fields based on basic user information
- Different user types/different permissions
- Filter dropdown lists based on other fields
- Export data in a tabular manner via csv
- Conditionally show/hide fields
- Multi-part forms
Other:
- Preview the form and Test the workflow prior to saving data
- Create editable and publishable versions of the form and workflow
Betty Blocks Expertise: These additional features would require IT experience needed in data modeling, bridging data, API specifications and set-up, SSO/permissions, condition logic.
- Multiple workflows, multiple forms/pages
- Create data models and own data
- Auto-fill text into fields based on certain conditions
- Generate pdfs from any data stored and/or captured
- Display and search of tabular data
- Multiple attachments per email notification
- Scheduled processes
- Manipulation of data
- Date calculations
- Eligibility calculations
- Looping through stored data
- Custom code
Expertise: These features would require a Service Team IT developer.
Time: These features would require week(s) for set-up and testing per feature or data source.
- Connectivity to Salesforce
- Connectivity to Tableau
- Connectivity to other data sources (especially non-API)
- Dynamic approval workflows
These features are not possible to create within a Betty Blocks application at this time:
-
Custom CSS (stylesheets) inserted directly
-
Visualize data in graphs, charts, etc.
-
Export data into designed reports
-
Allow a single user to have multiple roles
The following list provides details, examples and definitions of the features listed above.
Kuali Build features:
- Gather form data – intake request form, approval form, incident form
- Store form data – data entered and captured on a form stored in Betty Blocks
- Secure/NetID login – UW NetID needed to log into application
- Display public data without a required login – ability to build applications that display only public information with no login required for users
- Collect quantitative and qualitative data – quantitative data = number, price, checkbox; qualitative data = long text
- Upload images – select allowable file extensions e.g. png, gif
- Upload documents – select allowable file extensions e.g. doc, txt
- Customize help text in-form – add help text by fields
- Customize form text – change data field labels, button labels, text on form
- Conditionally make fields required/perform validation based on prior criteria – value selected in field above causes a field below to be required
- Import/use live campus data via API – consult service team and KnowledgeBase articles for accessing CAOS API, Person API, etc.
- Export form data to another campus database via API or another Kuali application – consult the service team and KnowledgeBase articles for approvals and how-to
- Automatic email notifications based on triggers – e.g. upon submitting a form, send an email to approver
- Auto-fill fields based on basic user information – e.g. select a Kuali user name (from all UW-Madison staff), then email and NetID will auto-fill
- Different user types/different permissions – e.g. student user types see certain pages and fill in certain data, administrative staff can edit additional sections and see all current student data given permission
- Filter dropdown lists based on other fields – e.g. a WI county selected and list of cities within county appear in next field’s dropdown list
- Display in tabular manner data in tabular manner and export via csv – e.g. data displayed in multiple rows and columns with a button to export to csv file format
- Conditionally show/hide fields – value selected in field above causes a field below to be seen or hidden
- Generate pdfs from data captured – export form data, workflow history, and/or comments from workflow with LCS service team assistance
- Multi-part forms – forms with multiple sections can be broken out into different pages????
Other:
- Create testing application and production application – allow others to test your application and make adjustments, then create a copy without the testing data and publish
- Editable and Publishable versions of the form and workflow – Edit the form and/or workflow and run through the preview prior to publishing it for others to see and use
Betty Blocks additional functionality:
- Multiple workflows, multiple forms/pages – forms with multiple sections broken out into different tabs/pages/steps
- Create data models and own data – create data many-to-many data relationships; responsible data stewardship of the data captured and stored
- Auto-fill text into fields based on certain conditions – e.g. a WI county selected and extension main office address fills in
- Generate pdfs from any data stored and/or captured – create a form of the desired layout with data to display, add a pdf button to export
- Display and search of tabular data and export via csv – e.g. data displayed in multiple rows and columns with a button to export to csv file format
- Multiple attachments per email notification – e.g. send a pdf of the data entered in the form plus any artifacts uploaded to the form
- Scheduled processes – e.g. weekly updates, looping through data for clean-up
- Manipulation of data
- Date calculations – e.g. determine how many days since a certain date entered on the form
- Eligibility calculations – e.g. prior to displaying pages, determine if the user meets eligibility criteria and if not, display a page indicating such
- Looping through stored data – e.g. change the status of records depending on certain criteria or purge depending on criteria
- Custom code – e.g. code a custom action step using Javascript and Command-line tools
Service Team assistance required:
- Connectivity to Salesforce – data exchange between Salesforce CRM and a BB application
- Connectivity to Tableau – data sent to Tableau for Tableau dashboard, chart
- Connectivity to other data sources (especially non-API) – data pulled or sent to something other than CAOS API, Person API, like a standards registry
- Dynamic approval workflows – e.g. depending on dollar amount or other criteria, the form needs approval by different supervisors/stakeholders
Not capable:
- Custom CSS inserted – e.g. each application’s style is set, no import of stylesheet allowed
- Visualize data in graphs, charts, etc. – recommend exporting to Tableau or csv/excel to visualize
- Export data into designed reports – only the data can be exported, the format in which the data should appear can’t be exported
- Allow a single user to have multiple roles – Per UW’s SSO set-up , only one roll will be used per user. If you were using standard BB authentication, and a user was given multiple roles, their access would be at the least privileged role.