Done By/Check By Signature Page

When an operator performs an action during execution that has been configured to require a Done By and/or Check By confirmation, the Done By / Check By Signature page appears. The logged on operator must complete the confirmation using the authentication process before proceeding with the action.

The Done By /Check By Signature page includes the following information based on the information passed during the Execution action:

• Type of action being requested

• Type of Electronic Signature required (Done By and/or Check By)

• Whether comments are required, and

• A list of changes for the approvers to view before signing. For example, the Changed Values grid displays the Parameter Target original and new value or the Parameter Actual original and new value along with the unit of measure. It also displays the Changed By details.

The mandatory fields are marked with an asterisk (*) indicator.

Once the Done By / Check By signature page is opened, a user or users will need to enter a comment (may be optional) and sign for their particular role in the confirmation process. Only the signature types that are configured for the given action will be required. For example, if only Check By is configured, the Done By signature section will not appear (and vice versa). If both are configured, the Done By signature must occur before the Check By.

To sign, the user presses the Sign button and must enter their login credentials. They can enter comments before or during the signing process, but once signed, the comments cannot be changed.

NOTE: The browser will not save the password even if the browser settings is configured to save the password. You must enter the user name and password whenever you want to sign the Done By/Check By actions.

Validating the Authorization for Actions

Validation ensures:

• Check By user cannot be the same as the Login user.

• The Done By /Check By actions are performed by users as per the configuration. When signing, if a user is not permitted to perform the selected signature type for the given action, an error message appears notifying the user that permission has been denied. The error message also provides some information as to why access was denied. For example, in the case if Done By /Check By action is performed by same user, the following error message appears: Check By user cannot be the same as the Done By user.

• The Done By/Check By Settings are configured for the respective action. In the case of an error, the following exception is thrown: The required signatures have not been properly acquired to perform this action.

• The Done By/Check By Settings for the user are configured for the selected Parameter Group. If the user does not have the permission to edit the selected Parameter Group, an error message appears "User [Domain\User ID] does not have the Parameter Group [XXX] permission to edit the value for Parameter."

In the case of successful validation, the Done By/Check By signature page is closed and the requested action will be performed. For example: Assign Formula.

The action calls are validated during runtime and as per the configuration defined, the following Done By/Check By Signature page will be prompted:

• Assign Formula

• Download Formula

• Assign Recipe

• Start Recipe

• Hold Recipe

• Restart Recipe

• Pause Recipe

• Resume Recipe

• Abort Recipe

• Stop Recipe

• Abandon Recipe

• Hold Capability

• Restart Capability

• Pause Capability

• Resume Capability

• Abort Capability

• Restart Capability

• Acknowledge Capability

• Force Transition

• Change Runtime Parameter Values (Targets/Extensions Before Start)

• Change Runtime Parameter Values (Targets/Extensions After Start)

• Change Runtime Parameter Values (Actuals)

Canceling Done By/Check By Signature Action

For a single equipment and in some other specific cases, only one signature page can be active at a time. In these cases, the one Done By/Check By Signature page will be canceled and the newer one will become active. These scenarios can occur if two users are working on the same Recipe/Formula at the same time. There are also some cancellation scenarios that can occur if you try to use the DoneBy/CheckBy Signature page from two browser tabs at the same time.

The following rules are applied for canceling an active Done By/Check By signature action (within the same equipment scope):

• Parameter edits will cancel outstanding Start Request signature pages.

• Parameter edits will cancel outstanding Ack Request signature pages.

  • Only if the edits are for the Capability being Acked.

• Parameter edits will cancel Parameter edit Request signature pages.

  • Only if the same Parameter is being edited

• Start Requests will cancel outstanding Parameter Edit request signature pages

• Ack Requests will cancel outstanding Parameter Edit request signature pages

  • Only for Parameters with the same Capability being Acked

• Assign requests will cancel all other outstanding request signature pages

• Any request will cancel outstanding assign request signature pages.

When a Done By/Check By signature page is canceled, then all other options in the dialog are disabled and only the “Cancel” button is available. Also, an error message “Another Done By/Check By action has canceled this authorization attempt” appears in the Done By/Check By signature page.