Article ID: 885031
Article Last Modified on 6/2/2006
APPLIES TO
- Microsoft CRM 1.2
SYMPTOMS
Microsoft® Business Solutions CRM 1.2 Workflow Manager will not allow a new WAITstatement condition to be added to an Activity Task that is contained in a nested IF/THEN/ELSE statement.
CAUSE
This can occur for workflow rules that are created for all entities, as the problem exists in the WAITstatement conditions that are needed in an IF/THEN/ELSE statement.
To reproduce this issue, create a workflow rule and setup the following structure. When attempting to add the WAIT condition statement for Activity2, Activity2 will not appear in the list.
After a Contact is created, if the e-mail address is not empty, create an Activity Task, and then wait for that task to be completed. Once the task is completed, create another Activity Task, and then wait for that task to be completed. You will be unable to setup a WAIT condition statement for the second task. The following is the rule that the proceeding steps will create:
When the Contact is created:
if
Contact.emailaddress1 not null
then
Task: Activity1
wait
Task: Activity1 is completed
end wait
Task: Activity2
wait
<<add conditions here>>
end wait
end if
EXPECTED RESULT: Task: Activity1 and Task: Activity2 should, but do not, appear in the list for the second WAIT conditionstatement when creating the workflow rule.
RESOLUTION
Microsoft CRM has a fix for this problem that is part of a cumulative update. The cumulative update information is described in the following Microsoft Knowledge Base article:
904435 Update Rollup 2 is available for Microsoft CRM 1.2
Keywords: kbmbsemail kbmbsworkflow kbmbsmigrate kbprb kbqfe kbhotfixserver KB885031
