Have You Seen Workflow Lately? Click here to check out all the new features in the latest version.

Supercharge your GE solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Learn more about the Proficy 2024 releases, by signing up for one of our upcoming events.

Home
Data Administration
Electronic Signatures and Audit Trails
Purpose of Electronic Signatures
Electronic signatures are intended for application developers, process control engineers, and workflow users who want or need to incorporate electronic signatures and audit trails into their operations.
Audit Trail Reports
Workflow provides the ability to generate reports based on your audit trail and electronic signature data.
Filter electronic signatures

Workflow Products Documentation

Data Administration
- Data Administration Introduction
- Electronic Signatures and Audit Trails
  - Electronic Signatures and Audit Trails
    Workflow provides the ability to electronically sign forms in the run-time environment and to create an audit trail of those signatures, as well as audit other configuration changes made to the system.
  - Purpose of Electronic Signatures
    Electronic signatures are intended for application developers, process control engineers, and workflow users who want or need to incorporate electronic signatures and audit trails into their operations.
    - How to Use Electronic Signatures
      Electronic signatures are the computer-generated, legally-binding equivalents of handwritten signatures. They uniquely identify the persons responsible for an action.
    - Signatures During Workflow Run Time
      When a running workflow requires an electronic signature for a particular section, the appropriate operator must sign and/or verify the task/task step action or form; otherwise, the workflow will not proceed further.
    - Electronic Signature Tracking
      Each time an operator signs an action, a detailed electronic record is written to the electronic signature audit trail.
    - 21 CFR Part 11 Overview
      21 CFR Part 11 is a United States Government Food and Drug Administration (FDA)-mandated regulation that requires all electronic records and signatures, paperless records, and reporting procedures related to the manufacture of a product be captured and stored securely for businesses under its control, such as the Bio-Pharmaceutical and Food and Beverage industries.
    - Audit Trails
      Workflow provides audit trail capability that allows you to keep a traceable record of actions that are performed within your system. Actions that regulators are concerned with are typically those actions that commonly occur in a production environment.
    - Configure Audit Trails and Electronic Signatures
      The Audit/E-Signature editor is used to configure audit trails and electronic signature failure limits.
    - Audit Trail Reports
      Workflow provides the ability to generate reports based on your audit trail and electronic signature data.
      - Add the sample audit reports
      - View electronic signature and audit reports
      - Synchronize the run-time and reporting databases
      - Filter audit reports
      - Filter electronic signatures
      - IAuditTrail
        IAuditTrail allows you to write entries to the audit trail.
- Data Sources
- Archives
- Custom Property Types
- Transferring Workflow
- Reporting

Filter electronic signatures

Before you begin

The reporting database must be installed before you can proceed.

Procedure

In the SQL Server Reporting Services web interface, click the View tab.
To set the time range of electronic signatures, in the Start Date and End Date fields, enter the date and time.
To filter electronic signatures, from one of the following drop-down lists, select an item:
- Performer Groups
- Verifier Groups
- Is Successful
- Is Cancelled
- Is Failed
Or, in one of the following fields, enter search criteria.
- Performer Username
- Verifier Username
- Performer Full Name
- Verifier Full Name
- Performer Comment
- Verifier Comment
Note: Wildcard searches using the % character are supported. For example, you can search for % in the Verifier Username field and get all reports where a verifier signature was made.