For example, your system could be configured to require a signed spatial calibration (object) before you
can start a spectral calibration (action); or it could be configured to require a signed spectral calibration,
a signed install run, and a signed plate file (objects) before you can start a regular run (action).
The objects that are required for an action can be signed at two dierent times:
•
Before you start a run (see “Signing an object before a regular run is started” on page 246)
•
When you start a run (see “Signing an object when a regular run is started” on page 247)
Signing an object before a regular run is started
Note: The Sign button is displayed only if your SAE account role has permission to sign objects.
If your system is configured to require a signature when you start a regular run (that is, not a calibration
or an install run), you can sign the required objects at the time the objects are generated or created,
instead of waiting to sign when you start a run. The objects that are required are configured by your
SAE administrator.
When you run or create any of the objects listed below, you can sign any of the objects by selecting
Actions4Sign in the associated screen.
•
Spatial calibration
•
Spectral calibration immediately after it runs, or by accessing it in Spectral calibration history
•
Install run immediately after it runs, or by accessing it in Install run history
•
Plate file when you create it, or by accessing it in the library
For example, if a signed spatial calibration is required, you can tap Actions4Sign at the end of a
spatial calibration. You can also open a spatial calibration after it is complete and sign it.
Chapter 10 Use the instrument with the Security, Auditing, and E‑signature (SAE) v2.1 module
Signing an object before a regular run is started
10
246
SeqStudio
™
Flex Series Genetic Analyzer with Instrument Software v1.0 User Guide
To Next Page
Loading...
