...
Feature | LEAP | Kuali Build |
---|---|---|
Coding | Low Code option allows addition of JavaScript to events and in application start. | No custom coding. |
Workflow | Requires custom code for audit trail. | Built-in audit trail. |
Routing | Restrictive routing, requires buttons and hide rules. | More flexible routing options. |
Dashboards | Requires a great deal of custom code to build a dashboard. | Has built in dashboard for individual Submissions, Drafts, and Action Lists across all Kuali applications. |
Export/Back End Data | Can export based on filters of fields and records in an admin screen. Can only save one filter; filters are complex to create. | Exports entire record set and fields; can filter on column values, perform an open search, and save multiple searches/filters and share them with others. |
Requires custom coding. | Can produce a PDF of the entire document. | |
Web Services | Can consume rest-based services or soap if a developer creates a custom soap interface. Rest services can be configured by the application developer. Web services can be consumed between LEAP applications. | Can consume rest-based services. Soap services requires separate middleware translation. Rest services centrally configured by Kuali admin; available to all developers (more restrictive control coming in future release).No ability to consume web services between Kuali Build applications (intended for future release). |
Access Control | Groups configured and maintained by the developer in each application but require redeployment of the application. | Groups centrally maintained by Kuali Administrator but can be used across multiple applications and do not require redeployment of application. |
Cloning | Requires custom coding to allow user to clone a record. | Can clone requests from their submission list. |
Deployment | Developers build in test environment; ITS publishes to production environment. Changes impact existing records so care must be taken to account for records still in flight. Unable to see what previous versions of form. | Developers work in production environment only and can publish their changes. Changes only impact new records going forward. Version history of the records is preserved. |
Testing | Form preview can be used to preview start stage of form. Workflow testing requires multiple accounts to verify permissions, workflow, and notifications. | Form preview can be used to preview form at start stage. Workflow simulator can be used by developer to test workflow and notifications without need for multiple accounts. |
Tables | Can create tables on form to hold unknown number of subset data. | Tables coming in next release of product (expected Oct 2021)are available but without the option to make required on the table itself or items in it. No formula to sum table data. |