Managing Change Tasks

[simonbourne]

I have a Workflow that is used for the creation of Change Requests.  The Workflow automatically extracts information from the change form (Implementation Plan and Test Plan fiels) and creates 2 Change Tasks when the Change Request is submitted to Review Request.  That's easy.....job done.

However, there are instances when the Change Request is Rejected due to insufficient of incorrect information.  At this point, the State of the Change Request is reset to Draft.

No here's the challenge.  Just suppose the details of the Implementation Plan or Test Plan are then updated to address the issue that caused the Change Request to be Rejected.  and the change is then progressed to Review Request again.  According to the Workflow, new Change Tasks should be created and populated with the (updated) information from the Change Request.

When I try this, it all works fine but..... no new Change Tasks are created and the original Change Tasks are not updated.  They retain the original (now incorrect) details.

How do I make the Workflow update the existing Change Tasks, or create new Change Tasks?

[Kannan Nadar]

Hello Simon,

You can have a after update business rule to update the change tasks associated with the change whenever the test plan or implementation plan field value changes.

Thanks,

Kannan

[simonbourne]

That sounds like a good solution.   So I've created a Business Rule to execute AFTER the Implementation Plan changes.

But I'm unsure of how to format the script in the Advanced tab.   Is this correct?

[Michael Ritchie]

Simon, are the change tasks also moved back to the "draft" state?   You could accomplish this in the workflow via run script.   Might be better that way so you "compartmentalize" all the components into one place.   Where this breaks down is if these fields can be edited after the change approvals or through the lifecycle of the change which is where a business rule is the way to accomplish it.   Really up to you.

Now to address your question above with the business rule, business rules are essentially triggers as records are inserted, updated, and deleted.   They run on the record performing these actions.   So in your case the change_request record is being updated so the business rule needs to be set on that record instead and it will then update the child change_task records.   You currently have this set on the change_task which is not correct.

[simonbourne]

Yes, I've tried using a script contained within the CREATE TASK, but it's not pushing the value through to the Task after I update it.

Do I need to