The problem with TR.Value is that if the name hasn't been changed then it
will be null.  If you just use Value it will use the value if it has been
changed or not.  Unless you want to test that TR.Value is null as part of
your run if.  Also I don't think that you can use the TR.Value in anything
but the run if qualification.

Another option would be to use a table field that refreshed after all the
workflow was done and pull the information from that.

Personally, I would just use the '! and maybe a perform-release-pending
right after the push fields action.

HTH,

Brian Goralczyk

On Fri, Dec 16, 2011 at 1:53 PM, Danaceau, Chris (CONTR) <
[email protected]> wrote:

> **
>
> How about using the TR.Value which should capture the changed name?****
>
> ** **
>
> -- ****
>
> Chris Danaceau****
>
> 301-903-8741****
>
> Contractor to the Department Of Energy****
>
> ** **
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> [email protected]] *On Behalf Of *Garrison, Sean (Norcross)
>
> *Sent:* Friday, December 16, 2011 2: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_Join~!"
> (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"_
>



-- 
Brian Goralczyk
Phone 574-643-1144
Email [email protected]

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to