More Processing Activities using Workflow and Queues

Posted on March 24th, 2010 Mitch Milam  Print 1 comment

In the previous article we discussed how to use workflow to move activities between queues.

We noticed and issue last week related to how the users were actually processing the activities that would result in the workflow failing.

It turns out the users were changing the value of the picklist we use to move activities between queues and also closing the activity as completed.  This caused the workflow to fire because of the change in the picklist but since the activity was already closed, the workflow failed because it tried to update a closed record.

To prevent this occurrence from happening, we need to insert a bit of code at the beginning of the workflow to check the activity status:

So when we start the workflow, we check the status of the activity ( a fax in this case ) and if it is either Completed or Canceled, then we stop the workflow with a status of Completed.

This will prevent the workflow from attempting to update a closed activity.

Dynamics CRM, Workflow

(1 votes, average: 4.00 out of 5)

 Loading ...

612 views