Organizes Document Oriented Process
i-doc is one of the document management software in the market that permits the user to explore beyond the realms of plain record management and automates all possible document oriented workflow. Although in the lower version of i-doc , Version 3.0 Standard, the workflow is standardized and static, the higher versions offer a broad scope, where the users, without any technical knowledge, can customize their work with simple drag and drop method on a workflow designer.
Available in i-doc standard version, this workflow is very simple and addresses to its viewing and searching purpose. The pre-defined workflow path involves uploading of the documents, approving them, publish them on approval or reject them on non-approval. Authorized viewers get mail notification for all approved and published documents.
Anybody assigned with the role that includes upload can do this task and wait for the administrator to approve these documents.
Usually the administrator approves the documents before they automatically start reflecting in the interface, which is termed as â€˜Publishedâ€™. No documents would be reflected until is passes through the approval stage.
Users who are selected to view the documents during the course of defining viewing rights, would get a notification regarding its â€˜Publishedâ€™ status.
For organization with a more complex document life, this is the ideal solution, as the administrator can define the path of the document and automate the task without depending on the developers. With the help of a workflow designer attached with every module, the administrator can create multiple related workflows, resorting to drag and drop techniques. A workflow contains four basic components listed below. A non-technical person should have a vivid conceptual clarity regarding these four components.
The first action that commences the workflow, associated with the user and the specific module is the activity.
On completion of the activity, a â€˜Taskâ€™ is assigned to a user or a set of users. A task is followed by positive path and negative path. Each path leads to another set of task in the same pattern.
A â€˜conditionâ€™ would denote the â€˜ifâ€™ and â€˜butâ€™ factors helping in more intricately defining the path and their consequential tasks.
â€˜Actionâ€™ is the final effect on the document that brings an end to the workflow after a complex amalgamation of all other components, represented with various shapes and colors that are dragged and arranged on the workflow designer.