Glide List Auto-Save and Add/Remove Multiple Behavior

[PareshW]

We have a requirement where the Enforce Restriction checkbox controls access to a record.

 

Expected Functionality

• When Enforce Restriction is set to true, two Glide List fields should become visible:
  • Allowed Members
  • Allowed Groups
• The purpose of Enforce Restriction is to restrict record visibility to:
  • The person assigned to the record.
  • Members of the Admin Team, who can view the record based on a backend query/business rule configuration.
• When users add members or groups to the Allowed Members or Allowed Groups fields, those values should be saved as part of the record configuration.

 

Issue Encountered

We are experiencing an issue with the Glide List fields, specifically when using the Select Target Record / Add/Remove Multiple functionality.

1. When we add a value to Allowed Members or Allowed Groups using the Select Target Record option, the selected value appears to be automatically saved to the backend before the user completes the overall record update.
2. Because the value is being saved immediately, when we subsequently click Add/Remove Multiple, the previously selected record is sometimes not displayed in the Selected area.
3. The Add/Remove Multiple popup also becomes blank intermittently, making it difficult for users to add or remove multiple values.
4. Another issue occurs when working with both Glide List fields:
   • If we select values in Allowed Members and then click Allowed Groups, the selection in Allowed Members is automatically saved.
   • Similarly, if we select values in Allowed Groups and then switch to Allowed Members, the selection in Allowed Groups gets automatically saved.

Question

Is this expected behavior for Glide List fields when a reference qualifier, business rule, or backend query is being used to enforce record-level restrictions?

If this is expected behavior, what would be the recommended ServiceNow approach/best practice to prevent the Glide List values from being committed automatically while the user is still editing the record?

We would specifically like to ensure that:

• The selected values remain available in the Add/Remove Multiple popup.
• Switching between Allowed Members and Allowed Groups does not prematurely save the values.
• Values are committed only when the user saves/updates the main record.
• The backend restriction/query continues to work as intended after the record is saved.