Service Requests in Domain Separation

[Ryan S]

I have a domain-separated instance and looking for advice/guidelines for building out service requests. What factors should help determine in which domain a service request should be built? Some scenarios below, particularly scenario 2 would like to understand reasoning behind an approach:

1. Every client uses the same form/flow (global)
2. Every client uses the same form/flow except 1 client needs an extra approval step:  Do we create an override in the client's domain or just do logic in the flow?
3. Several clients need different forms (different fields and/or different dropdown values) and different flows: global for 'standard' then overrides for each client?

[Niamul Arifin]

Hi Ryan, 

First of all, you need to identify what domain your Service request should be in. Based on your question, sounds like it ll be either global domain or a shared top level domain where you are managing all of your MSP's clients.

If I understand correctly, a form/flow/catalog item will be used by all clients, except one specific client of yours, who will use the same flow but have additional approval requirements. You can have that extra approval step in the flow designer flow by using the sys_domain as part of your trigger condition. If the trigger is TRUE in the flow, then it ll go through ACTION which is going to have that additional ask for approval step. If FALSE, then it ll skip the additional approval and continue as usual for the rest of the clients.

Hope this helps. Please mark complete if my comment answers your question.