Change Management: Smooth transition between CR and CN

[LawrenceS]

Currently the transition between a Change Request (CR) and Change Notice (CN) (created from a CR) is very awkward and NON-INTUITIVE.  The CR should register that the CN has been completed and finish that task automatically without the user having to go back and say yes I created the CN from the CR even though the system already knows that I did it!  I propose the CR task to create the CN be completed upon creation of the CN.  If this is too chalanging, make the page go automatically to the task page upon completion of the ECN when created from the ECR.  All the logic is already in the system, Change Management should be able to take advantage of it!

Current Steps:

1. Receive task to create CN from a CR
2. Go Create CN from CR and set up routing from within the CN
3. Come back and complete task that says yes I created the CN.  This is necessary to remove the task from the users My Task list on their PDMLink homepage.

Proposed Steps

1. Receive task to create CN from a CR
2. Go Create CN from CR and set up routing from within the CN

(Note that at this point PDMLink should recognize that you created the CN from the CR and automatically complete the Create CN task and ‘remove’ it from their My Tasks list.)

[STEVEG]

Couldn't agree more.

[JeffZemsky]

Today we already skip this step if a CN exists.  If desired you can add a Sync Robot today to look for the creation of a Related CN and as a result have it close out existing Task if the new CN is created.  Here is a quick example I created:

There is a new Sync Robot - Close Task on CN generation that listens for CN creation.  It tests to see if the CR then has a CN linked to it.  If so it fires the Close route which Terminates the Create New Change Notice Task.  I also added a link from the Create New Change Notice Task that terminates the Sync robot if the user happens to select Complete Task

Here is the robot code (I did this for 11.0 - the syntax for 10.2 and earlier is a little different as in 11.0 there are new flexible Change Associations)

Also with 10.2 M030 with the Native Task Templates one can add Attributes, Actions and Tables to Workflow Tasks from the PBO.  In this case one could add the Create actions from the CR to leverage the normal create process from within the Change Task process then the user could hit task complete.   Notice in the example below in the Workflow Activity the user can Edit the Change Request, create a new Change Notice, Subscribe, etc.  Also shown are some attribute groups from the Change Request, Attachments, Affected Objects and some related Changes tables.   Further - as I noted above an admin could add a sync robot to listen for the CN creation and close the task automagically.