Thanks for all of the responses on this. I decided to go with the idea of display-only fields in Task, and this seems to work for what my users need.
Thanks, Shane Buchholz Systems Analyst II - Remedy Information Services Operations Samaritan Health Services From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Sabyson Fernandes Sent: Wednesday, October 06, 2010 11:31 AM To: arslist@ARSLIST.ORG Subject: Re: Pushing Field data from Incident to Task ** Shane, What you are looking for is the set fields action that is triggered when the Relate Ad-hoc Task action is triggered via the Add task button. You will need to add to the list of fields in that set field, so when the user is creating the ad-hoc task this information is updated. Now, there is an issue if the fields that are copied across get updated on the incident you need to add additional workflow to push the updates to all the tasks that have this information. We have the relationship and you can view the parent incident/change, but I know techs do not want to open up the incident form, from the task as it involves extra clicks and they end up having many windows open in the background. To get around this update issue, I use display only fields on the task form and when the task is opened I pull the information back from the parent request (incident/change). Hope this is helpful. Regards, Saby --- On Tue, 10/5/10, Shane Buchholz <sha...@samhealth.org> wrote: From: Shane Buchholz <sha...@samhealth.org> Subject: Pushing Field data from Incident to Task To: arslist@ARSLIST.ORG Date: Tuesday, October 5, 2010, 5:40 PM ** I am hoping that someone may be able to help me in what is probably a simple process that I am overcomplicating. We have a need to add additional fields to both the Incident and Task forms in ITSM. What I am trying to work out is how to push values from the Incident into the Task when the Task is first created. Right now some basic data flows through (Requester Info, Location, etc.), but I have been unable to duplicate this. The process should work as follows: 1. Incident is created (HPD:Help Desk – Best Practice View) 2. User starts to create a Task (HPD:Help Desk Dialogs – Task View) 3. Request Type set to Ad Hoc and Relate button (z3Btn_AddTaskTG) clicked. 4. Task form (TMS:Task) is opened, and select data is preset in the Task. What I need to do is add functionality so that my fields populate from step 3 to step 4. I have a fairly good understanding of general workflow in ARS, but not a very good knowledge of the more advanced functions. Pulling logs of the workflow as it happens has not helped me to determine where the data push takes place. ARS 7.5 ITSM 7.6 SQL 2005 Windows 2008 (64-bit) Any help would be appreciated, and I apologize if this is a simple solution that I have just not discovered yet. Thanks, Shane Buchholz Systems Analyst II - Remedy Information Services Samaritan Health Services ________________________________ Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
