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
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
