The problem with using an approach that pushes from Change to Task is that there are all kinds of forms in between. Instead I created a filter on Change Submit that will push the value to the tasks. This has the added benefit that the end user can pick a template with some default notes, edit those notes, save the change and the notes are then pushed to the underlying tasks. Here are the details:
The solution I came up with is: Filter Associated Forms: CHG:Infrastructure Change Execution Options: Submit Run If: 1=1 If Action: Push Fields Data Destination: Server Form Name: TMS:Task Qualification: $Infrastructure Change ID$ = 'RootRequestName' If No Requests Match: Take No Action If Any Requests Match: Modify All Matching Requests Field Mapping Notes $Detailed Description$ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
