000031758 - Auto-restrict groups causes Update Content Node to not display non-existent groups for an administrator in RSA Archer

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on May 22, 2019
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000031758
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer UI
RSA Version/Condition: All

The Auto-Restrict Groups function of the user/groups and record permissions fields should only apply to content. However, if an administrator has this field option set and then attempt to configure an update content node to update this field, the configuration excludes any group for which the admin is not a member.

Steps to Reproduce

  1. Login to Archer as a system administrator that does not belong to any Groups.
  2. Navigate to Application Builder
  3. Add a user/groups field to any application
  4. In the field options, set the Field Population section to use All Groups and All Users. Select the Auto Restrict Groups check box (screenshot attached). Save changes
  5. Invoke the Lookup again. Note that as an administrator, you can still see all groups. This is correct.
  6. Create an Advanced Workflow in the app
  7. Add an Update Content node.
  8. Configure the update content node to update the user/groups field. Note in the configuration that you cannot see any group you do not belong to. This is incorrect.

Expected Result
System administrators should be able to view all groups during the configuration of the Update Content node, regardless of the associated field having Auto Restrict Groups selected.

Actual Result
Users/Groups and Record Permissions fields only show the admin groups of which he/she is a member.

User-added image

User-added image

User-added image
WorkaroundDeselect auto-restrict groups before configuring the Update Content node, then re-select it once the workflow has been saved.