VV
Hi all,
I have different processes like "Create account"; "Add mandate on account"; "Add account to reporting" etc...
At a high level, I have the same structure for all these processes:
Validate request + Implement request + Confirm to customer.
All these processes are triggered by the same paper form. One filled in form can be the trigger of different processes.
For instance, a customer requests via the same form the creation of an account with a mandate for the partner...
To model the processes individually is OK but I have problem with the multiple request.
Indeed, I have the following requirements:
For 1 form (multiple request or not...) if the customer is to be contacted in the validation step, he cannot be contacted more than 1 time; For 1 form (multiple request or not...) the customer has to receive only 1 confirmation.
=> The multiple request creates dependencies between the processes
As there is a lot of possible combination, the list of possible multiple request is quite long.
Question: do you have any suggestion to model those dependencies in a light and clear way?
Thanks in advance,
I would model this as multiple processes. At the high level model the dependencies Validiate Request -> Implement Request -> Confirm Request. Implement Request would then have a subprocess assigned to it that shows the detail - Evaluate Request Type followed by and OR branch and then the process to be performed for each type of request Create Account, Add Mandate, etc. Each of those would in turn have a subprocess that contains the detail of taking care of that request type.
