000033254 - Record can be saved with no entry for a required field for a previously created record in RSA Archer

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Oct 11, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033254
Applies ToRSA Product Set: Archer
RSA Version/Condition: All
Product Description: Archer Platform
IssueAfter editing a field configuration to make it required, previously existing records that did not have an entry for that field can be edited and saved without adding an entry for the field.  No error or warning message is displayed.

To reproduce:
  1. In the application builder, open any application and edit any field.
  2. Select the Required option and save the field.
  3. Navigate to any previously existing record for this application and click the Edit button.
  4. Note that the red asterisk (*) is displayed indicating that the field is required.
  5. Click Save.
  6. Note that the record is saved without any pop-up error or warning message.


  1. Open the record again and click Edit.
  2. Make a change to any field, such as adding text to a text field.
  3. Click Save.
  4. Note that you now received a warning message telling you that the field is required.

CauseEven though you open a record in Edit mode and click Save, Archer does not actually execute a record save action if no data has been changed in the record. Since the record save action is not performed, the required field is not evaluated.

On the other hand, if you were to open the record in Edit mode, enter or change data in any field, and then click Save, the required field would be evaluated as part of the record save process and you would see an error message telling you that the required field has not been entered.

RSA Archer Product Management has previously evaluated whether this is how the application should work, and they have confirmed that it is working as intended. 
ResolutionIf you do not change anything in the content the save does not actually trigger when the Save button(s) is clicked. Editing a field causes the required field to be evaluated. This is functioning as intended.