Communicating within domain orders

[molayd]

Hi members,

As per recommendation in sample flows/sub-flows in OMT demo data, Order Stage is used to control the flow progression among several domain order flow.

For example, a CFS flow should only start after its child RFS has order stage as X.

For some reason, we can't use the order stage. What's best possible alternate way/solution to achieve such inter order communication?

Thanks,

Molay

[Tony Chatfield1]

Hi, can you clarify the reasons why you cannot use the OOB solution?
Also, what exactly you mean by 'domain orders'? I assume that as a OMT your instance domain separated? why does this prevent the use of order 'stage'?
If you are building custom flows\sub-flows then you can trigger functionality based on any fields content, but moving away from the OOB solution would involve unnecessary development and technical debt.

Perhaps you could update this thread to provide clear details of your business requirements, use case and the reason you have for not utilizing OOB functionality?

[molayd]

Hi Tony,

---

@Tony Chatfield1 wrote:

Hi, can you clarify the reasons why you cannot use the OOB solution? [Molay] In organization, there are multiple tenants for OMT application. Hence the governance board is reluctant to make any custom entry in Order Stage table.
Also, what exactly you mean by 'domain orders'? I assume that as a OMT your instance domain separated? why does this prevent the use of order 'stage'?[Molay] Product, Service & Resource orders are known as domain order.
If you are building custom flows\sub-flows then you can trigger functionality based on any fields content, but moving away from the OOB solution would involve unnecessary development and technical debt.

Perhaps you could update this thread to provide clear details of your business requirements, use case and the reason you have for not utilizing OOB functionality?

---