Does anybody have any Design Best practice for interactions between projects?
Within a project, design best practice between workflows is understood and documented.
Orchestrator provides the ability to “Schedule” but does not give “Dependency”.
The scenario would be a “Project” in Studio, creates a “Package” which is then defined as a “Process” for use in Orchestrator. Depending on the success or otherwise of that “Process”, a different “Project” may need to execute in order to “Clean-up” from the error situation.
The same “Clean-up” process might be used for different “Process” executions, which therefore does not suggest that the code should be duplicated into each “Process” as extra workflows.
My only thought is to use an Orchestrator queue and place information on that. Such an approach would mean a lot of executions of the “Clean-up” process to check on the state of the information on queue.