Re: How do I force a filter to only happen after save? i.e. phase 3 ....
I tried the Temp table that ARSmarts mentioned and was not able to get it to fire on Delete. When it sent the command using Application-Delete-Entry $SCHEMA$ $1$ it did not trigger the filter action that ran on Delete. I am on ARS 7.5 patch 6 so I hope it isn't a bug but am going to run some more tests to make sure I didn't configure something wrong. Kelly - this is a good idea and I am currently researching. It looks like you can enter in the mapping using a form called Define Command and Command Parameters. I need to register my app (since it is custom) using the CAI Application Registry but in theory this might work. Am I missing something? Thanks, Sean From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: Thursday, December 22, 2011 11:17 AM To: arslist@ARSLIST.ORG Subject: Re: How do I force a filter to only happen after save? i.e. phase 3 ** It sounds like this (and ARSmarts') answer is essentially creating your own CAI:Events system. Rather than adding another form and workflow to be maintained, could you just use then event engine already there? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Babineau, Robert Sent: Monday, December 19, 2011 12:21 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: FW: How do I force a filter to only happen after save? i.e. phase 3 ** So, not knowing all the workflow in your process, I can't recommend anything to change to make it work with phase 1 and phase 2 processing, so I'll answer your question directly. There is no filter phase override to make them run in phase 3 (only phase 1). However, the following actions do occur in phase 3: Notify, Run Process, and DSO. The run process includes external and internal run process directives. We had a similar issue with phase processing that was addressed with a temp form and 2 filters. Here is what we did: 1) Create a temp form (called whatever) and create 1 filter that runs on Submit that does a Run Process action of Application-Delete-Entry $SCHEMA$ $1$ (remember you may need to put the $SHEMA$ keyword in quotations if your form name has spaces in it). 2) Create a 2nd filter on the temp form that runs on Delete which does a push to the form you need processing on phase 3 to occur. So, if you follow the flow, you get: 1) Push from Form A to Form B and Temp for (i.e. 2 push actions). 2) All workflow for phase 2 runs on form B. 3) Phase 3 processing kicks off (i.e. the run process) and deletes the entry on the Temp Form which triggers the update to Form B (simulating a Phase 3 update). Now, you'll also need to remember that because you are doing 2 pushes to Form B (one from Form A and one from the Temp Form), you need to disable any workflow processing from the 1st push (i.e. form A). This is accomplished by pushing a special keyword or possibly a status value to form B in the 1st push that triggers a Goto action on Form B to jump to 1001 (i.e. jump over all workflow execution). That way you don't get workflow firing twice on one update. One other thing to note is that because the 2nd push is executed from a delete action, you don't get any feedback (i.e. messages) published back to the end user (if you have any). You can get around this by creating an After Modify/After Submit active link that possibly reads the result message from Form B. You'd have to store the message on Form B somewhere in a field. Hope this is the kind of answers you were looking for. Robert Babineau, P.Eng. Bell Aliant robert.babin...@bellaliant.camailto:robert.babin...@bellaliant.ca From: Garrison, Sean (Norcross) [mailto:sean.garri...@fiserv.com] Sent: December 16, 2011 3:14 PM 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
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
CAI:Events is an ITSM form. We don't currently have ITSM and Sean said it was a custom CRM application they've created. However, if you do have ITSM and this form on your system, I'm sure you could easily incorporate this feature into that form (if it doesn't already exist OOTB). Robert Babineau, P.Eng. Bell Aliant robert.babin...@bellaliant.ca From: Logan, Kelly [mailto:kelly.lo...@proquest.com] Sent: December 22, 2011 12:17 PM Subject: Re: How do I force a filter to only happen after save? i.e. phase 3 ** It sounds like this (and ARSmarts') answer is essentially creating your own CAI:Events system. Rather than adding another form and workflow to be maintained, could you just use then event engine already there? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Babineau, Robert Sent: Monday, December 19, 2011 12:21 PM To: arslist@ARSLIST.ORG Subject: FW: How do I force a filter to only happen after save? i.e. phase 3 ** So, not knowing all the workflow in your process, I can't recommend anything to change to make it work with phase 1 and phase 2 processing, so I'll answer your question directly. There is no filter phase override to make them run in phase 3 (only phase 1). However, the following actions do occur in phase 3: Notify, Run Process, and DSO. The run process includes external and internal run process directives. We had a similar issue with phase processing that was addressed with a temp form and 2 filters. Here is what we did: 1) Create a temp form (called whatever) and create 1 filter that runs on Submit that does a Run Process action of Application-Delete-Entry $SCHEMA$ $1$ (remember you may need to put the $SHEMA$ keyword in quotations if your form name has spaces in it). 2) Create a 2nd filter on the temp form that runs on Delete which does a push to the form you need processing on phase 3 to occur. So, if you follow the flow, you get: 1) Push from Form A to Form B and Temp for (i.e. 2 push actions). 2) All workflow for phase 2 runs on form B. 3) Phase 3 processing kicks off (i.e. the run process) and deletes the entry on the Temp Form which triggers the update to Form B (simulating a Phase 3 update). Now, you'll also need to remember that because you are doing 2 pushes to Form B (one from Form A and one from the Temp Form), you need to disable any workflow processing from the 1st push (i.e. form A). This is accomplished by pushing a special keyword or possibly a status value to form B in the 1st push that triggers a Goto action on Form B to jump to 1001 (i.e. jump over all workflow execution). That way you don't get workflow firing twice on one update. One other thing to note is that because the 2nd push is executed from a delete action, you don't get any feedback (i.e. messages) published back to the end user (if you have any). You can get around this by creating an After Modify/After Submit active link that possibly reads the result message from Form B. You'd have to store the message on Form B somewhere in a field. Hope this is the kind of answers you were looking for. Robert Babineau, P.Eng. Bell Aliant robert.babin...@bellaliant.camailto:robert.babin...@bellaliant.ca From: Garrison, Sean (Norcross) [mailto:sean.garri...@fiserv.com] Sent: December 16, 2011 3:14 PM 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
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
It sounds like this (and ARSmarts') answer is essentially creating your own CAI:Events system. Rather than adding another form and workflow to be maintained, could you just use then event engine already there? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Babineau, Robert Sent: Monday, December 19, 2011 12:21 PM To: arslist@ARSLIST.ORG Subject: FW: How do I force a filter to only happen after save? i.e. phase 3 ** So, not knowing all the workflow in your process, I can't recommend anything to change to make it work with phase 1 and phase 2 processing, so I'll answer your question directly. There is no filter phase override to make them run in phase 3 (only phase 1). However, the following actions do occur in phase 3: Notify, Run Process, and DSO. The run process includes external and internal run process directives. We had a similar issue with phase processing that was addressed with a temp form and 2 filters. Here is what we did: 1) Create a temp form (called whatever) and create 1 filter that runs on Submit that does a Run Process action of Application-Delete-Entry $SCHEMA$ $1$ (remember you may need to put the $SHEMA$ keyword in quotations if your form name has spaces in it). 2) Create a 2nd filter on the temp form that runs on Delete which does a push to the form you need processing on phase 3 to occur. So, if you follow the flow, you get: 1) Push from Form A to Form B and Temp for (i.e. 2 push actions). 2) All workflow for phase 2 runs on form B. 3) Phase 3 processing kicks off (i.e. the run process) and deletes the entry on the Temp Form which triggers the update to Form B (simulating a Phase 3 update). Now, you'll also need to remember that because you are doing 2 pushes to Form B (one from Form A and one from the Temp Form), you need to disable any workflow processing from the 1st push (i.e. form A). This is accomplished by pushing a special keyword or possibly a status value to form B in the 1st push that triggers a Goto action on Form B to jump to 1001 (i.e. jump over all workflow execution). That way you don't get workflow firing twice on one update. One other thing to note is that because the 2nd push is executed from a delete action, you don't get any feedback (i.e. messages) published back to the end user (if you have any). You can get around this by creating an After Modify/After Submit active link that possibly reads the result message from Form B. You'd have to store the message on Form B somewhere in a field. Hope this is the kind of answers you were looking for. Robert Babineau, P.Eng. Bell Aliant robert.babin...@bellaliant.camailto:robert.babin...@bellaliant.ca From: Garrison, Sean (Norcross) [mailto:sean.garri...@fiserv.com] Sent: December 16, 2011 3:14 PM 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
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
This is a really good idea and I believe it will work. I'm going to try it out and let you know if it worked. Thanks for your submission. Sean From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Babineau, Robert Sent: Monday, December 19, 2011 12:21 PM To: arslist@ARSLIST.ORG Subject: FW: How do I force a filter to only happen after save? i.e. phase 3 ** So, not knowing all the workflow in your process, I can't recommend anything to change to make it work with phase 1 and phase 2 processing, so I'll answer your question directly. There is no filter phase override to make them run in phase 3 (only phase 1). However, the following actions do occur in phase 3: Notify, Run Process, and DSO. The run process includes external and internal run process directives. We had a similar issue with phase processing that was addressed with a temp form and 2 filters. Here is what we did: 1) Create a temp form (called whatever) and create 1 filter that runs on Submit that does a Run Process action of Application-Delete-Entry $SCHEMA$ $1$ (remember you may need to put the $SHEMA$ keyword in quotations if your form name has spaces in it). 2) Create a 2nd filter on the temp form that runs on Delete which does a push to the form you need processing on phase 3 to occur. So, if you follow the flow, you get: 1) Push from Form A to Form B and Temp for (i.e. 2 push actions). 2) All workflow for phase 2 runs on form B. 3) Phase 3 processing kicks off (i.e. the run process) and deletes the entry on the Temp Form which triggers the update to Form B (simulating a Phase 3 update). Now, you'll also need to remember that because you are doing 2 pushes to Form B (one from Form A and one from the Temp Form), you need to disable any workflow processing from the 1st push (i.e. form A). This is accomplished by pushing a special keyword or possibly a status value to form B in the 1st push that triggers a Goto action on Form B to jump to 1001 (i.e. jump over all workflow execution). That way you don't get workflow firing twice on one update. One other thing to note is that because the 2nd push is executed from a delete action, you don't get any feedback (i.e. messages) published back to the end user (if you have any). You can get around this by creating an After Modify/After Submit active link that possibly reads the result message from Form B. You'd have to store the message on Form B somewhere in a field. Hope this is the kind of answers you were looking for. Robert Babineau, P.Eng. Bell Aliant robert.babin...@bellaliant.camailto:robert.babin...@bellaliant.ca From: Garrison, Sean (Norcross) [mailto:sean.garri...@fiserv.com] Sent: December 16, 2011 3:14 PM 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.comhttp://www.wwrug.com ARSlist: Where the Answers Are_ _attend WWRUG12 www.wwrug.comhttp://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
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
Hi Sean To avoid the filter jump the phases, the correct syntaxis for the filter is `! no ~! Regards. J. Emilio Vargas From: Garrison, Sean (Norcross) [mailto:sean.garri...@fiserv.com] Sent: December 16, 2011 3:14 PM 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.comhttp://www.wwrug.com ARSlist: Where the Answers Are_ _attend WWRUG12 www.wwrug.comhttp://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
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
Hello Sean, Here is the trick to force a filter to run in phase 3. - On the form on which you want to run the filter, add a display-only field, that will be the trigger indicating it is a phase 3. - Create a dummy form, that will contain temporary values, among which the request ID of the record you want filters to exec in phase 3 - Create a filter link to your first form: this filter makes 2 things: - a push to the dummy form with your entry-id - a Run Process Application-Query-Delete-Entry where you delete the entry you have just created - Create a second filter, attached to the dummy form, that executes on DELETE, and that makes a push to your first form, pushing a value to the display-only form. - Create filters attached to the first form, where the Run if contains 'TR.Display-Only Field' != $NULL$, that you want to run in phase 3. Existing filters should be added a AND TR.Display-Only Field' = $NULL$ in their Run If. In fact the trick here is that filters running a process are executed in phase 3. So the Application-Query-Delete-Entry is executed in phase 3, then it restarts the whole processing in your dummy form, which in turns restarts the processing in your first form. Best regards, The ARSmarts Support Team ARSmarts winner of the Best New Product award at WWRUG11 www.ARSmarts.com On 16 Dec 2011, at 22:51, Garrison, Sean (Norcross) wrote: ** Thanks Chris, My workaround is close to that – add a table field to the “People” form and loop through each record. This will send the “TR” values instead of the “DB” values like I am seeing. Since I am 99% of the way there with what I have I am trying to avoid the rewrite I’m going to try a few more things to see if it resolves my issue. Thanks, Sean From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Danaceau, Chris (CONTR) Sent: Friday, December 16, 2011 3:54 PM To: arslist@ARSLIST.ORG Subject: Re: How do I force a filter to only happen after save? i.e. phase 3 ** 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:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 2:14 PM To: arslist@ARSLIST.ORG 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_ _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
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
I faced with a similar issue couple of years ago when I need to work on a child parent updating each other. I ended up using a perl script. The perl script just sends a flag to the form B(Client in you scenario) from form A (People) using the the arsperl api call. I invoked this perl script with a runprocess on a filter on form A. RunProcess is phase 3. The perl script was not very complicated, it was just a few lines and just pushes only one value to form B using an arsperl api call. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
Use “PUSh Fields”, “Direct SQL” to ignite filter. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of patchsk Sent: Saturday, December 17, 2011 11:18 AM To: arslist@ARSLIST.ORG Subject: Re: How do I force a filter to only happen after save? i.e. phase 3 ** I faced with a similar issue couple of years ago when I need to work on a child parent updating each other. I ended up using a perl script. The perl script just sends a flag to the form B(Client in you scenario) from form A (People) using the the arsperl api call. I invoked this perl script with a runprocess on a filter on form A. RunProcess is phase 3. The perl script was not very complicated, it was just a few lines and just pushes only one value to form B using an arsperl api call. _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ The information in this email may contain confidential material and it is intended solely for the addresses. Access to this email by anyone else is unauthorized. If you are not the intended recipient, please delete the email and destroy any copies of it, any disclosure, copying, distribution is prohibited and may be considered unlawful. Contents of this email and any attachments may be altered, Statement and opinions expressed in this email are those of the sender, and do not necessarily reflect those of Saudi Telecommunications Company (STC). ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
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:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 1:14 PM To: arslist@ARSLIST.ORG 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.comhttp://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
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:arslist@ARSLIST.ORG] On Behalf Of Tommy Morris Sent: Friday, December 16, 2011 2:35 PM To: arslist@ARSLIST.ORG 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:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 1:14 PM To: arslist@ARSLIST.ORG 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.comhttp://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
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:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 1:58 PM To: arslist@ARSLIST.ORG 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:arslist@ARSLIST.ORG]mailto:[mailto:arslist@ARSLIST.ORG] On Behalf Of Tommy Morris Sent: Friday, December 16, 2011 2:35 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG 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:arslist@ARSLIST.ORG]mailto:[mailto:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 1:14 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG 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.comhttp://www.wwrug.com ARSlist: Where the Answers Are_ _attend WWRUG12 www.wwrug.comhttp://www.wwrug.com ARSlist: Where the Answers Are_ _attend WWRUG12 www.wwrug.comhttp://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
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
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:arslist@ARSLIST.ORG] On Behalf Of Tommy Morris Sent: Friday, December 16, 2011 12:12 PM To: arslist@ARSLIST.ORG 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:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 1:58 PM To: arslist@ARSLIST.ORG 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:arslist@ARSLIST.ORG] On Behalf Of Tommy Morris Sent: Friday, December 16, 2011 2:35 PM To: arslist@ARSLIST.ORG 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:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 1:14 PM To: arslist@ARSLIST.ORG 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
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
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:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 2:14 PM To: arslist@ARSLIST.ORG 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_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
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) chris.danac...@hq.doe.gov 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: arslist@ARSLIST.ORG] *On Behalf Of *Garrison, Sean (Norcross) *Sent:* Friday, December 16, 2011 2:14 PM *To:* arslist@ARSLIST.ORG *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 bgoralc...@gmail.com ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: How do I force a filter to only happen after save? i.e. phase 3 ....
Thanks Chris, My workaround is close to that - add a table field to the People form and loop through each record. This will send the TR values instead of the DB values like I am seeing. Since I am 99% of the way there with what I have I am trying to avoid the rewrite I'm going to try a few more things to see if it resolves my issue. Thanks, Sean From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Danaceau, Chris (CONTR) Sent: Friday, December 16, 2011 3:54 PM To: arslist@ARSLIST.ORG Subject: Re: How do I force a filter to only happen after save? i.e. phase 3 ** 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:arslist@ARSLIST.ORG] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, December 16, 2011 2:14 PM To: arslist@ARSLIST.ORG 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_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
