Use Workflows

You can define controls for creating and modifying objects in Axon using a workflow. A workflow is a series of predetermined steps that a SuperAdmin can define for creating or modifying an object.

A workflow ensures that the right people have the opportunity to provide input, challenge, and approve matters related to the object that is created or modified. At each step in the workflow, Axon notifies the stakeholders that they must make a decision about the object. If the workflow for a change request requires the role of approvers at various stages of the lifecycle, the approvers must approve or reject the object for the workflow to move to the next stage.

The series of steps in a workflow ensure that objects are created in Axon according to the data governance principles in your organization. Only users with the proper role and access can create or modify Axon objects. The workflows available for a change request might vary depending on the facets.

Axon includes a Business Process Model and Notation (BPMN) 2.0 workflow component to support data governance and change control functionality.

You can create default and custom workflows in Axon. A SuperAdmin user can define a default workflow for a facet, and the workflow applies to all the objects in the facet. Apart from the default workflows that the SuperAdmin has configured, an object stakeholder can define a custom workflow for a specific object within a facet.

Stakeholders in a Workflow

The stakeholders that can participate in a workflow depend on the object facet that a user wants to modify.

Facet Stakeholders

The roles that the administrator has configured for a facet become the workflow stakeholders for the facet objects. For example, if the SuperAdmin user has configured the Project Manager and Project Steward roles for the Project facet, then users that have the Project Manager or Project Steward responsibilities can participate in workflows to create or modify Project objects.

When a user raises a change request for an object, you can see the stakeholders of the change request in the following locations:

To create stakeholder roles for a facet, see the Axon Data Governance 7.2.1 Administrator Guide.

Requestor

Any user in the organization, including users that are not stakeholders for a facet, can raise a change request to create or modify an object. Such a user is called a Requestor. In addition to the facet stakeholders, you can add the Requestor as a stakeholder in the swimlanes of a workflow.

To see the Requestor of a change request, go to the Change Request facet and see the Created By field in the Summary tab.

Note: A change request can have only one Requestor person. After a change request is raised by a Requestor, you cannot choose another person as the Requestor.