RE: Filter Phasing and EscalationsLyle, There is an easy way to check this out. Have a sample escalation logged and you can see if the ations are run in phases or in sequense. I'd think that they run in sequence just because of the nature of escalation - there is only one set of actions, one escalation runs at a time. Personally, I use the "touching" aproach described earlier in this tread and I consider it best practise.
Regards, Nicky Madjarov phone: 973-202-4278 Find out how to bust your AR System performance @ http://www.SpeedUpARS.com ----- Original Message ----- From: Guillaume Rheault Newsgroups: public.remedy.arsystem.general To: [email protected] Sent: Wednesday, May 06, 2009 4:09 PM Subject: Re: Filter Phasing and Escalations ** It could be a "documentation bug" -Guillaume -----Original Message----- From: Action Request System discussion list(ARSList) on behalf of Lyle Taylor Sent: Wed 05/06/09 3:57 PM To: [email protected] Subject: Re: Filter Phasing and Escalations That's interesting - their documentation specifically states that it can be used in escalations as well. Thanks for the info! Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rosana Aira Sent: Wednesday, May 06, 2009 1:17 PM To: [email protected] Subject: Re: Filter Phasing and Escalations ** Hi, I found this KB in the knowledge base of BMC support site. It is KB KM-000000025929 and it reads: "Question How is Application-Release-Pending implemented and used in workflow? Answer Application-Release-Pending does have an effect but it is very specific. It releases only pending Push Fields actions on ARSetEntry (Modify) and makes those available to subsequent filters. The Push Fields action needs to be in a filter set to run out of phase (ending in `!) and the Application-Release-Pending needs to also be in a filter that runs out of phase. Filter processing on FormA Filter1`! - push action to FormB Filter2`! - Application-Release-Pending Filter3`! - set fields reading same record from FormB (pushed data is available here) Filter4 - set fields reading same record from FormB (pushed data is available here) If Filter2`! is disabled, then Filter3 and Filter4 no longer have access to the pushed data, but queries the record before the push occurs. " HTH Regards. Rosana On Wed, May 6, 2009 at 2:06 PM, Lyle Taylor <[email protected]<mailto:[email protected]>> wrote: Right, and that takes me back to my question: will that naming convention have the same effect on the actions in an escalation like it does for a filter? Thanks, Lyle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Grooms, Frederick W Sent: Wednesday, May 06, 2009 7:59 AM To: [email protected]<mailto:[email protected]> Subject: Re: Filter Phasing and Escalations I have used it and it seems to work. The trick is since it is a Run Process action (Phase 3) you put it in its own filter with a naming convention of `! to force the action to run in Phase 1 Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Guillaume Rheault Sent: Wednesday, May 06, 2009 7:30 AM To: [email protected]<mailto:[email protected]> Subject: Re: Filter Phasing and Escalations Hi Lyle, FYI - I've yet to see the Run Process Application-Release-Pending work. Even with 7.5, it seems not to work....it has not worked for me in the past or now, the way I was expecting it to work.... -Guillaume -----Original Message----- From: Action Request System discussion list(ARSList) on behalf of Lyle Taylor Sent: Tue 05/05/09 7:59 PM To: [email protected]<mailto:[email protected]> Subject: Re: Filter Phasing and Escalations Hi Dave, Thanks for replying, but I'm afraid I don't understand where you're trying to take me here. I understand what the various workflow is and where it executes. The problem is that not all actions happen as they are encountered in the workflow due to phasing. This can occasionally cause problems, because something that you may have expected to happen sooner in the workflow processing may not have yet been completed, because it happens in another phase or has been placed later on the queue. This appears to be happening here. Most of the time, things work as expected - however, I've seen it where not all of the processing from step two of my escalation has occurred before step three gets executed, I _think_ due to filter phasing and how the queues for the various filters on the two forms get managed. Basically, the documentation makes it sound like filter phasing applies to escalations as well as filters. If that's the case, then I just need to know whether the `! naming convention also applies. If so, then I think the approach I'm taking will work, namely: 1) Tag all new records 2) Run Process: Application-Release-Pending 3) Process all tagged records 4) Run Process: Application-Release-Pending 5) Tag any remaining records as "No Configuration Matched" Thanks, Lyle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Shellman, David Sent: Monday, May 04, 2009 8:45 PM To: [email protected]<mailto:[email protected]> Subject: Re: Filter Phasing and Escalations Lyle, Filters are actions that occur on the server. They function basically the same if a record is changed by a person, an API call, or an escalation. This includes phase 1, 2 and 3 actions. You can check by turning on filter logging on the server. ------Original Message------ From: Lyle Taylor To: Arslist ReplyTo: Arslist Subject: Re: Filter Phasing and Escalations Sent: May 4, 2009 9:57 PM Let me clarify a bit. The documentation states that you can add the Run Process action Application-Release-Pending between each of the actions to get what I'm looking for and mentions that it can be used in escalations. However, since it normally runs in phase 3, you have to use the special filter naming convention to override filter phasing for it to be applied properly between the push fields actions. I guess my question boils down to this: do filter phases apply in escalations, and if they do, can you add `! to the escalation name to override phasing just like you do with filters? Thanks, Lyle -----Original Message----- From: Lyle Taylor Sent: Monday, May 04, 2009 4:05 PM To: '[email protected]<mailto:[email protected]>' Subject: Filter Phasing and Escalations Hi All, Can anyone tell me if filter phasing applies to escalations? I have a three-step process involving two forms, and I need to guarantee that certain actions happen in a specific order. I'm also trying to process records in batches, so I have an escalation that does something like this: 1. Set the status of all records in Form A to "Process" 2. Set the field "Process Now" in Form B 3. Set the status of all records in Form A whose status is still "Process" to "No Configuration Matched" Basically, Form A contains records to be processed, and new records can be added to it at any time. Form B contains configurations that map back to zero or more records in Form A. At intervals, I set the status of all new records in Form A to Process. Dave ------------------------- [email protected]<mailto:[email protected]> (Wireless) _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> Platinum Sponsor:[email protected]<mailto:sponsor%[email protected]> ARSlist: "Where the Answers Are" NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> Platinum Sponsor:[email protected]<mailto:sponsor%[email protected]> ARSlist: "Where the Answers Are" -- 1) Colabore con la eliminación de los correos en cadena, y la incorporación no deseada a diversas bases de datos. Envíe los correos para UD. mismo, como destinatario y con copia oculta (CCO) a los demás .Borre (Supr) todos los remitentes anteriores. 2) Antes de imprimir este correo, pensá en el medio ambiente Saludos, Rosana _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
