Home > Workflow

Workflow User Guide

Workflow access

The workflow can be accessed through the following icon in EBX.Manager:

If the user has some work items to do, the icon will look slightly different:

Worklist

The worklist shows all processes waiting for a user interaction on which the current user can interact.

This worklist looks like this:

Conditions and script tasks will never be shown.

The first level of the tree describes the published processes which are available to create process instances.

The second level shows the process instances.

The third level shows waiting work items

Icons memento

	Work item offered to one of the roles of the current user, or allocated to him for one of the process instances of the publication.
	No work item for current user for the publication.
	Process instance is over.
	Work item offered to one of the roles of the current user or allocated to him for this process instance.
	No work item for the current user for the process instance.
	The work item is allocated to the current user but not started.
	The work item is allocated to a different user than the current user.
	The work item is over.
	The work item is offered to one of the roles of the current user.
	The work item is offered to a role to whom current user does not belong.
	The work item is allocated and started by the current user.
	The work item is allocated and started by another user.

Creation of a process instance

Two ways exist to create a process instance:

• through the GUI of the worklist by selecting a publication,

• through a trigger.

It is possible to define a specific documentation.

Starting a process instance

A token is created at the beginning of a process instance. This token jumps from step to step following the links defined in the process definition.

Three cases are possible:

• The token arrives on a script task: this one is run immediately and requires no user interaction.

• The token arrives on a user task: one or more "work items" are created. This work items need user interactions.

  A work item is over when the GUI user clicks "Accept" or "Reject". For each work item, the user can specify a comment.

• The token arrives on a condition: it is immediately evaluated to define which route has to be followed.

When a step is completed, the token proceeds to the next step.

User tasks: life cycle

Each user task spawns one or several "work items" which have the following life cycle:

1. Offered to one or several profiles,

2. Allocated to a user,

3. Started,

4. Complete (with state Accepted or Rejected).

In the event of any failure, the user task can be set to an error status.

View history of a process instance

The history allows to follow the routes taken by a token for a given process instance. It is then possible to see the comments written by users, the errors etc.

History table

The history table and neighbour tables allow access to the whole details about a process instance.

The access to such data is done by browsing the main branch . 

Graphical workflow history

The access to the graphical workflow history is done by clicking on a process instance in the work list tree.

Boxes representing user tasks, scripts and conditions are clickable, to display the corresponding information panel.

Each work item can be rolled over with the mouse, displaying a small panel with information regarding this work item.

Home > Workflow