000030289 - Notification does not go out from changed criteria RSA Archer

Document created by RSA Customer Support Employee on Jun 14, 2016•Last modified by RSA Customer Support on Jul 17, 2019
Version 5Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000030289
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
RSA Version/Condition: 5x,6x
IssueWe have two rules:
  1. Notify Submitter- New Assessment Ready (sends notification When a new record is created)
  2. Notify Submitter- Submitter Changed (sends a notification when the submitter is changed in target Application – Applications ). Both the rules linked to one action Notify Submitter- New Assessment Questionnaire Ready-new.

We are having an issue with 2.Notify Submitter- Submitter Changed. Submitter fields in questionnaire inherit username from Applications IT owner field. When we change the IT Owner in Applications, this Notify Submitter- Submitter Changed rule gets satisfied and sends an email to the users that are chosen. The following action happens when there is a change in IT owner.

User-added image
ResolutionCustomer wanted to trigger a notification from the changed. This worked in scenario #1 because it was on a new record create/save. In scenario #2, the change happened on the child side and was inherited by the parent. However, since no change was made on the parent (where the DDE Notification was), no parent save happened and the notification did not trigger.

In order for the Notification to go out, it needs to be created and trigger from the child application or have an edit/save action on the parent to trigger it from there.

Attachments

    Outcomes