$1$ is the same as $Request ID$ if a form when created, has not have had the database name altered. In case of AP:Alternate, I think this has been altered to Entry ID.. Check the database name..
That being said, its safer to use $1$ in your workflow as irrespective to whatever changes are made to the database name of that field, it will always work.. Joe From: Larry Barnes Sent: Thursday, December 08, 2011 3:10 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Re: Application-Query-Delete-Entry ** First, let me thank you for all the input. I struggled with the Application-Delete-Entry $SCHEMA$ $Request ID$, because the "AP:Alternate" form doesn't have a field called "Request ID". Upon further digging, from the clues you gave, I used the following to get the results I was looking for. Run If Qualification: ('Status' > "Current") AND ('End Date' < ($DATE$ - (86400 * 180))) Run Process: Application-Delete-Entry "$SCHEMA$" $1$ I had to put the $SCHEMA$ inside of quotes and the $1$ field represents the Alternate ID field in the form; found this hiding on the second tab. Thanks again, Larry B. -------------------------------------------------------------------------------- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jason Miller Sent: Thursday, December 08, 2011 11:33 AM To: [email protected] Subject: Re: Application-Query-Delete-Entry ** I was thinking the same thing. On Thu, Dec 8, 2011 at 11:18 AM, LJ LongWing <[email protected]> wrote: Joe, I know this discussion comes up every once in awhile....but you and I seem to differ in our opinions of how it works. So...based on your statement below, having the escalation set a field, and having a filter fire on that field being set, then performing the delete will be 'faster' because of a 'fire and forget' type of mechanism? I would argue that an action of delete within the escalation, and a setfield causing a filter to fire that causes the delete are 'the same', in that the escalation thread does not 'go onto the next record' till after the filters on the current record are done...so, in essence, the performance of either action would be the same and the escalation thread would still be tied up for exactly the same amount of time regardless At least, that's my understanding :) -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe Martin D'Souza Sent: Thursday, December 08, 2011 11:33 AM To: [email protected] Subject: Re: Application-Query-Delete-Entry End Date as Linda pointed out should be a field on that form you are searching for, represented by 'End Date' in the qualification and not $End Date$.. That being said, LJ's suggestion is right.. The qualification should be in the Run If of the Escalation and the run process should be Application-Delete-Entry $SCHEMA$ $Request ID$ Having an Escalation with no Run If instructs it to be run over the entire data table. You do not want to do that in case you have like a million or more records in it.. It may probably hang the escalation thread waiting for it to complete.. Also a faster way to do it would be to 'mark that entry for deletion' using a tag on a field created for that. This would mean that the Escalation would do a single update to that table which is a faster operation that multiple deletes and be done with it.. Create a filter that runs if the $USER$ is AR_ESCALATOR and the flag for delete is set, to delete that entry. So on a fairly large set of data, although the deletes are still potentially happening triggered by that filter, the escalation thread has already finished processing the escalation and is ready to take on a new job.. Joe -----Original Message----- From: LJ LongWing Sent: Thursday, December 08, 2011 12:54 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Re: Application-Query-Delete-Entry Larry, Your approach is a bit ‘off’. An escalation performs a search that matches your qualification, and then performs your action on ALL records that match that qualification. So in this case, I would expect your run-if qualification to be ('Status' = "Past") and ($End Date$ < ($TIMESTAMP$ - (86400 * 180))) Or, whatever qual you want to identify your specific records, Then, from there, you will be modifying ‘that’ record…so you wouldn’t want to then perform an Application-Query-Delete-Entry, you could simply perform an Application-Delete-Entry $SCHEMA$ $Request ID$ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Larry Barnes Sent: Thursday, December 08, 2011 10:23 AM To: [email protected] Subject: Application-Query-Delete-Entry ** Hello Listers, I'm trying to learn how to delete records that are past and the End Date is more than 6 months prior to todays date. I built the escalation and when I run it nothing happens. Can someone point in the right directions with the Run Process syntax. I'm using SQL 2008 and Windows 2008. ITSM is 7.5 The form I'm deleting from is: AP:Alternate Run IF Qualification is: 'Status' = "Past" (also tried without setting a Run If Qualification) Run Process is: Application-Query-Delete-Entry "AP:Alternate" ('Status' = "Past") and ($End Date$ < ($TIMESTAMP$ - (86400 * 180))) I have also tried: Application-Query-Delete-Entry "AP:Alternate" ('Status' = "Past") and ($End Date$ < ($DATE$ - (86400 * 180))) Thanks in advance for your time, Larry B _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
