Validating Objects and Outputs

This section includes the following topics.

• About Object Validation
  Your organization must develop standards for testing Oracle Life Sciences Data Hub defined objects to demonstrate that they are valid; that is, that they handle data as they are designed to do, without introducing any corruption.
• About Output Validation
  By default, outputs inherit the validation status of their Execution Setup. The Execution Setup inherits its validation status from its executable instance. An instance cannot have a higher validation status than its source definition.
• Validation Statuses
  There are four validation statuses in Oracle Life Sciences Data Hub: Development, Quality Control, Production, and Retired. Your organization must develop a policy on the use of validation statuses.
• Changing Objects' Validation Status
  Object definitions and instances both have a validation status.
• Changing Outputs' Validation Status
  To change an output's validation status, do the following:
• Adding Supporting Information
  Before you promote an object to the next validation status, your organization may require that you provide documentation about the object: either a link to an output generated by the object, such as a report or log file, or a document such as a functional requirements document for the object.
• Validation Rules
  The system enforces the following rules based on objects' validation status.