Transition triggers prompt transition changes by either manually initiating, automatically initiating, initiating through orchestration or logic blocks, or on a specific date and time. The table below summarizes the transition triggers that you can use to initiate a transition.

Transition TypeTransition initiates...Example
Manual 
When an application user manually changes the state from the row action or form action menu. 

For manual transitions, you can optionally define a data item of type Label. If defined, the label on the data item is displayed on the row and form action buttons used to transition the workflow. If no label is defined, the buttons display the default Transition to <To Workflow State> text.


Approval 
Based on the response of a user that has the authority to approve or reject a workflow transition.

Auto 
Automatically based on the amount of time that has passed. The time durations you can choose from are Queue Immediately, Process Asynchronously, Queue in 15 Minutes, Process Asynchronously, Queue in 1 Hour, Process Asynchronously, Queue in 12 Hours, Process Asynchronously, and Queue in 1 Day, Process Asynchronously. For Queue Immediately, Process Asynchronouslythere is about a 15 second latency. 

Automatic transitions make asynchronous changes to a record. Once automatic transitions have been initiated, the record is locked until all auto transition have occurred and the record automatically refreshes upon completion. Use these transitions during stages of the business process that do not require user interaction with the record. Or, if the transition initiates complex logic blocks that should be run in their own transaction boundary, regardless of user save.

If you add auto transitions on your workflow, you can optionally select the Enable Synchronous Processing checkbox to enable synchronous processing on your automatic transition triggers. Rather than being queued for asynchronous processing in the background, synchronous processing transitions run in their own transaction boundary but occur immediately after the record is edited by a user and saved.

For example, financial records are often set up to manually transition into Ready to Post, out of which they auto transition to Posted. During that auto transition, lots of calculations are performed, ledgers and balance tables are updated, and so on. To prevent users from making conflicting changes to a record while those updates are ongoing, the record is read-only. 

Orchestration 
When another table's workflow has reached a specific state/state type. Orchestration can be set up between any two tables. For orchestration in header and detail tables, you can configure it so that:
  • The header drives the details—The header state transitions all the detail lines to the same state.
  • The details drive the header—The detail lines must all have the same state before the header transitions to the same state. 
For example, you could initiate a transition on table one when table two reaches a state of Reimbursed and a state type of Closed. 
Logic Block Controlled By a logic block Queue Workflow State Change action. Logic block controlled transitions are initiated by a UI action or a batch job. The UI action or batch job executes a logic block that queues the state change which matches the From State in the workflow. 

For example, a logic block transitions a work order from Released to Complete when the final product completion transaction is processed. The batch job to release work orders moves the work order from Ready to Release to Released.

Effective Date On the date, or date and time, found in the Date or DateTime data item specified in the Effective Date Data Item field.

If the date specified in the data item is in the past, the transition is initiated. At five minute intervals, the system submits any outstanding workflow records with the current effective date transition to the workflow processing queue. 

If the data item in the transition is a Date type it will transition at midnight in the tenant's default time zone. If the data item in the transition is a DateTime type it will transition the instant in time defined in the time zone defined. Both will default to tenant time zone if no time zone is specified. 

You can select either On Date or Next Day in the Effective Date Onset field to initiate the transition on the exact date found in the data item, or the day after the date specified in the data item. For On Date, data items of type Date transition at 12:00am on that date, while data items of type Date Time transition at that date and time. If the Effective Date Offset is Next Day, the transition occurs 24 hours later. 

For example, if the DateTime data item holds a value of 9:30am on March 1, 2023, and you had a value of On Date selected, the transition would occur at that exact date and time. 
Report By a Report Success or Report Error condition. The Queue Report to Run action is typically triggered by a logic block transition, then a report transition is initiated by the report's success or failure.
See the Configure a Report Transition for workflow topic. 
For example, a logic block success transition could initiate a report to run and change the state from In Progress to Send Deposit Invoice. If the report succeeds, a report transition changes the state from Send Deposit Invoice to In Progress. If the report errors, a report transition changes the state to Failed to Send.

Workflow Throttling

Workflow throttling reduces the likelihood of contention between workflow transitions running in parallel. By default, the system processes as many transitions in parallel as possible. Parallel processing can cause contention issues if multiple transitions are trying to update the same record. 

Auto Transitions can enable throttling by selecting the Enable Throttling checkbox on the transition in the workflow definition. The majority of workflow Auto Transitions do not have risk of contention and do not need to be throttled, however, there are several scenarios where it should be enabled, such as:

  • Auto Transitions which update the same record in the same table.
  • Multiple Auto Transitions which orchestrate a single record. For example, multiple Detail records orchestrating the same header record. In this instance, throttling should be enabled in the detail records. 

Throttled transitions limit the number of workflow transitions that can be executed in parallel. For detail tables, transitions are processed one a time for the associated header record. For other tables, throttled transitions limit the number of workflow transitions that can be executed in parallel.