Difference between revisions of "Workflow"

From SNIPER Systems
Jump to: navigation, search
Line 1: Line 1:
SNIPER D.M.S always had a simple workflow management requesting review and approval before a document is released.
+
The system automatically handles the workflow for each document and stores changes, versioning, comments made, etc.
To Create a workflow
+
===Validation cycle===
 +
The normal workflow requires, when loading a new document or a new version, to indicate some users or groups of users as reviewers and/or approvers. Users that are listed as reviewers and approvers are required to explain their approval to the document. When this operation is completed, thus all listed users have made their review/approval, the state of the document will set to 'released'.
 +
 
 +
The reviewer/approver can deny its approval to the document. In this case the document state is set to 'rejected'.
 +
 
 +
A doc that are not set reviewers and approvals take immediately the state of 'released'.
 +
 
 +
As approvers/reviewers one can indicate groups of users. In this case the review/approval should be made by any of the users belonging to the group.
 +
 
 +
The document owner may at any time amend the list of reviewers/approvers.
 +
 
 +
===Documents status===
 +
Possible states for a document are:
 +
 
 +
#Draft pending approval: one or more of the approvals referred to have not yet expressed their approval.
 +
#Draft pending review: one or more of the listed reviewer have not yet expressed their review.
 +
#Released: the document has successfully completed its validation cycle.
 +
#Rejected: the document has discontinued its validation cycle.
 +
#Expired: you have exceeded the target date for completion of the validation of the document.
 +
#Obsolete: the status of a released document can be changed to obsolete. This is intended as an alternative to the cancellation of the document. #Obsolete state is reversible.
 +
===Expiration===
 +
For each document in production can be set a due date. Once passed the day set are no longer possible revisions or approvals and the document goes into an 'expired' state.
 +
 
 +
The deadline is considered only for the latest version of the document and has effect only on document processing.
 +
 
 +
===To Create a workflow===
 
* Navigate to Admin-Tools in the top bar
 
* Navigate to Admin-Tools in the top bar
 
* First Go to Workflow States and create the statuses that your document will go throw
 
* First Go to Workflow States and create the statuses that your document will go throw

Revision as of 21:38, 4 August 2015

The system automatically handles the workflow for each document and stores changes, versioning, comments made, etc.

Validation cycle

The normal workflow requires, when loading a new document or a new version, to indicate some users or groups of users as reviewers and/or approvers. Users that are listed as reviewers and approvers are required to explain their approval to the document. When this operation is completed, thus all listed users have made their review/approval, the state of the document will set to 'released'.

The reviewer/approver can deny its approval to the document. In this case the document state is set to 'rejected'.

A doc that are not set reviewers and approvals take immediately the state of 'released'.

As approvers/reviewers one can indicate groups of users. In this case the review/approval should be made by any of the users belonging to the group.

The document owner may at any time amend the list of reviewers/approvers.

Documents status

Possible states for a document are:

  1. Draft pending approval: one or more of the approvals referred to have not yet expressed their approval.
  2. Draft pending review: one or more of the listed reviewer have not yet expressed their review.
  3. Released: the document has successfully completed its validation cycle.
  4. Rejected: the document has discontinued its validation cycle.
  5. Expired: you have exceeded the target date for completion of the validation of the document.
  6. Obsolete: the status of a released document can be changed to obsolete. This is intended as an alternative to the cancellation of the document. #Obsolete state is reversible.

Expiration

For each document in production can be set a due date. Once passed the day set are no longer possible revisions or approvals and the document goes into an 'expired' state.

The deadline is considered only for the latest version of the document and has effect only on document processing.

To Create a workflow

  • Navigate to Admin-Tools in the top bar
  • First Go to Workflow States and create the statuses that your document will go throw
  • Then Go To Workflow actions And create The action you need (The Action here is just the name that will connect the work flow steps with each other)
  • Finally you go to Workflow and create your workflow
    • After you create the workflow you will got an area to create the steps of the workflow each step most have user (User Mangment) and action and status


Workflowman.png


Workflow-states.png


Workflow-actions.png


Workflow.png