Dynamic Workflow Integrations

• Configure the Integration and Data
• Workflow Configuration
• Form Configuration

At times, you may find it necessary to send data from a step within a Kuali Build workflow through an integration - and you need to be able to pick and choose which information is sent.

Configure the Integration and Data

Build Admins and app administrators can already configure an integration step to be used within a Kuali Build workflow. This will generally be a web application your campus IT staff has have set up or created to execute functionality that falls outside the scope of Kuali Build.

You can configure what data should be sent to the integration, including URL parameters, query parameters, HTTP Post body values, and HTTP headers by establishing an API integration, and then determining the exact values sent to these inputs within the Workflow Integration step that uses this integration.

Additionally, you can configure what data the integration will send to be used in a Kuali Build application - provided that the data is formatted as JSON.

Workflow Configuration

When configuring a Workflow Integration step that uses an integration that requires one or more pieces of data as inputs, the user must configure where that data will come from. It can either be from data on the form or a fixed value. When a Workflow is configured with an Integration step that has specified output fields, those output fields will be available to use in subsequent Workflow steps. For example, outputs that specify valid Kuali Build User objects (with a valid id and label) can be used as assignees in future workflow steps and most outputs can be used in Workflow Branch steps and Notifications.

Form Configuration

When an Application is configured with a Workflow Integration step that outputs data, that data can be shown on the form using the Read Only special gadget type. That field will remain empty until the Integration step has run and a valid value is returned from the Integration.