The FileHold workflow engine is designed specifically to streamline the review and approval of files as they proceed through their lifecycle in the document management system. In many collaborative work environments, this labor intensive growth stage of the document is where the most time savings can be realized using the workflow functionality of Filehold’s document management solution.
Using Document Workflow to Assist with File Management:
Organizations typically must manage a number of internal processes in order to track things like order processing, purchase requests and travel expenses. Workflow brings order to these independent processes in a transparent, dynamic, and robust fashion making it a key part of the document lifecycle.
Let’s take a look at the basic elements and roles of users involved in the records management system’s document workflows. Consider the following diagram.
What is a Workflow?
A workflow contains one or more activities (reviews and approvals) to be completed during the lifecycle of a document. Workflows can be used with all of the document types: document, record and offline, in the document management system.
Workflows are created in the web client interface by the Library Administrator. Observers and participants are assigned and then the workflows are associated with document types (schemas).
The workflow must then be initiated at the document level by a user of the the document management system. The initiator can be any user with Document Publisher or higher permission in the document management system that are members of the document schema associated with the document.
Groups can be named as observers of the workflows but only individual users will be able to be participants.
Every time a workflow is initiated a unique workflow instance is created and managed by the FileHold workflow engine. The underlying workflow engine is designed to manage literally thousands of simultaneous workflow instances for thousands of files.
Once initiated the first activity in the workflow begins. Users who are assigned the workflow tasks are referred to as participants. In this example it the first activity is for the review of a document. Participants are notified by email or via their task list of any new task requiring attention.
When all tasks in the activity are completed the activity is considered complete and the next activity begins. On completion of the last activity in any workflow the documents management system recognizes that the workflow is complete. The time from workflow initiation to completion can be from hours to months to years depending on the process being managed. The entire time the workflow is in progress observers can be designated to watch over the workflow, the workflow itself modified and tasks reassigned.