HRSD Preliminary Vancouver release notes: Identify a security policy
The preliminary release notes for the Vancouver release are available as Release Testing Preview (RTP).
⚠️ Note: These preliminary Vancouver Release Testing Preview release notes contain draft content. With the launch of Vancouver Early Availability, visit docs.servicenow.com to read the official Vancouver release notes and product documentation.
In addition to ACL's to secure records, HR Service Delivery offers COE Security policies as a way to configure which groups are allowed access to COE tables. Read more on it here.
Good practice
A good practice is to (in addition to documenting) always fill in the Description for configuration or scripting. For ACL’s you can do this:
(Note: Description content is blurred, as the Out of the Box (OOTB) description for this record is not the best example of a clear descriptive Description)
Missing fields
However, until the Vancouver release, this was not possible. Any assumptions or intend of the developer/configuration is not clear when you open the record:
You have to dive into the documentation (hopefully) created by the person that configured the record. As there are no Name or Description fields available:
There is already a field called “Display name” [sys_name] prior to Vancouver. However, that is read only by default and only contains the table name, regardless of the configuration:
Vancouver to the rescue!
However, the Preliminary release notes for the Vancouver Release show something promising:
Identify a security policy by capturing its name and short description in the Policy name and Short description fields on the COE security policy form.
(Note: Above image is an artist rendition and does not reflect the real form in Vancouver)
I would prefer Name and Description, which is more common on the platform. However, it is great to have this OOTB to make it clearer what the intend of the configuration is.
Want to know more about COE Security policies and ACL's related to HR Service Delivery? Read more here:
https://www.servicenow.com/community/hrsd-articles/hr-security-evaluation-acl-s-and-coe-security-pol...
