The 'Create New Workflow' interface can be accessed from the top navigational bar and is used to design and publish workflow diagrams that map out operational processes relating to case handling to be followed by users of the Iinsight system.
When the workflow creation process is started the first mandatory step is to define the workflow's name, and the service contract to which it relates and to provide a description of the workflow process - once these three items are confirmed the design stage can commence.
Each workflow in the iinsight system maps the progress of one or more activities and item costs applied in a pre-determined sequence to a specific service contract that has been designed to fulfill the case requirements. This is presented graphically as a branching structure composed of 'nodes', each of which is representative of an activity or item cost that progresses from a pre-determined beginning at the commencement of the workflow, to one of one or more conclusions.
The Workflow creation interface is comprised of two key tabs, which become available to the user once the preliminary name, service contract, and description information have been defined. The first of these, the 'Create New Node(s); Relationship(s)' tab allows the user to create new activity and item expenses, as well as to create relationships that link one or more nodes to each other.
When creating activities or items, those required for the workflow can be selected from the list offered, before being added to the workflow with the 'Create Node(s)' Button. Once these activities and items have been added to the workflow as nodes, they can be dragged and positioned as required.
There is only one System Node available at this time - New Referral. This can be set as the starting point to trigger the first Activity or Item once the case has been assigned.
The final option of the 'Create New Node(s); Relationship(s)' tab is the creation of 'Link Relationship(s)', which is fundamentally different to the nodes already covered in that rather than representing the cost of an item or activity, a link represents the chronological progression from the process represented by one node, to the process represented by the next.
A link relationship takes one of three forms, as detailed below:
A '1 to 1' Relationship | A direct relationship that defines the progression from one node to the next in chronological order, which may or may not specify a timeframe in which the progression is to be completed. The first node of this relationship should be defined as the starting point for the entire workflow. |
A '1 to Many' Relationship | A branching relationship defines the progression from one node to two or more child nodes in chronological order, each branch of which may or may not specify a timeframe in which the progression is to be completed. The first node of this relationship may be defined as the starting point for the entire workflow. |
A 'Many to 1' Relationship | A branching relationship defines the progression from two or more nodes to a single child node in chronological order, each branch of which may or may not specify a time frame in which the progression is to be completed. |