I have a question. If I add a Run parallel actions action to my workflow, and I end the workflow on one branch of the parallel actions, so that the workflow ends when some action is completed on that branch, whether or not the actions on the other branch, (such as a pause), have completed, is the workflow engine smart enough to end that pending action, or will it put the workflow engine into some kind of endless lock in the background by keeping the action pending in the timer service forever? For example of what I mean, see the attached images of my workflow, and workflow history, where I tested this. The workflow works the way I want it to, I am just concerned about creating timer service or workflow service issues.
Solved! Go to Solution.
Can I ask why you have designed your workflow in such a way? is there a reason why the pause and email notification have been separated? Without testing that I would assume that the pause and email will complete before the flexi task is responded to and then after the task is responded to the workflow will terminate.
It really depends on how long it takes. It depends on how long it takes the approvers to approve their tasks. There may be an occasion when an approver is out of the office. So they may not get to it for a few days. A good example of this is a holiday or a vacation. What is the reason for the Pause? Is there any reason you couldn't send the email out before the Flexi-task and not do the Parallel Action at all?
The request is for a workflow on a calendar, which will notify the assignee of the event when it is scheduled, and create a task for him to create presentation documents for the meeting. They want reminders to go out at different non-standard intervals, ie. for one type of event at 30 days prior to the event start date, and 14 days prior to the event start date, for other types of events, only 14 days prior to the event start date. Since you can only create cyclical, recurring reminders with the built in task reminders, and no additional tasks will trigger on the flexi-task until it is completed, I figured the parallel actions option would be the best way to manage the requirement. And adding the end workflow action, after the flexi-task completes, will prevent the reminders from going out if the task has already been completed.
Why not create a site workflow for the some of the reminders? You can also create logic to determine the amount of days and use (if else) and send a notification accordingly in a list workflow.