Is Low Code Solutions right for me?

The following list provides details, examples and definitions of the features listed above.

Low complexity:

• 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 or validation messages
• 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

Medium complexity:

• 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 – consult 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 reviewer
• 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 filled in
• Different user types/different permissions – e.g. student user types see certain pages and fill in certain data, administrative staff see other pages of all current student data
• 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 – create a form of the desired layout with data to display, add a pdf button to export
• Multi-part (page/tabs/steps) forms – forms with multiple sections broken out into different tabs/pages/steps

High complexity:

• Static approval workflows – e.g. a filled out form always gets sent to the user’s immediate supervisor
• Video and help pdfs embedded – e.g. before filling out a field, the user clicks on a help video that opens in a new tab
• Embed application pages on a UW WordPress website – e.g. data collected in a BB application is formatted and displayed in a certain way which then appears in that same format on a different website’s page

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 CCS 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.