That's true. For 14 records that might not really be a biggie. I remember using a server side table field for a record count much greater than 14 (but not larger than a few hundreds) where it would take about 5 seconds for an operation to complete. That's about the time it took to load that table field. But when I used the other method it was quicker. Like you I was surprised too, considering that this alternate method would query the database as many times as the number of records. My expectation was the alternate method to be slower but I found otherwise.
I don't really recall what I was attempting to do but since then I've preferred to avoid using server side table fields. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 03, 2007 4:12 PM To: [email protected] Subject: Re: Automatically Creating Child Ticktes I'm not sure how it could be more efficient than a server side table field and seems to require much more work. Rather than determining the "next record" this method already determines this for you as you are just looping through the table. We're talking about looping through 14 records, so I don't get where the efficiency is going to come into play. In this method, you don't set any display only fields from the configuration form, no lookups, it's a call guide, hit the first record, create the child ticket, hit the next record, create child and exit at the end of the table. No setting of a counter, just submit and issue a call guide for a table loop. Maybe I'm missing something? Scott Original Message: ----------------- From: Joe D'Souza [EMAIL PROTECTED] Date: Wed, 3 Oct 2007 16:02:37 -0400 To: [email protected] Subject: Re: Automatically Creating Child Ticktes Scott, You could avoid using a table field as well as pushing data into the configuration form. You could do this by creating display only fields on the parent form to contain the information you want from the configuration form. Then when initiating the filter guide set a display only counter for the request id of the configuration form and set the initial value to 0 or 000000000000000. Start the filter guide by looking for a request id that is greater than this counter, which will get you the first record and process that record, and at the end of processing that record reset the counter with the request id of the configuration record. Check for the next configuration record.. continue this and exit when the counter is set to null when there is no matching request for a configuration record with a greater value of its request id.. This method however has a drawback if you have defined a sort order on the results list which will sort the records to any other fields other than the request id. If you for some reason need to change that default sort order than having a server side table field like you described would work better. I've used this method in the past and found it to be more efficient than having server side table field.. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 03, 2007 3:39 PM To: [email protected] Subject: Re: Automatically Creating Child Ticktes Jaimie, I think all of the responses has gotten you to where you want to go. The only thing that I would add is this: Add a table field to the Parent ticket form that references the "configuration" form for the 14 child tickets. I would then run a filter guide over this table on submit of the Parent Ticket. By doing it this way I do not have to push any data from the Parent Ticket to the Configuration Form and finally to the form where the child tickets are stored. All of the data that is required to create the child tickets resides directly on the Parent Ticket (through the use of the table field). This also meets Joe's requirement that if a Parent Ticket is generated through the API the child tickets are still created. This may have been what Joe and others had in mind, but I did not see anywhere the specifically mentioning the use of a server side table loop so I thought I would offer it up. Scott Parrish IT Prophets, LLC (770) 653-5203 http://www.itprophets.com Original Message: ----------------- From: Joe D'Souza [EMAIL PROTECTED] Date: Wed, 3 Oct 2007 14:47:52 -0400 To: [email protected] Subject: Re: Automatically Creating Child Ticktes 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.... No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.14.0/1046 - Release Date: 10/3/2007 10:08 AM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
