Answered

Set priority between possible errors in an Ad-Hoc SubProcess.

I've been digging for an answer to this in the BPMN Documentation and tutorials around the web but couldn't find one so far.

Situation is as follows:

  1. - I have a 'Check Order Status' ad-hoc subprocess, which itself contains tasks such as 'Check if order will meet the delivery deadline' and 'Check for other problems';
  2. - In case the order suffers a delay, the subprocess is interrupted to trigger a 'Ask department in charge for new deadline'. If the employee finds out the order had a problem (i.e. the order was cancelled for whatever reason), they start a refund process;
  3. - Both 'Order has suffered a delay' and 'Order had a problem' are error events attached to the subprocess;
  4. - The problem lies here: If an employee identifies a delay before a problem, it will inevitably trigger 'Order has suffered a delay' event and will never be able to spot the existing (fatal) problem, which is much more severe than a delay. The subprocess MUST be ad-hoc - since tasks therein cannot be sequential.

My proposed solution would be to set some sort of priority between the error events... but I'm not really sure how I would do that. Otherwise, I would have to turn 'Check for problems' and 'Check delay' into a sequential flow, but that would be much inaccurate.

Could you guys give me some sort of light?Thanks in advance,Dan.

photo
0

Dear Dani,

We have into our Process Xchange a process about Ad Hoc. It will help you: http://help.bizagi.com/processmodeler/en/index.html?process_templates.htm

In addition, in our sub-process types, we have an Ad hoc sub-process: Is a group of activities that has no REQUIRED sequence relationships. A set of activities can be defined, but the sequence and number of performances for the activities is determined by the resources of the activities.

hmfile_hash_48124cb1

Regards