000035198 - RSA Archer changed Data Driven Events firing unexpectedly on record edit without user changes to the record

Document created by RSA Customer Support Employee on Feb 19, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035198
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
RSA Version/Condition: 5.5.x, 6.0.x, 6.1.x, 6.2.x
IssueThe "Changed" data driven event is unexpectedly evaluating to true when editing records, even though users haven't changed anything in the field.
ResolutionThe Archer documentation provides two example scenarios for the "Changed" data driven event operator where both scenarios depend on users changing a value in the field.

What it does not clarify is that the "Changed" data driven events can trigger immediately upon record edit, even though the user has not changed anything in the field.

Examples of where this can happen include scenarios where the system is forced to remove the previously saved value from the field and selecting either nothing, or an alternative value. This results in a "Changed" data driven event rule to evaluate to True immediately when the record is edited by any user.

Specific examples:

  1. Auto restrict groups option enabled on the field where a user is not a member of the group that was saved into the field previously.
  2. User accounts have been deleted that were saved into the field previously.
The functionality of the "Changed" operator will be better clarified in the Archer Help in a later release.