You might have to do this with an escalation instead of filter. Or an escalation that triggers filters.
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Tommy Morris Sent: Friday, December 16, 2011 12:12 PM To: [email protected] Subject: Re: How do I force a filter to only happen after save? i.e. phase 3 .... ** It actually causes the filter to skip phasing altogether. Filter is triggered, it fires until complete. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 1:58 PM To: [email protected] Subject: Re: How do I force a filter to only happen after save? i.e. phase 3 .... ** It is my understanding `! forces a phase 1 operation not a phase 3. Sean From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Tommy Morris Sent: Friday, December 16, 2011 2:35 PM To: [email protected] Subject: Re: How do I force a filter to only happen after save? i.e. phase 3 .... ** You need to change the ~! To `! in the filter name From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 1:14 PM To: [email protected] Subject: How do I force a filter to only happen after save? i.e. phase 3 .... ** I have a workaround for this but I don't really like it. But here is the problem I am trying to solve: We have a custom crm app that contains people and clients. I am trying to trigger an event for each client related to a person whenever a field is changed on the people record. I have set up a filter that does a push fields to a temp field on a join form to fire the workflow. Here is what is happening: 1. I change the person's last name. 2. Filter processing begins and filters fire. 3. Filter processing phase 2 begins. 4. I do a push fields to a join form to trigger the event. 5. Filter processing phase 3 begins. <Filter Level:0 Number Of Filters:50> Checking "CKFR:DM:People-on_Submit/Modify-990-PushContactChangesToPeople-Assn_Joi n~!" (990) --> Passed -- perform actions 0: Push Fields -> "CKFR:DM:People-Assn_Join" <deferred to phase 2> Even though I changed the name from "Smith" to "Jones" in my event I get "Smith" because the processing was done in phase 2. I am not pushing the "Last Name" field to the join form because it already has it (that's why I created the join in the first place). In addition because the "Jones" is in transaction it is not committed in the db yet. I have a workaround but for the sake of learning was wondering if anyone has run into this before and what I could do to resolve it. I have tried the following options: 1. Put a ~! At the end of the filter name. 2. Use "Application-Release-Pending" run process command before the action fires in the filter. 3. Use "Application-Set-Filter-Phasing "value" where value = "1". This didn't work either. 4. Use the "PERFORM-ACTION-APPLY" run process command Thanks, Sean _attend WWRUG12 www.wwrug.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"_ _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"
