Validation
The Validation feature is for projects in critical environments and helps protect against inadvertent changes that might damage system functions. For instructions, see the step-by-step section.
When you change or command a validated object in the Flex client, the Validation Required dialog box might display, depending on several factors such as the configured validation profile, the configuration of Four Eyes, and the requirement of a comment. See the following table for more detail.
Validation Profile | Required User Action | Audit Trail Activity | |
Four Eyes Not Enabled | Four Eyes Enabled | ||
Disabled | No input | No input | None NOTE: If an object being edited is a validated object that creates an activity log, then entries in the Audit Trail column of the Log Viewer display Audit Trail. However, if the object is a non-validated object (Validation Profile = Disabled), then the entry displays as an Activity. |
Monitored | No input | Supervisor name and password1 | System logs action |
Enabled | Comment | Supervisor name and password1 + | System logs action |
Supervised | User password1 | User password1 + | System logs action |
1If you have autofill enabled on your browser, the password it returns will not work due to Desigo CC encryption. You can either turn the autofill option off in your browser, or select the password and manually enter the correct password.
You can add a comment one of two ways, depending on the validation profile configuration:
- User entered, or
- Selecting a predefined comment from the drop-down menu, if configured in the install client.
Additional Information for Four Eyes Authentication
- Approval must occur on the same client machine on which the change or command is initiated.
- Supervisors are limited to those designated as a supervisor by an administrator in the user or user group configuration.
- Supervisor approval can be initiated by any designated approver as long as the approver also has access to command that object.
- Supervisor must be a different user.
Log Viewer
Once you accept the entries to the Validation Required dialog box, the system records the changes, which you can review in the Log Viewer. The log serves as an audit trail record to achieve regulatory compliance for validation.
Object Version
The object version number increases if you modify or command a validated configuration object or property. However, modifying or commanding a validated status attribute object or property does not increase the object version.
Examples
- Modifying or commanding the High Alarm Limit or Discipline configuration property increases the validated object version.
- Modifying or commanding the Present Value status property does not increase the validated object version.
Validation Logs for Changes to Valid Field in Object Configurator
In the Object Configurator, various expanders contain the Valid check box, which enables the individual configuration of data points and properties.
This allows you to set specific behaviors different from what the associated Function and Object Model set as default (for more information, see Object Configurator).
When you select the Valid check box and perform a specific configuration, the Validation logs provide information about the Valid option change and the subsequent configuration actions.
However, when you deselect Valid to get back to the default condition, the Validation logs only contain the change to the Valid option (Valid value ... changed by user from Valid to Invalid).
In analyzing the log, you should therefore interpret this action as a reset-to-default for the entire set of involved configuration items.