Parallel Split / Uncontrolled Merged - Human activities don' disappear

[Former Member]

Hi,

I am modelling a BPM process, where users can perform approvals via 2 "channels". The first "approve-option" is a Human activity (-> UWL-Task), second is another application, calling an Intermediate Message Event WebService of the process.

I modelled it using a parallel split with 2 branches (first contains the Human activity, second contains the Intermediate Message Event). By using an Uncontroled Merge after that, I want to make sure that the process continues if ONE of the two approval-options is used.

Now I am facing the problem, that the Human activity (UWL task) still appears after the Intermediate Messaging Event has been called. When looking at the Flash Process Diagramm, it shows me that the process instance continued after the uncontrolled merge (-> good), but there is still a "green dot" pointing on the Human activity (-> bad ;).

I want the Human activity to be kind of "skipped" by the BPM engine when the process flow continues, triggered by the other branch (Intermediate Msg Event).. Is there a better way of modelling such kind of scenarios or did I maybe miss something?

Thanx in advance!!!

Mirco

[Former Member · Accepted solution]

Hi Mirco ,

I haven't tried this scenario myself but it should be possible.

Did you check this blog ? /people/soeren.balko/blog/2010/01/22/enjoy-netweaver-bpm--part-3-workflow-patterns-reloaded--netweaver-bpm-720 (Cancellation and Force Completion Patterns)

This will give an idea on how to model

Regards, Anil

[Former Member · Accepted solution]

Hi Anil,

thanks a lot for your help.

From my point of view, it seems to be possible to use the "Cancellation Pattern" by encapsulating the Human activity in a sub-process - although this will be more effort than I expected (new Intermediate Messaging event, new Service-Configuration in NWA, issue about calling principal and SAP_BPM_SuperAdmin role).

I will check if it works!

Thanks

Mirco

[Former Member · Accepted solution]

Hi,

just to confirm, the solution via Subprocesses - using the Cancellation pattern - solved our problem.

Thanks again

Mirco