Table Driven Dynamic Parallel Processing and Deadline...

[Bratzler, Loren]

You should be able to just set a deadline on the approval task and then put your send mail step in that deadline path.  Due to the nature of how parallel processing blocks work, the deadline path will only be enforced on the users who do not make their decision.

Here is an example where I created a parallel processing block.  There is a “requested end” deadline set on the Primary Decision step.  If the approver does not make their decision by the time the deadline is reached, the workflow takes the outcome path labeled “Primary Deadline Reached”.  In my example, I am then using a Process Control step to set the Primary Decision task to obsolete which then causes the workflow to take the “Decision Not Made” path.  However, in your case, you could replace the Process Control with a send mail step and send the notification to the current user occurring in the instance of the processing block.



[cid:image001.png at 01D09EB0.C7B70F00]

Loren Bratzler
Norfolk Southern Corporation

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Richa Gupta
Sent: Thursday, June 04, 2015 2:45 AM
To: SAP Workflow Users' Group
Subject: [EXTERNAL] Table Driven Dynamic Parallel Processing and Deadline...

Hello Folks,

I am developing a workflow for Journal Entry approval where in I need to use table driven dynamic parallel processing along with deadline.

So, for user decision step I have implemented parallel processing. But in modelled deadline path, I need to send an email only to that approver who misses the deadline.

So, question is how can I come to know which all users missed deadline and who all have taken action on user decision.

Kindly suggest.

Regards,
Richa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20150604/022fc4e0/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 23716 bytes
Desc: image001.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20150604/022fc4e0/attachment-0001.png