Post Data Ingestion Workflow description

Roles

The following roles are assigned during this workflow:

• Owner
• Technical Steward

Workflow initiator

The process starts automatically when a schema asset is added to the Business Analyst Community.

Workflow status transformations

No status transformations happen within this process.

Post Data Ingestion Workflow walk-through

Diagram

Preliminary checks

When you trigger a new ingestion, the workflow checks if the newly created asset is a Schema asset type and belongs to the Physical Data Dictionary domain of the Schemas community. If not, the workflow ends.

If an owner has been defined, the workflow checks if it is the same user who started the ingestion. If there is no owner defined, the workflow ends.

Ownership

If the owner is not the same user who started the ingestion, the proposed user for this role is presented with a task to accept reject or reassign ownership.

When the user accepts or the owner is the same as the user who started the ingestion, the workflow moves to assigning a technical steward.

If the proposed owner refuses, the user who started the ingestion is presented with a task to propose a new owner and this step of the process is repeated.

When refusing ownership, the proposed owner can also directly propose a new owner who must accept, reject or reassign ownership.

Technical steward

After accepting ownership, the owner is presented with a task to assign a technical steward.

The technical steward is informed about the assignment and reminded to set additional attributes.

Post Data Ingestion Workflow configuration

Access the workflow configuration via Settings → Workflows → Definitions → Post Data Ingestion Workflow.

Description

This workflow is triggered each time a new datasource is ingested in order to set up the correct rights and roles over the created assets. Te permission are inherited by all assets contained in this schema, unless otherwise specified in the Applies to section.

Applies to

This workflow definition applies to the Schema asset types from the Schemas domain in the Business Analysts Community.

Configuration variables

You can edit the configuration variables directly from the workflow definition page by clicking in the upper-right corner of the variables table.

The available configuration variables are automatically generated. For more information about user task generated variables, see General workflow settings.

Start label

The start label is the name of the workflow when it is visible as a button on a resource page or in the drop-down list when you add it as a button on a dashboard. You can find the Start Label section in the upper-right corner of the workflow definition page.

Default value: Post Data Ingestion Workflow

Click Edit to edit the label.

Start event

A start event is an event that triggers the workflow, for example starting the workflow when an asset is created.

The workflow starts when an asset that matches the Applies to restrictions is added to the glossary.

Roles

The roles define the permissions to manage the workflow. For example, if a certain tasks must be urgently executed but the responsible person is on sick leave, a user with the defined role can reassign that task to somebody else.

Action	Roles
Start workflow The button with the start label is available to users with these roles.	There is no packaged default value.
Stop workflow The option to cancel the workflow is available to users with these roles.	There is no packaged default value.
Reassign tasks The option to reassign the task is available to users with these roles.	There is no packaged default value.

Other

The settings in this section define global restrictions that apply to the workflow such as:

• Accessibility to guest or logged in users.
• Checking that the roles required by the workflow are not empty.
• Preventing the same worflow or other workflows from running on the same resource.
• Making the workflow available to be added to a dashboard.

Setting	Enabled
Any guest user can start the workflow.	No
Any signed in user can start the workflow.	No
Perform candidate user check on workflow start.	Yes
This workflow can only run once at the same time on a specific resource.	Yes
Lock resource.	No
Show in global create.	No