CATSWeb Manager User Guide - Managing Signature Controlled Operations

Managing Signature Controlled Operations

Contents

Introduction
Overview
Signature Controlled Operations - Issues
Signature Controlled Operations - Actions
Signature Controlled Operations - Subtasks

Introduction

CATSWeb Signature Controlled Operations enable signature requirements to be integral parts of the workflow process. When a signature controlled operation is implemented, a record cannot move forward in the workflow process until all required signatures (or authorized proxy signatures) have been added to the record. Signature requests may be routed to the appropriate users in serial or parallel fashion.

Advanced Feature

Signature Controlled Operations are an advanced CATSWeb feature. Administrators should be thoroughly familiar with basic CATSWeb workflow before configuring Signature Controlled Operations.

Here is an illustration of how a typical signal controlled operation would work, using the example of a Preliminary Disposition Approval operation defined for Issues:

A new Issue is entered and a disposition request is assigned.
Three users collaborate on the Issue, each entering various aspects of the Preliminary Disposition, including Notes and File Attachments.
An authorized user initiates signature requests for the Issue. This is done by editing the record and changing the value of the signature request field from Signatures Not Requested to Request Signatures. When the Issue is saved, CATSWeb automatically adds signature request tasks for the users who must sign the record, and sends each of them an E-mail notification message.
Users who view the Issue will now see the signature request status as being Signatures Requested. Depending on various options configured by administrators, they may find that they can no longer edit the Issue, or add new Notes, File Attachments, etc.
As required signatures are added to the record, the list of signatures gets longer, while the list of signature requests for the record gets correspondingly shorter. When the last required signature is added, CATSWeb automatically sets the signature request status to Signatures Completed. Various users are automatically notified via E-mail that the signatures have been completed.
The record is now ready for its next workflow step.

Signature Controlled Operations - Issues

Issue records can have the following signature controlled operations defined on a category by category (form by form) basis:

Issue Submission Approval - This operation forces signature approval of the initial Issue submission, and must be completed before any Disposition information may be entered (if the Issue category includes a Disposition step), or before the Issue may be assigned to an Action (if the Issue category does not include a Disposition step).
Preliminary Disposition Approval - This operation forces signature approval of Preliminary Disposition information, and must be completed before the Final Disposition (and Action Request) may be entered. This operation does not apply to Issue categories without a Disposition step.
Final Disposition Approval - This operation forces signature approval of Final Disposition information, and must be completed before the issue may be assigned to an Action, or ReDispositioned. This operation does not apply to Issue categories without a Disposition step.
Action Assignment Approval - This operation does not actually block the workflow process as the other operations do. It is provided to enable the Action assignment to be approved, and can allow the Issue to then be locked, preventing further edits or other modifications.

Signature Controlled Operations - Actions

Action records can have the following signature controlled operation defined on a category by category (form by form) basis:

Action Completion Approval - This operation forces signature approval of an Action before it may be completed. A configuration option can be set that will automatically set the Action status to Completed when the last approval signature is added.
Action Closing Approval - This operation forces signature approval of an Action before it may be closed. A configuration option can be set that will automatically set the Action status to Closed when the last approval signature is added..

Signature Controlled Operations - Subtasks

Subtask records can have the following signature controlled operation defined on a category by category (form by form) basis:

Subtask Completion Approval - This operation forces signature approval of a Subtask before it may be completed. A configuration option can be set that will automatically set the Subtask status to Completed when the last approval signature is added.
Subtask Closing Approval - This operation forces signature approval of a Subtask before it may be closed. A configuration option can be set that will automatically set the Subtask status to Closed when the last approval signature is added.