I think your solution would be creating a configuration form where you store the configuration of these 14 tickets you are supposed to create. You have not yet been clear if the Summary and Description of these 14 tickets originates as static information that could be stored with this configuration, or whether it comes from the original parent ticket. Depending on where that comes from, you may or may not require to store that along with the CTI configuration of child tickets.
Your next step would be to have a filter create a unique GUID. Then create workflow that would run through this configuration, when you press your button to save. The best way to do this is using a filter guide. An active link guide/active links would work to do the above, but would fail if you try to create the parent ticket through an API or through a web service. Have your filter guide run through each record of the child ticket configuration and during each loop create a child ticket for each of the configuration records using the GUID that was created as a related key. Do not forget to index the GUID field both in the parent as well as the child record form (if the child record form is different from the parent).. If the child record form is the same as the parent, make sure that you mark the parent with a flag that distinguishes it as a parent. Before triggering the filter guide to run through the child record configuration form, check for this flag, failing which you might end up with an infinite loop. I think that should pretty much work for you.. Cheers Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 03, 2007 2: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 at www.arslist.org ARSlist:"Where the Answers Are"
