A process modeled in Workbox is readable and transparent. As you can see on the diagram, all the phases and the transitions between them are clearly visible.

For each of the processes you can define a set of roles. Roles allow you to determine who should be able to perform actions in a given state. Workbox will visualize which roles have permissions for which actions and states.

For each of the processes you can define a set of roles. Roles allow you to determine who should be able to perform actions in a given state. Workbox will visualize which roles have permissions for which actions and states.

Workbox utilizes standard SharePoint permissions. Assigning users to roles, domain groups or SharePoint groups is both easy and intuitive. The possibility to exclude users from roles further extends the functionality.

Workbox can perform many automatic tasks during transition of the process phase (state change). Users can easily define a sequence of operations – like sending an e-mail, item change or granting permissions – that will automate the process.

Workbox allows you to use data from various sources. Advanced data linking mechanism allows you to retrieve data from virtually every place in the SharePoint environment. It also allows you to connect to external sources (e.g. an SQL database). This data could then be used, for instance, in conditions, as element field values, e-mail message…

Using a workflow is very simple. During a process, user makes a decision and selects a desired action from an item’s context menu or an item’s details form.

Before launching an action, user can be requested to provide some information, which then could be used in the workflow. This is done through action launch forms, displayed prior to action launch. The forms are designed to look like standard SharePoint forms, but are highly customizable and provided with a set of validation mechanisms.

Designing an action launch form is a simple task. After setting the form header and footer (where you can use lookup data, HTML code and even JavaScript functions), you simply assign a set of variables in which the data will be stored. For each variable a new form field will be generated.

You can set a field type you’d like to use, for instance a Yes/no field for binary values. Each field type has a set of attributes, where you can provide things like the field’s default value, decide whether the field is to be required, what values it should accept, etc.

Information about the current process’ state is shown as a standard SharePoint column. This makes it possible to group, sort or filter items by state.

Detailed information about the workflow is located on the workflow history view. Here you can learn who and when launched which action and with what parameters, what data were used in the process, check the flow’s duration time and find where the workflow was idle longest. It also gives you insight into eventual errors and warnings that appeared in the process.