delay activity in event handling scope activity - windows workflow sharepoint -

I am trying to create a scenario:

• assigned a task to the user
• To get a task, the manager is created to reassign the user function (do not ask, they want it like this)
• An email The reminder is required to be sent to the task.

Therefore, I have to use EventHandlingScope for it Thought:

• I'm hearing for the work change on the main branch Eventhandieldcope activity,
• Listening to reassign the job change in the event-driven branch - and if the task of reassignment is activated, then assign the user again to assign the first task
• Use delay in another event driven branch activity and check periodically Make that User Defined Close to Rik and sending an e-mail reminder

So, I though Gtnahndscop would be good for this, except delay activity is largely problem.

If I put a delay activity in one of the event handlers branches it seems to fire once but not more. Whereas if I put an on-task change activity, then every time a job changes.

So, is this the expected behavior? Why not delay activity loop? How can I separate it? My idea is with the CAG, but it looks a bit more complex ...

UPDATE: The problem with the CAG is that till the delay is done, the whole thing is blocked, Even if the on-change event has been removed. It makes sense, but makes it a bit complicated to use.

Update 2: I have changed the text again to make it clear to the candidate

> Listen to activity .

Listen to activity 3 EventDriven Activity is given for the first time. Your "user is completed work" branch for the first time, the second "changed the user assigned the manager" branch and the third one delay activity Your Email

Listen to any branch in the activity can accomplish the activity and when listen, other activities will be canceled in the activity.

To ensure you It will require that the "User Complete" sequence sets some values, while the loop can be tested by that when the user completes a task, then the loop is released.

When the "User Function" Full "sh Apart from Aakha, no branch is responsible for fulfilling , listen to activity will bring back the workflow loop to listenActivity and all 3 including the DelayActivity The event will re-execute activities.

Note that this is something different from the EventHandlingScope approach because "Users will listen to the task" will be canceled and will be executed again, whereas this will not happen with the Event HandlingScope. IMO is a better system because it means that the user acting at the beginning of the ear at present is finally guaranteed to be unchanged (because if it is changed then the whole activity is dismissed and A new start)

Event handling: Why was it removed once in a spouse

The set which you effectively set up is an opportunity that is listening to two incidents is. One of your managers changed the appointment of the user, the other was a "timer removed incident".

Now, in the manner described in the document, it seems that some loop is included as if any of these activities are restarted, though it is not quite like it, it is actually the original Continues to listen for the incident and if any other incident is removed then the material will be replayed again.

In case of delay activity there is some internal "timer removed incident", which is being used to listen when timelines are set when delay is first recorded. So that the timer set fire to the proper time, then he hears for the incident. Once the "timer removed incident" is heard, after removing the scope returns, there is no resume of the initial code which is timeout setup Does anyone so Mr. coming from "Timer Fired event".