SignedWrite() runtime behavior

At runtime, the SignedWrite() function does the following:

1. Checks the target Attribute for Signed Write or Verified Write configuration.

   If not so configured, the following error message appears: Operation Failed. Attribute does not have the correct security classification.

2. Checks Galaxy security.

   If the Galaxy is not secured, the following error message appears: Operation Failed. Galaxy is not secured.

3. There are several ways to write to an Attribute configured with Secured Write or Verified Write security classification, it is possible to have multiple SignedWrite() and other Secured/Verified writes pending from the same script, or even from multiple scripts running side-by-side.

4. Determines which dialog is required—Secured Write or Verified Write—and pops up the appropriate dialog box.

   If Smart Cards are enabled, the function displays different versions of the Secured Write and Verified write dialog boxes.

5. Lists the predefined comments, if any, from the configured Predefined Comments list. Up to 20 comments are supported.

6. Enables comment editing if the Comment_Is_Editable parameter is configured and comment enforcement is other than PredefinedOnly.

7. Acquires the user credentials and authenticates them.

   If the user credentials are invalid, an error message appears. The function will attempt the write only if the credentials are valid.

8. Checks if comment enforcement is mandatory, and displays an error message if the comment is empty.

9. Performs the write if user credentials are valid and the comment entry satisfies the comment enforcement parameter.

10. Provides a return status.

11. Following a Secured or Verified Write a security Event is written to the event log, including the signee name, verifier name, if any, Type of write: "Secured Write" or "Verified Write", Comment, if any entered by user, Reason Description, if any provided, Field Attribute description, if any, or the Short Description of the Application Object, if no Field Attribute description exists.

Each call to SignedWrite() is distinct from any other. The success or failure of any individual write does not affect other attempted writes.

Entering user credentials for SignedWrite() is distinct from logging on to the client application. The user can modify attributes configured with Secured or Verified Write even if another user is logged on, without affecting the session of the logged-on user.