- Create a form. - Store the 14 new CTIs on it. - Also put the parent CTI on it. - Put hidden fields on your main form. - When you click the button, first go lookup the matching 14 CTIs from the form and set the hidden fields. - Next, push fields to create records using the values in the hidden fields to create the child tickets. - Like Joe suggested, use GUID or a concatenation of $USER$ + $TIMESTAMP$ to create a unique key to link all the children to their parent.
Norm -----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"
