Sweety, When you perform an action on a single record, filters act on that record. They can cause set/push, that affects other records, and those records will have their own filters.
Escalations perform a query, and then take actions on any record that matches the query, potentially causing filters that fire on that record to fire. does that make sense? On Mon, Jun 2, 2014 at 1:07 PM, Sweety <sweetykhann...@gmail.com> wrote: > Hi List, > > I was reading the BMC wiki and found something weird in filters and > escalations. Wiki says filters act on current requests and escalations act > on all matching requests. I can modify requests through filters which are > not currently accessed by user. Filters acts on current requests - This > statement is not making any sense to me. Filters can also act on all > matching requests in Run If condition. > > Escalations act on all matching requests - Make sense. All workflows act > on all matching requests even filters and active links. Why there is a need > to mention it. > > Can anybody explain me what BMC is trying to say here? > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
