20R1 Data Model Changes: Platform

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 Platform data model. These data model updates are automatically included in all Platform Vaults, but Admins must make configuration changes to make them available. For information on feature functionality, see What’s New in 20R1.

Made the following changes on the User object:

• Added System Owned User field (system_owned_user__sys); this is a Yes/No field that distinguishes normal licensed users from system-owned users like System and App Owner.
• Added Edit Localized Labels field; this is an object reference to Language (language__sys) and is only active when the Enable Multilingual Labels setting is on.

Made the following changes to support Document Archive:

• Added the Archived Date (archived_date__sys) DateTime document field to the Base document type; this field only displays in the Doc Info page if it is not blank. It is a system-managed field that Vault automatically populates.

Made the following changes to support the Unmodified Source Rendition Type for Modified Vault Documents feature:

• Added the Unmodified source (unmodified_source__sys) rendition type to the Base document type; this rendition is automatically generated.

Made the following changes to support the Test Data Packages feature:

• Enabled object type support on the Outbound Package (outbound_package__v) object and added the following object types:
  • Migration (migration__sys)
  • Test Data (test_data__sys)
• Added the new field Test Data User (test_data_user__sys) to the Outbound Package (outbound_package__v) object; this text field supports defaulting user references.

Made the following changes to support the feature Attach Multiple Documents in Checklist Responses:

• Added the fields Documents Allowed (documents_allowed__sys) and Documents Required (documents_required__sys) to the following objects:
  • Question Design (question_design__sys) for the Base (base__v) object type only
  • Available Answer Design (available_answer_design__sys) for the Base (base__v) object type only
  • Library Question (library_question__sys) for the Base (base__v) object type only
  • Answer Library Design (answer_library_design__sys)
  • Response (response__sys) for the Base (base__v) object type only
  • Available Answer (available_answer__sys)
  • ‘Target Object’ Response (<target object>_response__sys) for the Base (base__v) object type
  • ‘Target Object’ Available Answer (<target object>_available_answer__sys) for the Base (base__v) object type
• Added the following new objects:
  • ‘Target Object’ Response-Doc (<target object>_response_doc__sys) as a Checklist Response Document object class

Made the following changes to support the Checklist Design Versioning feature:

• Added new objects:
  • Checklist Design Master (checklist_design_master__sys)
• Added fields to the Checklist Design (checklist_design__sys) object:
  • Checklist Design Master (checklist_design_master__sys)
  • Version (version__sys)
  • Version Description (version_description__sys) Version Controlled (version_controlled__sys)

Made the following changes to support the Aggregate Checklist Designs feature:

• Added new objects:
  • Sub-Checklist Design (subchecklist_design__sys)
• Added fields to the Checklist Design (checklist_design__sys) object:
  • Aggregate Checklists (aggregate_checklists__sys)
  • Owner (owner__sys)

Made the following changes to support future functionality:

• Added the Suggested Links (annotations_suggested__v) document field