Workflows: Analysis

Introduction

This document is the outcome of the analysis workflow – workshop with the customer. By completing this document, a workflow can be created. In that case, the developer shouldn’t be necessary for the person who was attending the workshop.

3 Workflows Configuration

Description

Name: <fill in the name of workflow>

Diagram: <In case available a design document can be added, an example has been added below. Please replace this diagram with the actual diagram>

Description: <a detailed functional explanation of the workflow, step by step >

#

Element of process Detail
<use same names as defined in diagram> <Explain the expectations of the step in detai>

Reference to use case

<Please tell in detail the reference to the use case. This can be a ticket number or a description of the usecase>

Workflow applies to

Asset

In case the workflow is based on an asset (resource workflow), you can fill in the restrictions for which asset the workflow will be applicable.

#

Asset type Domain/community Status
<asset type restriction> <domain or community restriction> <status restriction>

Community

No further restrictions can be added in case the workflow is applicable to a community. (resource workflow),

Domain

In case the workflow is based on a domain (resource workflow), you can fill in the restrictions for which asset the workflow will be applicable.

#

domain type Community
<domain type restriction> <community restriction>

4.4 Global

In case the workflow is NOT based on any resource, we have a global workflow. In this case, there are no restrictions on the applicable workflow.

General Settings

Please define the general settings in the table below.

# Setting Variable
1 Start Label <how the workflow will be displayed in DGC>
2 What event(s) start the workflow? <Choose start events for this workflow>
3 What status transformations happen in this workflow? <Choose start events for this workflow>
4 Who can Start the workflow? <role(s)> 
5 Who can Stop the workflow? <role(s)> 
6 Who can reassign the task? <role(s)> 
7 Any guest user can start the workflow? <Yes/No>
8 Any signed in user can start the workflow? <Yes/No>
9 Perform candidate user check on workflow start <Yes/No>
10 This workflow can only run once at the same time on a specific resource <Yes/No>
11 Lock Resource <Yes/No>
12 Show in global create <Yes/No>

Variables

Some parameters are mandatory to startup the workflow. Please specify them below.

# Variable Name Value Description
<name of the variable> <value of the variable> <clearly explain the use of this variable>

Workflow impact on Operating Model

This section describes the general Operating Model characteristics which are relevant for designed workflows and is created to help to set up workflows and understand dependencies and impact.

There are no explicit changes to the Operating Model by designed workflows. However, workflows are configured to be executed within defined and described below Roles, Asset Types, Asset Statuses, and Communities.

Community

Explain which community can have any impact on the new workflow. (eg. Workflow can only run if community A exists)

# Community Name Description
1 <potential impacted community name or description of that community> <description of the impact on the specified community>

Domain

Explain which domain can have any impact on the new workflow. (eg. Workflow can only run if community A exists)

# Domain Name Description
<potential impacted domain name or description of that domain> <description of the impact on the specified domain>

Assets

Please refer to “Table 2 – applies to Asset Types” for the information of the asset type used in these workflows. The developed workflows will be tested with the corresponding asset types, and the impact of the workflow on those asset types will be verified.

Attribute Types

Specify customized attribute types that are needed to run the workflow.

# Attribute Name Type
<name of the attribute> <type of the attribute>

Relation Types

Specify customized relation types that are needed to run the workflow.

# Relation Head Role Corole Relation Tail
<name of the head asset type> <name of the role> <name of the co role> <name of the tail asset type>

Status Types

Specify customized status types that are needed to run the workflow.

# Status Assigned to Asset
<name of the status> <related asset type>

Roles (Resource and Global)

Define which roles are required and should exist and be configured for workflows to work properly.

# Role Comments (purpose)
<name of the role> <what a user with this role means in the workflow>

Workflow Notification email templates

The table below described the email templates that are used in the workflow to notify workflow participants.

# Template Name Description
<template name> <when will this email be sent, which details are in this email,…>

 Useful links:

You have to login to comment.