With every release, we update the data model to better support evolving needs and new feature functionality. With this release, we’ve added the following components to the data model. These data model updates are automatically included in all Vaults, but Admins must make configuration changes to make them available. For information on feature functionality, see What’s New in 19R2.
Data Model Changes for User Role Setup Source
This change introduces two non-required, non-editable fields on objects with the User Role Setup class: Source (user_source__sys) picklist and Source Reference (user_source_ref__sys) text field. In future releases, Vault applications will use these fields to track the origination of User Role Setup records and protect system-generated records.
Note: Although Vault prevents users from saving values in the Source and Source Reference fields, the fields do appear as editable when working with User Role Setup objects. We recommend using field-level security to make these fields read-only for all security profiles except Vault Owner.
Data Model Changes for Lifecycle Stages
Veeva has made the following changes to the data model for all vaults:
Added Lifecycle Stage (stage__sys) document field to all document types to support the Lifecycle Stages functionality. This field is visible from the document UI and field values are not editable.
Added Lifecycle State Stage ID (state_stage_id__sys) document field to all document types to support the Lifecycle Stages functionality. This field is visible from the document UI and field values are not editable.
Data Model Changes for Checklist Objects
We have implemented various changes to the Platform data model for checklists. These changes support functionality in Vault Training that builds on the Checklists feature. There are no functionality changes to Platform vaults or to other applications.
- Added Points (
points__sys) field to Checklist Design object, Section Design object, and Question Design object, as well as runtime Checklist, Section, and Response objects - Made Checklist Category (
checklist_type__sys) field not required on Checklist Design object and runtime objects - Enabled object types on Available Answer Design object and runtime Available Answer object
- Added Correct Answer? (
correct_answer__sys) field to Available Answer Design object and runtime Available Answer object - Added Answered Correctly (
answered_correctly__sys) field to runtime Response object