Cascading Workflow Triggering
Cascading Workflow Triggering
Embedded Files
What is it?
What is it?
Most of the relationships between forms start from triggering. Triggering one's action causes a particular action, process, or a situation to happen. In the DragOnce platform, there are several types of triggering representing different types of relationships.
The source table and the target table are linked together and it is called parent-child relationship. It is used when one table’s value refers to the value in another table (usually a primary key of another table).
Cascading Workflow Triggering is a way of passing the value from Parent Form to Child Form, it is to to follow the workflow state of Parent Form.
How and When to use it?
How and When to use it?
In Cascading Workflow Triggering, the user has to connect the Source Form with the Target Form(s). After that, when the workflow state of the Source Form changes, this action will cause the Target Form(s) to change its state. The filtering function is available in Cascading Workflow Triggering to enhance the flexibility.
Use Case 1: Trigger one edge in one state
Use Case 1: Trigger one edge in one state
Workflow in Source Record:
Workflow in Source Record:
Workflow in Target Record(s):
Workflow in Target Record(s):
Use Case 2: Trigger more than one edges in one state
Use Case 2: Trigger more than one edges in one state
Workflow in Source Record:
Workflow in Source Record:
Workflow in Target Record(s):
Workflow in Target Record(s):
Use Case 3: Trigger more than one edges in different states
Use Case 3: Trigger more than one edges in different states
Workflow in Source Record:
Workflow in Source Record:
Workflow in Target Record(s):
Workflow in Target Record(s):
Use Case 4: Trigger one edge from different Forms
Use Case 4: Trigger one edge from different Forms
Action to start from Source Form
1st to Target Form A by Source Form
2nd to Target Form B by Form A
Information !
By default, there is an upper limit (1000) of times of workflow triggering per action, which is a shared limit.
Source form and target form of an update trigger rule do not have to be mother & son records (reference table relationship), they can be 2 unrelated forms.
Form(s) in Core Data can’t be selected as the target form.
The cascading workflow triggering will be done by 'System' (as shown in activity log).
No permission checking for cascading workflow triggering, meaning the rules are triggered regardless of the action taker’s permission rights to change target records’ workflow state.
Validation checking is valid for cascading workflow triggering. If target records don’t pass edge validations, the triggering will be counted as ‘failed triggering’.
Page updated
Report abuse