Weird Synchronous Dialog Chain & Substitution Problem

[NAT GOVENDER]

Hi Loren,

Please check in you container who are the excluded agents  for Task TS90000009.
I think that your excluded agent for task in second approver might be the initiator of first step.



Kind Regards

Nat Govender
Specialist - SAP Workflow
IT Parts Logistics
Toyota South Africa Motors (Pty) Ltd - Durban
T +27 31 910 2645  F+27  86 607 0414
E ngovender4 at toyota.co.za<mailto:ngovender4 at toyota.co.za> W www.toyota.co.za<http://www.toyota.co.za/_>

If you tell the truth, you don't have to remember anything.
People may not remember exactly what you did, or what you said but they will always remember how you made them feel.

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Bratzler, Loren
Sent: 12 August 2014 10:36 PM
To: SAP Workflow Users' Group (sap-wug at mit.edu)
Subject: Weird Synchronous Dialog Chain & Substitution Problem

I have a weird problem that is occurring with a synchronous dialog chain when there is UWL substitution involved.

For our invoice approval workflow, the approval process is a two-step process.  The first step launches the CHANGE method of the FIPP business object.  Then the second step is a standard user decision step with approve and reject options.  We use the "advance with dialog" option on these two steps so that the user will automatically see the approve and reject buttons when they exit from the CHANGE screen for the business object (making this a synchronous dialog chain).  Our approval process is such that the immediate supervisor of the person who created the invoice is always the first approver of an invoice.  Then if that person does not have the necessary dollar authority, we determine a final approver and send an approval task to that second person.

The issue we are running into occurs if the first approver happens to also be a UWL substitute for the final approver.  When the first approver completes the user decision step (the second step of the two-step dialog chain), the final approver's task is automatically starting in the first approver's inbox.  This is causing the task to be reserved in the first approver's inbox and the final approver never sees the task at all.

I did some testing in our QA system and was able to replicate the issue.  Here is the log when the first approver is not a UWL substitute for the final approver:

[cid:image001.png at 01CFB6BC.3EF38F90]


And here is the log when the first approver is a UWL substitute for the final approver.  The difference being that the final approver's task is being started automatically for the first approver:

[cid:image002.png at 01CFB6BC.3EF38F90]

It doesn't make sense that this is happening because the agents assigned to the first approver step (step 8) and the agent assigned to the final approver step (step 36) are not the same.
[cid:image003.png at 01CFB6BC.3EF38F90]

[cid:image004.png at 01CFB6BC.3EF38F90]

Has anyone ever run into something like this before?

Loren Bratzler
Norfolk Southern Corporation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140813/1351d698/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 33932 bytes
Desc: image001.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140813/1351d698/attachment-0004.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 34542 bytes
Desc: image002.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140813/1351d698/attachment-0005.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 20467 bytes
Desc: image003.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140813/1351d698/attachment-0006.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 20354 bytes
Desc: image004.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140813/1351d698/attachment-0007.png