Workflow scope defines the level of records that a workflow can effect; it is similar to access levels. You can define user scope when you want to run workflows on records owned by a user, but if an organization level is set, any record can trigger a workflow.
The workflow scope levels are shown in the following screenshot:
We have the following options to set workflow scope:
- User: If workflow scope is set to User and is set to run when an entity record is created, the workflow will only be executed if the owner of the workflow creates a record.
- Business Unit: When workflow scope is set to Business Unit and is set to run when an entity record is created, the workflow will execute when any user from the same business unit of the workflow owner creates an entity record.
- Parent: Child Business Units: When workflow scope is set to Parent: Child Business Unit and is set to run when an entity record is created, the workflow will be executed when any user from the same business unit and from all the subordinate business units of the workflow owner create an entity record.
- Organization: If workflow scope is set to Organization and is set to run when an entity record is created, it will be executed when any user creates an entity record.
When an automatic workflow is initiated, the security of the workflow owner is enforced, but when an on-demand workflow is initiated, the security of the current user is enforced to run the workflow.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.