Workflow Templates Overview

How does FileHold Handle Workflow Templates and Ad-hoc workflows?

FileHold allows library administrators to create pre-defined workflow templates and associate these templates with the different types of documents (also called document schemas) managed by the library. For example a ‘Travel Expense Approval’ workflow template would most likely be associated with the Expense Report document schema. This means that as end users add Expense Report documents to the library they will have the option to quickly initiate ‘Travel Expense Approval’ workflows with routing, tasks and due dates specifically tailored for the approval of expenses. Use the following link to learn more on associating workflow templates with document schemas.

Use the following link to learn more on managing document schemas.

Library administrators are able to provide a range of flexibility for the initiator when define the activities, participants, tasks and other properties of a workflow instance. This ranges from a 100% pre-defined workflow template that the initiator cannot modify - to ad-hoc workflows that are 100% defined by the initiator.

In the following below example the order processing, purchase request and travel expense document types have pre-defined workflow templates associated with them with a unique number and sequence of review or approval activities. For marketing documents that are added to the library initiators need to be able to define workflows in an add-hoc fashion to accommodate the variety of different review scenarios that occur in the marketing department.

Use the following link to learn more about setting up workflow templates.