Validation Rules

The system enforces the following rules based on objects' validation status:

• You can change an object's validation status only when it is checked in. If the object is not checked in, the system tries to checks it in. If another user has checked it out, you cannot change the validation status.

  Changing the validation status of a checked-in object does not change the version number of the object.

• You cannot promote an object instance to a validation status higher than its underlying object definition.

  For example, if you create an instance of a Program definition whose validation status is Quality Control, you can promote the instance to a validation status of Quality Control, but you cannot promote it to Production until the definition has been promoted to Production. However, the system attempts to promote the definition to Production when you promote the instance, and if you have the necessary privileges on the definition, and if the definition is not checked out by a different user, the promotion succeeds.

• Validation status is version-specific. Each time you create a new version of an object by checking it out (including checking out a definition through an instance) the system automatically gives the new version a validation status of Development. The system does not change the validation status of any existing versions.
• When you copy an object, the validation status of the copy is set to Development no matter what the validation status of the original is.
• You cannot run an Execution Setup whose validation status is less than the validation status of its owning object instance unless you have the IQ Submit security privilege on the Execution Setup.
• To be installed in a Work Area, object instances must have a validation status equal to or greater than the usage intent of the Work Area.
• The Work Area cannot be promoted to a validation status higher than the validation status of any of its object instances. However, if you try to promote a Work Area to a status above that of any of its objects, you have the opportunity to promote all the object instances and their underlying definition versions to the same status in a cascade operation.

  The cascade validation fails if a different user has checked out any of the object definitions in need of promotion.

• No executables can be run in a Work Area until the Work Area's validation status is equal to or greater than its usage intent value, except by users with the special Install Qualify Submit privilege on the Work Area. This is to allow testing of the Work Area before making generally available for use.
• Full installation and the Replace operation on Table instances in partial installation are not allowed in Work Areas with a usage intent of Production. This is to protect production data from deletion.
• You cannot remove a Table instance whose validation status is Production from a Work Area of any usage intent.