This is one reason I created the idea: Improve the method of overriding Filter Phases https://communities.bmc.com/ideas/3639
Since you are creating everything for the email yourself there is one other method you can use. Do a push action to the AR System Email Messages form yourself Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mueller, Doug Sent: Wednesday, January 04, 2017 2:22 PM To: arslist@ARSLIST.ORG Subject: Re: Dialog panels and Notify action ** Thomas, THAT is the tradeoff. You get the current values when you override phasing. You cannot say, phase for this attribute to get the final value but not for that attribute. That is where you need to make the call about what your specific situation is and choose the right option. If you are modifying, then the requestID is available. If you are creating, then it is not until phase 3…. Doug From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Thomas Miskiewicz Sent: Tuesday, January 03, 2017 10:51 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: Dialog panels and Notify action ** Doug, is overriding Filter phasing in connnection with notifications a good idea? I mean when we do that we won't be able to send out the Request-ID in the notification. Thomas On 3 Jan 2017, at 19:03, Mueller, Doug <doug_muel...@bmc.com<mailto:doug_muel...@bmc.com>> wrote: ** Dustin, There are three options that I can think of for you to consider. 1) Don’t NULL the value – the notification runs in phase 3 and will pick up the FINAL value of the field not an intermediate one. This stores the value in the field. 2) Put the value in a display only field (as suggested) – This stores nothing to the DB, but the value in the display only field is available throughout the phases of the operation. 3) Override the filter phasing. End the name of your filter (yes, this is a naming convention rather than a filter option, and there is lots of history for why this is this way, but it is….) with `! (that is a BACKQUOTE followed by an exclamation point). This will override the phasing of the filter for this filter and cause the notification to be executed NOW not in phase 3. OK, honestly, it just takes a snapshot of all the values and saves then for the notification rather than actually sending the notification right now but the result is the same… This would use the CURRENT VALUE AT THAT TIME of the field not the value at the end of the transaction. This should work for your situation (a quick test would confirm it). For your situation, you may find that the third option is the simplest solution without needing extra work or handling. Doug Mueller From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Fawver, Dustin Sent: Tuesday, January 03, 2017 9:43 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: Dialog panels and Notify action ** Tim, That is a most excellent idea! I may have to change some things in that panel, depending on what management wants, so if that's the case I'll give that a try. Thanks again! --Dustin Fawver HelpDesk Technician East Tennessee State University (423) 439-4648 ________________________________ From: Action Request System discussion list(ARSList) <arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>> on behalf of Timothy Powell <timothy.pow...@pbs-consulting.com<mailto:timothy.pow...@pbs-consulting.com>> Sent: Tuesday, January 3, 2017 7:56 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: Dialog panels and Notify action ** Not knowing how the field value is getting set, I’m going to guess that it’s set/input by the tech at transaction time. That said, If you only need the contents of this field for the transaction/message (and the value is actually stored elsewhere), maybe you can just use a Display Only field. Tim From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Fawver, Dustin Sent: Monday, January 02, 2017 7:18 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: Dialog panels and Notify action ** Greetings, once again! I have figured this out, but I would still like some advice. What was causing my issue is that I was setting the field in question to $NULL$ after the Notify action within the filter. I even tried setting the field to $NULL$ in a different filter step with a later execution order. I suppose this is due to filter phases. (https://docs.bmc.com/docs/display/public/ars91/Filter+phases). Aside from emailing the contents of this field, the contents are also copied to one of two other fields, depending on the tech's choice, that are also saved to the database. Thus I don't need yet another copy of the field's contents. For those who may have encountered this before, should I create another active link that executes After Modify that sets the panel's fields to $NULL$ and then calls Commit Changes? Thanks again! --Dustin Fawver HelpDesk Technician East Tennessee State University (423) 439-4648 ________________________________ From: Fawver, Dustin Sent: Saturday, December 31, 2016 7:09 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Dialog panels and Notify action Greetings! I have created a dialog floating panel containing a character field of which I want to be able to email to the user. The recipient's email is constructed from another field on the form followed by the domain. While the user gets the email, the value of the specific field in question is not being put into the text of the notify action. No email templates are being used at this time. I checked the permissions thinking that they may be playing a part. The Public group has View permission on the form, the dialog panel and the character field. When that didn't help, I thought that maybe the workflow that hid the panel was causing the character field to be inaccessible, although the filter seemed to disagree with me. In the filter workflow that actually fires the Notify action, I placed a Message action immediately before the Notify action to show the value of the field. The prompt correctly displayed the value of the field, but it doesn't appear in the email message. The value of the field is plain text. I also tried placing the value of $Case ID+$ (the request ID) right before the character field name and it comes through just fine. I hope this makes sense. Since this is something that's new in 9.1 and not something that I was trained on, what is it that I'm overlooking? Thanks! --Dustin Fawver HelpDesk Technician East Tennessee State University (423) 439-4648 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
