Okay, I would suggest the following: Create an intermediary form. On this form, you will have a 'Keyword' field.
Now, whenever your parent ticket is closed (being a store is decommissioned) you push an update to all matching requests to the intermediary form. You will need to push probably at the very least the parent ticket number. This might prove difficult, as the ticket number won't be generated yet, so you might need to use an active link running on after submit so you have access to the ticket number. I'm guessing that there are different store types, such as 1, 2, 3, etc. So, your intermediary forms could have an entry for each of the child tickets that need to be created based on site type. So, do your push fields on your parent ticket to the intermediary form where Site Type = Site Type, and modify all matching requests, push the record ID and any other info you need. Now, on each of those records, you will have a CTI setting, and whatever else you need. On Modify (using a filter, of course, because at this point on your intermediary form Active Links won't be firing) you will need one filter that will do a push fields where 0 = 1 to the child form and push the CTI and related info. This is a good dynamic way to do it so in the future if you determine you need another type of ticket created, you can easily add it without modifying workflow. Thanks, Gary Opela, Jr Sr. Remedy Developer Leader Communications, Inc. 405 736 3211 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 03, 2007 1:27 PM To: [email protected] Subject: Re: Automatically Creating Child Ticktes Each time they decommission they only use a specific set of CTI's. So every time they did a decommission on the specific ones would be used and they are only used in this scenerio. I'm with you on the macros, I'm not a big fan of them either... On Oct 3, 2:23 pm, Kaiser Norm E CIV USAF 96 CS/SCCE <[EMAIL PROTECTED]> wrote: > Well, if you ever worked with me, you know one of my mottos in Remedy > development is this: NO MACROS! > > How are the CTIs on the 14 child tickets supposed to be determined? Once > you decide that, I bet it can be automated and then you just push those > determined values using the PUSH FIELDS action. > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > > [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, October 03, 2007 1:18 PM > To: [EMAIL PROTECTED] > Subject: Re: Automatically Creating Child Ticktes > > How would I change the CTIs though on the child tickets? I was > wondering if I could create macros for the different types of tickets > they want, then have an AL that fires when they create the first > ticket and do the Run Macro action off the AL so it would > automatically create all 14. Or would that mess confuse Remedy? > > On Oct 3, 2:12 pm, Kaiser Norm E CIV USAF 96 CS/SCCE > <[EMAIL PROTECTED]> wrote: > > How about just using a PUSH FIELDS with CREATE A NEW REQUEST if no > > matching requests are found? Use a blank PUSH FIELD IF qualification > and > > Remedy will create a new record in the child form each time the AL is > > executed. You can create as many of these actions as you want (14). > > > Norm > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > > [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > > Sent: Wednesday, October 03, 2007 1:07 PM > > To: [EMAIL PROTECTED] > > Subject: Automatically Creating Child Ticktes > > > I was wondering if anyone knows of a way or has heard of a way to > > automatically create child tickets after clicking on the save button > > of the parent ticket. My company wants to create these child tickets > > automatically instead of having to manually input them. They are > > asking for 14 additional tickets to be created upon clicking on the > > save button and all will have different CTIs. I don't think there is > > a way to do this, but I figured I would post just the same. > > > They would also like all 14 tickets to auto save and give ticket > > numbers.... > > ________________________________________________________________________ > > _______ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where > > the Answers Are" > > ________________________________________________________________________ > ___-____ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where > the Answers Are"- Hide quoted text - > > > - Show quoted text - > > ________________________________________________________________________ > _______ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where > the Answers Are" > > ________________________________________________________________________ ___-____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where the Answers Are"- Hide quoted text - > > - Show quoted text - ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
