We were seeing something similar. Basically before the upgrade setting a field with public/view permissions would allow it to be seen by any recipient. After the upgrade, this no longer worked and the data only showed in the email if the recipient had permissions to the field. We had to add an entry to the Centralized Configurations on the AR System Administration Console. It seems 9.1 tightens the security around the data allowed to show in an email.
Under Component Name : com.bmc.arsys.server.shared We added Setting Name: Ignore-Form-Permissions-For-Notification-Data Setting Value: T Hope that helps Thanks, Todd Arner From: ARSList [mailto:[email protected]] On Behalf Of Mike Galat Sent: Thursday, January 11, 2018 11:31 AM To: '[email protected]' Subject: 9.1.x Notify Action Delivery Mechanism Hi - We are currently working toward upgrading from AR System 8.1.02 to 9.1.03/(or 9.1.04). Currently our lab server is running 9.1.03. We are running into an issue with the Notify action in Filters. The Notify Delivery Mechanism allows a few values: 1: Alert 2: Email 3: User Profile Default 99: Cross-Reference For cross reference, you can then pass an integer value to define the delivery mechanism at runtime: 0: No delivery 1: Alert 2: Email 3: User Profile Default By running some filter logging we have narrowed down the types of delivery mechanisms that succeed/fail. It has been our experience with 9.1 that using: * User Profile Default (3) or Cross-Reference, with User Profile Default (99/dynamic 3) SUCCEEDS. * Email (2) or Cross-Reference, with Email (99/dynamic 2) works FAILS. What I mean by succeeds or fails is this: When it succeeds, the email goes out, and all variables in the subject and text get expanded. So suppose I send a notification for a ticket being opened User Profile Default, and the subject has $Ticket #$ has been opened at $Create Date/Time$ The email's subject will contain: "PT-123456 - has been opened at - 1/1/2018 09:04:36 AM" When it fails, the email goes out, and all variables in the subject and text DO NOT get expanded. So suppose I send the same notification for a ticket being opened, using Email delivery mechanism, and the subject has $Ticket #$ has been opened at $Create Date/Time$ The email's subject will contain: " - has been opened at - " Has anyone else experienced this behavior. If so, were you able to fix it, and how? Note: changing the notify mechanism is not an option, as we use email in many filters. All of this works just fine for us in Remedy 8.1.02 Thanks! Mike Galat ---------------------------------------------------------------------- The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be protected under state or federal law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please forward the communication to [email protected] immediately and destroy or delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
