You can configure workflow version-specific settings in the Settings tab of a workflow version.
Available settings include cleanup policy, execution priority, security, runtime settings, triggers, notifications, and input parameters. If API callout is selected as a trigger, the API endpoint and token are also displayed in the Settings tab.
In the Overview section, you can update the name and description for the workflow definitions. You can specify a Category for the workflow definition so that you can quickly filter the workflow on the home page later. The Name, Description, and Category fields are for a workflow definition and apply to all the versions of that workflow definition.
You can add information about the workflow version in the Version Details field.
In the Cleanup Policy section, define the number of days that the Workflow Run data, including attachments and logs, are retained. Only Workflow Runs without pending, processing, or queued tasks will be deleted.
For all non-production environments, the default setting is 30 days with a configurable time range of 1-45 days.
For production environments, the default setting is 45 days with a configurable time range is 1-90 days.
See Use Data Query to report on Workflow for accessing workflow logs and reports using Data Query.
In the Execution Priority section, you can select the priority of this workflow relative to other workflows in the same Workflow instance.
Higher-priority workflows take precedence over lower-priority workflows. When a workflow of higher priority is initiated, it will be placed ahead of lower-priority workflows that are running. Depending on the available resources, lower-priority workflows may be paused until resources are released.
If you set all workflows to High, the execution sequence will not change as they are the same priority. Zuora recommends that you set high priority only for important workflows that need to be run without delay.
- Encrypt Files - If this option is selected, all files in this workflow version are stored with client-side encryption.
- Secure Error Messages - If this option is selected, the original messages of the unhandled errors are invisible for information security reasons. The error message will be shown as "Workflow will not report sensitive errors for unhandled exceptions."
Ignore Pending Status - Workflows are placed into the
Pending status if there are pending tasks during execution, such as the Approval Task, Delay Task, and Callout Task Retry. If you’ve set a workflow to ignore the
Pending status, the workflow status switches to
Finished and the On Finish branch could execute multiple times for each occurrence of pending tasks moving to the
Error status. As a result, this could also create unwanted success or failure notifications.
In the Workflow Triggers section, select the triggers for the workflow version.
- On Demand - The workflow version will run when manually initiated.
- Callout - The workflow version will run upon an API callout. This option must be selected to integrate with the Configurable Payment Retry feature or the Collections Window feature in Collections.
- Scheduled - The workflow version will run based on the configured schedule. If this option is selected, configure the running schedule in the Schedule Config section.
A scheduled workflow run will be skipped under the following circumstances:
- Another workflow run is in the Queued or Processing status.
- A pending task will run within three minutes. For example, if a delayed task from a previous run is scheduled to run in 2 minutes of the next scheduled time, the next workflow run will be skipped.
- The workflow version is deactivated.
You can set the Active Scheduled Run Check option to False to prevent any previous workflow run from blocking a later run. But note that setting this option to False could potentially lead to the situation where multiple scheduled workflow runs are run at the same time and on the same data set.
Note down the callout URL and API token displayed in the Callout Configuration section. If you intend to integrate Workflow with Configurable Payment Retry feature or the Collections Window feature of Zuora Collections, you need the URL and API token for system integration. See Set Up the Configurable Payment Retry Feature or Set Up the Collections Window Feature for more details.
In the Mapped Input Fields and Params sub-section, define the mapping between data fields in callouts and corresponding data fields in the workflow version. When a defined parameter is passed via callout, it will be recognized by the workflow. In the workflow version, the passed-in parameter is referenced by in the format of Data.<Object>.<Field>.
For example, if you define the following pair of input and workflow fields.
|Callout Field Name||Object||Field Name||Datatype|
You can reference this parameter using this Liquid statement.
Click Add New Mapping to add a new pair of data fields, and click Update to save the fields and parameters that you enter.
Always Show Prompt
You can configure to be prompted to set the value(s) of the input fields each time before a workflow version is run.
Make sure the workflow version is in the Inactive status. You cannot modify active workflow versions.
Under the Inputs section, toggle on Always Show Prompt.
Later when you run the workflow version manually, you will always be prompted to set the input values. Make sure that you set the version back to Active.
In the Workflow Email Notifications section, configure the events upon which you want to receive notifications and enter the email addresses for receiving notifications.
See Enable alert notifications for workflow failures for more information.