Programmatic E-Signature Workflows

Sepasoft MES Module Suite

Programmatic E-Signature Workflows

The system.mes.signature.authorization scripting functions provides the essential tools to programmatically manage and enforce electronic signature workflows within the MES. These functions are a critical component for ensuring process integrity, adhering to compliance standards, and automating user-level approvals. By leveraging these functions, you can build robust, event-driven signature challenges directly into your industrial applications.

Below details the three core functions of the module, explaining their parameters, return values, and how they work in sequence to create a complete workflow for queuing, triggering, and monitoring e-signature requests.

The Signature Authorization Workflow at a Glance

To effectively use the authorization scripting functions, it is crucial to understand the end-to-end workflow. These functions are not designed to be used in isolation but rather as part of a coordinated, three-step process: defining and queuing a request, triggering the user interaction, and optionally, querying the status of all pending requests.

The standard workflow follows this logical progression:

Step 1: Queue Request: system.mes.signature.authorization.queueAuthRequest() - Define the signature requirements and callback actions.

Step 2: Trigger Challenge: system.mes.signature.authorization.triggerAuthRequest() - Present the signature challenge to a user in a specific session.

Step 3: Get Pending Requests (Optional): system.mes.signature.authorization.getPendingAuthRequests() - Retrieve a list of all outstanding requests.

Scripting Function Reference

Together, these three functions—queueAuthRequest, triggerAuthRequest, and getPendingAuthRequests—provide a complete and robust programmatic framework for managing MES electronic signatures, from initial definition and workflow configuration through direct user interaction and final status monitoring.


Sepasoft MES Module Suite