Configure Security Checkpoints for Approval Process

Explanation

The purpose of security checkpoints is to provide extra security in a specific function, method or business flow. With an activated security checkpoint on a function the current user will have to re-authenticate in order to fulfill the function. Additionally, whenever a security checkpoint is successfully passed a security checkpoint log is written, creating an audit trail of what was done.

Security checkpoints can be configured for the following activities of the approval process:

• Approve an Approval step of a Document Revision or an Object (e.g Customer Order, Change Request) where Approval process is enabled - DOCMAN_APPROVE_STEP
• Reject an Approval step of a Document Revision or an Object (e.g Customer Order, Change Request) where Approval process is enabled - DOCMAN_REJECT_STEP
• Approve a document with or without approval routing. If approval routing is enabled, all approval steps must be in the Approved state to approve the document revision - DOC_REV_SET_TO_APPROVED
•  Approve a structured document with the Structure feature enabled - DOC_STRUC_TO_APPROVED

You can activate and deactivate security checkpoints individually, but security checkpoints can also be activated and deactivated on a system level. To activate/deactivate a security checkpoint individually click View Legacy Checkpoints, select the specific checkpoint and click Activate/Deactivate.

Prerequisites

Only a system administrator can access and configure the security checkpoints.

System Effects

• When the security checkpoint is active and turned on, the end user will be presented with an extra authentication dialog at the checkpoint.
• Successful security checkpoints are logged and can be viewed on the Security Checkpoint Log page.