Workflows in HoriZZon help users to collaborate on model packages. HoriZZon has one built-in workflow that is predefined by BiZZdesign, but also supports custom workflows, which you can define yourself. Workflow requests can be made for diagrams, views, objects and relations in a model.
Types of workflows
Default workflow "Change request"
The default workflow "Change request" is predefined by BiZZdesign and addresses a common collaboration pattern in a modeling context. This default workflow cannot be updated or deleted, you can only change its code and icon if desired.
A change request allows a user to request an implementation of a modification of a model, through an implementer. Once the implementer has performed the modification and completes the change task, the flow terminates. In case of a rejection, a new task is assigned to the requester. The requester can decide to withdraw the request or to provide additional information and reopen the request (revise), which results in the assignment of a new change task to the implementer. The change request workflow is illustrated with a BPMN process in the figure below.
HoriZZon also supports the use of custom workflows. If your organization has its own workflows that you want to use in HoriZZon, you can create workflows definitions in Enterprise Studio and upload them to HoriZZon. In a workflow definition the data, participants and order of the workflow process are determined.
Workflow definitions can be created using the BPMN template model "Empty model with workflow diagram". In this template model the following diagram types are available to specify the different aspects for a custom workflow:
- Process diagram for defining the order of the process
- Forms diagram and Metadata diagram for defining the data in the process ("what is the workflow about?")
- Resources diagram for defining the people in the process
Example of the components of a workflow definition
Required roles for working on workflows
Working on workflows requires specific roles for the users to be able to perform the operations.
|Starting workflow requests based on the default workflow||Consumer, Contributor, Designer, or Lead Designer|
|Starting workflow requests based on a custom workflow||Contributor, Designer, or Lead Designer|
|Performing workflow tasks||Contributor, Designer, or Lead Designer|
|Terminating workflow requests|
Contributor, Designer or Lead Designer (only own requests)
Administrator or System Administrator (all requests)
|Managing workflows (editing, deleting)||Lead Designer, Administrator or System Administrator|
|Creating custom workflows (definitions) in Enterprise Studio||Designer or Lead Designer|
|Uploading custom workflows to HoriZZon||Lead Designer|