Assigning Workflow Rules to Conceptual Objects
Workflow rules are assigned to a conceptual object are triggered whenever any type of change is initiated on the top level object. Transactions to parent and children are aggregated so that if there is a pending change to a parent record, a change initiated to the child record will be appended to the pending parent transaction.
Changes to child objects only trigger workflow transactions if the setting, Triggers Workflow?, is selected in the workflow rule. You can also control whether workflow is triggered for changes to the conceptual object and for any associated child objects (entity level).
To configure workflow for a conceptual object
1. On the Menu toolbar, click Define > Objects and navigate to the object you want to modify.
2. Click the object name and select the Workflow Rules tab.
3. In the Conceptual Object Rule Assignment, select the corresponding workflow rule.
Note:
When you assign a rule at the object level, it is triggered for any type of data change, insert, update, delete, and restore.
4. For each associated object, select whether a change triggers workflow and which type of rule is applied. Use the following table as a guideline.
Option | Description |
Triggers Workflow? | Whether to trigger workflow when a change is made to the child object. Workflow is always triggered on the top level object. |
Entity Level Workflow Rule? | Indicates whether to trigger the workflow rule assigned to the conceptual object or assigned to the child object. If this option is selected then the entity level workflow is triggered if its parent is already approved. Otherwise, if there is a pending change to the parent object, the conceptual object level workflow is triggered. Note:
This option is ignored if there is an unapproved change to a parent record. That is, the conceptual object workflow is triggered and the child record is appended to the pending parent transaction. |
5. Click Save.