Workflow and Domain separation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
8 hours ago
Hello everyone,
I know this is quite a noob question but does workflow bypass the domain separation rule.
As I understand if I have a a record on LEVEL_1 domain it should execute LEVEL_1 workflow. However, my record is in LEVEL_1 domain but it the example#1 workflow on global and example#2 workflow on LEVEL_1 are both executed.
The example#1 workflow on global stopped executing only when I create a clone for the global workflow, make it the LEVEL_1, make the run condition as "Run if no other workflows matched". Now only example#2 workflow on LEVEL_1 is executed.
Is this just the behavior of the workflow?
As I see this in the docs "A flow in one domain cannot override or prevent a flow from another domain from running. Workflow Studio runs any flow that is visible to the current user and whose trigger conditions have been met. For example, a flow belonging to the TOP domain that is triggered by the creation of an incident record runs anytime an incident is created, regardless of whether the incident is created in the ACME or INITECH child domains." . Ref: Docs | ServiceNow
And "A user in a child domain may check out but not copy a workflow from a parent domain. When a user in a child domain checks out a workflow from a parent domain, the system creates a version of the workflow in that user's domain. This new version is a unique record in the Workflow [wf_workflow] table. After the user publishes this new workflow, other users in the child domain use the new workflow, which overrides the workflow from the parent domain. The original workflow in the parent domain is no longer visible to users in the child domain." Ref: Domain separation and Workflow • Zurich ServiceNow AI Platform Capabilities • Docs | ServiceNow
