Show only results for:


WorkFlowSystem is a server based module for UniversalPlantViewer (UPV) to improve collaboration in teams when working with the UPV by providing a shared platform.

The main features include handling changes done in the UPV and serve them for the different team members.

Functional description

Workflow overview

A list of all workflows visible to the currently logged in user:

Grid states: Users can manage their own grid settings for future reuse.

The browser automatically holds the last grid configuration and reloads it the next time the site is accessed.


Views are a way of filtering the activities based on a predefined set of conditions.

New views can only be created by the administrator.


Templates define the properties of a workflow type.

The WorkFlowSystem comes with a predefined set of workflow types. Administrators can customize and add new templates.


Workflows are organized in a plant/project structure.

Each entry can be assigned a “UPV Model Url” for the models location which will then be automatically be opened when accessing UPV data in a workflow.

This assignment also controls the list of available plants/projects when using the WFS inside the UPV.

Access control

The access to activities is based on user groups associated to the plants/projects structure.

There are four different access levels, each including the rights of the preceding level:

Setting Description
None Workflows are hidden to the user
Limited Read

Only basic information of the workflow is shared (Name/Stakeholders)

Further details are prohibited

Full Read All details of the workflow can be accessed
Read/Write Allows changing the workflow

Users get assigned to groups.

The groups are assigned to the respective plants and projects including the selected access level.

Users only gain access to the workflows assigned to a plant/project if at least one access level is set.

Admin accounts get full access to everything.

Access control – Codelist permission

In addition to the additive user group access setting it is possible to prohibit the access to workflows based on a code list for a more fine-grained access control.

When using this feature only user groups with the explicit assignment will be able to see the affected workflows.


Only a Project Manager will be able to see workflows with status “New”.



Access control


Templates are defined by XML notation making it possible to control the generated input form. The demo dataset includes multiple samples.

Supported input field types:

Type Description
Text Free text
Integer Full numbers
Decimal Floating point numbers
Date Date (excluding time of day)
CodeList Dropdown using a separately managed list of options
The attribute “codeListId” is used as reference

A field can be modified with attribute “translate” for referencing the translation key used in the user interface.

All input field types can be combined with following modifiers as child element:

Type Description
Required Forces a value to be set.
Hidden Hides field in user interface.
DefaultValue Set a predefined value on workflow creation in user interface.
Synthax: ValueUsedAsDefault Synthax for CodeList

There are multiple new features planned for the template system:

  • Email notifications - f.e. when a field changes to a specific value.
  • Further validation options - f.e. allowed value range for type Integer.
  • More supported types.
  • Grouping of fields in the user interface.


Views are in Odata notation and bind directly to the database structure.

Odata is an open standard. You can find further information on building queries f.e. here: