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 From: Lyle Taylor Sent: Monday, May 04, 2009 4:05 PM To: '[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] (Wireless)
