Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Kuali Build is intended as a self-service workflow tool for University departments to build their own workflow applications on a platform that is centrally supported by ITS and Kuali.  The rich capability of forms design and workflow engine along with an easy to use interface provides a much more effective and efficient experience as compared to using PDF or Word documents for facilitating electronic workflow. 

For access to Kuali Build we recommend attending a one hour introduction.  If you would like to request an introductory session, please submit via the Technology Support Center Portal:  https://techsupport.uconn.edu/



Roles and Responsibilities

...

Comparison of LEAP and Kuali Build for Developers

FeatureLEAPKuali Build
CodingLow Code option allows addition of javascript on events and in application startNo Custom Coding
WorkflowRequires custom code for audit trailBuilt in audit trail
RoutingRestrictive routing, requires buttons and hide rulesMore flexible routing options
DashboardsRequires a great deal of custom code to build a dashboardHas built in dashboard for individual Submissions, Drafts and Action Lists across all Kuali applications
Export/back end dataCan export based on filters of fields and records in an admin screen.  can only save one filter.  filters are complex to createexports entire record set and fields, can filter on column values and can perform an open search, can save multiple searches/filters and share them with others
PDFRequires custom coding Can produce a pdf of the entire document
Web ServicesCan 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 applicationsCan consume rest based services.  soap services requires a separate middleware translation.  Rest services are centrally configured by Kuali admin and available to all developers (more restrictive control coming in future release).  There is no ability to consume web services between Kuali Build applications (intended for future release)
Access ControlGroups are configured and maintained by the developer in each application but require redeployment of the application.Groups are centrally maintained by Kuali Administrator but can be used across multiple applications and do not require a redeployment of the application.
CloningRequires custom coding to allow for user to clone a record.Users can clone requests from their submission list
DeploymentDevelopers build in a test environment and ITS publishes to production environment.  Changes impact existing records so care must be taken to account for records that are still in flight.  Unable to see what form looked like at point in time.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.
TestingForm preview can be used top preview the start stage of the form.  Workflow testing requires multiple accounts to verify permissions and workflow and notifications.Form preview can be used to preview the form at the start stage. Workflow simulator can be used by developer to test the workflow and notifications without the need for multiple accounts.
TablesCan create tables on form to hold unknown number of subset data.Tables coming in next release of product expected Oct 2021