Trigger types for input contracts
On Demand trigger
The On Demand trigger is initiated through a direct API invocation via REST, specifically the Job Manager Submit API. π See the Job Manager APIs page for more details.
The API accepts variables, which are passed to the instance as process variables. Any variables specifically declared in the template when creating a contract are combined with the set of variables supplied through the REST call. If the same variable name appears both in the contract template and the REST request, the value from the REST request takes precedence.
Time trigger
Time-based actions are executed at specific times, like daily at 6 a.m. When the designated time is reached, the workflow rule reassesses the record to verify that it still meets the rule criteria. If it does, the workflow rule performs the specified actions.
Trigger Requirements: A cron expression is needed. The workflow instance starts when the time specified in the cron expression matches the current time. No additional variables are introduced to the workflow instance.
Contract Variables:
cronExpression - required
Type: plain text [STRING]
Example: * * * _ ? _
systemEnableLogDebugToFile - optional
Type: Enabled/Disabled [BOOLEAN]
systemErrorHandlingWorkflowTemplateName - optional
Type: Enabled/Disabled [BOOLEAN]
jobManagerPriorityQueueName - required
Type: WUI custom [QUEUE]
Default: Default Queue
systemWorkflowInstanceSingletonMode - optional
Type: Enabled/Disabled [BOOLEAN]
Additional variables:
contractNameThisInstanceBelongsTo
Type: plain text [STRING]
Example: ContractName
templateNameThisInstanceBelongsTo
Type: plain text [STRING]
Example: TemplateName
centralLogCorrelationId
Type: plain text [STRING]
Example: d90fef7b-1517-4ad6-b836-18b6b4645be7:0
Last updated