Suppose I have two Processes deployed, one that reads from an excel and adds rows to a single database table, and a second one that reads from all the tables in the database and writes output to a text file.
I want each of these Processes to be available standalone. At the same time, I want a third Process that first adds row to the table (Process1), then writes to the text file (Process2) and then maybe emails that text file to someone. In other words, I want to orchestrate (in the SOA sense) the two available Processes into a third super Process.
If at any time I wish to update Process1 or Process2, I should not have to touch the “super Process” at all.
The only available solution to this problem I have found so far is maybe to publish Process1 and Process2 as libraries, but that requires a workaround as the “Highest Applicable Version” Runtime Rule is not yet available. Is there a better way to do this? Note that I want my two processes to be executed one after the other, never simultaneously (so maybe “Start Job” activity does not help?)