Value from Change Request to Task
What is the easiest way to push a field value from a change request (using a change template) to a task (using a task template)? I would like the Notes field of all tasks to have the same text as the Notes field of the Change Request that created them. The documentation from the BMC Remedy IT Service Management 7.6.04: Administering - Part 2 course suggests that variable templates will do it, but I couldn't figure it out. KA343484 suggests workflow is needed. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: Value from Change Request to Task
We had a similar requirement. And the way we did was, find out the existing filters that push change request number(parent ID ) to the tasks and then add notes field also into that filter. On Thursday, July 5, 2012 11:49:10 AM UTC-7, Bob Lind wrote: > > What is the easiest way to push a field value from a change request (using > a change template) to a task (using a task template)? I would like the > Notes field of all tasks to have the same text as the Notes field of the > Change Request that created them. The documentation from the BMC Remedy IT > Service Management 7.6.04: Administering - Part 2 course suggests that > variable templates will do it, but I couldn't figure it out. KA343484 > suggests workflow is needed. > > ___ > > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: Value from Change Request to Task
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"
