<< Click to Display Table of Contents >> RayQC > 8.0 > User Guide > Settings Behavior |
Within the behavior view of the RayQC settings section, users can manipulate the following configuration options:
Set this slide toggle to YES to prevent manual overriding of element values which were automatically calculated as plug-in results. The default setting is NO, which means that users may change the result that has been delivered by plug-ins. There is no strict recommendation to lock plug-in results or not - it is up to the decision of the quality control manager to allow manual adjustments or not.
The signing options defined within the signing tab o the settings view do not automatically trigger checklist signing. They just prepare RayQC to be able to sign checklists in general. Setting the slide toggle to YES enables checklist signing, whilst setting it to NO disables it. The combination of general settings and separate option switch makes it fairly easy to keep permanent signing options but at the same time be able to make actual use of them flexibly as required.
The slide toggle is not accessible for modifications as long as there is no keypair profile defined in the signing tab. Please define a key pair profile by using the interface in the signing tab to enable the toggle control.
One aspect of system security is checklist signing. Since checklists may run scripts and execute applications on the local device, it is a matter of enterprise security to make sure that no malware is brought into the system, and that no unauthorized modifications are executed. By activating this option, any checklist that is not signed will not be opened by RayQC - or executed for that matter. Allowing only signed checklists is the safer mode of operation, since it allows to knowing about the origin of checklists at any time.
If an environment is set up to reject unsigned checklists, the idea to make sure signing has been performed by the application of a trusted certificate is just one tiny step away.
Note: Activating this option does not automatically reject checklists that are not signed at all. It simply rejects those checklists, that are signed, with untrusted certificates. To make sure only checklists signed by trusted certificates are loadable, both options Reject checklists without signature and Reject untrusted certificates have to be enabled! |