8

Example: Lets say I have a workflow which send an email 2 days before warranty enddate. This workflow is triggered on the "Created" of a entity.

step 1: wait condition - process timeout < (warrantyendate - 2)
     after wait: send email.

So when the record is created, the workflow is started. But what happens when the user goes back and updates the warranty enddate.

Does the workflow check the updated warranty enddate or does it still use the enddate entered when it was triggered (i.e the initial on create value)?

Sabrish Ayyappan Balachander
  • 241
  • 1
  • 10
  • 3
    When you try to perform the scenario what result do you see? Won't just trying it give you your answer? – BenPatterson1 Aug 08 '12 at 17:48
  • @BenPatterson1 I was testing with a date time field and it ran into infinite loops (and crm enventually stoping the execution because of this), so I thought will seek some help. I have managed to get rid of that and found the answer. Thanks. – Sabrish Ayyappan Balachander Aug 08 '12 at 20:00

2 Answers2

8

My understanding is that the workflow uses the data in the system at the time of execution.

The important thing to take note here is that a workflow can be executed many times, at these times the data in the system can be different. Crm caches the state of the workflow, but not the data. Process Architecture for Microsoft Dynamics CRM 2011 describes this.

So, each time the process timeout condition is checked it will use the current value of warrantyEndDate. If the value is changed, next time the condition is checked the new value will be used.

In any case as @BenPatterson1 suggests, you are probably best just testing to be sure.

James Wood
  • 17,286
  • 4
  • 46
  • 89
4

After trying this myself, if the value of the field included in the condition changes, the workflow engine fires up from sleep(waiting) and checks the condition again.

If it meets the condition, then continues to the next step or will continue to wait.

Sabrish Ayyappan Balachander
  • 241
  • 1
  • 10