Flow Designer and Domain Separation Considertation

[BhupeshG]

Recently I came across few things with Flow designer on a domain separated instance which otherwise works fine which I believe we should consider before we deploy such flows in Domain separated instances.

1) Write flows in Higher domain if that is to be inherited by all domains and they inherit the same process. 

2) Prefer to run the flow as User who initiates the session rather than system. This will ensure flow context is created in user domain. Same like workflow.

3) ensure this property com.glide.hub.flow.approval.group_member.use_query_no_domain is set to true. Else you might up end up having issues in approval not generated if approval group or group members are in parallel domain or higher domain.

By default, Flow Designer only generates approvals for group members who are visible from the domain of the parent request. You need to set the above property to True to bypass this limitation.

4) Edit Flow Designer content in the domain to which it belongs else it may create a override copy in child domain

I hope this information helps !

Idea , views and comments are welcome. Anything that others have faced and resolved, please feel free to add so that this information can be appended.

[drrob]

I'm still having issues with this.

A RITM has been created in a domain, but the approval group is in a different domain, and the members are from that domain. When Ask for Approval, then only the approval user from the same domain as the RITM are attached.

I have the property mentioned above set, it doesn't seem to make any difference.

On Vancouver release.