Change Task Affected Objects

[StanBalish]

Add affected objects to all change tasks for a change notice instead of just the initial or "default" change task.  Currently when a change task gets created via a change notice only this initial change task will have the affected objects list populated.  Any additional change tasks created in the work flow show none.  You can manually add them but this causes duplicates to be added to the change notices affected objects (this is addressed in another  product idea related to this topic).

[d_graham]

Stan,

Read your idea.  You want all change tasks on a change notice to automatically have the same affected data of the first (original) change task.

If a new change task is added to the change notice it should automatically have the affected data from the original task added to it.

If the original change tasks gets edited (affected data added or removed) all other existing change tasks should be automatically updated accordingly.

If the original change task gets delete the oldest existing change task becomes the new original.

If I understand you correctly it is very doable to automate all of this.

Can you confirm that I know I understand correctly?  I'll write come test code to do this.

David 

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.