Sap Signavio Process Manager User Guide en
Sap Signavio Process Manager User Guide en
2024-03-22
2 Signing up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 What kind of SAP Signavio user am I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2 The BPM Academic Initiative. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3 Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6 Explorer overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1 The Explorer menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.2 The Explorer view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.3 Viewing diagram details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
6.4 Working with folders and diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7 Navigation Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8 Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1 Create a diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.2 Editor Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.3 Open and Save Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
8.4 Editor toolbar and keyboard shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
8.5 Add and connect elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
8.6 Move and change elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.7 Format diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.8 Work with modeling conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8.9 Process hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.10 Create subprocesses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.11 Add Live Insights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
8.12 Add links to SAP Signavio Process Insights content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8.13 Link to files in diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
8.14 Display attribute overlays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
8.15 Compare revisions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
8.16 Custom graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
10 The dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
10.1 Working with the dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
10.2 Use the dictionary while modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Overwrite dictionary entries locally. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
10.3 Merging dictionary entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
10.4 Referencing external data sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
10.5 Recommendations: Dictionary Content Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
10.6 Tutorial: How to use the dictionary as a modeler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
14 Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
15 Collaboration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
15.1 Invite Modelers to Edit a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
15.2 Inviting Stakeholders to Comment on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
15.3 Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268
15.4 Granting Read-Only Access to Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
15.5 Publishing Diagrams in SAP Signavio Process Collaboration Hub. . . . . . . . . . . . . . . . . . . . . . . . . . 272
15.6 Inviting Users to Access a Diagram in SAP Signavio Process Collaboration Hub. . . . . . . . . . . . . . . .276
15.7 Organizing Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
15.8 The Notification and Activity Feed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
15.9 Translating Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
15.10 Executing Processes in SAP Signavio Process Governance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
15.11 Working with Approval Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
16 Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
16.1 Generating Process Documentation Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
18 Importing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
18.1 Import an SAP Signavio Archive (SGX) File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
18.2 Import a BPMN 2.0 XML Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
18.3 Import the APQC Process Classification Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
18.4 Importing an ARIS Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
18.5 Import a Microsoft Visio Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
18.6 Upload Documents and Pictures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
18.7 Import Dictionary Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
18.8 Import a Set of Dictionary Items as a JAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
19 Exporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
19.1 Export Dictionary Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326
19.2 Export a Diagram as PDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
19.3 Export a Diagram as an Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
19.4 Export a Diagram as a SAP Signavio Archive (SGX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
19.5 Export a BPMN Diagram as XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
19.6 Export a Diagram as XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
19.7 Export a DMN Diagram as XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
19.8 Export DMN Diagrams as Drools Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
19.9 Exporting Diagrams to Red Hat Decision Manager Projects on GitHub. . . . . . . . . . . . . . . . . . . . . . 337
19.10 Translate Content with PO Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
If you are new to SAP Signavio, we recommend to read the sections First steps with SAP Signavio Process
Manager [page 11] and What kind of SAP Signavio user am I? [page 13].
If you are already familiar with SAP Signavio Process Manager, navigate the table of content on the left or use
the search to find the sections that are most relevant to you.
• Featured Videos
• Tutorial Videos
• SAP Signavio Blog
• White Papers
• SAP community page for SAP Signavio
Learn how to create and access your SAP Signavio Process Transformation Suite account.
SAP Signavio is a web-based application. Use your existing account email and password to log in to the SAP
Signavio Process Transformation Suite [page 9].
• If you need to register for the software at https://www.signavio.com , choose (more options) and
Free Trial.
• If you received an invitation email to the SAP Signavio software, select the link in the email to get to the
page.
• If you are using the On Premise version of SAP Signavio, get the local URL from your workspace
administrator.
Note
• The email address you use to sign up cannot contain the German umlauts (such as ä, ö, ü) as special
characters.
• If you register for a trial account with an email address that has been invited to join a SAP Signavio
workspace, this license will be automatically added to your new account.
• When you receive an invitation email, use this same email address to sign up with the proper license.
Browser Compatibility
SAP Signavio supports all popular browsers. For a detailed description of the supported browsers, see Browser
Compatibility.
After you've created your SAP Signavio Process Transformation Suite account (see section Create your SAP
Signavio Process Transformation Suite account [page 8]), use your account email and password to log in.
In case your workspace administrator has created the account for you, you received an email to reset your
password. When SSO is enabled for your workspace, you log in using a shared link (see section Log in using a
shared link [page 10]).
Note
If you don't have the SAP Signavio Process Transformation Suite license, SAP Signavio Process
Manager explorer or SAP Signavio Process Collaboration Hub opens, depending on your user license.
When SSO is enabled for your workspace, you log in through a shared link. The link is shared with you, for
example, in an invitation email or on a Wiki page.
Note
We recommend that you bookmark the shared link for future logins. Depending on your workspace
configuration, you might only be able to log in to the SAP Signavio Process Transformation Suite through
the shared link.
When SSO is enabled for your workspace, you log in through a shared link. The link is shared with you, for
example, in an invitation email or on a Wiki page.
1. Go to the local URL or select the shared link to open the login page. You can get the local URL from your
workspace administrator.
2. Enter your account email and password and choose Login. SAP Signavio Process Manager explorer opens.
Related Information
This chapter provides an overview of the features of SAP Signavio Process Manager.
The Explorer
After logging in, the explorer opens in your browser. It allows you to navigate through diagrams and files stored
in your workspace. Here you can create new diagrams and publish them in SAP Signavio Process Collaboration
Hub or share them by other means. As SAP Signavio supports open standards, importing diagrams from
other systems is easy. In the explorer, you can adjust your personal settings. Administrators can also configure
workspace settings here. For details, see Explorer overview [page 20].
The Editor
The editor can be accessed by opening a diagram or creating a new one. Using the editor, you can create and
edit all kinds of supported diagrams. For details, see section Modeling [page 35].
Besides BPMN 2.0, SAP Signavio supports Decision Model and Notation (DMN) [page 140] , ArchiMate, and
many Further notations [page 226].
QuickModel
QuickModel gives you the possibility to create simple BPMN-diagrams in seconds by use of a spreadsheet-like
interface. Diagrams created in this application can be edited in the editor like any other diagram to add
complexity or update the process. See section Modeling with QuickModel [page 228] for details.
The Dictionary
The dictionary [page 83] allows you to manage and re-use specific modeling elements. It also allows you
to ensure all your modelers are using the same terms and elements in your organization-specific modeling
environment.
The launchpad of SAP Signavio Process Collaboration Hub provides access to your published process
landscape, see section Your launchpad.
The diagram and revision comparison tool helps you to keep track of changes. See section Comparing revisions
[page 66] for details.
You can run BPMN Simulation and DMN simulation to analyze key performance indicators and bottlenecks
and apply your business decision logic directly within the tool. The DMN Test lab [page 186] helps you to
continuously check whether your decision logic is consistent with your initial requirements. See sections
BPMN Simulation [page 236] and DMN simulation [page 198] for details.
Support
Our team is constantly improving and extending SAP Signavio Process Manager. You will find the latest version
number and our release notes at https://www.signavio.com/release-notes/ .
Please contact our SAP Signavio service experts from the SAP for Me portal .
You can also send a support request from the editor. Go to the user menu and select Send feedback from the
drop-down list.
Related Information
The following sections explain the different user types of SAP Signavio Process Manager. If you already know in
what way you would like to use the software, you can select the topic that is relevant for you.
Learn how to collaboratively model business processes in BPMN (Business Process Model and Notation) or EPC
(Event-driven Process Chains) with SAP Signavio Process Manager. In addition to BPMN and EPC, we support
all popular open modeling languages for business users.
In section Business Process Modeling and Notation (BPMN) [page 205], you learn how to create, edit, and work
with BPMN diagrams.
Use the Decision Manager to model business decisions in a structured and formalized manner all stakeholders
can easily understand using the Decision Model and Notation (DMN) . Integrate your DMN diagrams
seamlessly into your BPMN process landscape.
In the section Decision Model and Notation (DMN) [page 140], you learn about creating, editing and managing
decision diagrams.
Use the ArchiMate Edition to create a visual, business domain-crossing description of your enterprise
architecture. Employ ArchiMate together with your BPMN process landscape.
In the section ArchiMate, you learn about creating and editing Enterprise Architecture diagrams.
I'd like to create a process diagram, but don't know BPMN very well
Learn how to use the QuickModel to create valid BPMN processes through a spreadsheet-like interface.
Create your first processes in just a couple of minutes or add and maintain element attributes in a fast and
well-structured manner.
In the section QuickModel [page 228], you learn how to use the application to quickly create BPMN diagrams.
Get to know SAP Signavio Process Collaboration Hub: view process diagrams and discuss them with your
colleagues.
In the section Your launchpad, you learn how to use the tool to work on diagrams together with colleagues and
external stakeholders.
Make use of a Approval Workflows to ensure that diagrams have been approved by specific users or user
groups before they are published in SAP Signavio Process Collaboration Hub.
In the section Approval workflows [page 288], you learn how to start and work with approval workflows.
I am a workspace administrator
Learn how to configure your workspace in order to get the most out of SAP Signavio Process Manager and to
maximize the benefit considering the unique needs of your organization.
Moreover, learn how to integrate SAP Signavio products into your organization's IT infrastructure and enable
smooth and hassle-free process, business decision and enterprise architecture documentation, utilizing your
existing IT systems to the fullest extent.
As a workspace administrator, you will find information about configuring the software in the Workspace
administration section of the manual.
The BPM Academic Initiative is a joint program of SAP Signavio and several international universities
to support business process management in academic teaching and research. As part of the Academic
Initiative, SAP Signavio allows students and teachers to use the academic process modeling platform at
academic.signavio.com for free, given the purpose is non-commercial and non-productive.
Note the following differences between SAP Signavio's academic platform and the commercial offering:
If you accidentally registered for the Academic Initiative at academic.signavio.com , please create a new
account for one of the following systems:
If you want to transfer your data from the academic platform to one of our production systems, please contact
our SAP Signavio service experts from the SAP for Me portal .
The fastest option is to use the diagram preview (see section Viewing diagram details [page 26]). Select a
diagram in the Explorer and hit the space bar or use the arrow symbol at the bottom left of the main window to
expand the preview section.
Preview in SAP Signavio Process Collaboration Hub allows you to quickly navigate the diagrams of your
workspace. To open the preview, open the explorer and select Share - Preview in SAP Signavio Process
Collaboration Hub.
By default, the system informs you about every change made to a diagram you are working on in a team. There
are multiple ways to disable notifications:
• Select the diagram in the explorer, open the activity feed (with the space bar) and choose Don't notify me.
• Open your profile settings under Setup - My profile in the Explorer and scroll down to the notification
settings to adjust them.
• Please ensure your browser supports SAP Signavio. Read more in section Log in to the SAP Signavio
Process Transformation Suite [page 9].
• After a system update, in rare cases it is necessary to refresh the internal storage (cache) of your browser.
For this, open the application in your browser and use one of the following commands (depending on your
operating system):
• Windows: Ctrl + F5
• Apple: Cmd + R
• Linux (typically): F5
You can use personal profile settings to customize SAP Signavio Process Manager according to your needs.
Profile settings are centrally managed in the My profile dialog, which can be accessed via Setup - My profile.
In the 'My profile' dialog you can customize your user profile
Note
If you have registered multiple workspaces with the same email address, the settings for password,
language and user name apply globally for all workspaces. The settings or information about licenses,
groups, tips, and subscriptions apply to the current workspace.
Global settings
Global settings apply to all the workspaces you are registered with.
Parameter Description
Academic title, first name, last name These three fields make up your user name. It appears
whenever you interact with the software or a colleague, like
in diagram version histories in the activity feed or when you
invite someone to collaborate. Changes in the user name are
only displayed after reloading the page.
Email The email address you are registered with at SAP Signavio
Process Manager. You will get notifications from the SAP
Signavio software to this address if you have subscriptions.
Language Here you can specify the language for your personal profile.
After clicking Save, the page will be reloaded in the selected
language.
Local settings and information apply only to the workspace you are currently working in.
Parameter Description
Edition This entry tells you what SAP Signavio licenses you are reg-
istered for. If you need additional licenses, please contact
your administrator.
Groups The user groups you are a member of are listed here. Ad-
ministrators can add and delete users to user groups as
explained at Manage users and groups.
Display today's top tip automatically Activate the checkbox if you would like to see a new tip every
day after login.
Subscriptions All your subscriptions are listed here. You can delete those
that are no longer needed by clicking Remove. By default,
new users are automatically subscribed to weekly email up-
dates about changes to the 'Shared documents' folder.
Today's top tip is displayed every day when you first open the Explorer.
You can deactivate the automatic display of tips in your profile settings.
The explorer is the entry and management point of SAP Signavio Process Manager. In the explorer you can
manage folders and diagrams, create new diagrams, export diagrams, generate reports, as well as publish
and embed diagrams. You can also edit your profile settings and manage the administrative aspects of your
workspace. You can access the editor, SAP Signavio Process Collaboration Hub and other functions in the
software via the explorer.
From the explorer view you have access to all tools that SAP Signavio Process Manager offers.
• View
The central area Double-click diagrams in the editor to open them. Unread diagram comments are
displays the file displayed as small speech bubbles attached to the corresponding files. You can
contents of the switch between the views, The icon view [page 24] or The list view [page 24].
selected folder. At the bottom of the central view is the activity feed and the diagram preview.
• Menu
The toolbar with a drop-down menu allows you to access different functions. Read more in the section The
Explorer menu [page 21].
• Search function
The search function is a useful tool to quickly find diagrams. In addition to the full text search, the
advanced search option offers you a method to add specific search criteria. You can find a detailed
description in the Search functions [page 259] section.
• Folder tree
The folder tree on the left allows you to quickly navigate within your workspace. Read more at Working with
folders and diagrams [page 28].
• Diagram details
The notification and activity feed allows you to view and manage the history of a diagram and to modify
notification settings of diagrams and folders. By pressing the space bar you can open the preview panel
(see Viewing diagram details [page 26]) and the version overview (see The notification and activity feed
[page 277]) of a diagram at the bottom.
• Personal profile
You can customize the explorer by adjusting your Personal profile settings [page 17] according to your
needs.
New
In the dropdown menu New, you can create new folders and diagrams. The new folder is created at the location
that is currently open in the explorer. If you create a new diagram, a blank canvas opens in the editor in a new
tab. The menu item QuickModel opens a new BPMN 2.0 diagram in QuickModel.
Edit
Here, you can open the editor or QuickModel to edit diagrams, simulate BPMN (see BPMN Simulation [page
236]) and DMN (see DMN simulation [page 198]) diagrams and test DMN diagrams (The DMN Test lab [page
186]). To gain an overview of activities about a specific diagram you can display comments on diagrams in
SAP Signavio Process Collaboration Hub and compare versions of diagrams (see Comparison [page 66]).
The folder content currently displayed in the explorer can be moved, copied, deleted, and renamed. BPMN 1.2
diagrams can also be migrated to the newer BPMN 2.0 format.
Import/Export
You can import and export files in SAP Signavio Process Manager. This means you are able to upload files to
your workspace and also download diagrams from your workspace onto your computer in different formats.
The Reporting menu allows you to create different kinds of reports about diagrams. This enables you as a
business user to analyze your process hierarchy offline with decision makers and analysts, regardless of your
familiarity with BPMN modeling.
To view and export reports analyzing your workspace and process model usage, see section Process Model
Dashboards.
Share
With the Share menu, you can use your Shared Documents folder to publish diagrams to SAP Signavio Process
Collaboration Hub and share documents in a variety of ways with your colleagues.
Approval workflows
Approval workflows [page 288] are evaluating processes that diagrams have to go through before they are
automatically published to SAP Signavio Process Collaboration Hub. You can start approval workflows as
well as edit published diagrams. Approval workflows are managed and executed in SAP Signavio Process
Governance. If you are interested in further functionalities of SAP Signavio Process Governance, you can get
more information here: https://www.signavio.com/products/workflow-accelerator/ .
Invitations to comment/edit
The second section of the menu lets you invite modelers to edit. You can also use it to invite SAP Signavio
Process Collaboration Hub users and external stakeholders to comment on diagrams.
Invite to comment
You can invite anyone to comment on a diagram - all you need is their email address. They will receive an email
with a link that leads directly to the corresponding diagram in the commenting view. Unregistered users can
view and comment only on the specific diagrams they were invited to.
The menu item Manage feedback invitations lets you revoke any invitations to comment on a diagram.
You can invite modelers registered in your workspace to edit a diagram. As all modelers are able to edit all
diagrams in the Shared documents folder by default, this function serves as notification to let fellow modelers
The option to Invite to fill out QuickModel follows the same basic concept, only instead of the Editor, the link
leads to the diagram in QuickModel [page 228].
In this menu section, you can view approval workflows, view diagrams in SAP Signavio Process Collaboration
Hub, publish and unpublish diagrams, and invite users to open diagrams.
Preview
SAP Signavio Process Collaboration Hub offers a structured and detailed overview on diagrams. Before
publication, you can check how a SAP Signavio Process Collaboration Hub user would see the diagram. This
option can also be useful for modelers who need to to become familiar with complex diagrams before editing
them. Also, SAP Signavio Process Collaboration Hub provides a full screen view for diagrams.
Publish
You can select one or several diagrams or folders and publish them (see Publishing diagrams in SAP Signavio
Process Collaboration Hub [page 272]). The corresponding diagrams will be visible for all users in the folder
tree. They will not be accessible for colleagues who have been invited to comment on a specific diagram by
email but do not possess a SAP Signavio account.
Unpublish
You can use this option to remove a diagram from the folder tree. This option has no influence on feedback
invitations. If you would like to revoke those as well, please click on the menu item Manage feedback Invitations
and remove the corresponding e-mail addresses from the list.
If you click this option, you can send an invitation to any e-mail address.
With the dialog that opens, you can embed the corresponding diagram into external systems (see Embedding
diagrams in external systems [page 341]).
In this view, diagrams and folders are represented as icons. For diagrams, a small preview is provided that
allows you to find the diagram you are looking for faster.
Details about a selected diagram can be found at the bottom of the Explorer in the activity panel (see Viewing
diagram details [page 26]) .
When working on diagrams collaboratively--for example, in SAP Signavio Process Collaboration Hub--it is
possible to comment on diagrams and diagram elements. Unread comments that were created by users who
are not members of your workspace will be marked with a little speech bubble symbol in the Explorer.
To view your colleagues' comments, open the respective diagram in the Editor. To read more about
commenting, go to section Comments [page 268].
Diagrams and folders are listed along with additional information about each file. Selecting an element
activates the diagram preview in the preview panel at the bottom if the panel is extended.
Clicking the title of a row sorts the elements by the selected column.
You can individually configure which of the diagram attributes are shown as columns in the table view. All
attributes on diagram level and the attributes Revision , Last Change , Last Author and Published are
available.
1. Click Setup , then Edit general configuration . A dialog box will open.
2. In the Explorer section, you can edit the table columns preferences. Click Add attribute to add another
attribute to the list view.
You can rearrange the order of the attributes using the arrow icons and configure the size and the position
of the attribute column. To delete an attribute from the list view click the trash button.
3. Click Save to save your settings. The list view is updated with the attributes you have configured.
After saving a diagram in the editor (after renaming it, for example), the explorer view may not be up-to-date
anymore. In this case, a dialog is asking you to refresh.
In both the list and in the icon view, you see the file path on top of the list. If you want to jump to a parent folder,
click the corresponding folder name.
The following example shows how to jump back to the 'Shared documents' folder:
The notification and activity feed allows you to view and manage version history, and to edit notification
settings for diagrams and folders. If you have selected one or more diagrams or folders, the feed is displayed as
Notification settings
As soon as changes to a diagram or folder are made, notifications are sent at configurable intervals as emails.
In the notification and activity feed, you can configure the notification settings of the selected diagrams or
folder.
• daily
• weekly
• monthly
• cancel subscription
The activity feed allows you to get a preview of the selected diagram and to view and manage the version
history. You can find detailed information about this feature in the section The notification and activity feed
[page 277].
Folders allow you to organize and structure your workspace, even if you have a large number of diagrams.
Diagrams placed in Shared documents can be viewed and edited by all users of a workspace. Workspace
administrators can enable the My documents folder, which is private. Other users can't view or edit this folder.
Notes on working with multiple users and workspaces can be found in the Managing users and access rights
section.
The main workspace folder is Shared documents. The My documents folder can additionally be enabled by a
workspace admin.
Within these folders, you can create subfolders to organize your diagrams.
Clicking the arrow next to the folder/s name or on folder/s name itself will collapse or extend the folder. This
way, you can quickly switch between folders and still keep track, even if you have an extensive folder structure.
If the name of a folder is cut off due to the width of the folder column, the full name will appear when hovering
over it with your mouse. You can also extend the folder column by dragging its border line to the right.
Note
Workspace administrators can choose to disable the My documents folder for every user in the workspace.
This prevents documents from being inaccessible. It also fosters collaboration by restricting drafts to
Shared documents. For new tenants, the folder My documents is disabled by default. The folder can be
enabled by an administrator under Setup > Edit general configuration.
Shared documents
This folder contains diagrams you can work on alone and together with other modelers.
There are two ways to collaborate with colleagues: joint modeling within your workspace, and inviting
colleagues to comment on diagrams.
• Only colleagues who are registered in your workspace are able to actually edit diagrams. Find out more
about defining access rights to diagrams and the Dictionary at Managing access rights.
• Each person invited to comment on a diagram is able to do so - also those who have no SAP Signavio
Process Manager account. In the section Inviting process stakeholders to comment on a diagram [page
263], you will learn how to invite process stakeholders to comment on a diagram.
My documents
Workspace administrators can enable the My documents folder for all users under Setup > Edit general
configuration. Diagrams in this folder and its subfolders are private. Other users can't view or edit them.
1. If you want to create a subfolder, first navigate to the folder in which you want to locate the new folder.
2. In the menu bar, click New > Folder . A dialog pops up, in which you can enter the folder name.
Note
To move published folders and diagrams, you need publish access rights on the published elements and on
the target folder.
5. Finally, click Move . The folder or diagram is moved to the selected location.
Copying diagrams
Note
You can only copy diagrams and groups of diagrams, not entire folders.
1. Select the diagram you want to copy. To copy several diagrams at once, hold the Ctrl key while selecting
them. Or, draw a selection frame around the diagrams.
2. In the menu bar, click Edit and then Copy . The Copy dialog opens.
3. Select which folder you'd like to place the copy in.
4. Optionally, you can select one of the following options by activating the corresponding checkbox:
• Copy linked models, too Please note that BPMN call activities are not copied.
• Copy all revisions of the diagram .
Note
1. Click Copy . The copied file is then located in the selected target folder.
1. Select the folder or diagram to be removed in the main area of the Explorer. To select multiple folders, keep
Ctrl pressed while selecting, or draw a selection frame around them.
2. In the menu bar, click Edit > Delete . A confirmation dialog appears.
3. Click Yes to delete the selected object.
Note
The selected objects are moved only in Trash, from which you can restore objects if necessary. Objects
will be permanently deleted after you empty Trash.
4. To delete objects permanently, select the Trash folder in the folder navigation. All objects in Trash are
displayed.
5. Select the objects you want to delete permanently.
6. In the menu bar, click Remove. A confirmation dialog appears.
7. Confirm by clicking Yes. The selected items are permanently deleted.
Diagrams and folders that have been deleted are moved to Trash folder. If you do not explicitly remove them
from there, they can be restored.
1. Go to the Trash folder. It can be found in the folder tree on the left.
2. Select the files you want to restore.
3. Click Restore in the menu bar.
Discover the actions you can take with the SAP Signavio Process Manager navigation bar at the top of your
view.
Note
This navigation bar displays the label of SAP Signavio Process Manager. This identification of your current
working product is useful if you navigate back and forth between other SAP Signavio products and workspaces.
The navigation bar allows for quick access to common functions across SAP Signavio products. Each product
displays a navigation bar with its own product-specific available icons.
• SAP Signavio logo: Select the logo to navigate back to your current working product's
home page.
• App Switcher: Here you can view the SAP Signavio products to which you can navigate. Your view
reflects the products you are able to access. When you click a product name, the selected product opens in
a new tab.
• User Profile Menu: This icon displays your own initials as the logged-in user. The drop-down menu
offers the following options:
• Workspace: You can check which workspace you are currently using.
• Editing mode: You can select an editing mode such as Simulation or QuickModel. The options depend
on the current notation.
• Logout: Choose this option to log out of SAP Signavio Process Manager.
This section explains how you create models in all notations in SAP Signavio Process Manager in the following
sections:
For information about modeling with specific notations, see section Modeling notations [page 104].
Get an overview of the SAP Signavio Process Manager editor. In the editor, you model BPMN processes, value
chains, DMN diagrams and more.
In SAP Signavio Process Manager, new diagram files are created in the explorer. You edit diagrams in the editor.
To create a new diagram, click New in the explorer and select a modeling notation from the drop-down list. The
editor opens with a blank canvas.
Get an overview of the SAP Signavio Process Manager editor. In the editor, you model BPMN processes, value
chains, DMN diagrams and more.
In the editor, you design, edit and format diagrams. You can also perform checks on your diagrams. This
overview can help you find the functions you need.
Shapes Contains all modeling elements available for a notation. Add elements from the shape reposi-
tory [page 41]
Toolbar Tools to edit and format diagrams Editor toolbar and keyboard shortcuts
[page 38]
Canvas The area on which you design and edit diagrams Move and change elements [page 48]
Attributes Edit attributes of your modeling elements. Edit attributes [page 48]
App Switcher Navigate to other SAP Signavio products that you're allowed Navigation Bar [page 33]
to access.
Help Choose from a list of help resources. Navigation Bar [page 33]
User Profile Menu View the current workspace, change the editing mode, or log Navigation Bar [page 33]
out of SAP Signavio Process Manager.
Learn how to open diagrams in the explorer of SAP Signavio Process Manager, save diagrams, run modeling
convention checks, and restore an older version of a diagram.
In SAP Signavio Process Manager, you open diagrams in the explorer. You edit diagrams in the editor.
Open a Diagram
Save a Diagram
While you keep the editor browser tab open, your changes are saved automatically in the background. When
you save the diagram, you create a new diagram revision.
All items related to a diagram by links are listed when you save a diagram.
4. Depending on the modeling notation, you can open the modeling convention checks by choosing
(Review). This closes the Save dialog.
You can save the diagram with errors and warnings.
5. Choose Save.
A new revision of the diagram is saved.
1. Select a diagram.
2. Choose Expand in the bottom panel of the explorer. Alternately, you can press the space bar.
The panel expands, showing a preview of the diagram.
3. To access previous revisions, choose Feed. The activity feed is displayed.
4. Select the revision you want to restore and choose Restore revision.
5. Add a comment and confirm in the dialog.
The previous revision is restored.
Related Information
Editor Toolbar
Save diagram
Save a copy: You can save the diagram as a copy. The copy is
saved in the same directory as its original.
Undo/ Redo
Bold
Italic
Perform checks
• Syntax check
• Simulation capability
• Cost and resource analysis checks
Keyboard Shortcuts
Open diagram In the explorer, double click the diagram In the explorer, double click the diagram
name name
Open diagram preview In the explorer, select the diagram and In the explorer, select the diagram and
press Space press Space
Zoom Press Ctrl + + to make everything larger Press ⌘ + + to make everything larger
Full-screen Press F11 to use full-screen mode, press Press ⌘ + Ctrl + f to use full-screen
F11 again to exit full-screen mode mode, press ⌘ + Ctrl + f again to exit
full-screen mode
Resize element Hold Ctrl and drag the element connec- Hold ⌘ and drag the element connec-
tor to resize in all directions tor to resize in all directions
Hold Shift and drag the element con- Hold Shift and drag the element con-
nector to resize proportionally nector to resize proportionally
Hold Alt and drag the element connec- Hold Alt and drag the element connec-
tor to resize without snapping tor to resize without snapping
Move elements Hold Alt or Ctrl while moving an ele- Hold Alt or ⌘ while moving an element
ment to move without automatic snap- to move without automatic snapping or
ping or orientation lines orientation lines
Adjust space between elements Press Ctrl + M and add or remove Press ⌘ + M and add or remove space,
space, press Ctrl + M again to deacti- press ⌘ + M again to deactivate
vate
Select elements of the same type Select one or more elements and press Select one or more elements and press
Ctrl + I ⌘+I
Next steps
How to add elements to a diagram from the shape repository or the interactive shortcut menu, pools, lanes,
and gateways. How to connect elements with sequence flows and message flows.
• You can drag elements from the shape repository onto the canvas.
• You can use the interactive shortcut menu when you click an element on the canvas.
• You can copy and paste elements.
The shape repository in the left panel of the editor lists all modeling elements available for a notation. For
notations with lots of elements, elements are grouped into subsets. To change subsets, click the current subset
and select a different subset from the drop-down list.
2. Hold the mouse button and drag the element onto the canvas. Green icons indicate where you can
place an element.
3. To label an element, double-click the element and enter the label text in the text box.
The label is saved when you click outside the text box. Available dictionary entries are suggested while you
type.
Example
Example:
Note
Which elements are shown in the interactive shortcut menu depends on the selected subset of modeling
elements. If you miss an element in the shortcut menu, check which set of modeling elements is selected in
the shape repository.
When you want to add an element and set its position, click the element icon and drag the element to its
position. The new element is added to the diagram where you release the mouse button.
Example
Add a pool by dragging the Pool/Lane element onto the canvas. Collapsed pools can't contain elements.
To add more lanes to a pool, drag a Pool/Lane element onto the left or right edge of a lane.
Example
• Click the header and drag the lane to it's new location.
• Click the header and use the arrow icons that are shown in the lane to move a lane up or down.
Example
To connect elements with flows, drag the flow onto the target element. You can also use the flow icons from the
interactive shortcut menu.
Example
Example
When a connection isn't possible, red marks are displayed on the edges of the element.
When you drag a gateway onto a flow, the flow is split and connected to the gateway.
Copy elements
You can copy elements to create similar elements. You can also copy parts of old diagrams to reuse in new
diagrams.
1. Select the element you want to copy. Hold the Shift or Ctrl key to select multiple elements.
2. Click to copy, click to cut and click to paste elements. You can also use the shortcuts Ctrl +
C to copy, Ctrl + X to cut and Ctrl + V to paste elements.
Note
• Copying elements between different diagrams can take a while, because they are copied to the server
first.
• An internet connection is required for copying elements between diagrams, but not for copying
elements inside one diagram.
Remove elements
1. Select all elements you want to remove. To select multiple elements, press and hold the left mouse button
and draw a frame around the elements, or press and hold the Ctrl key while you click the elements.
How to edit a diagram while you're creating it, change elements while modeling and add space to the canvas
wherever you want. How to change element attributes to adapt modeling elements.
While modeling, you can change the position of elements and labels.
You can also adjust the space between elements or change the canvas size.
Example
Example:
To change the name of a label, double-click the element. Available dictionary entries are suggested
automatically.
Note
For more options, keep one or more of the following keys pressed while you drag the element:
Example
Example:
Note
Shrinking the canvas isn't possible if there are elements in the affected area.
1. Enable the space adjusting function by clicking in the toolbar, or use the shortcut Ctrl + M.
The mouse cursor turns into a cross and two lines are displayed on the canvas.
2. Where you want to adjust the space, click, hold and move the cursor.
Space is added or removed depending on your movements.
Example
Example:
4. Disable the space adjusting function by clicking in the toolbar, or use the shortcut Ctrl + M.
2. Click the inward-pointing arrow to shrink the canvas, click the outward-pointing arrow to expand
the canvas.
Zoom
To view the complete diagram on your screen, use the zoom icons, and .
To return to the standard zoom level and view the diagram in its default size, click .
Note
Changes that affect the appearance and behavior of an element, but not its type, can be made in the
attribute panel. For example, to change a task into a script task, you set the attribute Task type to Skript.
You can change the element type. For example, in BPMN the following transformations are possible:
• task to subprocess
• plain start event to message start event
• collapsed pool to expanded pool
Example:
Edit attributes
Modeling elements have several properties you can edit. These properties are called attributes. You can use
attributes to change the appearance of an element (for example the background color or label). Attributes can
also be necessary to execute a process, for example the decision logic in a DMN diagram is an attribute.
You edit attributes in the attribute panel on the right side of the editor.
Note
The first section of the attribute panel contains custom attributes, which can be defined by your workspace
administrators.
You can change attributes for one element and diagram-wide attributes.
• To select all elements of one type, select one element and press Ctrl + I. All elements of the same type are
selected.
• To select all elements of multiple types, select elements from each type and press Ctrl + I. All elements of
the chosen types are selected.
Example
Example:
Attributes are displayed when diagrams are viewed in SAP Signavio Process Collaboration Hub. Which
attributes are shown for SAP Signavio Process Collaboration Hub users depends on visibility settings for their
user group.
Attributes can be populated from a linked diagram if an attribute with the same ID is available for both the
linking element and the linked diagram. For details, see section Displayed attributes of SAP Signavio Process
Collaboration Hub user guide.
Your workspace administrator can create attributes with the same ID for different elements. The workspace
administrator guide explains how to do that in section Add and manage custom attributes.
Options to align and distribute elements on the canvas and how to change elements so they match your
corporate design.
To add clarity and to customize a diagram, you can re-align and resize elements and change their color, size,
label, border and background style.
Use the alignment menu in the toolbar to align or distribute selected elements.
Select the elements to align or distribute and choose from the following options:
You can change the attribute values of an element in the attribute panel to change its appearance:
• Change the label either by clicking the element or the attribute name.
You can change the labels with the following tools in the toolbar:
1. Select the element that has the format you want to copy.
• To select all elements of one type, select one element and press Ctrl + I. All elements of the same type are
selected.
• To select all elements of multiple types, select elements from each type and press Ctrl + I. All elements of
the chosen types are selected.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
A modeling convention consists of modeling guidelines regarding notation set, labeling, process structure and
diagram layout
With modeling convention checks, you can find out if a diagram violates these guidelines. You can run a check
while modeling or when you save a diagram. Additionally, you can create a modeling conventions report after
a check that contains an summary of the errors. Modeling conventions can be defined by your workspace
administrator.
Elements which violate conventions are flagged with an exclamation mark. To view a short info about the
violation, hover over the exclamation mark. Additionally, the information is summarized in a table below the
process diagram.
In the table, click the element to view it in the diagram. If available, click the link icon for more information
about a guideline.
Example
Example:
You can create a modeling convention report for one or multiple diagrams in the explorer. The report contains a
summary of violations of modeling conventions and is generated as an XLSX file.
Short overview about process hierarchies and the notations you use to create them.
You create process hierarchies to map the processes on all levels of your organization.
With value chain diagrams, you can create high-level perspectives on your process landscape. The diagram
elements are linked in chronological order to show the hierarchical relationships between processes and
process groups. With the collapsed process element, you can link BPMN diagrams to the value chain diagram.
BPMN is used to map the detailed processes. The processes in BPMN diagrams are also showing different
process levels. You create a high-level overview of a main process and in separate diagrams you model
subprocesses. Then you link these subprocesses to the main process. We recommend linking subprocesses
with the collapsed subprocess element, which links to subprocesses defined in separate models.
When you create a high-level overview of the main process, you model subprocesses in separate diagrams and
link these subprocesses to the main process.
There are two ways to add subprocesses to diagrams, as expanded or collapsed subprocesses.
With the expanded subprocess element, subprocesses are shown with the main process. Since this does
increase diagram size and visual complexity, we recommend using the collapsed subprocess element, which
links to subprocesses defined in separate models.
Subprocesses can be complete processes or partial processes. They can only be executed as parts of a larger
process.
You can reuse subprocesses in multiple diagrams. We recommend using a subprocess in the following cases:
A subprocess needs to be a process, with a start and end event. When you have a complex activity that cannot
be meaningfully divided into different tasks, use a task element in your process model.
Subprocess elements
The notations in which you use subprocesses are usually value chains and BPMN models. In value chains, you
use the Collapsed Process element. In BPMN diagrams , you use the Collapsed Subprocess element.
Elements that link to other diagrams are marked with a + icon. This is the Collapsed Subprocess element in
BPMN:
Note
The following descriptions apply to BPMN diagrams, linking diagrams to elements is similar for other
notations.
• When you have a complex diagram, you can group parts into subprocesses.
• You can add a Collapsed Subprocess element to your diagram.
• From the subprocess element, you can create a subprocess diagram that is automatically linked.
• When you already have a subprocess defined, you can add a subprocess element to the main diagram
and link your defined subprocess to this element.
You can link diagrams in your workspace, or diagrams in other locations via URL.
Example
1. Select a Collapsed Subprocess element in your diagram and click the + symbol.
The dialog for adding a link opens.
2. Select one of the options to add a link:
• Use existing diagram: Select the diagram to link in the folder structure.
• Use web link: Paste the URL to the input field.
3. If the preview is too small, enlarge the dialog.
4. Click Link diagram.
The diagram is linked to the subprocess element.
1. Select a Collapsed Subprocess element in your diagram and click the + symbol.
The dialog for adding a link opens.
2. Enter a diagram name in the text field.
3. Select the diagram type.
4. Click Link diagram.
A diagram is created and opened in a new tab.
Once you have added a linked subprocess to a process, you can open the linked diagram from the subprocess
element.
A preview of the currently linked diagram is displayed. If the preview is too small, enlarge the Establish link
dialog.
You can view all related items in the attribute panel in the section Diagram relations.
In addition, all items related to a diagram by links are listed when you save a diagram.
How to add insights and KPIs to BPMN diagrams and value chains. The following Live Insights shapes are
available: Traffic Light, Progress bar, Indicator, Ring chart, Cockpit, Trend icon, Value
With the Live Insights shapes, you can add insights and KPIs you want to monitor to BPMN diagrams, value
chains, and navigation maps.
For that, you add a Live Insights shape to your diagram and link it with a widget from SAP Signavio Process
Intelligence. Users can then view the Live Insights in SAP Signavio Process Collaboration Hub.
In SAP Signavio Process Intelligence, thresholds need to be defined for the widgets that are linked to Live
Insights shapes. In SAP Signavio Process Manager, the color of the shape indicates how the current result of
the widget relates to the defined thresholds. The following example shows how the sentiment shape reflects
the current widget result:
The color of a shape is only visible in SAP Signavio Process Collaboration Hub. In SAP Signavio Process
Manager, the shapes stay grey.
For BPMN diagrams and value chains, you find the Live Insights shapes in the Live Insights shape repository. A
workspace administrator can enable this shape repository for you.
The visibility of Live Insights in SAP Signavio Process Collaboration Hub is subject to requirements. Read more
in section Display Widgets in Other SAP Signavio Applications.
1. In SAP Signavio Process Intelligence, get the ID of the widget you want to add to your diagram. Read more
in section Display Widgets in Other SAP Signavio Applications.
2. In SAP Signavio Process Manager, open your diagram and add or select a Live Insights shape.
3. Open the attributes panel and paste the widget ID to Driving widget.
4. In addition, you have the following options:
• Name: Enter a name for the shape.
• Documentation: Enter a description for the shape.
• Additional widget: Add more widgets by pasting their IDs. The widgets are displayed in the details panel
of the diagram when users click the Live Insights shape.
1. In SAP Signavio Process Manager, open your diagram and add or select a Live Insights shape.
2. Open the attributes panel and enter the value you want to display in Manual value.
3. In addition, you have the following options:
• Name: Enter a name for the shape.
• Documentation: Enter a description for the shape.
• Additional widget: Add more widgets by pasting their IDs. The widgets are displayed in the details panel
of the diagram when users click the Live Insights shape.
4. Save your diagram.
Next steps
Deep links from SAP Signavio Process Insights standard performance indicators can be added to diagrams as
links in custom attributes.
Read more about using attributes in section Edit attributes [page 48].
To be able to view the linked content, users need the necessary permissions in SAP Signavio Process Insights.
Read more in the following sections of the user guide for SAP Signavio Process Insights:
• User Management
• Roles in Default Role Collections
From a diagram or from diagram elements, you can link to online documents, files in your document
management system, or files in your network.
• To access documents from different elements or diagrams, link them to dictionary entries.
• To make the document accessible only from one diagram, use a custom attribute.
We recommend to create dictionary entries to link documents to elements. You can reuse dictionary entries
throughout your process landscape.
Note
The documents aren't uploaded to SAP Signavio Process Manager. Ensure that all users can access the
linked documents.
Custom attributes are defined by your workspace administrator. The name for the custom attribute used for
linking documents is specific to your workspace.
Note
SAP Signavio Process Manager is not designed as a document management system. We recommend
linking to documents instead of uploading documents.
1. Select the diagram element to which you want to add a linked document. If you don't select an element,
the link is added to the diagram.
2. Open the attribute panel.
3. In the section Custom Attributes, select the custom attribute used for linking documents in your
workspace.
Attribute overlays are attribute visualization layers. With attribute overlays, you can show attributes directly on
the diagram. You can use different icons and colors for overlays.
Attribute visualization layers are available for the following diagram types:
• BPMN diagrams
• Value chain diagrams
• ArchiMate diagrams
• Organization charts
Attribute overlays are managed by your workspace administrator. They also set the rules that determine when
an attribute overlay is displayed.
Note
We recommend to add attribute overlays as the last step when editing a diagram, because when you
change anything, you need to add the overlay again.
If a diagram contains attribute overlays, the number of available overlays and the number of visible overlay
categories are displayed.
Users can show or hide overlays and select which overlays they want to view.
Compare different diagrams and different revisions of the same diagram with this function.
With the diagram and revision comparison tool you can track changes to revisions made to your diagrams. In
addition to the Explorer Comparison view, here you can do the following:
• Compare two revisions of the same diagram side by side with revisions such as additions, edits, and
deletions.
• View changes made by other users on a diagram.
• Approve and apply changes made by other users on a diagram.
• Improve collaboration between users working on a diagram (see section Collaboration [page 262]).
• Locate duplicate diagrams after you have imported diagrams to your workspace (see section imported
[page 312]).
You can open the diagram comparison tool in the following components:
• In the explorer, select a diagram or two diagrams you want to compare and click Edit > Compare revisions/
diagrams.
• In the BPMN simulation, editor, and QuickModel, click Diagram comparison in the user menu.
• In the activity feed, select a diagram revision from the feed and click Open to Compare.
• In SAP Signavio Process Collaboration Hub, open the diagram comparison tool from the diagram actions.
Display options
With the Zoom Slider you can change the size of a diagram. When using the Zoom Slider, both diagrams
move simultaneously. You can navigate to different sections of a diagram by holding left-click and moving the
diagram.
To use the Zoom Slider on an individual diagram revision, disable the Synchronized Scrolling option.
Select revisions
The comparison view displays all edits made to a diagram in your workspace in the form of revisions. You can
view revisions of a diagram in two ways:
To view different revisions of your diagrams using the Revision drop-down menu, follow these steps:
1. On the first revision window, select the required revision from the Revision drop-down menu.
2. On the second revision window, select the required revision from the Revision drop-down menu.
3. The comparison and revision tool displays the selected revisions for the diagram side by side.
To view different revisions of your diagram using the Choose revisions/diagram option, follow these steps:
The diagram comparison displays structural and logic differences between diagrams or diagram revisions.
Hover over each icon of an element to get more detailed information.
At the bottom of the window, you find information about the number of changes for every change category. You
can select which changes are shown.
Note
Next steps
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
You can upload custom graphics for use in Customer journey maps, Value chains [page 202], BPMN 2.0
diagrams and navigation maps. Uploaded files must be in SVG format and individually no larger than 20 KB.
For images uploaded in the explorer, file size is limited to 20 kB for all notations, including navigation maps.
Images uploaded with the image manager while creating navigation maps have a size limit of 50 kB.
• IT System
• Additional Participant
Value chains
• Process
• Collapsed process
• Persona
• Touchpoint
• Moment of truth
• Customer
• Decoration
Navigation maps
• Images
Custom graphics are tied to the workspace to which they are uploaded. If you have multiple workspaces and
want to use custom graphics in each, you must upload them separately to each workspace.
Note
Custom graphic files do not count towards the file limit for a workspace.
5. In the Custom attributes section, click the Custom Graphics tab. Click the Add button. The Upload Custom
Graphic dialog opens, with details about the upload requirements for SVG files.
6. Click Choose File and select the file you want to upload. The Name field is prefilled with the file name. A
preview of the image is displayed. Edit the name if you want, and click Add.
1. Your custom graphic is displayed in a list in the Custom Graphics tab, where you can now set and use it for
modeling.
Note
1. In the SAP Signavio Process Manager explorer, open Setup > Define notations/attributes.
The Define notations/attributes dialog opens.
2. In the Modeling language section, select either customer journey map, value chain, BPMN 2.0 diagram, or
navigation map.
3. In the Diagram element types section, select the element type from which you want to delete the graphic.
4. In the Custom attributes section, click the Custom Graphics tab. Click Remove.
5. Confirm in the dialog. The graphic is deleted from the workspace and no longer available in any diagram.
Validation criteria
SVG is a flexible, powerful file format. However, this flexibility makes it vulnerable to security exploits. To
prevent possible security problems, SAP Signavio Process Manager will check each SVG file you try to upload
and scrub anything potentially malicious from the file. It will then show you a preview dialog, so you can see
the differences between the original and scrubbed file. If the scrubbed file is acceptable to you, you can then
continue with the upload.
• The root element of the SVG must contain the required attributes either width and height or viewBox. The
width and height attributes must be absolute size.
• The attributes of the SVG file must not contain JavaScript in attributes
• The elements and attributes of the SVG file must not contain URLs
• The SVG file must not exceed the size limit of 20 KB
• The SVG file must not exceed the supported complexity of 2000 anchor points
Here is the list of allowed tags and attributes for SVG files:
Tags: "svg", "style", "g", "path", "ellipse", "circle", "polygon", "rect", "line", "polyline", "defs", "clipPath", "mask",
"use", "radialGradient", "linearGradient", "stop"
Once uploaded, custom graphics can be used in customer journey maps, value chains, BPMN 2.0 diagrams
and navigation maps.
Models with custom graphics can be imported, exported and published to SAP Signavio Process Collaboration
Hub the same as standard models.
When organizations start a process initiative, their target audiences have different perspectives, even though
it's one initiative with the same goal. Those perspectives could depend on the location, role, department,
regulations, and more.
Employee onboarding in Germany, for example, is a little different than in the US. HR personnel, IT staff, the
hiring manager, and a new hire could all be involved in this process, and each of them will have a different focus,
different needs, and different expectations. Additionally, everyone involved cares about the current state of the
process, though not all are as invested in its future development.
In SAP Signavio Process Manager, process variants represent these different perspectives on a main process.
For each variant, you define characteristics that differentiate it from its process template and from other
variants. These characteristics are implemented as dimensions (dictionary categories) and values (dictionary
entries).
Our variant management tools enable process owners and modelers to identify and model variants, control
their relationships, reduce redundancy, track and propagate changes, and support users in consuming the
required variant depending on the context and their role.
Note
Related Information
A variant group consists of exactly one template and at least one variant. Each variant can only be attached to
one template.
The variant group carries the same name as its template. You can easily identify a template, a variant, or a
variant group as a whole by means of the following labels or icons:
Template Template
Variant
Activities
Most activities related to variant groups are performed in SAP Signavio Process Collaboration Hub. Which
actions you are able to perform depends on your role and authorizations, and where you access the diagrams.
Related Information
A process model that has been defined as a main process for creating or attaching process variants.
A process template is associated with at least one variant. However it's possible to make a diagram a template
without immediately attaching variants, and to add them later on. Variants can also be detached from a
template.
Deleting a process template disconnects the associated variants, and they lose their dimensions and values.
You can't undo the deletion and the dissociation of the variants.
You manage process templates in SAP Signavio Process Collaboration Hub. Which actions you are able to
perform depends on your role and authorizations, and where you access the diagrams.
A variation of a process model that differs from its template in at least one dimension or value.
Variants enable those involved in a process to work more efficiently and have a better understanding of the
process. They enable those who are modeling processes to manage complexity and at the same time achieve
more transparency and efficiency.
Note
You can attach a variant to a template that uses the same modeling notation. To a BPMN model, for
example, you can only attach BPMN variants.
You manage process variants in SAP Signavio Process Collaboration Hub. Which actions you are able to
perform depends on your role and authorizations, and where you access the diagrams.
Related Information
Use dimensions and values within these dimensions to differentiate process templates and variants.
The following diagram is interactive and contains examples of possible dimensions that you can use to define
process variants and templates:
Geography
Multinational companies need to manage processes in different countries and regions while keeping variations
in respect to a standard process to a minimum.
Product
Companies with different product lines and brands need to manage processes related to different products,
manufacturing sites, capabilities, and procedures.
Customer Type
Companies that produce and sell to different kinds of customers need to introduce variants related to the
different channels their customers use.
Process variants differ from their template in at least one value. That value either belongs to the same
dimension used by the template, or to an additional dimension.
Example
These could be dimensions and values created by a company that produces coffee and tea:
Activities
Dimensions are stored as dictionary categories, and values are stored as dictionary entries.
You can add and edit dictionary categories in the SAP Signavio Process Manager editor. Any dictionary
category that you want to use as a dimension in variant management needs to be defined as such:
Display details about a variant group in the SAP Signavio Process Manager editor.
When you edit a diagram that belongs to a variant group, the system displays details about the template and its
variants in the attribute panel.
• Process template
• Process variants
• Dimensions and values of the edited diagram
When you choose the link to a template or variant, the diagram opens in a new tab.
When you choose Manage dimensions, SAP Signavio Process Collaboration Hub opens, where you can
configure the dimensions and values of the diagram.
Related Information
Changes to a process variant or a process template are documented in the notification and activity feed. The
following actions, among others, are documented in the feed:
If notifications have been enabled by your workspace administrator, you can subscribe to a diagram or a folder
to receive email updates.
Related Information
The dictionary is the central object management repository in SAP Signavio. A dictionary entry represents
an object that is relevant for one or more of your processes. With the dictionary you can manage and re-use
specific modeling elements. The dictionary also helps you make sure all your modelers are using the same
terms and the same elements in your organization-specific modeling environment.
The dictionary is a crucial component to achieve a consistent and well-structured business objects
management in your diagrams.
Note
Access rights for the complete dictionary and dictionary categories are set by your workspace
administrator. The actions available to you depend on your access rights.
In the dictionary, you can search, view, create, edit, delete, and publish dictionary entries.
• To open the dictionary, click the Dictionary folder in the navigation tree on the left side of the explorer. The
dictionary opens in a new browser tab.
• To view a dictionary entry, select it. Its full description, a list of attached documents, and a list of diagrams
referencing that entry is displayed.
1. Click the category that you want to display (for example, 'Roles').
2. Use the alphabet links at the top to navigate to the entry you are looking for faster.
• To find out where a specific dictionary entry is referenced in your process landscape, select the entry and
click Show usages.
A dialog displays the type and name of the referencing elements, as well as the names of the referencing
diagrams.
With Load next, you can view links to the referencing elements to analyze the whole chain of references.
If there are multiple languages activated for your workspace, you can switch between them by clicking the
language symbol .
Dictionary entries that have not been translated into the currently selected language are displayed in their
default language and marked with a country flag.
Full-text search
Similar to the activity feed in the explorer, the dictionary feed allows you to manage revisions.
• Restore
Restores your entry to a previous version. This does not delete revisions, but lets you to switch between
them.
• Publishing
Makes this revision available in SAP Signavio Process Collaboration Hub. By default, the newest revision is
automatically published upon creation.
• Unpublishing
Revokes the revision's publication in SAP Signavio Process Collaboration Hub.
Note
The buttons to publish and unpublish revisions are only active in categories for which Publishing Mode
has been set to Manual. See Defining custom categories for dictionary entries for details.
1. Click New in the top toolbar. The New Entry dialog opens.
2. In the New Entry dialog box, add the following information:
1. Choose the dictionary entry you want to edit and click Edit. The edit dialog for dictionary entries opens.
2. Edit the dictionary entry.
3. Click Save.
Note
If the category of the dictionary term you are trying to edit is set to automatically update when making
changes, the diagram elements that refer to this entry are updated automatically. This creates new
versions of the diagram. If there are a lot of diagrams affected, it can take up to 30 seconds to save
your changes.
2. Click the Delete button in the top toolbar. A confirmation dialog lists the affected diagrams.
3. Click Yes to confirm deletion.
Reference documents
1. Select a dictionary entry and then click Edit. The Edit entry dialog box opens.
2. In the attribute Relevant documents, select Add a new document. The dialog Link files/pictures opens.
3. Select a file from your SAP Signavio Process Manager directories. Alternatively, you can upload a new file
or picture from your local file storage or add a link.
4. Click Add. The selected file is added to the dictionary entry.
Note
More about external data sources is described in section Creating external data sources.
Note
The following section applies to dictionary entries that are set to manual publishing mode. By default,
dictionary entries are automatically published together with the diagram.
In that case, make sure that the current dictionary entry is also published when publishing the diagram.
Link dictionary entries to diagram elements and create new dictionary entries while modeling, directly in the
editor.
Note
Access rights for the complete dictionary and dictionary categories are set by your workspace
administrator. The actions available to you depend on your access rights.
Available dictionary entries are suggested when you enter a label name.
Note
This feature supports wildcards (*). For example, typing C*O may return the entries CIO, CFO, and CEO.
1. Enter a label for the diagram element. While you type, dictionary entries are suggested below the element.
By default, only dictionary entries whose category type matches the element type are suggested.
2. Click an entry to link it to the element. The entry's title is now the element's label and the attribute
values of the dictionary entry are applied. Elements that reference dictionary entries are marked with the
dictionary icon .
Example:
To find available dictionary entries, use the search below the shape repository.
Example
Example:
New entries are created in the language currently selected for the diagram. To translate entries, open them in
the dictionary. See section Working with the dictionary [page 83].
If an element references a dictionary entry, you can view the entry by clicking .
To edit the entry, click Open in dictionary. The full dictionary entry opens in a new browser tab.
When you want to link an element to a different dictionary entry, you first need to remove the current link.
If a dictionary entry is set to manual publishing mode and has been altered without being republished, the
editor displays a warning.
To avoid this, make sure you publish the current entry dictionary along with the diagram you're creating.
This section describes local changes for attributes. To edit a dictionary entry, see section Editing dictionary
entries [page 83].
To specify a value for the current process context, you can overwrite attribute values from a referenced
dictionary entry locally.
Caution
Local modifications are not applied to the dictionary. When you overwrite dictionary entries, these changed
element properties are no longer managed centrally in the dictionary. This can cause inconsistencies
between elements that reference the same dictionary entry.
1. Open the attribute panel. All attributes that are defined by a dictionary entry are marked with the
dictionary icon .
2. In the diagram, select the element with the attribute you want to change.
3. Click the attribute value in the attribute panel.
You are warned that local changes do not affect the dictionary entry.
4. Click OK to continue. Depending on the attribute, an editing dialog opens.
5. Enter the attribute value. When the new value is applied, the attribute is marked with a red dictionary icon
Note
You can't overwrite a dictionary attribute value with its default value.
1. Open the attribute panel. All attributes with local changes are marked with a red dictionary icon .
To report and prevent overwriting of attributes, you can use modeling guidelines.
The dictionary allows you to keep all the terms that are often used in your diagrams in one easy-to-reference
place. However, over time the use of terms can change, entries with a similar meaning but different description
might be added, and extraneous copies of existing entries might be created when many modelers work
together. Duplication can also happen when importing Signavio archive (SGX) files, because entries from these
files will automatically be added to the dictionary. Regardless of the source, merging dictionary entries will help
you keeping the dictionary in good condition.
1. Open the dictionary and choose the category the entries can be found in.
2. Choose the first dictionary entry you want to merge. You can select multiple entries at once.
3. Click Merge Dictionary Entries.
4. Enter the name of the second dictionary entry into the field Add Dictionary Entry. Use the auto-completion
here. You can merge as many entries as you want using this method.
5. Choose the elements to be added to the resulting entry. Attached documents, linked dictionary items, and
links are added to the target entry automatically.
6. Click Merge and confirm the warning.
The entries are merged. The resulting entry will be displayed, and can now be edited.
Note
To be able to reference external data sources, you need to implement and configure the corresponding
interface first. Read more at Managing external data sources.
Once an external service has been set up, it can be selected in the dictionary under Simple Type - External
Enumeration of Values .
In the dictionary, all categories that can be used to define input data can have dictionary entries that make use
of external data. To be able to define input data for a category, the check-box Use as DMN input data has to be
activated.
To reference an external data source in a dictionary item, use Simple Type in the Type Definition field and
choose ExternalService as Value Domain . Now, the field Service allows you to select one of the services that
have been registered:
When the dictionary item is used in a decision table, the service response will determine the data type, for
example enumeration or hierarchy.
The dictionary is included with SAP Signavio Process Manager and can be used in SAP Signavio Process
Collaboration Hub and integrated with SAP Signavio Process Governance. This document explains how to
create useful dictionary content for your workspace, how to maintain the dictionary and how to keep it
consistent over time.
Getting Started
The initial dictionary contains the default categories and exemplary entries for most categories. The default
categories cannot be deleted. The exemplary entries give you an idea how entries can look like for the different
categories.
While dictionary entries and categories differ from company to company and between industry sectors, the
following four categories are usually useful for all customers:
• Organizational units
• Roles
• Departments
• External participants
Note
Often, activities and events are not suitable for standardization across a workspace and therefore hard to
define as dictionary entries. You can leave the default categories Activities and Events empty.
When you have existing definitions and possible entries for one category or multiple categories, we recommend
that you add these existing content to the dictionary. Dictionary entries can be added one by one using the
dictionary interface. There are two additional ways to add dictionary entries:
You can import existing definitions into the dictionary as Excel files. You import one category or one
subcategory at a time. For a successful import, the structure of the Excel file needs to fulfill certain
requirements.
To make sure that the structure of the Excel file matches the requirements, export one of the available
dictionary categories and use this file as a template.
Every modeling shape provides the option to directly create a new dictionary entry without leaving the current
model. When no preexisting definitions to populate the dictionary are available, modelers can fill the dictionary
while they are mapping processes.
To keep the dictionary consistent and to avoid the creation of duplicates, we recommend that you have
designated dictionary managers. Only this group of users should get write permissions to the entire dictionary
or specific categories, for example, you can appoint two managers for IT-systems and two different managers
for organizational units.
Every dictionary entry has a unique ID that is used to link the entry to an element. This means the suggested
dictionary entries can be used by all modelers while still in the suggestion category. The link between dictionary
entries and modeling shapes stay intact when dictionary managers change the category of entries.
The dictionary managers should regularly take over entries from the suggestion categories so that new entries
are added to the main categories in reliable intervals. Dictionary managers can subscribe to the suggestion
categories to get notified about changes automatically.
Avoiding Duplicates
• Modeling users create a new entry, but a similar entry already exists.
• When you import Excel files with dictionary entries, the option Create new entries for all rows is enabled.
• SGX files are imported, with the enabled option to import the contained dictionary entries.
When several languages are set for your workspace, users can select a language for a dictionary entry. This can
result in duplicate entries that are not easily recognized because they are in different languages.
When you use suggestion categories and designated dictionary managers, they should detect duplicates when
they move entries out of the suggestion category.
When you import Excel files with dictionary entries, select the options carefully to avoid undesired results.
When you have duplicate dictionary entries, you can merge entries so that no information gets lost.
You can delete dictionary entries and all dictionary categories you have created. It is not possible to delete the
default categories.
Before you can delete a dictionary category, you have to delete all entries in that category, or move them to
different categories. You also have to delete all attribute definitions used by this category and all dictionary link
attributes that reference the category.
This tutorial describes how to use the Dictionary as a business process/business decision modeler.
• ...reference and create dictionary objects directly from the modeling canvas.
• ...drag & drop existing dictionary entries as modeling elements from the element repository onto the
canvas.
• ...manage changes to diagram elements.
Following our recommendations will increase your modeling speed as well as the consistency and
completeness of your process landscape.
Let's start by creating a new process as part of our example process landscape.
First, we create a pool for our company. The pool ACME AG can be dropped from the dictionary entry
repository on the left side of the modeling canvas. It is directly available under Frequently used dictionary
items :
Drag & drop from the element the dictionary entry repository
The attribute values are fetched from the referenced dictionary entry
We are not sure if a corresponding dictionary entry exists, so we simply start to fill in the corresponding label.
As we type, the dictionary entry Approver is suggested as a reference.
Note
If the default Dictionary settings have not been changed, only dictionary items that match the
corresponding element type are suggested. In our case, only organizational units and IT systems are
suggested and e.g. no events or activities. IT systems can be referenced from pools and lanes because they
are similar to organizational units in their ability to execute tasks. For example, the task 'Send email' can be
executed by both an employee and an IT system.
We can assume that this event is only occurring in this one diagram, so we don't need to create a dictionary
entry for it.
Subsequently, we create the task Review employment contract. No dictionary entry is suggested by the system.
Let's now assume that we need to create the same task in a different process later on. Thus, we create a new
dictionary entry by clicking the dictionary icon at the lower left corner of the element:
Now, we want to link the IT system that the approver needs to use. We don't know which system to use exactly,
so we use the filter function of the dictionary element repository to gain an overview over our IT systems:
We identify Personnel System as the correct IT System and drag it onto the modeling canvas:
We can refer to the steps described above to continue adding elements to our model.
However, when revising the process, we find that the role Approver is too generic for our purpose:
A warning is displayed, as element attribute and dictionary item attribute will no longer be consistent
The warning sign indicates the inconsistency between element attribute and dictionary item attribute
However, this procedure is not recommended, as it makes it very hard to detect the difference between the
approver in our current lane and other lanes referencing the approver object. Moreover, it is no longer possible
to centrally manage the attribute value via the Dictionary.
This option is recommended if the dictionary entry is generally not correct or lacks information. This does not
apply in our case.
As our approver is a human resource/legal specialist, we need to add more specific information. However, we
can assume that the approver reference in other diagrams doesn't match our new specification. In that case,
we will need to click the dictionary icon next to the entry and select Remove link :
Note
We recommend to avoid inconsistencies between dictionary entries and referencing elements and to avoid
re-purposing dictionary entries because of one specific reference . In such cases, the creation of a new
Dictionary is usually the best alternative.
SAP Signavio Process Manager supports multiple modeling notations: BPMN for business process models,
value chains, customer journey maps, DMN for decision diagrams, ArchiMate for enterprise architecture
diagrams and more.
In this section, you find the editing features of the different modeling notations:
• Section Business Process Modeling and Notation (BPMN) [page 205] explains how to model business
process diagrams in the editor.
• With Value chains [page 202], you create high-level perspectives on the process hierarchy in your
organization.
• Customer journey maps depict a customer's perspective on a product or service that contains specific
touch points that link customer experience with process architecture.
• With Decision Model and Notation (DMN) [page 140], you model decision diagrams to describe frequently
made decisions of an organization. It is also possible to simulate decisions and define and execute test
case for DMN decision logic.
• Enterprise architecture diagrams enable you to visualize your corporate IT system architecture within and
across business domains. You can learn how to model in section ArchiMate.
• In addition, SAP Signavio Process Manager supports a set of Further notations [page 226] that are of
lesser importance in practical process management scenarios.
BPMN is an industry standard for modeling business processes. The standard is published by the Object
Management Group (OMG) and supported by a variety of vendors and consultants.
SAP Signavio Process Manager supports BPMN 2.0, including all modeling elements and attributes. With this
version of the standard, you can define activities, control flow, data flow, organizational dependencies, and
system dependencies of business processes.
SAP Signavio is committed to BPMN, has been and continues to be involved in the standardization process,
and promotes BPMN in industry and academia.
This section describes the special features of modeling a BPMN diagram. Find more on modeling instructions
that apply to all notations in section Modeling [page 35].
Note
Which subsets or which elements within a subset are available to you depends on the settings of your
workspace. Your workspace administrator can customize the subsets.
Example
Example
The modeling elements correspond to the BPMN standard. Find an overview in the element guide Business
Process Model and Notation: An introductory guide .
• Live Insights
Add insights and KPIs you want to monitor to diagrams, read more in section Add Live Insights [page 61].
• IT systems
Define artifacts as IT systems.
• Additional participant
Add more participants to an activity.
When connecting two elements, the connector type is automatically determined according to the BPMN
standard. For example, connectors between tasks are sequence flows, while connectors to annotations or data
objects are associations.
To show the bending points of a connector, hover over it. You can drag any existing bending point to a new
location.
To add a bending point, click the connector and drag the new bending point to its location.
• drag the bending point to a location that is on a line with the two neighboring bending points
• drag the bending point onto a neighboring bending point
Example
Example
You can move horizontal or vertical connector sections that are between bending points or between a bending
point and another element. To do so, hover over the connector, click the yellow area, and drag it onto it's new
location.
Example
Example
Note
The BPMN specification uses the term boundary event instead of attached intermediate event.
With attached intermediate events, you can react on events that occur during the execution of a task. For
example, if a customer cancels an order while it is still being processed, the order processing needs to stop and
tasks need to be executed that cancel the order.
• To attach an intermediate event to a task, drag it onto a task. A green border in the task indicates that the
event can be attached. Some intermediate events, like the link intermediate event, can't be attached to a
task.
Canceling The occurring event cancels the task and determines how to
proceed.
• To change an event to non-canceling, select it and disable the option More Attributes > Cancel activity in
the attributes panel.
Canceling events are displayed with a solid border, the border of non-canceling events is a dotted line.
Example
Example
Note
Changing the orientation can change the diagram layout significantly and even break the layout. Previous
layout states can't be restored.
• In the attributes panel, under Main Attributes > Diagram orientation, select the horizontal or vertical
orientation.
Further checks are available, read more in section Work with modeling conventions [page 56].
Next steps
Modeling elements have several properties you can edit. These properties are called attributes. You can use
attributes to change the appearance of an element (for example the background color or label). Attributes can
also be necessary to execute a process, for example the decision logic in a DMN diagram is an attribute.
You edit attributes in the attribute panel on the right side of the editor.
• To change the attributes for one element, select the element and open the attributes panel.
• To change diagram-wide attributes, choose any empty space on the canvas and open the attributes panel.
Note
The first section of the attribute panel contains custom attributes, which can be defined by your workspace
administrators.
You can change attributes for one element and diagram-wide attributes.
Example
Example:
BPMN includes a range of attributes. The following table lists the most important attributes.
Send, Receive,
User, Manual,
Service, Busi-
Is a call activity task, subprocess, event-sub- false A call activity links to a glob-
process
ally defined process or sub-
process. The called process
controls the flow. Non-stand-
ard start events are ignored.
multiple companies.
input, output
You can add documentation to an element to include more details. For example, if a rarely executed task
requires instructions, you can add these instructions as documentation.
Note
The element documentation can also be accessed in SAP Signavio Process Collaboration Hub.
The responsibility assignment matrix RACI is used to represent responsibilities for activities.
Add a lane to set all activities in this lane as responsible (R) in the RACI matrix. It's not possible to assign
additional RACI responsibilities to a lane element.
The element Additional participant can be linked to an activity with the connector Association (undirected). The
connector has the attribute Responsibilities to assign responsibilities.
Example
Example:
Note
To assign responsibilities to tasks, custom attributes for RACI need to be available in your workspace.
Custom attributes can be defined by your workspace administrator.
Example
Example:
To open the dictionary entry, click the icon and click Open.
The RACI matrix lists the 4 RACI assignments and an additional responsibility where no RACI category was
used:
• R - Responsible
• A - Accountable
• C - Consulted
• I - Informed
• X- Participates
To export a RACI matrix for one or multiple diagrams, follow these steps:
Key performance indicators have to be set for a quantitative analysis. The indicators can be set for task
execution probabilities and frequency. They also inform about cost and execution time.
Diagrams have to be structurally and semantically correct to create a quantitative analysis. SAP Signavio
Process Manager provides tools that allow you to check the corresponding properties of process diagrams.
KPIs can be set for each element in the Attributes section on the right in the Editor. Select an element, then
click the two arrows above Attributes to extend the section on the right. The KPI values for the corresponding
analyses are set under Cost and Resource Analysis and More Attributes. Simply click the corresponding
headlines to expand the KPI settings. When you are finished setting the KPI values for one element, simply
click the next element in the central section and add the corresponding values on the right. When you are
finished adding the necessary values to all elements, you can click the arrows on the left of the grey 'Attributes'
header to close the Attributes menu and proceed with the calculation.
The following attributes are key values for the process cost and resource consumption analyses:
Denotes how often a process is started via this entry point. Multiple start events that represent
alternative entry points for the process are allowed.
e.g. "1000"
Denotes how long it takes on average to complete the task. This value is required for a resource
consumption analysis.
e.g. "2.5"
Denotes the costs that come up during the activity. This key value is required for a process cost analysis.
e.g. "5"
Denotes the probability for choosing this sequence flow after a decision gateway/XOR-connector. This is
supposed to be a value between 0 and 1.
e.g. "0.2"
Caution
This is an optional value and represents the cost center for the activity costs.
e.g. "KS 1008"
Floating point numbers are accepted either in the form of "2.5" or "2,5" but will be automatically converted
to the notation of "2,5".
Checking completeness
After setting the KPI, you can trigger a check for completeness to ensure that all required values are present for
analysis.
Click the toolbar and select Cost and resource analysis check.
Some elements may now be marked with one of the following icons:
• The white exclamation mark on orange denotes that key values are missing for an element. It is also
attached to elements that will be ignored during an analysis, as it is not logically contained in those
measurements. (For example, a sending intermediate message event will be ignored during an analysis.)
This does not interfere with the analysis calculation, but some of the calculations may not be able to run
properly due to missing data.
• The white exclamation mark on red denotes a heavy structural or logical mistake. Additionally, some
modeling elements preventing an analysis are marked with this symbol--for example, a complex gateway
cannot be included in a process analysis.
This sign marks that an element interferes with the analysis calculation.
Hover over one of these symbols to get more details about the problem that occurred.
An analysis calculation can be triggered only after all severe mistakes (indicated in red) have been removed.
You can create different views for different audiences. In a view, you include what you want to show an audience
and exclude what the audience does not need to see.
• A model contains both user activities and elements for technical implementation. The audience wants to
focus on the technical implementation.
• A model contains different variants of one process. The audience should only view one variant.
• A model contains the expected path of a process and a number of exceptions. The audience doesn't need
to see the exceptions.
1. Extend the right panel and scroll to Views. All available views are listed.
• To create a new view, click Create new view.
• To configure an existing view, click the view.
The view configuration opens.
By default, you move both diagram versions in the preview. To move the diagrams separately, disable
Synchronous Scrolling.
Edit a view
You can exclude all Comments , Data objects, IT Systems, or Roles above the original view.
You can show or hide each element. In the original view, disable elements to exclude them from a view.
For pools, you have additional options. Select an option from the drop-down list at the bottom of the pool.
• Pool is opened: The pool and its content are included in the view. You can define view options for all
contained elements.
• Pool is collapsed: The pool content is not shown.
• Only content: No roles that are defined by the pool and its lanes are shown. Message flows attached to the
pool are hidden.
• Pool is hidden: Neither the pool nor its content is included in the view. Message flows attached to the pool
are hidden.
When you uncheck a pool, all elements in that pool are excluded from a view.
To keep the original diagram size and the original placement of the shown elements, disableReduce free space.
Duplicate a view
Delete a view
It is possible to include or exclude diagram elements from one or multiple views while editing a diagram--
without opening the views configuration. This makes it fast and easy to edit existing views.
• Behind each view that is stored in the attribute editor. check boxes will appear. Those can be empty,
checked or, if multiple elements were selected, colored green:
Only some of the selected elements are included in the view, but not all.
Empty
• Check or uncheck the boxes, to add/remove the elements selected from one of the views.
When you have views available, you can check while modeling if an element is visible in a view.
Open the view panel and click an element. The view which contains the element is marked.
Example
Example:
You can include views when you export a diagram as an SVG, PNG, PDF, or a BPMN 2.0 XML file. The
SGX export contains all views for a diagram. Read more about exporting diagrams in section Downloading/
exporting diagrams [page 326].
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
In this article, you will learn how to define custom risk management tables in the Dictionary.
In SAP Signavio Process Manager, you can document the risks and controls directly in your process landscape.
This is obtained via the element attribute.
Caution
To use this feature, you need to configure it first, see section Managing risks and controls definitions for
details.
1. Ensure that you defined Risks and Controls as described in Managing risks and controls definitions.
2. Select the element.
3. In the attribute panel under Custom Attributes click the defined category. The Risk Management dialog
opens.
4. Enter the name for the risk. While typing a name, the system automatically proposes possible names of
existing risks.
Caution
If you use an already existing risk attribute from the Dictionary, you can change locally the corresponding
value. Please be aware that this could lead to inconsistency and should be avoided. For more detailed
information see section Overwrite dictionary entries locally [page 91].
1. If you decide to create a new risk, you can now enter the risk definition.
To create an overview over all risks and controls, you can create reports, see section Generating risks
management reports [page 299].
When you need to update a specific risk or control, you can do this centrally in the Dictionary. The update will
affect all diagrams that reference this risk or control immediately.
Of course, you can also add new risks and controls in the Dictionary (see Using the Dictionary in the Editor
[page 88]).
To ensure your risks and controls definitions are updated when a process changes, you can employ approval
workflows, see section Approval workflows [page 288], that enforce a review by a risk management specialist
before a process revision is published in SAP Signavio Process Collaboration Hub or otherwise released into a
production environment.
In SAP Signavio Process Manager you can migrate BPMN 1.2 business process diagrams to BPMN 2.0. This lets
you reuse old diagrams modeled in BPMN 1.2 with new elements from BPMN 2.0.
SAP Signavio Process Manager allows you to automatically convert Event-driven Process Chains (EPCs) to
BPMN 2.0 diagrams.
Now, you can decide whether to convert Position/Roles and Organizations to BPMN 2.0 Pools and Lanes. The
system handles the assignment to Pools/Lanes via the custom Relation attribute Responsibility. To properly
assign a function to a Positions/Role or Organization, you need to set the corresponding attribute value to
responsible:
The system will create empty Pools/Lanes for all Positions/Roles and Organizations that lack a corresponding
responsibility assignment.
If you don't activate the corresponding checkbox, the system will convert Position/Roles and Organizations to
the SAP Signavio-specific BPMN extension Additional Participant instead.
Caution
EPC and BPMN 2.0 are not entirely congruent notations. The following EPC elements cannot clearly be
mapped to BPMN 2.0 elements and are ignored by the converter:
• Letter
• Email
• Fax
• Phone
• Entity
• Form
• Resource
If you use these elements in your EPC diagrams, we strongly recommend you to review and edit the
generated BPMN 2.0 diagrams after the conversion.
Caution
This articles introduces the FIM BPMN extensions, which are relevant for the German public
administration. The plugin for the editor is accessible on request.
The German Federal Ministry of the Interior created a BPMN extension for structuring BPMN-diagrams: the
so called FIM attributes (translates as Federal Information Management). These attributes equip processes in
departments and sectors of the public administration with reference attributes, to compare them with more
clarity on a national level.
The principle of the FIM initiative is: "The same content should always be described in the same way."
The attributes refer to common activity types like receive information or decide. These are activities that occur
commonly in the processes of the public administration, but different local authorities have different ideas of
implementing them. For example: Many local administrations use different forms to receive information for
public services, although on the basis of these information they have to decide over the same factual matters.
The FIM initiative strives to standardize the processes to reduce bureaucratic expenditure, using instruments
of process management.
In the BPMN extension, these processes are ordered into groups through FIM. The reference activity groups are
marked with different labels in the top right corner of a subprocess activity. This makes the the FIM groups
easy to recognize.
You can also use the add-on outside of the public administration context. It is a useful tool to structure
subprocesses and to standardize content that belongs to the same reference group.
Overview of FIM-attributes
The attribute labels can be used flexibly, but usually they refer to:
More information on how to create subprocesses is available in the section Create subprocesses [page 58].
You can drag lanes from the shape repository in the left panel. Drag the lane onto the head of a pool and a new
lane will be created. Find more information about pools and lanes in section Add pools and lanes [page 41].
You can change the orientation of a diagram in the attribute column under Main Attributes . Simply click the set
value ( horizontal or vertical ) of the attribute Diagram Orientation and change it correspondingly. The Editor will
automatically re-align the elements in the diagram after you confirm.
Custom attributes can be defined for each modeling element. Open the Explorer, click Setup and choose
Define notations/attributes . Now, select a subset (e.g. Business Process Diagram (BPMN 2.0) and BPMN
(complete)), the diagram element type (e.g. Task) and click Add custom attribute . Name the attribute and
choose the data type Link/URL. Click Create .
Note
This section describes the customer journey map notation that was introduced in 2017. The user guide for
our new SAP Signavio Journey Modeler can be found here .
Customer journey maps (CJMs) provide customer-centered entry points to your business process landscape.
CJMs are high-level intuitively readable diagrams that focus on the customer experience instead of internal
processes. They help you understand how your customers perceive your products and services in the context
of their everyday lives and how their key decisions, which for example lead to a purchase or churn, are
motivated.
Note
This section describes the customer journey map notation that was introduced in 2017. The user guide for
our new SAP Signavio Journey Modeler can be found here .
Customer journey maps are graphical representations of the steps a customer absolves when interaction
with your organization. They can include a wide variety of information, including things like critical decisions,
touchpoints, departments involved, IT systems, or any other points that are specific to your organization.
When creating a customer journey map, you model your organization from the outside in. Hence, customer
journey maps provide customer-centered entry points to your business process and/or enterprise application
landscape.
The following sections explain the customer journey map elements you can use in SAP Signavio Process
Manager.
Personas represent typical customers. A persona's attributes and their associated banners define their
motivations, goals and pain points, as well as typical characteristics like preferred media channels and IT
savviness.
Customer
A customer element represents a persona at a specific step of a customer journey. You can configure customer
elements to express their feelings and attitudes as gestures, for example as a thumbs up.
A customer.
As personas, customers can be either female or male, depending on their gender attribute.
Outcomes define what your customers are trying to get out of their experience. For example, an outcome of
the customer journey of a banking customer might be obtain loan. Outcomes can be either successes (hoisted
flag) or failures (flag on the ground).
Step
Steps (connected through paths) show the sequence of events at a high level and form the backbone of a
customer journey map around which supporting elements are arranged.
A sequence of steps.
Path
Touchpoints
Touchpoints represent steps where your customer comes into direct contact with your brand. Each touchpoint
relates to at least one of your business processes and roles or IT systems. Touchpoints can be either physical
(for example: a cash desk) or virtual (for example: social media).
Moment of truth
Moments of truth are key decision points that can make or break your business’s chance for succeeding with
the customer. They are either barriers (requiring customer empowerment) or signposts (requiring a customer
decision).
Trigger
Triggers start a customer journey. They can be either ideas (inspiration-driven) or demands (driven by need).
A trigger.
Text
Text labels describe specific customer journey map elements or element groups.
Banner
Banners are post-it-style notes that contain important textual information about a customer journey map
element or about the customer journey in general. The icon and default color of a banner depends on the
elements type attribute, which can be idea (light bulb), demand (bell) or goal (flag).
Decoration
Decoration elements provide additional visual information to support specific process steps. For example, a
package decoration element might indicate a delivery.
Note
This section describes the customer journey map notation that was introduced in 2017. The user guide for
our new SAP Signavio Journey Modeler can be found here .
To create a new customer journey map, open the Explorer and click New - Customer journey map:
The system opens the Editor with an empty diagram canvas in a new tab.
You can work on the customer journey map like a diagram of any other type.
Grouping elements
Note
Grouping elements makes it easier to model your process landscape, because it lets you move multiple
elements together as though they were one single element.
• Select a set of elements and click in the left bottom corner of the selection rectangle.
• Select a group and click in the left bottom corner of the selection rectangle.
After grouping elements in the Editor, open your customer journey map in SAP Signavio Process Collaboration
Hub. Click on each group and you will see all information about each element in the group displayed in the
annotation.
If you publish to or preview your customer journey map in SAP Signavio Process Collaboration Hub, you can
use the arrow keys on your keyboard to navigate through each step.
To do so, either select a step with your mouse, or simply press the right arrow key on your keyboard. The step
you selected will be highlighted, while the rest of the map will be greyed out.
If your step contains grouped elements, an information panel with information about each element will also be
displayed for the highlighted step.
Note
This section describes the customer journey map notation that was introduced in 2017. The user guide for
our new SAP Signavio Journey Modeler can be found here .
In customer journey map diagrams, touchpoints (see section Touchpoint [page 205] ) depict interaction
points between your organization and your (potential) customers. In other words, touchpoint elements are
entry points to your process and application landscape. When creating touchpoints in customer journey
maps, you should reference the business process diagrams, roles and/or IT systems that are involved in the
corresponding customer interaction.
To allow referencing process diagrams and - in the form of dictionary entries - roles and IT systems, create a
set of custom attributes for the touchpoint element type (see section Add and manage custom attributes). We
recommend creating the following custom attributes:
To reference a diagram or dictionary entry at a touchpoint, select the touchpoint element in the Editor and
open the attribute panel. Select the attribute you want to edit - for example Process links - and add the
reference:
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
Note
DMN version 1.2 introduced the diagram element decision service to the specification. This element is
not supported.
With DMN, you can describe and model frequently made decisions of an organization, which answer the
following questions:
The notation is designed to be readable by all types of business users in order to ease collaboration for all
stakeholders.
DMN and BPMN diagrams can be linked so that processes can be viewed separately from decisions, with the
advantage that the process is streamlined and the decision is traceable.
DMN consists of the decision requirements diagram and the decision table.
The decision requirements diagram is the graphical representation of the decision rule. For example, the
diagram below describes what information and decisions are needed to screen an applicant and decide
whether to hire or not.
From the decision table, the appropriate decision is read for each supplied input. For example, in the table
below it is defined whether or not an applicant must have specific technical knowledge, be fluent in certain
foreign languages, and must have gained experience abroad.
Before you start modeling a decision, it is helpful to answer the following questions:
In this section, the diagram elements and editing functions that are only available for this notation are
described.
For general creation and editing options that are available for all notations, read more in section Modeling [page
35].
In the shape repository, you can choose whether to use the core elements or a complete set of DMN elements.
Example
Decision
A decision element determines a result based on input data and a decision logic. Each decision element
provides a table for the decision logic. You can open the decision table by clicking in the decision element.
You can split a decision into one main and several sub decisions. To do this, you link several decision elements
in the necessary order. Read more in section Create sub decisions [page 148].
Input data
Via the input data element, you provide information for decisions. One input data element can be used by
multiple decisions and business knowledge models.
If you must model numerous data input elements, you can simplify this by using the complex data input
element. Read more in section Create complex input data elements [page 145].
With the business knowledge model element, you add a function containing business knowledge, for example,
in form of business rules, an additional decision table, or an analytic model.
Via this element, you can reuse decision logic. Read more in section Reuse decision logic via business
knowledge models [page 182].
Knowledge source
With the knowledge source element, you describe the source of rules for a decision, for example laws,
regulations, and guidelines.
A multi instance decision is a sub decisions which is executed several times. The result of a multi instance
decision is a value or a list that is used as input for another decision. Read more in section Create a multi
instance decision [page 150].
Group
Information requirement
This connector links any input data or decision element to the decision that requires the information.
Knowledge requirement
This connector links any business knowledge model that must be used by the decision logic, to the decision.
Authority requirement
This connector links any diagram element that acts as a source of guidance or knowledge to another diagram
element.
You can connect an input data element with a dependent knowledge source or a knowledge source element
with any dependent decision.
Association (undirected)
If a decision requires numerous input data, you must model many input data elements. You can simplify this by
creating a complex input data element in which you define all input data as attributes.
Example
Example:
To determine a discount, you need data on the purchase value and the customer status. Instead of
creating an input data element for both pieces of information, you create one complex data input element
and configure the purchase value and the customer status as its attributes. In the decision table, both
attributes are available.
Example
Example:
Example
Example:
6. To add more attributes, open the configuration dialog again by clicking the button.
When a lot of information has to be considered for a decision, you can outsource part of the information to sub
decisions. This makes the diagram easier to understand as the dependencies and input values are easier to
see. The logic of each decision is also easier to define.
Example
Multi instance decisions are sub decisions that provide input for other decisions. They are similar to a for-loop
in a computer program: They iterate decisions and expressions over a selected list. The list is contained within
the input data where the input data is either a list or a complex input data type.
Example
Example:
Each position of the purchase agreement is validated to determine the validity of the entire agreement.
1. Add a Multi Instance Decision element to your diagram and name it.
2. Add an Input Data element, which represents the list, and name the element.
3. In the attribute panel, define the input data element as a list in the Is list attribute.
4. Connect the two elements.
To do so, select the multi instance decision element and from its shortcut menu, drag the connector icon to
the input data element.
5. To specify the list over which the multi instance decision must iterate, click in the element.
The configuration dialog opens.
Example
Example:
Example
Example:
Decision logic specifies the details of a decision. This means you define rules in form of a decision table or
literal expression to describe which combinations of data lead to certain results. In addition to the rules, you
must define what happens when inputs meet multiple or no rules. This is done by specifying a hit policy.
In this section, the options for defining a decision logic are explained.
To learn how to specify the hit policy and set the completeness requirement, read more in section Define a hit
policy and the completeness requirement [page 158].
Decision logic can be presented as a table. A business rule that exists in your company is represented by a
decision rule in the decision table. All cells in a table row form a decision rule.
Table inputs are specified in columns. Each input has a specific data type. The output column shows the result
of the applied business rule. Like the inputs, each output also has a data type.
The decision rule then compares input data with the values in the cells.
To create decision rules, you must configure input data in the Inputs column and map them to output data in
the Output column.
Any input data modeled on the canvas is already available when you open decision table. You can add missing
input data by defining input columns in the table.
All input data defined via the table is added as input data elements to the canvas when the table is saved. You
also need to define decision rules and map the outputs.
To define input data and add decision rules, follow these steps:
1. Open the decision table. To do so, select the decision to which you want to add rules and click .
The decision logic configuration dialog opens.
You can also open this dialog via the Decision logic attribute in the attribute panel.
2. Configure the input data. To do so, follow these steps:
1. Double-click New Input in the column header, and enter a name for the input data.
If a dictionary entry exists, you can select it.
Example:
2. Below the input data name, double-click Text, select the type of the input data, and define its options.
If you have chosen a dictionary entry as data input, it depends on the entry's configuration whether
you need to specify the data type.
The following data types are available:
• Enumeration
• Text
• Number
• Boolean
• Hierarchy
• Date
3. In the same way, configure the output data in the Outputs column.
4. In the same way, you can configure the Annotations column to add information to the decision rules.
5. Define the first decision rule:
1. Double-click the left area of the first table cell. A list opens.
2. Select an operator to define the relation between the input and the output.
Read more on operators in section Decision table operators [page 155].
3. Double-click the right area of the same cell. Again, a list opens.
4. Select or enter an input value.
5. In the Outputs column, double-click the cell and enter an output value.
6. With the buttons at the top of the table, you can add more rules, input data, output data, and annotations.
7. To define more rules, you have the following options:
• You can continue defining rules cell by cell as described above.
• With Add rule > Duplicate rule, you can copy and paste existing rules.
• With Import/Export > Text Import, you can add text-based decision rules instead of defining the rules
cell by cell. Read more in section Import decision rules [page 156].
8. Select a hit policy for the decision table and specify the completeness requirement.
elements of and contains only Returns true if the input list contains
and only items the list in the decision table
contains as well.
Instead of defining the decision rules cell by cell, you can import text-based decision rules into the table.
The columns still need to be configured as described above. The individual rules can be in the form of a list,
separated by the delimiters tab, semicolon, or comma.
The import function doesn't overwrite or delete existing rules. Imported rules are always added.
• Relational operators like = and <= must be part of the field they relate to.
• For each rule, you need to start a new line.
• The import only supports the following literal expressions:
• not(value)
• not(value1, ..., valueN)
• !=value
1. Open the decision table and click Import/Export > Text Import in the top-right corner.
The text import dialog opens.
Example
Example:
As an alternative to the logic in the decision table, you can define logic via a literal expression.
Caution
If a literal expression is defined, it supersedes the decision logic in the decision table.
Literal expressions represent predefined logical algorithms or rules that can be used to automatically create
output results for decisions, often but not necessarily in a formal expression language. You can use literal
expressions to add logic that can't be expressed in the decision table, for example, function calls, interim
values, or list manipulation.
Read more about literal expressions in section Using advanced literal expressions (functions in DMN decision
elements) [page 164].
If decision logic can't be expressed formally, you can describe it with natural language. The description doesn't
have to be formal or executable.
Next steps
Create dictionary entries for input or output data in decisions [page 184]
With the hit policy, you define how your decision table manages inputs that are handled by several rules and
inputs for which no rules are defined. There are two types:
• Single hit policies produce one result per input. Here, only one rule is applied at a time, even if several rules
exist.
• Multi hit policies produce an array of outputs. Here, all applicable rules are considered regardless of their
position in the table. The resulting output can be a list or aggregated to a single value.
Unique (single) is the default hit policy. Read more in section Hit policy types [page 160].
To select another hit policy for a decision table, follow these steps:
Example
Example:
3. Select the hit policy. Find details on each hit policy type below.
4. In case of a multi hit policy, select the aggregation:
• Collect (multiple)
• Sum
• Minimum
• Maximum
• Count
Unique (single)
One input combination is covered by exactly one rule. It's assumed that all inputs are independent of each
other, so any combination is possible. Overlapping rules are not allowed.
Unique (single) is the default hit policy. In the decision table, it's indicated with the letter U.
Example
Example:
Depending on the current season, a retailer decides which product group to offer at a reduced price. Only
one product group can be offered, since only one season exists at the same time.
Input Output
Summer beverages
Autumn clothes
Winter food
Any (single)
Multiple rules cover the same combination of input values. This overlap is only allowed if the rules also lead to
the same result.
In the decision table, this hit policy is indicated with the letter A.
Example
Example:
If a credit applicant is younger than 18 years old and is already in debt, the application is rejected.
Otherwise the credit applicant gets a credit.
- no approved
>= 18 - approved
Priority (single)
Multiple rules can apply for one input value. The results are ordered according to their priority. The result with
the highest priority is returned.
In the decision table, this hit policy is indicated with the letter P.
Example
Example:
In a decision table, the logic determines at what age customers get certain discount vouchers. Customers
aged 18 or over get vouchers for sports equipment, and all customers older than 3 vouchers for toys. Both
rules apply to a 30-year-old customer. As the sports equipment has a higher priority, the customer gets a
voucher for this. Consequently, the output list is [sports equipment, toys, clothing].
Input Output
>3 Toys
- Clothing
First (single)
Overlapping rules are allowed, but only the first applicable rule is used. As the rules are evaluated from top to
bottom, you must sort the rules in the table.
In the decision table, this hit policy is indicated with the letter F.
Example
Example:
In a decision table, the logic determines at what age customers get certain discount vouchers. Customers
aged 18 or over get vouchers for clothing, and all customers older than 3 vouchers for sports equipment.
Both rules apply to a 30-year-old customer. As the rule for 18-year-old customers is at the top of the
decision table, this rule serves as the basis for the decision. The customer receives a voucher for clothing.
> 18 Clothing
- Toys
Collect (multiple)
By default, the collect hit policy collects the outputs of matching rules, but can be configured to determine the
sum, minimum, maximum, or count of matching outputs instead.
In the decision table, this hit policy is indicated with the letter C.
Example
Example:
An online shop adds a discount coupon to specific orders. The discount depends on the total sum of an
order. In the decision table below, the outcome differs depending on the aggregation set for the hit policy.
Given a 250$ purchase order, the following applies:
• Without aggregation set, the hit policy returns two coupons (5% and 25% discount) in no particular
order.
• With aggregation set to sum, the hit policy returns one coupon with 30% discount.
• With aggregation set to maximum, the hit policy returns one coupon with 25% discount.
• With aggregation set to minimum, the hit policy returns one coupon with 0% discount and disappoints
the customer in this scenario.
• With aggregation set to count, the hit policy returns 2, which doesn't provide any relevant information
in this scenario.
Input Output
<= 50$ 0%
> 50$ 5%
In the decision table, this hit policy is indicated with the letter O.
Example:
An online shop adds small gifts to orders. The gifts a customer receives depend on the total order sum. If
the order sum is 50$ or lower, the customer receives a discount coupon. If the order sum exceeds 50$, the
customer receives a small pack of high-quality coffee in addition to the coupon.
With an output order hit policy, for the total order sum of 250$ the table below will return the result
[Coffee, Discount coupon], sorted according to the order of the specified output list.
Input Output
- Discount coupon
In the decision table, this hit policy is indicated with the letter R.
Example
Example:
An online shop adds small gifts to orders. The gifts a customer receives depend on the total order sum. If
the order sum is 50$ or lower, the customer receives a discount coupon. If the order sum exceeds 50$, the
customer receives a small pack of high-quality coffee in addition to the coupon.
When applying a rule order hit policy, an input of 250$ will return the result [Discount coupon,
Coffee], sorted according to the order of the applying rules.
Input Output
- Discount coupon
Next steps
In case you have modeled your first DMN diagram, you are already familiar with DMN expressions for decision
logic, e.g. in the form of a simple smaller than statement. These expressions are explained in the chapter Model
a decision [page 142].
You might remember that you selected the corresponding operator from a drop-down list in the Decision Table
Editor.
A simple example is determining a discount based on the total value of a list of purchased objects.
To determine the sum, we need to use SAP Signavio's advanced literal expressions. The expressions are
based on FEEL, the friendly enough expression language specified as part of the DMN standard, which you can
download as PDF at https://www.omg.org/spec/DMN/1.0/PDF .
The single commands can be used in combination, like in the following example:
In the example, we calculate the total purchase sum of a list of items, considering a discount. The variables
used here correspond to the data types defined in Input Data element's attributes and can be set when
simulating the DMN diagram.
The documentation of all available expressions can be found at Documentation of all literal expressions [page
168] .
(1 - DiscountRate) * Sum(ListOfItemPrices)
In our example, we want to determine - as already mentioned above - a discount based on the total value of all
purchased items.
First, create the Purchased items Data Input element. The input should be a list of numbers of the type
currency.
Now create a Decision, connect it to the data input and label it Determine discount. Click the table icon in the
upper left corner of the Decision element to open the Decision Table Editor.
Create a Decision, reference the Data Input element and open the decision table editor.
To activate the literal expression input, click the header and delete the input reference in the table:
After inserting an initial '=' sign, available variables and functions are displayed.
Suggestions appear as you type. Type in Sum and select the Sum function. Then, insert the variable
PurchasedItems as a parameter of Sum:
Now, the decision logic's Input Data is the sum of all purchased items. You can define the decision logic as
usual.
Decision logic for determining a discount based on the total sum of purchased items
For example, you can split a decision into two daisy-chained elements, one with a decision table and another
one with literal expression logic.
'Calculate total sum' and 'Determine discount' as two separate Decision elements.
Open the 'Literal expression tab' and insert the literal expression.
Now, the decision element returns the sum of items as a Data Output and can be referenced by the following
Decision element.
If we create complex literal expressions, we can define variables - so called boxed contexts and reference them
in our decision function:
Caution
If a literal expression is defined, it supersedes the decision logic in the decision table.
This section lists all available literal expressions, grouped by operation type.
Abs
Abs(number):NUMERIC
Count
Round
Round(number,digits):NUMERIC
Ceiling
Ceiling(number):NUMERIC
Floor
Floor(number):NUMERIC
Integer(number): NUMERIC
Modulo
Modulo(divident, divisor):NUMERIC
Percent
Percent(number):NUMERIC
Power
Power(base, exponent):NUMERIC
Product
RoundDown(number, digits):NUMERIC
RoundUp
RoundUp(number, digits):NUMERIC
Sum
Day
Day(datetime):NUMERIC
DayAdd
DayDiff(datetime1, datetime2):NUMERIC
Date
Returns a date using the standard parameters of a date: year, month, day
DateTime
Returns the dateTime using the standard parameters of a data time. The last parameter 'hourOffset' is
optional.
Hour
Hour(datetime):NUMERIC
HourDiff
Hour(time):NUMERIC
Minute(time):NUMERIC
MinutesDiff
MinutesDiff(datetimes1, date2times):NUMERIC
Month
Month(datetime):NUMERIC
MonthAdd
MonthAdd(datetime, months_to_add):DATE
MonthDiff
MonthDiff(datetime1, datetime2):NUMERIC
Now():DATE
Today
Today():DATE
Weekday
Weekday(datetime):NUMERIC
Year
Year(datetime):NUMERIC
YearAdd
YearAdd(datetime, years_to_add):DATE
YearDiff(datetime1, datetime2):NUMERIC
List operations
Append
Adds the element to a copy of the provided list. Returns the manipulated copy.
Example : Append([2.5, 5.8, 4.3], 6.7) returns [2.5, 5.8, 4.3, 6.7].
AppendAll
Adds all elements from the second provided list to a copy of the first one. Returns the manipulated copy.
Example: AppendAll([2.5, 5.8, 4.3], [2.1, 3.5, 7.4]) returns [2.5, 5.8, 4.3, 2.1, 3.5,
7.4].
Zip
Assembles a list of objects out of a list of attributes and multiple lists of values. : Zip(["id", "value"],
[23a3e98, c45da1b], [40, 120]) returns [{id: 23a3e98, value: 40},{ id: c45da1b, value:
120}].
Caution
Before version 10.11.0 of the Decision Manager, the values were passed to the function as a list of lists, for
example:
Literal expressions that used the old Zip function have been automatically transformed to the new syntax.
ContainsOnly
AreElementsOf
Remove
This expression is available only in the Literal Expressions Editor (not in the Decision Table Editor).
RemoveAll
This expression is available only in the Literal Expressions Editor (not in the Decision Table Editor).
Avg
Max
Median
Min
Mode
Returns the most frequently occurring value of the given list. Returns the first (most left) most frequent value,
if several values occur most frequently (e.g. two values appear each two times).
Concat
IsAlpha
IsAlpha(text):BOOLEAN
Determines whether the text contains only alphabetic characters (A-Z, a-z). Umlauts and similar characters
(e.g.Ä, Å ß) must not be included.
IsAlphanumeric
IsAlphanumeric(text):BOOLEAN
Determines whether the text contains only alphanumeric characters (A-Z, a-z, 0-9). Umlauts and similar
characters (e.g. Ä, Å ß) must not be included.
IsNumeric
IsNumeric(text):BOOLEAN
Determines whether the text is a valid number containing only plus or minus sign, digits, commas, and decimal
points.
IsSpaces
IsSpaces(text):BOOLEAN
Len(text):NUMERIC
Lower
Lower(text):TEXT
Trim
Trim(text):TEXT
Returns the text string with all spaces removed except single spaces between words.
Upper
Upper(text):TEXT
Number
Number(text):NUMERIC
Returns the numerical value represented in the text string. Only a period (.) is allowed as a separator.
Number(text, default_value):NUMERIC
Returns the numerical value represented in the text string. Only a period (.) is allowed as a separator. Returns
default_value if unable to convert text into number.
Mid
Returns the character sequence of the length num_chars from the corresponding starting position of a text
string.
Left
Left(text, num_chars):TEXT
Returns the character sequence of the length num_chars from the start of a text string.
Right
Right(text, num_chars):TEXT
Returns the character sequence of the length num_chars from the end of a text string.
Text
Text(num, format_text):TEXT
Returns a numeric value as a text string in a specific format. The format is specified by the placeholders # and
0 and a decimal point..
TextOccurrences(find_text, within_text):NUMERIC
Example: TextOccurrences("can", "Can you can a can as a canner can can a can?") returns
6.
Contains
StartsWith
EndsWith
Logical operators
Not
Not(boolean): BOOLEAN
You can link DMN and BPMN diagrams so that processes can be viewed separately from decisions, with the
advantage that the process is streamlined and the decision is traceable.
1. Open your BPMN diagram and select the task to which you want to link the decision diagram.
2. In the attribute panel, set the Task type attribute to Business rule.
The DMN diagram is linked. To open a preview of it, click in the business rule task again.
Once the BPMN process is published to SAP Signavio Process Collaboration Hub, users can open the decision
diagram in via the BPMN process. With Run decision, they can then add data to the rules defined in the decision
diagram and determine the result of the decision. For more on simulation, read DMN simulation [page 198].
Instead of adding decision rules to a decision of a DMN diagram, you can integrate the decision logic from
another DMN diagram.
1. Open the decision table and click Link on the left side of the dialog.
The configuration dialog to create a link opens.
2. Navigate to the DMN diagram and select the decision you want to link.
3. Confirm with Link diagram.
The decision of the DMN diagram is linked.
Caution
In an older version of the decision logic editor, you were able to link a diagram without selecting a decision.
Such a link is incomplete and can't be read out by the simulation and test lab features. If you find such a
link, always edit it so that it links the decision.
If you want to run a decision multiple times with different data input, you can link it to a business knowledge
model. If you then link the business knowledge model to other decisions, they can reuse the logic of the linked
decision. This is called a boxed invocation.
Boxed invocations provide decision logic and input type information as a generic function, whereas decisions
directly linked to other decisions provide not only the input data types, but the specific input data objects.
In the following example, an insurance premium is calculated based on the applicant's and their spouse's risk
level. For each person, the same decision logic determines a different risk level. A link via a business knowledge
model allows calling the linked decision model with different data inputs. In contrast, a direct link to a decision
diagram will fail to distinguish between the two data sources.
To link a decision to a business knowledge model, click in the business knowledge model and select the
decision you want to link from the configuration dialog.
To reuse the logic of the decision linked to the business knowledge model, follow these steps:
1. Open the decision table and select the Invocation tab on the left side.
2. Map the linked and the invoked decision's input data.
3. Confirm with Apply.
The boxed invocation is set up.
You can find more information on boxed invocation in the DMN specification at https://www.omg.org/
spec/DMN/1.1/ .
Next steps
How to create dictionary entries that modeling users can use as input or output data in decisions of DMN
diagrams.
Caution
A workspace administrator needs to set up a dictionary category of which the entries can be used for DMN
modeling.
To create a dictionary entry for input or output data in decisions, create an entry in the dictionary as usual.
Read more in section Create new dictionary entries [page 88].
You need to create the entry in a dictionary category that is activated for DMN modeling.
You can tell if a category is activated for DMN modeling when its entries have the following settings:
Setting Description
Technical name If the dictionary entry is used as a data object for input or
output data, you can add a domain-specific export name.
Note
If the technical name and the class name are set, only
the class name is exported.
Class name If the dictionary entry is used as a data definition, you can
add a java source reference.
Note
If the technical name and the class name are set, only
the class name is exported.
Type definition You can specify the data type, the following options are avail-
able:
Example
Example:
With the DMN Test lab, you define and run test cases in order to check whether a DMN diagram fulfills certain
requirements. For example, you can ensure that diagrams still comply with the initial decision logic after
being extended, and you can control the correctness of specific input combinations and outputs in complex
diagrams.
To open the Test lab, select the diagram you want to test in the explorer and click Edit > Test DMN diagram.
After you have created all necessary cases, you can save them by clicking the Save button.
Note
To delete a test case, it must be saved first. To do so, click onto the number of the saved test case(s) you
would like to remove, then click Save.
In the following simple case, we want to determine a discount. The only input parameter here is the purchase
value. In the first test case, no value is given for the expected result as indicated by the red X on the left in the
result column. In the second case, the actual discount corresponds with the expected result as indicated by the
green check mark icon. In the third case, the expected result is different from the actual result, as indicated,
again, by the red X.
Often, you want to find out why a test case is producing a certain output. With the DMN simulation [page 198]
you can inspect a decision's behavior, for example to see exactly which rules fire for your input data set. To
open the simulation tool, select a test case and click Inspect in Simulation:
Then, the simulation tool applies the input data of your test case automatically.
To keep test cases when exchanging diagrams between SAP Signavio workspaces or using the test cases in
other tools, you can export and import the test cases as JSON files.
Caution
To export test cases for a diagram, open the Test lab and click Export Test Cases. The file is saved to your
browser's download folder. By default, the file is named after the diagram.
You can import test cases created in other software tools. To do this, you must convert the test cases into the
format supported by the Test lab. We recommend creating a template JSON file for test cases and adding the
existing test cases to it.
1. Open the Test lab and create a test case as described in section Create test cases [page 186].
2. To get a format template for a test case, enter one example for inputs and expected outputs.
3. To get the IDs of the values, enter examples for enumerations and attributes of complex data types.
4. To export the template file, click Export Test Cases.
The file is saved to your browser's download folder.
5. Open the template file in any editor and add your test cases to the testCases section.
Caution
Before you start customizing the template file, we recommend creating a copy as backup.
Read more on the file structure in section Structure of a test cases file [page 189].
6. Save your changes in the file and return to the Test lab.
7. To import the file with your test cases, click Import.
8. Select the file and click Open.
Your test cases are imported and added to the test cases you have already created.
{
"inputParameterDefinitions": [
{
"id": "DIAGRAM_ID/SHAPE_ID",
"shapeId": "SHAPE_ID",
"diagramId": "DIAGRAM_ID",
"modelName": "MODEL_NAME",
"requirementName": "INPUT_DATA_NAME"
},
...
],
"outputParameterDefinitions": [
{
"id": "DIAGRAM_ID/SHAPE_ID",
"shapeId": "SHAPE_ID",
"diagramId": "DIAGRAM_ID",
"modelName": "MODEL_NAME",
"requirementName": "TOP_LEVEL_DECISION_NAME"
},
...
],
"testCases": [
{
"inputValues": [
{
"type": "number|string|date|time|datetime|boolean|complex|
enumeration|hierarchy|list",
"value": "INPUT_VALUE"
},
...
],
"expectedValues": [
{
"type": "number|string|date|time|datetime|boolean|complex|
enumeration|hierarchy|list",
Caution
For convenience, the Test lab export adds name elements, for example name, modelName, and
requirementName, to add context to the exported file. The name elements aren't imported. However,
you must not change any name element, otherwise the import will fail.
Besides these name elements, all elements in the test cases file are required, otherwise the import will fail.
parameter definition
The ID is composed of
the diagram ID and the
shape ID as follows:
diagramID/shapeID
shape
DMN diagram
For outputParameter-
Definitions: Specifies
the shape name of the
top-level decision ele-
ment.
Values of type
"date" must be
represented as
ISO formatted
strings, for exam-
ple "2015-12-31".
Values of type
"time" must be
represented as ISO
formatted string,
for example
"T23:59:59Z" or
"T23:59:59-02:00"
.
For values of
type "complex",
read more in sec-
tion Complex value
[page 195].
For values of
type "enumera-
tion", read more
in section Enumer-
ation value [page
197].
List value
JSON example:
{
"type" : "list",
"value" : [ {
"type" : "number|string|date|time|datetime|boolean|complex|enumeration|
hierarchy",
"value" : "INPUT_VALUE"
}, {
"type" : "number",
"value" : "INPUT_VALUE"
}, {
...
} ]
}
Complex value
JSON example:
{
"type" : "complex",
"slots" : [ {
"id" : "0",
"value" : {
"type" : "number|string|date|time|datetime|boolean|complex|enumeration|
hierarchy|list",
value
JSON example:
{
"type" : "enumeration",
"value" : "0"
}
Hierarchy value
JSON example:
{
"type" : "hierarchy",
"value" : [ "1", "4" ],
}
The decision management extension of SAP Signavio Process Manager allows you to model, manage and
better understand complex business decisions. In the DMN simulation tool, you can simulate business
decisions by applying data to the rules that are defined in a decision diagram. The simulation tool helps you
to understand dependencies between sub-decisions and to identify scenarios for which no rules have been
established.
Note
The DMN Simulation is also available as an additional feature in SAP Signavio Process Collaboration Hub.
To open the DMN simulation tool, select the diagram in the explorer and click Edit - Simulate DMN diagram.
Select a decision in the diagram, either by clicking on it or by using the dropdown menu in the top right corner.
Then, scroll to the Inputs section and fill in the data of your simulation scenario. The Outputs section shows
the decision output as computed by the simulation tool. The Wildcard mode toggle affects the evaluation
semantics. Wildcard mode turned on means that empty input values are replaced with wildcards, which will,
for example, match all conditions in decision tables. When turned off, empty input values will remain undefined
during evaluation.
If the Wildcard mode is activated and one or multiple input parameters are not defined, the simulation
tool will determine the set of possible output values. This is helpful, for example, if in specific application
scenarios some input values remain unknown.
The progress bars in the decision elements indicates the extent to which data inputs are defined so far.
When scrolling down, you can see a decision table overview that highlights the rules that apply in the current
scenario:
The rules that apply to the provided input data are highlighted in green.
The SAP Signavio diagram comparison tool allows you to easily compare two diagrams, as well as different
revisions of one diagram. In the revision comparison, details about all changes in a diagram over time are
documented.
To open the comparison tool, select a diagram (or, in case you want to compare two different diagrams and
not revisions: two diagrams) and click Edit, then Compare revisions/diagrams in the top drop-down menu of the
explorer.
To load a different diagram for comparison, click Choose revisions/diagrams in the upper right corner of the
tool and select both diagrams to be compared in the dialog.
Clicking the pen icon of a changed element gives you detailed information about the adjusted element
properties.
To narrow down the changes, you can deactivate one or multiple check boxes in the panel below the canvas and
exclude changes made to attributes or to specific element types:
To learn more about the basic usage of the diagram and revision comparison tool, read the section Comparison
view [page 66]. The following section explains how to extract DMN-specific information from the comparison
tool.
To view the changes made to a Data Input element, select the element to see the exact changes.
To view the changes made to a Decision Table, select the element to access an overview of the changes.
How to create value chains in the SAP Signavio Process Manager editor.
With value chains, you can create high-level perspectives on your process landscape.
Each modeling element in a value chain represents a process or process group of a specific business unit. You
can link the elements in chronological order and show the hierarchical relationships between processes and
process groups.
In this section, the diagram elements and editing functions that are only available for this notation are
described.
For general creation and editing options that are available for all notations, read more in section Modeling [page
35].
Process
Collapsed process
The collapsed process element represents a business process that is linked to another process diagram.
To link the collapsed process element with a new or existing process, click the + symbol in the element.
Group
Process link
Use this element to create a hierarchy of process elements and process group elements.
Text note
Use the text note to add information to the diagram or a diagram element.
Association
To change the orientation of a process element or collapsed process element, select it and click at the
bottom. You have the following options:
• Left to right
• Right to left
• Top down
• Bottom up
Rotate text
To rotate text in a diagram element, select the element and in the attribute panel, choose a rotation value for
the Text direction attribute.
You can add Live Insights shapes to display the result of a SAP Signavio Process Intelligence investigation in a
value chain. Read more in section Add Live Insights [page 61].
11.5 ArchiMate
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
In SAP Signavio Process Manager, you can model enterprise architecture diagrams in the ArchiMate notation,
an open enterprise architecture modeling language for describing, analyzing, and visualizing enterprise
architectures within and across business domains.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
ArchiMate is an open enterprise architecture modeling language for describing and visualizing enterprise
architectures within and across business domains.
Developing enterprise architecture descriptions enables you to base requirements and stakeholder concerns
regarding your IT and business systems on formal and uniform models.
ArchiMate is a lightweight but comprehensive language that enables you to define the architecture of your
business and IT systems using a service oriented view model. It allows you to see your process architectures
over time. This is helpful in many areas, such as transformation and migration planning.
https://pubs.opengroup.org/architecture/archimate3-doc/
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
To create an ArchiMate diagram, open the Explorer and choose New ArchiMate 3.0 . Your browser will
open a new tab with the ArchiMate diagram canvas.
Find instructions on how to edit diagrams in the sections Add and connect elements [page 41] and Move and
change elements [page 48].
You can easily link BPMN diagrams to ArchiMate's Business Process objects.
Once you have created the business process object in ArchiMate, select the element and choose the attribute
Business process reference in the attribute panel.
Alternatively, you can choose (reference) in the upper right corner of the Business Process object.
Within the ArchiMate Editor it's easy to make use of the dictionary, see The Dictionary [page 83] for details.
The dictionary is modeling language-independent, meaning you can access entries you created from BPMN
diagrams in ArchiMate and vice versa.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
Please contact our SAP Signavio service experts from the SAP for Me portal .
CMMN is a notation that was created to allow more flexibility in the business process landscape. SAP Signavio
Process Manager supports CMMN version 1.1.
About CMMN
In a business process that has variation, it may be more efficient for a case worker to determine the sequence
in which to perform a set of tasks. For example, a hotel guest may always go through the same process when
checking in and checking out, while the regularly tasks to clean the room may vary from day to day.
In general, many BPM scenarios include actions that may diverge from the common sequence flow, within
a framework of set tasks. CMMN supports the flexibility of these workflows. The notation is designed for
scenarios when a case worker can decide in what order tasks or sequence flows shall be performed. A CMMN
sequence flow may be triggered by an event (event listener), a state (milestone) or with an action (task).
In SAP Signavio Process Manager, you can model the standard framework of the corresponding process in a
BPMN diagram and then link a BPMN sub-process to a CMMN diagram that defines flexible sequences. You can
also change a task in a BPMN diagram to a sub-process that links to a CMMN model, to define a number of
flexible actions more accurately.
You can create CMMN diagrams in the explorer like any other diagram and edit them in the editor. This chapter
explains the CMMN Elements and their alignment options on the modeling canvas. See Basic modeling with
the Editor [page 35] to learn about modeling diagrams with the editor.
To create a new CMMN diagram in the explorer, choose New Case Management Diagram (CMMN 1.1) .
The editor opens with a blank modeling canvas, ready for you to edit the diagram.
Starting with a blank canvas in the editor, you can add elements from the Shape Repository.
You can use the following elements from the shape repository to model your CMMN diagram.
The case plan model contains the case model. The case plan model encloses the whole diagram. You can place
the element first and resize it with the growing diagram by dragging its lower right corner, or you can model
the case and place the case file element when you have finished adding and connecting the other diagram
elements.
To label the file, enter a name into the ‘naming slip’ at the top left of the element. You can also attach an exit
criterion to the case plan model to indicate that the incoming sequence flow ends and completes the case.
Task
Tasks are the central elements in CMMN and BPMN notations. A task models a single action that needs to be
performed. In addition to the ordinary task, there are five different types of task elements in CMMN:
The model can depict each task as an ordinary task element or as a discretionary task, which is not obligatory
and may be performed at the case worker’s discretion.
• A non-blocking human task does not stop the sequence flow. In the case model, the task does not take
any time to perform. The task is complete at the same moment it starts, and the sequence flow continues
unstopped. All other tasks are ‘blocking’ by default.
A ‘process task’
• A decision task links to a DMN diagram. To link a diagram, click the symbol in the upper left corner of the
element. To learn more, see Integrating CMMN diagrams [page 219].
A ‘decision task’
• A case task links to another CMMN diagram. To link a diagram, click the symbol in the upper left corner of
the element. To learn more, see Integrating CMMN diagrams [page 219].
Discretionary Task
Every task type mentioned above also exists as discretionary task in the CMMN 1.1 definition. This means that
the case worker may decide whether to perform the task for that case.
In SAP Signavio Process Manager, you can create a discretionary task by creating an ordinary task of
the necessary type, for example a non-blocking human task and defining it as discretionary. Select the
corresponding task and open the Attributes panel on the right. Click the Discretionary attribute and activate the
checkbox.
When checking the box, the ordinary task transforms into a discretionary task.
Stage
Stages divide cases into subdivisions. You can group sequence flows, tasks and/or (sub-)stages into a stage.
• You can also define a stage as a discretionary stage. Select the corresponding stage and open the
Attributes panel on the right. Click the discretionary attribute and activate the checkbox.
An expanded stage.
Milestone
Milestones are sub-goals within the process model. They indicate that a certain point or stage within a case has
been reached or completed.
A milestone element
Sentries
You can attach the diamond shaped entry criterion and exit criterion symbol (called ‘sentries’) to any task,
milestone, stage or case file. There, they define dependencies or the direction of the sequence flow. Sentries do
not need to be attached to other elements - they may also stand alone within a sequence flow.
• The entry criterion indicates that the incoming sequence flow(s) directly attached to the sentry is/are
necessary to be finished before the sequence flow can continue.
In this example, the claim analysis starts when a claim with more than €100,000 has arrived and the claim
information document is available. The check finishes when a claims evaluation report has been created:
The entry and exit criteria mark the beginning and the end of this stage
You can attach several sentries of one type to an element. Each sentry defines its own entry or exit criteria for
its element. Two or more sentries of one type attached to one element define a logical ‘or’ relationship, while
several sequence flows attached to one sentry form a logical ‘and’ relationship.
If all workflows of one entry criterion have arrived at the element, the corresponding task can be performed. If
several criteria have to be met, more than one sequence flow can be attached to one sentry element. Similarly,
you can attach several exit criteria to an element. All sequence flows that exit one sentry will be executed,
unless a discretionary task follows.
Event Listeners
A listener waits for something to happen, usually to then trigger a new sequence flow.
The event listener, timer event listener and user event listener elements (left to right)
A case file item represents a data file or document that contains information that is relevant to the case, such
a patient file. Use a connector to attach a case file item to another element, to show that the other element’s
execution uses its data. It can also function as a trigger or a result and thus can stand at the beginning or at the
end of a sequence.
Other Elements
Connectors
A connectors between CMMN elements defines a relation. An entry criterion or exit criterion defines the
sequence flow direction or association.
Plan Fragment
A plan fragment contains a group of elements that exist outside the cases’ runtime. Plan fragments are
discretionary, as indicated by the dotted lines. Also, elements contained inside the plan fragment may contain
Planning Table
A planning table signifies that discretionary tasks are present. A collapsed planning table indicates that
discretionary tasks are not displayed, whereas an expanded planning table indicates they are shown.
A (collapsed) planning table (default) signifies that collapsed (or hidden) discretionary tasks are present in the
diagram. The hidden tasks are not modeled in SAP Signavio Process Manager. Instead, the modeler attaches
the planning table to a stage, human task (only) or case plan model to signify that (hidden) discretionary tasks
are available.
To hint that modeled, visible discretionary tasks are available in the corresponding stage or plan fragment,
add an expanded planning table to the element by unchecking the box defining the collapsed attribute in the
attribute panel.
Text Annotation
A text annotation contains additional textual information about the diagram, an element or a group of
elements.
CMMN Attributes
The following attributes can be set in the attribute panel by checking or unchecking the value of the
corresponding element. When the value is enabled, an icon will appear on the corresponding element or the
elements appearance will change, as depicted below.
• The discretionary attribute can be set for all kinds of tasks and stages. If the attribute is activated, the
task/stage may be performed if the case worker decides it is necessary. Plan fragments are by default
discretionary, this cannot be changed as it is a pre-defined condition in CMMN.
• The autocomplete attribute can be set for stages and case plan models.
• The manual activation attribute can be set for all kinds of stages and tasks. If the attribute is activated, the
corresponding element has to be triggered manually.
• The repetition attribute can be set for milestones, stages and tasks. If the attribute is activated, the case
worker will evaluate if the task needs to be repeated every time it is finished. If the result is ‘yes’, the task
will be repeated.
• The required attribute can be set for milestones, stages and tasks. If the attribute is activated, the
corresponding action needs to be completed for the sequence flow to continue or the containing element
to be completed.
You can seamlessly integrate CMMN diagrams with DMN and BPMN diagrams in your process landscape. You
can, for example, embed a CMMN model in a BPMN process by use of the BPMN sub-process as depicted
below. This allows you to model the static part of a process in BPMN and only depict the flexible part in a
CMMN model.
To add a diagram link to a CMMN model, first add the corresponding CMMN element:
Click the symbol in the top left corner of the diagram element and select a diagram of the corresponding type
in the dialog that appears or choose to create a new one. Click Link diagram to confirm.
If you chose to create a new diagram, the editor opens in a new tab, ready for you to edit the new diagram. After
modeling the new diagram, save both the new one and the CMMN model the new diagram is now linked to.
To add to CMMN model link to a BPMN diagram, add a collapsed subprocess and click the + -symbol at the
bottom of the element. In the dialog that opens, choose a CMMN model or create a new one by choosing Case
Management Diagram (CMMN 1.0) at the top under Create new diagram. Click Link diagram to confirm.
If you chose to create a new diagram, the editor opens in a new tab, ready for you to edit the new diagram. After
modeling the new diagram, save both the new one and the CMMN model the new diagram is now linked to.
You can also link CMMN diagrams in value chains the same way to create complete process levels that also
show in classic SAP Signavio Process Collaboration Hub. For more information on diagram hierarchy levels in
your process landscape, see Creating process hierarchies [page 58].
Use Navigation Maps to provide all users with an overarching linked view of all your processes.
With Navigation Maps, you create graphical process views. Similar to value chains, you create high-level
perspectives on your process landscape. Navigation Maps are more flexible than value chains or other
modeling languages and don't follow a strict standard. You can upload custom images to use as modeling
elements.
All elements except Live Insights can link to diagrams, folders, or URLs.
The most common use case is creating a navigation map that matches your corporate identity as an entry
diagram for SAP Signavio Process Collaboration Hub.
Use Navigation Maps to provide all users with an overarching linked view of all your processes.
• In the explorer of SAP Signavio Process Manager, choose New and select Navigation map from the drop-
down list. The editor opens with a blank canvas.
• In SAP Signavio Process Collaboration Hub, choose Create and select Navigation map. The editor opens
with a blank canvas.
To make content available for all users in SAP Signavio Process Collaboration Hub, it needs to be published.
• In the explorer of SAP Signavio Process Manager. See section Publishing diagrams in SAP Signavio
Process Collaboration Hub [page 272].
• In SAP Signavio Process Collaboration Hub. See section Publish and unpublish diagrams.
Related Information
Use Navigation Maps to provide all users with an overarching linked view of all your processes.
This section describes the navigation map elements and their options. All elements except Live Insights can link
to diagrams, folders, or URLs.
Bold
Italic
Shapes
• Triangle
• Rectangle
• Ellipse
• Arrow
• Line
Some formatting is possible from the toolbar, for details see section Editor toolbar and keyboard shortcuts
[page 38].
Additional formatting options are available in the Attributes panel, for example border style.
For details how to move and change a shape, see section Move and change elements [page 48].
In the Attributes panel, you can add an outgoing link to a shape, see section Add links to elements [page 224].
Live Insights
With the Live Insights shapes, you can add insights and KPIs you want to monitor to BPMN diagrams, value
chains, and navigation maps.
For that, you add a Live Insights shape to your diagram and link it with a widget from SAP Signavio Process
Intelligence. Users can then view the Live Insights in SAP Signavio Process Collaboration Hub.
In SAP Signavio Process Intelligence, thresholds need to be defined for the widgets that are linked to Live
Insights shapes. In SAP Signavio Process Manager, the color of the shape indicates how the current result of
The color of a shape is only visible in SAP Signavio Process Collaboration Hub. In SAP Signavio Process
Manager, the shapes stay grey.
Read more about Live Insights in section Add Live Insights [page 61].
Images
You can upload custom images to use in navigation maps. All images available for navigation maps are in the
Image Management.
Images for upload need to be in the SVG format. To prevent possible security problems, each SVG file you want
to upload is checked. Read more about the validation criteria in section Validation criteria [page 68].
Images uploaded with the image manager while creating navigation maps have a size limit of 50 kB for each
image file.
Upload images
Note
• Only images available in the Image Management can be added to navigation maps.
• Images that have been uploaded can only be deleted by your workspace administrator.
You can add links to all elements in a navigation map except Live Insights. You can link to another diagram or
folder in your workspace, or you can link to a URL.
2. In the Link row, click the right column and then click (more options). The dialog for adding a link opens.
3. Select one of the options:
• Create a new diagram: Select the type of diagram. The editor opens with a blank canvas.
• Use existing diagram or directory: Select a diagram or a folder to link in the folder structure.
• Use web link: Paste the URL to the input field.
4. Save with Link.
Example
In SAP Signavio Process Collaboration Hub, elements with a link show a movement effect when users hover
over them.
Example
For navigation maps, you can link dictionary entries from all categories to the following modeling elements:
• Text
• Shapes
• Images
Related Information
SAP Signavio Process Manager supports a comprehensive set of modeling notations. This article lists the ones
that are typically not relevant for the most common use cases.
Organizational Charts
Organizational charts outline the internal structure of a company. Illustrating a company this way shows the
internal hierarchy and how each role relates to others in the same organization.
Choreography Diagrams
Choreography diagrams depict the details of complex collaboration between process participants. This allows
for an analysis of how information is exchanged and how participants coordinate their actions. Choreography
diagrams are part of the BPMN standard, but are not widely used. We recommend staying with BPMN process
diagrams.
For more information on choreography diagrams, see the OMG BPMN specification document .
Conversation diagrams focus on communications between process participants. They allow for the viewing of
relationships at a glance. Conversation diagrams are part of the BPMN standard, but are not widely used. We
recommend sticking to BPMN process diagrams when modeling process participant interactions.
For more information on Collaboration diagrams, see the OMG BPMN specification document .
Event-driven process chains (EPC) are used to model business processes. EPCs capture and visualize
processes, but are - unlike BPMN - not executable. EPCs generally focus on the lower levels of the process
hierarchy (operational sequences of processes). While EPCs were popular in some European countries in the
late 90s and early 2000s, they have now been eclipsed by BPMN, which is more appealing to both business
users and technical experts. We don't recommend using EPCs.
Use case diagrams are used to view what actions can be performed collaboratively between systems and
users. They are a part of the UML (Unified Modeling Language) standard.
Class diagrams show the properties, methods, and relationships of a system's classes. They are commonly
used to describe object-oriented programing code. They are a part of the Unified Modeling Language (UML)
standard.
Note
This section describes all options for this function. Which options are available depends on your license and
the settings made by your workspace administrator.
QuickModel makes capturing BPMN processes very fast. With QuickModel, you enter information about a
process into a table. A process diagram is dynamically generated from this table.
• to create BPMN diagrams even if you are unfamiliar with the modeling conventions
• to speed up diagram creation for complex processes by modeling the main path first
• to see at a glance if information is missing in an existing BPMN diagram and to add it with low effort
• model one sequence of tasks including the start and end events
• specify the organizational unit for the pool and assign participants to tasks in lanes
• specify main attributes for tasks, for example IT systems and data artifacts, as well as custom attributes
Additional BPMN elements, such as decisions and parallel sequences, can be added later in the graphical
editor.
In the QuickModel editor, you create BPMN 2.0 diagrams by entering process information into a form and a
table.
To customize the activities list, click and select the columns you want to display. To set the selection as
your default, use Save as default.
Note
4. Under Activities, add the tasks of your process and specify their attributes, read more in section Add tasks
and specify attributes [page 232].
The diagram preview updates dynamically.
5. Confirm with Save.
The diagram is saved.
You can close the diagram or open it in the editor. To open it, open the user menu and choose Graphical
Editor.
Example
Example
Note
The order of the tasks in the table corresponds to the order of the tasks in the diagram.
1. Double-select a cell in the What? column and type the task name.
Read more on the meaning of the columns in section Overview over main attributes for tasks [page 228].
2. Continue with one of the following options:
• To add another task, choose Enter.
• To specify an attribute of your first task, press the tab key.
You can customize the columns in the activities list, read more in section Show or hide task attributes [page
228].
While you type the name of tasks and attributes, dictionary entries can be suggested. To link a dictionary entry
to the task or attribute, select the entry and press Enter.
When a task is linked to a dictionary entry, you can rename the task. This has no effect to the dictionary entry.
Renaming doesn't work for attributes.
How to create dictionary entries is described in section Working with the dictionary [page 83].
You can't change the order of tasks in the activities list. You can only add a task between two existing ones. To
do so, select the lower task and choose Add activity above.
Remove a Task
To remove a task, select it in the activities list and choose Remove activity.
Related Information
You can edit BPMN diagrams in the QuickModel editor even if they weren't created with QuickModel.
The tabular activities view provides an overview of the tasks and attributes. This way, you can quickly check
diagrams for completeness and add missing tasks and attributes.
Editing Options
You can add, rename, and remove the following elements in the QuickModel editor:
• diagram attributes
• tasks and collapsed subprocesses
• roles
• task attributes
To add a task, click the plus sign in the first column, double-click the first cell in the new row, and specify the
name.
Example
Example
You can't change the order of tasks in the activities list. You can only add a task between two existing ones. To
do so, select the lower task and choose Add activity above.
To remove a name for a task or an attribute, select the cell and press the Del key.
Collapsed Suprocesses
Existing collapsed subprocesses are displayed and can be edited like tasks.
In the QuickModel editor, editing of diagrams with decisions and multiple task flows is limited as follows:
• Roles can't be edited. The Who? column is then marked with an asterisk.
• You can only rename tasks, you can't add or remove tasks.
To open a diagram in the QuickModel editor, you have the following options:
• Select the diagram in the explorer of SAP Signavio Process Manager and click Edit > Edit QuickModel.
• Go to the diagram in SAP Signavio Process Collaboration Hub and click > Edit with QuickModel. Read
more in section Actions.
To switch from the graphical editor to the QuickModel editor and back, use the options QuickModel and
Graphical editor in the user menu.
Read more on the graphical editor in section Editor overview [page 36].
While you type the name of tasks and attributes, dictionary entries can be suggested. To link a dictionary entry
to the task or attribute, select the entry and press Enter.
When a task is linked to a dictionary entry, you can rename the task. This has no effect to the dictionary entry.
Renaming doesn't work for attributes.
How to create dictionary entries is described in section Working with the dictionary [page 83].
Related Information
Get an overview of the SAP Signavio Process Manager Simulation tool. With the Simulation tool you can
visualize process runs and analyze processes based on step-by-step, configurable one-case, and multiple-case
scenarios. This provides information about cost, cycle times, resources, and bottlenecks in your processes.
With the BPMN simulation tool you can visualize process runs and analyze processes based on step-by-
step, configurable one-case, and multiple-case scenarios. This provides information about cost, cycle times,
resources, and bottlenecks in your processes.
Note
Modeling users who only have read access to a diagram can use the BPMN simulation tool, but can't
manage the diagrams simulation scenarios.
Simulating BPMN diagrams can help to increase process awareness and can answer specific questions like:
Caution
• Open explorer, select a model and choose Edit Simulate BPMN Diagram .
• When you have opened a diagram in the editor, QuickModel or the diagram comparison tool , expand the
user menu and click Simulation.
• Step-by-step simulation [page 237]: Step through the process element by element and focus completely
on the process flow.
Note
• Multiple-case simulation [page 240]: Simulate multiple process runs, taking into account configured
probabilities and analyzing quantitative data and bottlenecks.
To create and manage simulation scenarios, read the Managing simulation scenarios [page 247] section.
You can export the results of the multiple case simulation as an XLS spreadsheet, read the Exporting
simulation results [page 251] section.
If you're unsure what specific metrics in the simulation results mean, read the Simulation metrics result [page
240] section.
In case you encounter issues with the BPMN simulation tool, read the Troubleshooting issues with the BPMN
simulation feature [page 258] section.
With the step-by-step simulation function you can go through a process element by element and focus
completely on the process flow.
Example
1. Open the BPMN simulation tool. Read the Access the BPMN simulation tool [page 236] section.
2. Select the Step by Step function.
3. Choose Play.
4. Choose through the process flow step-by-step.
When passing an exclusive (XOR) gateway, determine the next sequence flow, by clicking the required
path.
5. Choose Restart to restart the step-by-step simulation.
Read how to use the one-case simulation function in SAP Signavio Process Manager. With the One-case
simulation function you can simulate one specific case and analyze costs and the time consumption for that
case.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
With the one-case simulation function you can simulate one specific case and analyze costs and the time
consumption for that case.
Before running the one-case simulation, configure a scenario on which the simulation is based on. Read the
Managing simulation scenarios [page 247] section.
During the simulation, the simulation tiles display the overall costs, total cycle time and resource consumption
at the current position in the process (left column) and of the complete previous run (right column). The
bottleneck tile is only relevant for multiple-case simulations.
• Cycle time: Refers to the amount of time between start and completion of a process while
• Resource consumption is the overall time process participants committed to process execution.
Example
1. Open the BPMN simulation tool. Read the Access the BPMN simulation tool [page 236] section.
2. Select the One case function.
3. Select a scenario and click Play.
The BPMN Simulator automatically goes through the process flow step-by-step.
4. When passing an exclusive (XOR) gateway, select the next sequence flow. If you don't select the next path,
the simulation continues and selects a path automatically (based on the probabilities given) when the
timer symbol on the top right of the element completes.
Example
Example
Example
Example
Read how to use the Multiple-case simulation function in SAP Signavio Process Manager. With the Multiple-
case simulation function you can simulate multiple process runs which take into account the configured
quantitative figures and analyzing quantitative data and bottlenecks.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
With the multiple-cases simulation function you can simulate multiple process runs which take into account
the configured quantitative figures and analyzing quantitative data and bottlenecks.
Before running the multiple-case simulation, configure a scenario on which the simulation is based on. Read
the Managing simulation scenarios [page 247] section.
During the simulation, the simulation tiles display the overall costs, total cycle time, resource consumption,
and bottlenecks at the current position in the process (left column) and of the complete previous run (right
column).
• Cycle time: Refers to the amount of time between start and completion of a process.
• Resource consumption is the overall time process participants committed to process execution.
Example
1. Open the BPMN simulation tool. Read the Access the BPMN simulation tool [page 236] section.
2. Select the Multiple Cases function.
3. To configure the duration of the simulation, click Duration.
4. Enter the required number of days and click Save.
5. Select a scenario and click Play.
The BPMN Simulator analyzes the selected scenario and displays the results in the process diagram and
on the simulation tiles.
6. For detailed quantitative information on the current run, click More.
Example
Example:
7. To simulate the another run through of all process instances in the previously calculated scenario, click
Play.
The following table shows simulation outcomes on a diagram after running the multiple-case simulation:
Waiting instances Waiting instances display as blue dots placed above the in-
going sequence flow.
Running instances Running instances display as blue dots within the border of a
task.
After running the multiple case simulation, result metrics are available for the current run of the simulation.
• Costs
Costs
The multiple case simulation calculates the average, minimum, maximum, and total costs. The simulation
determines all cost types based on the simulation result. To access the Costs metrics, click the Costs tile.
Example
Example:
The following table discusses the descriptions for each table in the Costs tile:
Table Description
Costs per task The table displays the costs for every task of your process.
It includes average, minimum, maximum and total costs for
each task.
The multiple case simulation calculates the average, minimum, maximum and total cycle times. As for the
costs, the simulation determines the cycle times based on the simulation result. To access the Total cycle time
metrics, click the Total cycle time tile.
Note
The total cycle time can exceed the simulation time span. This can happen for two reasons:
• Your resources can't handle cases fast enough and process instances get delayed.
• The cases that occur in the last hours / minutes of your simulation time frame exceed the time frame
before they are completed.
Example
Example:
The following table discusses the descriptions for each table in the Total cycle time tile:
Table Description
Cycle Time The cycle time of a process instance is overall time needed
for each process instance to complete from start to finish.
The table shows the selected process instance's cycle times
as well as the total sum of all run cycles.
Execution times incl. resources and waiting times The execution times of activities executed within a process
instance can be influenced by the availability of resources as
well as working schedules. The table shows the pure execu-
tion time taken for each activity including the time waiting
for missing resources and the time taken due to working
schedules. Waiting times due to missing resources are listed
as bottlenecks and are available under Bottlenecks [page
246] tile.
Execution times incl. waiting times The table shows how long the execution time took for each
activity including the working schedules and excluding all
available resources. The values are the pure execution times
of tasks in addition to the time a task had to wait because
the assigned resource were unavailable.
Pure execution times Within a process instance, several activities are executed.
These values are the actual execution times of tasks where
someone is actively working on the tasks. The execution can
occur sub-sequentially, delayed or in parallel. The table dis-
plays how long the pure execution time took for each task.
Resource Consumption
The resource consumption lists the consumed time and the workload for each process resource.
The consumed time is the total time a resource spends on executing activities. The workload is the percentage
of the available time a resource is occupied with executing activities.
To access the Resource consumption metrics, click the Resource consumption tile.
Example
Example:
Table Description
Bottlenecks
A bottleneck occurs when a resource's limited availability increases the waiting times of cases. Waiting times
describe how long cases are idle because no resource is available to execute the current activity.
Example
Example:
The following table discusses the description for the table in the Bottlenecks tile:
Table Description
Read how to create and manage scenarios in the SAP Signavio Process Manager Simulation tool. With
scenarios you can configure the data sets used when running the One-case and Multiple-case simulation
functions.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
Before running a one-case or multiple-case simulation, configure the data that the simulation is based on by
creating a scenario.
When you open a diagram in the simulator for the first time, it automatically contains one scenario based on
the diagram's Cost & Resource Analysis attribute. Read the Configure the cost & resource analysis attribute
[page 251] section to configure the Cost & Resource Analysis attribute.
With scenarios you can manage different data sets for simulating one process. You can edit the scenario data
by clicking on the corresponding tabs.
Costs
In the costs tab you can configure the execution costs for each task in the scenario.
Example
Example:
In the duration tab you can configure the execution time for each task in the scenario.
Example
Example:
Note
We recommend a Normal distribution in case the task execution times are likely concentrated
around a certain value.
Frequency
In the frequency section you can configure the start frequency of the start event and the execution probability
of gateways and events in your scenario.
Example
Example:
In the resources tab you can define a roles work schedule and cost per hour.
Example
Example:
You can create an additional scenario by choosing (add). Choose between creating a scenario based on the
Cost & Resource Analysis attributes (Create from template: None) or using the data of another scenario as a
starting point.
To configure the Cost & Resource Analysis attribute, follow these steps:
In SAP Signavio Process Manager use the Export Excel feature to export the results of a Multiple-case
simulation to an Excel XLS file.
You can export the results of a Multiple-case simulation [page 240] as XLS (Microsoft Excel) files. To export
the results, click the Excel Export button below the simulation tiles. An Excel (XLS) file is generated. The file is
saved to your browser's download folder.
• Overview
• Costs
• Total cost charts
• Total time charts
• Resource consumption
• Bottlenecks
• Bottleneck charts
• If more than one simulation scenario was executed, the Excel file includes two extra tabs, one for each
scenario run in the simulation.
Note
If you are using Microsoft Excel 2010, make sure to deactivate the Protected View, by clicking Enable Editing
to make sure the spreadsheet is displayed correctly.
If there are problems with displaying the charts in the report, check if you have opened the report with a
program that allows the editing Excel diagrams. If this is not the case, we recommend to open the report
with one of the more recent versions of Microsoft Excel.
Overview
The Overview tab contains general information about the simulation runs.
Costs
The Costs tab displays the minimum, maximum and average costs of the simulation runs and task executions.
The Total cost charts tab visualizes the cost relation of executed tasks in the latest runs. If multiple runs were
executed the latest and previous runs of total costs data display in the tab.
The Total cycle time of a process instance measures the time between process start and process completion.
The tab shows process instance cycle times and activity execution times:
The Total time charts tab visualizes the data of the Total cycle time tab. If multiple runs were executed the latest
and previous runs of the total cycle time data display in the tab.
The Resource consumption tab contains information about all Resources (lanes) which where occupied with a
task and displays their workloads in relation to reach other:
The Resource consumption charts tab visualizes the data of the Resource consumption tab. If multiple runs
were executed the latest and previous runs of the resource consumption data display in the tab.
Bottlenecks
The Bottlenecks charts tab visualizes the data in the Bottlenecks tab:
Scenario Tabs
The last two tabs contain information about each scenario's properties:
When using the SAP Signavio Process Manager Simulation tool certain process conditions are required. If
those conditions are not met, issues may occur when using the simulation tool. If you experience any issues
when using the Simulation tool, read this section to troubleshoot those issues.
• The syntax of the diagram must follow BPMN 2.0 syntax rules. The process flow mustn't be interrupted.
• To check if a diagram follows BPMN 2.0 syntax rules, use the Check syntax option in the Editor.
• Elements that affect the process flow, but cannot be clearly specified regarding their impact on the process
flow, mustn’t be used. Example elements are the inclusive gateways, non-interrupting boundary events,
conditional sequence flows, message flow and subprocess.
The standard search is a full text search. With (advanced search), you can filter results. You can save your
searches as smart folders for quick access.
• To search, enter the search terms into the search box and choose Enter.
• Diagram titles
• Attributes of diagrams and elements
• Element labels
• Comments
• Revision information
• Content of uploaded files
• Dictionary entry links
Wildcard (*) The wildcard character (*) is a placeholder for one or more
characters.
For example, the search term lab*r returns results for both
British English (labour) and American English (labor).
AND Connect search terms with AND to only get results that con-
tain all terms.
Advanced Search
With the advanced search, you can limit the search to a specific attribute. Attributes on diagram and element
level can be selected.
Smart Folders
The (smart folder) is created in the Smart Folders directory in the navigation panel of the explorer.
Caution
The content of a smart folder changes dynamically according to the content of your workspace.
When you select (smart folder) and choose Edit, the following actions are available:
• Move
• Delete
• Change name/description
Search Results
If a search returns many hits, they are displayed over several pages. To navigate the result pages, use the arrow
buttons next to the page number.
By default, search results are displayed in icon view. For list view, choose (list view) in the top right corner.
For dictionary entries, the category shown is Linked diagrams of dictionary item. To search for dictionary
entries, use the search function in the dictionary. See section Full-text search [page 83] for details.
To access the folder in which an item is located, select the item and click Go to parent.
To leave the search results view, select any folder in the directory.
In SAP Signavio Process Manager, there are several ways to enable collaborators to contribute to your business
process and business decision landscape.
Fellow modelers in your workspace can by default edit and comment on all diagrams in the workspace's
Shared documents folder. You can also invite modelers to edit to call attention to a diagram. They can also
preview diagrams in SAP Signavio Process Collaboration Hub which also provides a reader-friendly diagram
presentation, with its full screen view and detailed documentation.
Stakeholders who do not have access to your workspace can be invited to comment on diagrams. The modeler
needs to send an invitation from the Explorer's Share menu to grant access. For external persons, the link acts
as a key to SAP Signavio Process Collaboration Hub where unregistered stakeholders can see and comment
on diagrams. The stakeholders click a link they receive by email that allows them to see and comment on
diagrams.
Exporting diagrams and sharing, saving or printing them is another collaborative option for modelers. This way,
diagrams can be transferred between SAP Signavio workspaces (SGX) and SAP Signavio and other modeling
softwares (BPMN 2.0 conform XML), saved locally, and sent by email (PDF, SVG or PNG) or printed out.
After you created or updated a diagram you might want to notify your fellow modelers and invite them to
further refine the diagram. Or if you noticed that a diagram has not been updated for a long time, you might
want to invite your colleagues to check its actuality and have it updated if necessary.
Note
To be able to edit a diagram directly in the editor, users must be registered in your workspace. Persons
who are not registered can use the commenting feature in SAP Signavio Process Collaboration Hub to
contribute indirectly (see Inviting process stakeholders to comment on a diagram [page 263]).
With Invite modeler to edit, you can send registered workspace users an invitation to edit diagrams. Unless
configured otherwise, all modelers in your workspace can edit diagrams that are stored in the Shared
documents folder. If you try to open a diagram while it is being edited by a colleague in the Editor, a warning
will be displayed. You can still edit the diagram, but if you save, you will override the changes made by your
colleagues.
1. Select a diagram.
2. Choose Share Invite modeler to edit in the menu bar. The dialog Invite modeler to edit opens.
3. Select the arrow to get to the next page.
4. All registered users with editing rights are displayed on the left. Select the people you want to invite.
Note
You cannot grant additional access rights to people using this dialog. It only sends notifications. If you
want to add more people to your workspace, ask your system administrator. To discuss your diagrams with
colleagues, you can also invite them to comment.
How to invite internal and external stakeholders to edit or comment on diagrams, create stakeholder-specific
views, and how to withdraw commenting rights.
One of the most powerful features in collaborative process design is inviting process stakeholders to review and
comment on diagrams. This functionality allows you to get a large number of contributors involved. They do
not need to be modeling experts to work with you in SAP Signavio Process Collaboration Hub.
This way, you can invite people who have a deep understanding of the business process and can contribute
to proper process documentation and process innovation without having to be familiar with SAP Signavio
software.
A special feature of the commenting function is that the commentators do not need to be registered users in
your workspace. You can invite anybody via email to comment on your diagrams.
Note
This section describes how you can invite colleagues who are not users of SAP Signavio Process Manager
to comment on diagrams. To take advantage of SAP Signavio Process Manager in the long term, however
we recommend that you use reading and commenting access rights in SAP Signavio Process Collaboration
Hub.
Note
When you invite collaborators in the editor, the invited collaborator can view the unpublished diagram in SAP
Signavio Process Collaboration Hub preview and add comments.
If the collaborator has an account with a modeling license, the collaborator can also edit the diagram in the
editor and QuickModel.
Remove Collaborators
You can remove collaborators from the diagram. After removing access, collaborators can no longer view the
diagram and add comments.
3. Choose the email address of the collaborator you want to remove and choose (delete).
4. Confirm with Done.
1. In the explorer, select the diagram or the diagrams you want to share.
2. Choose Share Invite anyone for feedback .
The dialog for sending the invitation opens.
3. To change your diagram selection or to add additional diagrams, choose Choose diagrams.
4. Confirm your selection with Next.
5. Under Email addresses, paste the email addresses.
Multiple entries are separated by commas, semicolons, or line breaks.
6. To receive a copy of the invitation email, activate Send a copy to me.
7. If you have selected only one diagram, you can create a simplified view of the diagram. To do so, activate
Selection of a simplified view.
If you have selected multiple diagrams, this option is not available.
Read more in section Simplified views on diagrams [page 265].
8. Under Message, you can customize the invitation message.
9. Choose Send.
Invitation emails with a web link are sent. The link opens the diagrams in SAP Signavio Process
Collaboration Hub.
Never forward a link that was sent to you. Anyone who has the link can view and comment on the diagram
in the name of the original recipient. In case a diagram link has been compromised, please contact our SAP
Signavio service experts from the SAP for Me portal .
If single sign-on is enabled but not enforced in your workspace, the invitation emails generated using the share
option contain two web links:
Single sign-on is configured by your workspace administrator, read more in section Single sign-on using SAML.
Simplified views can ease reading a diagram, especially if the colleague you invited is not a modeling expert.
You can also hide irrelevant information to make viewing diagrams easier.
As described above, simplified views can be created while inviting colleagues to comment on a diagram.
You can create simplified diagram views in the editor before you invite stakeholders to comment.
Use the Manage access rights dialog to view the collaborators that were invited to comment on a diagram.
15.3 Comments
Comments are displayed in the comment panel. To open the comment panel, choose (Comment). You
can also open the comment panel directly from (Notifications) when you receive a notification about new
comments.
Note
Comments are only visible for the last published revision and the newest revision.
View Comments
You can still access comments on elements that were deleted during the editing process. These comments
become process level comments and they are labeled to indicate that they refer to a deleted element.
To filter by comment status, choose Status and select a status from the list.
To display comments for one element only, you have the following options:
Note
When you are viewing only comments for an element, new comments are added as comments on this
element. Clear the element filter to add a comment on the diagram.
1. Open a diagram.
1. Open a diagram.
2. Choose an element. The comment panel for the element opens.
3. Choose Add comment.
4. Enter your comment and click Comment. The comment is posted and is labeled with the element name.
Collaborators are notified.
1. Open a diagram.
When you want to address a comment directly to someone, you can mention this person in a comment.
Mention someone by typing an @ followed by their name while you enter a comment. When you mention
someone in a comment, they are notified.
Edit Comments
Reject Comments
Reject comments that don't trigger any changes to the diagram, for example because other changes make it
obsolete.
When you reject a comment, it is hidden in the default comment view in SAP Signavio Process Collaboration
Hub. SAP Signavio Process Collaboration Hub users can still view rejected comments when they select
Rejected when filtering comments by status.
To reject a comment, choose (more options) in the comment and select Reject. The comment is labeled
Rejected and hidden in the default comment view.
To display a rejected comment again, choose (more options) and select Show.
When you resolve a comment, it signifies to your collaborators that the comment has been taken care of.
To resolve a comment, choose Resolve. Resolved comments are labeled Resolved. Users who posted a
comment get notified when their comment is resolved.
To re-open a comment, choose Re-open. The Resolved label is removed. Users who posted a comment get
notified when their comment is reopened.
Note
Your changes are saved immediately. The number of updated comments is shown.
To make changes to the comment status visible to collaborators, you need to save the diagram.
The status changes only for the first comment in a commenting thread.
Delete Comments
Note
Comment Notifications
Note
Modelers get notified for all revisions, SAP Signavio Process Collaboration Hub users only get notified
about actions on the published revision.
SAP Signavio allows you to share diagrams with collaborators in read-only mode. For read only access without
the commenting option, create a link to send to your colleagues via the embedding function.
The system allows you to generate a link to a PNG-picture representation of your diagram.
When opening the diagram via this link, the most recent version of it will be displayed.
Note
To revoke link access and at the same time stop all sharing and embedding of a diagram, click Stop sharing
the diagram for read-only access in the Embed diagram window.
Every modeler who has the corresponding rights to publish a diagram can publish it in SAP Signavio Process
Collaboration Hub. You can also define and use approval workflows to publish diagrams. Read about this in the
section Approval workflows [page 288].
Apart from diagrams, pictures and files stored in your SAP Signavio file storage can be made available in SAP
Signavio Process Collaboration Hub too. Publishing those files is similar to publishing diagrams. Depending on
your configuration settings, you might need to explicitly publish dictionary entries. Read more about publishing
dictionary entries in the section Publishing dictionary entries [page 83].
Note
Administrators can grant users the right to publish, edit or delete diagrams in the Shared documents folder.
Please contact an administrator and ask them for the corresponding rights if you cannot access these
options. You can learn how to grant access rights in the section Defining access rights.
1. In the menu bar, choose Share then Publish to SAP Signavio Process Collaboration Hub. The corresponding
dialog box opens.
2. Select the diagrams you want to publish. You can publish up to 1024 diagrams at once.
3. To publish an older revision of the diagram or to revert changes to a published diagram, use the activity
feed of the diagram. Select a diagram and choose Expand in the lower left corner of the Explorer.
Alternatively, you can select the space bar on your keyboard.
5. The activity feed will now be displayed. Select the revision you want to publish.
Note
Just one revision of a diagram can be published. To publish multiple revisions, save a copy of the
diagram and then publish the corresponding revision.
1. Select one diagram or several diagrams at once, which you want to unpublish.
2. Choose in the menu bar Share and then Unpublish from SAP Signavio Process Collaboration Hub . The
selected diagrams are now unpublished.
To revoke a single published diagram, you can also use its activity feed.
1. Select a diagram and choose Expand in the lower left corner of the Explorer. Alternatively, you can hit the
space bar on your keyboard.
4. Choose Unpublish:
It is often useful to know what the published version of a particular diagram looks like in SAP Signavio Process
Collaboration Hub. To find this out, select the diagram in the Explorer and click Share - Open published version.
In many situations, you may want to point one or several readers to a specific diagram.
For this purpose, you can send emails containing the link to a diagram in SAP Signavio Process Collaboration
Hub and additional information via the explorer invite.
You can also use this feature to encourage somebody to have a look at SAP Signavio Process Collaboration
Hub in general. Open the Invite to SAP Signavio Process Collaboration Hub dialog without selecting a
diagram. The link in the email will lead to the entry point of SAP Signavio Process Collaboration Hub.
The diagram preview provides information about a diagram and its revisions in the Explorer.
Once you have created diagrams and then updated or changed them at least once, you have the option to see
what was changed by whom at what time in the activity panel.
Notification Configuration
Note
In the activity panel, you can set how frequently you receive email updates about specific diagram(s) or
folder(s). If you subscribe to a folder, you will receive updates regarding all the diagrams and sub-folders
contained within. You can daily, weekly or monthly notifications. Alternately, you can unsubscribe from
notifications entirely.
Additional Functions
The activity panel provides a preview of the diagram/folder as well as detailed information and management
options regarding its version history.
1. Select a diagram/folder.
2. Choose Expand in the lower left corner of the Explorer. Alternately, you can use the space bar on your
keyboard:
4. To view the activity feed and manage the change and version history of the diagram, choose Feed button.
The activity feed will now be displayed.
The visualization will highlight the elements that have been changed.
10. To hide the panel again, choose the space bar or choose Collapse.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
You can model your diagrams in multiple languages. This allows viewers and modelers who do not understand
your standard diagram language to collaborate with you.
Multilingualism is a feature which is available in the Editor, SAP Signavio Process Collaboration Hub and in the
Dictionary. You need to configure languages in the Explorer (see section Configure language settings for all
users) to use this feature.
The following explains how to translate a diagram and the modeling elements. Note that you need to have
already defined your desired language in the Explorer.
When creating a new diagram, it will be displayed in the default language of the workspace. To change the
default language, read the section Set a default language.
The current language of a diagram can be switched in the editor via the drop-down list on the
right side of the upper toolbar.
Note
If the list is not visible for you, it is possible that there are no languages defined for your workspace. As a
workspace administrator, you can define a set of available languages in the Explorer's configuration dialog,
which is described in the section Configure language settings for all users.
The highlighted elements have not been translated into English, yet.
Diagram elements that were already translated are displayed will be displayed normally. In our example, the
task 'Problem lösen' was already translated. If the label was formatted, this formatting will be kept.
Diagram elements that are not yet translated are highlighted in red--in this example, the incoming message
event 'Lieferung der Ware' is only available in German (thus, the "de" in brackets).
Translating Diagrams
Translating diagrams means defining a translation for each diagram element in each required language, which
can include all element labels and documentation.
This chapter describes how diagrams can be translated into other languages. This is especially useful when
multiple people are involved on the translation, each translated into one language. Later in this chapter, you will
learn how to translate a diagram in different languages at the same time.
1. First, select which language you want to translate. Proceed as explained above. Elements that were not yet
translated are highlighted in red.
2. Double-click an element to define its label.
4. In the attribute panel, you can also add documentation in the current language.
Translate the remaining diagram elements in the same way. After saving the diagram, it will be accessible in all
languages of the workspace.
Sometimes, a modeler might want to define a diagram in multiple languages while modeling the diagram. In
this case, it is recommended to have the required languages set available while modeling.
1. Add languages to the diagram via the language tool of the Editor toolbar.
2. Select all the languages you want to work with in your diagram. They will appear in the attribute panel on
the right hand side.
You can migrate the contents of a digram from one language to another. This is especially helpful when
switching between dialects of a specific language (for example, British English to American/Canadian English).
or if the diagram was created in the wrong language and you want to correct this.
Note
When opening a diagram, the system will ask you for the diagram language if no default is defined.
1. Choose the language drop-down list, then select Migrate diagram to a different language. The
corresponding dialog box opens.
In this example a diagram was created without language definitions. The content was defined in German. As
the workspaces' default language is English, the diagram was configured to be in English when the language
tools were activated. The content is now supposed to be migrated from German to English and the German
contents are supposed to be removed.
Caution
Keep in mind that translations that you make within the framework of this feature are only visible in SAP
Signavio Process Collaboration Hub.
1. Select the name of a diagram, folder or file name you want to translate in the Explorer.
2. Open the Edit menu and choose Change name/description (for files and folders) or Rename (for diagrams).
3. Now you can add translations of the name in all available languages.
Related Information
Note
SAP Signavio Process Governance is a platform for process governance. To use the SAP Signavio Process
Governance integration, you need to purchase SAP Signavio Process Governance licenses. For more
information, contact [email protected].
If the process has not been deployed to SAP Signavio Process Governance and you are the workspace owner,
you can deploy the process (see section Process deployment).
Read more on process execution in the user guide of SAP Signavio Process Governance.
Note
We are working on expanding and improving the functions related to process governance.
For more information about SAP Signavio Process Governance, contact [email protected].
For this function, the installation of SAP Signavio Process Governance is necessary in addition to SAP
Signavio Process Manager. The approval workflow functionality can only be activated if SAP Signavio Process
Governance was successfully installed.
Approval workflows enable you to control validation of diagrams before publishing. Approval workflows ensure
that decision makers and BPM experts review and approve the quality and factual correctness of a diagram
before it is published in SAP Signavio Process Collaboration Hub.
Approval workflows make sure that diagrams have been approved by a list of users before they are published in
SAP Signavio Process Collaboration Hub.
Approval workflows can be configured to automatically publish an approved diagram to SAP Signavio Process
Collaboration Hub, or to send rejected diagrams back for editing.
5. You receive a confirmation that the approval workflow has been started successfully. This dialog also
contains a link to the workflow instance.
If the diagram is approved, you can see that the approval status of the diagram has been updated in the
explorer.
This section describes how you work as a recipient of an approval workflow task.
As soon as a modeler requests an approval from you, you receive an email with a link to the case in SAP
Signavio Process Governance.
1. Click the link to open the approval task. The approval task opens in SAP Signavio Process Governance.
2. Check whether the corresponding diagram fulfills your requirements.
3. Click the Show comments link to open the diagram in the commenting view.
4. Click the Compare revisions link to get a better overview over recent changes via the Comparison [page 66]
tool.
5. Open the explorer to access further functions:
• To open the diagram again, double-click it or select it and click Show comments, then Compare
revisions/diagrams.
• To check whether a diagram complies with modeling conventions, select Modeling conventions (XLSX).
The report is especially helpful when you conduct a formal approval with focus on BPMN quality.
• To point a colleague to a diagram, select the diagram you want to share and select Invite to SAP
Signavio Process Collaboration Hub.
• Start approval workflow triggers a new approval workflow case for the selected diagram.
• To get an overview of all pending approval workflows, you can either click Show started approval WFs or
Open approval task list in the upper panel.
Show started approval WFs provides a basic overview in the explorer, whereas Open approval task list
opens a more detailed, filterable view in SAP Signavio Process Governance.
6. Once you have finished the review, go back to the approval case in SAP Signavio Process Governance to
approve or reject the change.
In the explorer, a rejected diagram is marked with a red X, an approved diagram with a green check mark,
and a published diagram with a globe icon.
SAP Signavio Process Manager allows you to create various customizable reports in the form of spreadsheets
or as PDF files. This enables business users to analyze your process hierarchy offline, and in formats decision
makers and analysts are already familiar with.
The standard reports that are accessible via the explorer's Reporting dropdown menu cover most business use
cases. If you require a special kind of report that is not provided by the tool, you can ask one of your workspace
administrators to create a custom template.
Note
Many of the reports access default dictionary categories during the generation process. In case you
suspect that your dictionary configuration causes problems during the generation of a report, take a look at
the section Defining custom categories for dictionary entries.
It is possible to export process documentation documents as PDF and Microsoft Word files. Process
documentation documents are comprehensive documents that contain both diagram graphics as well as
relevant diagram attributes, such as description and responsibilities.
As a workspace administrator, you can create individual templates for process documentation reports. A guide
on how to create new templates can be found in the corresponding chapter of this manual. Once created, a
custom template can then be selected during the creation of a process documentation report.
Analysis
SAP Signavio Process Manager provides a possibility to set key performance indicators (KPI) in event-driven
process chains (EPC) and BPMN 2.0 process diagrams, which allows detailed process analyses.
A process model metric contains information about the usage of diagram element types and can be created for
any diagram type:
To create a summary of element details that are used in your BPMN 2.0 or EPC diagrams, read the following
chapter:
Workspace administrators can create reports that list for each user the groups the user is a member of:
Governance Report
Workspace administrators can access usage data of your workspace with the governance report. For example,
you can see at a glance how many process models have been created.
With the process documentation report in SAP Signavio Process Manager you can generate a report that
includes information about diagrams, element descriptions and dictionary entries in your organization. The
process documentation report comes in PDF or Microsoft Word format.
Note
This section describes all options for this function. Which options are available depends on your license and
the settings made by your workspace administrator.
In SAP Signavio Process Manager you can generate process documentation reports. These reports contain all
your diagrams, including all element descriptions, and dictionary entries.
You can generate process documentation report in a PDF or Microsoft Word format.
The process documentation report in PDF format generates. Access the report from your browser's downloads
folder.
1. Open the explorer and choose Reporting > Process documentation (Word).
The process documentation (Word) dialog opens.
2. Select the required diagrams.
3. To add a filter, choose Add filter.
The edit filters dialog opens.
4. Select a folder from the drop-down list where you want to search in.
5. Define the rules for the filter query.
6. Choose OK.
Diagrams discovered by the filter query are selected for the process documentation (Word) report.
The edit filters dialog opens and displays the number of results returned from your filter query.
7. Choose OK.
8. In the Configuration section, select a template for the report from the Templatedrop-down list.
If there are existing custom process documentation templates, you can use them when creating a process
documentation report. Otherwise, the SAP Signavio template is set by default.
9. Select the required language for the report from the Language drop-down list.
10. Enter information for the Title, Organization, Author, Date, and Version fields.
11. In the Export linked subprocesses section, select which linked subprocesses must be included in the report
from the drop-down list.
The following options are available:
• No linked subprocesses
• Linked subprocesses of all levels
• Linked subprocesses of the first level
12. Choose Generate documentation.
The Important information dialog opens.
13. The dialog indicates that the table of contents won't be up-to-date when opening the generated report.
Choose OK and follow the steps described below after the report generation is complete.
The process documentation report in Word format generates. Access the report from your browser's
downloads folder.
See how to generate the responsibility assignment matrix / RACI report in SAP Signavio Process Manager.
The responsibility assignment matrix / RACI report creates an XLSX file which displays the responsibilities for
activities in the selected BPMN diagrams. Read Responsibility assignment according to RACI [page 115] for
more information.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
This section explains how to generate the responsibility assignment matrix / RACI report.
1. Open the explorer and choose Reporting > Responsibility assignment matrix / RACI.
The Responsibility assignment matrix / RACI dialog opens.
2. Select one or multiple diagrams to include in the report.
3. You can select the following options:
• Use merged cells in output spreadsheet
• Export file as XLS (Excel 97)
4. Choose Start analysis.
5. The responsibility assignment matrix / RACI report generates. The file is saved to your browser's download
folder.
See how to generate the responsibility handovers matrix report in SAP Signavio Process Manager.
When different roles or organizations participate on processes, the process flow gets handed over from one
participant to another at defined places. These roles are represented as pools and lanes in BPMN 2.0 process
diagrams. Event-driven process chains (EPC) use attached roles, positions and organizations. A responsibility
handover can be either a sequence or an information flow.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
This section explains how to generate a Responsibility handovers matrix report for a BPMN 2.0 process
diagram. These steps also work for Event-driven process chains (EPC).
Note
If custom attributes linking to organizational dictionary entries were defined, they are included in the
calculation.
BPMN 2.0 process diagrams and Event-driven process chains (EPC) can attach IT systems information to a
task. With BPMN, those IT systems can be tagged as an 'Input' or an 'Output'.
The IT system usage matrix reports creates an assignment matrix that shows which IT systems data is read
from during an activity, and which IT system data is written to. You can choose whether the assignments refer
to diagrams or roles. The report also includes IT systems that are linked as dictionary entries from a custom
defined attribute.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
This section explains how to generate IT system usage matrix reports for a BPMN 2.0 process diagram. These
steps also work for Event-driven process chain (EPC) diagrams.
1. Open the explorer and choose Reporting > IT system usage matrix (by diagrams).
The IT system usage matrix (by diagrams) dialog opens.
2. Select one or multiple diagrams to include in the report.
3. You can select the following options:
• Use merged cells in output spreadsheet
• Export file as XLS (Excel 97)
4. Choose Start analysis.
The IT system usage matrix (by diagrams) report generates. The file is saved to your browser's download
folder.
1. Open the explorer and click Reporting > IT system usage matrix (by roles).
The IT system usage matrix (by roles) dialog opens.
2. Select one or multiple diagrams to include in the report.
3. You can select the following options:
• Use merged cells in output spreadsheet
• Export file as XLS (Excel 97)
4. Choose Start analysis.
Note
If custom attributes linking to organizational dictionary entries were defined, those will also be included in
the calculation.
See how to generate the Job Profile report in SAP Signavio Process Manager.
In SAP Signavio Process Manager you can automatically create job profiles based on your documented process
landscape. The Job Profile report allows you to view all activities that an organizational role is involved in.
In contrast to the diagram-centered RACI report, the Job Profile report creates a role-specific matrix over all
workspace diagrams.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
This section explains how to generate a Job Profile report in SAP Signavio Process Manager.
See how to generate the risk & controls report in SAP Signavio Process Manager.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
With SAP Signavio Process Manager's integrated risk management feature, you have the ability to define risks
and controls directly at any step of a process within the process model. These risks and controls can be defined
and then associated with the corresponding activities.
You can use the risk & controls report to view an overview of potential risks and related controls. This report
summarizes all information about the risks and controls in the selected process models.
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
The section explains how to generate the Risk & controls report.
1. Open the explorer and choose Reporting Risk & controls report .
The Risk & controls report dialog opens.
2. Select one or multiple diagrams to include in the report.
3. You select the following options:
• Use merged cells in output spreadsheet
• Export file as XLS (Excel97)
4. Expand the Show additional attributes in the report option. The following attribute options are available:
• Documentation
• Process target
• Process maturity level
• Process owner
• IOS9000ff relevant
• Responsible
Note
It isn't possible to include table attributes. You can't select risk management attributes on diagram
level as the report includes them by default.
See how to generate the modeling conventions report in SAP Signavio Process Manager.
With the modeling conventions report you can create a report that checks if the selected diagrams are
compliant according to a specified modeling convention.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
Note
Custom modeling conventions are also available in the Modeling conventions section. Read Managing
modeling conventions for more information.
See how to generate the Documents usage matrix report in SAP Signavio Process Manager.
Data objects can be attached to an activity in BPMN 2.0 and are indicated as an input or output. In Event-driven
process chain (EPC) diagrams, documents can be attached to functions. The Documents usage matrix report
creates an Excel file for one or multiple diagrams describing the assignment of documents to tasks. Linked
dictionary entries representing a document are also included in the report.
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
The Documents usage matrix report displays the documents that are attached to an element as a BPMN
attribute as either 'Input' or 'Output' documents. For Event-driven process chain (EPC) diagrams, an
information flow can be directed using the 'Information Flow' attribute.
Note
If there are custom attributes defined which link to dictionary entries that represent documents, they are
included in the calculation.
This section explains how to generate a Documents usage matrix report for a BPMN 2.0 process diagram.
These steps also work for Event-driven process chain (EPC) diagrams.
See how to generate the process characteristics with element details report in SAP Signavio Process Manager.
The Process characteristics with element details report is an Excel file that contains an overview of elements
and attribute values found in the selected diagrams. Attributes without values are not listed in the report.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
The following diagram types can be used in the process characteristics with element details report:
• BPMN 2.0
• DMN 1.1
• ArchiMate
• EPC
• Value chain
• Organization chart
This section explains how to generate a process characteristics with element details report.
The process characteristics with element details report generates. The file is saved to your browser's download
folder.
See how to generate the process model metrics report in SAP Signavio Process Manager.
With the process model metrics report, you can generate a statistics report for your diagrams.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
• Type
• Number of Elements
• Number of Edges
• Number of Forks
• Operators
• Number of Subprocesses
• Number of linked Files
• Number of Dictionary Links
• Number of Process Steps without Responsibility Definition
• Number of Responsibility Handovers
• Path
• ID
• Revision
• Last saved by
• Date of last publication
• Open in Explorer link. The column contains a link that opens the selected diagram in the Explorer.
This section explains how to generate a process model metric for a BPMN 2.0 process diagram. These steps
also work for Event-driven process chain (EPC) diagrams.
The process model metrics report generates. The file is saved to your browser's download folder.
See how to generate the quantitave reports in SAP Signavio Process Manager.
SAP Signavio Process Manager enables you to run quantitative analyses of your processes. After setting KPI on
diagram elements, you can generate the process cost analysis and resource consumption analysis reports for
BPMN 2.0 process diagrams and event-driven process chains (EPC). Read Setting key performance indicators
(KPIs) [page 118] for more information.
The resource consumption analysis report allows for the computing of time consumption per task or process.
Read Resource consumption analysis report [page 306] for more information.
Both reports consider the execution probability and frequency before computing the actual resource
consumption or costs.
See how to generate the process cost analysis report in SAP Signavio Process Manager.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
Process cost analysis reports displays the computed costs that occur in a process. The report displays the
costs, tasks, and cost centers in a table.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
This section explains how to generate the Process cost analysis report.
See how to generate the resource consumption analysis report in SAP Signavio Process Manager.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
A resource consumption analysis report calculates the time consumed for a process or a task. It can help you
find complex and time consuming tasks and plot out the resource consumption of process participants.
Note
You can include up to 50,000 diagrams. Depending on the number of diagrams, report generation can take
up to an hour, and you need to keep the browser tab that started the generation open.
This section explains how to generate the resource consumption analysis report.
Note
To generate a user/group assignment report, you need to have workspace administration privileges.
The user/group assignment report generates a list of users and their group memberships in your workspace.
The users and groups displayed in the report are pulled from the users and groups defined in the User
Management section of SAP Signavio Process Manager Read Manage users and groups for more information.
For each user, the report lists all user groups the user is a member of as a direct member. If a user is a member
of group and that group is a member of a group listed in the report they are listed as an indirect member.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
The governance report provides an overview of the user activity in your workspace. You can view aggregate
metrics (for example, the number of unpublished diagrams). You can use these metrics to draw conclusions
regarding the success of your process modeling initiative.
Caution
The aggregates in the governance reports also consider diagrams you don't have permission to access.
Your current access rights are taken into account for the linked search.
Data Description
SAP Signavio Process Collaboration Hub The number of Page visits represent a single user opening
any published object (diagram, file, or Dictionary item) in
SAP Signavio Process Collaboration Hub. Every time some-
one opens one of these items in SAP Signavio Process
Collaboration Hub, it's counted as a view and displays in the
report.
Learn how to view and export reports analyzing your workspace and process model usage with Process Model
Dashboards.
Note
To access Process Model Dashboards, you need to have workspace administration privileges.
Process Model Dashboards are pre-defined dashboards accessible within SAP Signavio Process Collaboration
Hub. These dashboards use the data from SAP Signavio Process Manager to provide you with detailed analysis
of your workspace and process model usage.
You can add filters to your data, and export your reports as CSV files.
Learn more in section Process Model Dashboards in the SAP Signavio Process Collaboration Hub user guide.
SAP Signavio value accelerators specific for a theme (such as product or industry) may include one or a
combination of the following:
Use of SAP Signavio value accelerators is optional and not part of the business functionality of the products of
the SAP Signavio Process Transformation Suite. Value accelerators are subject to change and may be changed,
discontinued, or replaced by SAP at any time for any reason without notice.
To access the value accelerators, visit the SAP Signavio Process Explorer landing page and choose Access it
now. You need to be an SAP-registered user, for example a P- or an S-user.
Related Information
This section discusses how to share diagrams and dictionary entries using import features:
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
With this feature you can import diagrams that were exported as SAP Signavio archive (SGX) to your
workspace.
• You can add dictionary entries to the dictionary or merge with existing entries. You can also import custom
attributes and modeling language configurations.
• You can only run one import at a time in a workspace. When trying to run an import, all users in a
workspace with the necessary rights can see if an import is in progress.
• There is a 500 MB import file size limit.
• On the History tab of the import dialog, you can view the details of the last 50 imports, for example the
import time, the import status, and which items imported successfully.
1. Open the explorer and choose Import / Export Import SAP Signavio archive (SGX) .
Options Notes
Import contained Files/Pictures If you disable this option, no linked documents and files
are imported.
Import custom attributes and modeling language configu- This option is only available for administrators.
rations
Note
Import an SAP Signavio archive (SGX) file containing all the process models of a package that is
published on SAP Signavio Process Explorer, read more in SAP Note 3329491 .
Related Information
Note
Access to this feature depends on your workspace settings. For more information, contact your workspace
administrator.
The BPMN 2.0 standard includes an XML notation and enables the platform with independent exchange
of BPMN 2.0 diagrams. To get more information about the BPMN 2.0 specifications, go to https://
www.bpmn.org .
In SAP Signavio Process Manager you can update your BPMN 2.0 model by importing a new XML file. The
import updates each process and subprocess in your model, and creates a new diagram if a subprocess
doesn’t exist.
1. Open the explorer and choose Import / Export Import BPMN 2.0 XML .
The Import BPMN 2.0 diagrams from .bpmn files dialog opens.
2. Choose Choose File.
3. Select a XML file that complies with the BPMN 2.0 XML standard.
The diagram imports.
If the imported file is not standard-compliant, the system displays errors and warnings. Some elements won't
import due to errors in the BPMN 2.0 XML file.
Each element requires bpmndi information such as process flow and graphical information.
Elements with no bpmndi information still import but display warnings. For example, if an element doesn’t
contain graphical information during import, the import completes but elements without the graphical
information are excluded from the import.
Opening a diagram with warnings after import can contain missing elements.
Sometimes the import of BPMN 2.0 XML files is impossible due to errors unknown to the system. For example,
the imported file isn't a valid BPMN 2.0 XML. For further assistance, please contact our SAP Signavio service
experts from the SAP for Me portal .
Related Information
With this feature, you can import APQC frameworks into your workspace.
The hierarchy structure of the APQC framework is represented by a folder tree in SAP Signavio Process
Manager.
Once the import is done, every element in the sheet "Combined" is represented in the workspace in different
forms (depending on the hierarchy level of the element):
• level 1 (X.0): a folder and inside of it a value chain with the same name including / linking to all direct child
elements
• level 2 (X.X): a folder and inside of it a value chain including / linking to all direct child elements
• level 3 (X.X.X): depending on whether the hierarchy for this part goes down to level 4 (only one more level
of direct children) or level 5 (two more levels)
• stops at level 4: a BPMN diagram including all direct child elements as activities
• stops at level 5: a folder and inside of it a value chain including / linking to all direct child elements
• level 4 (X.X.X.X): depending on whether the hierarchy for this part goes down to level 4 (no more children)
or level 5 (one more level of child elements)
• stops at level 4: activity elements in a BPMN model (see above)
• stops at level 5: a BPMN diagram including all direct child elements as activities
• level 5 (X.X.X.X.X; optional): activity elements in a BPMN model (see above)
• A single, top-level value chain is created linking to all imported level 1 value chains.
The diagram's Description attribute contains the corresponding APQC glossary term.
If you already have a workspace, please contact our SAP Signavio service experts from the SAP for Me
portal to activate the APQC importer.
Import Requirements
To import a framework as an Microsoft Excel spreadsheet, the spreadsheet must have a specific structure.
Official APQC files always already have this structure, but custom documents might need adjustments.
• The file needs to include a sheet called Combined which contains the list of folders and diagrams to be
created
• The first three columns of this sheet need to represent the following information in this exact order:
• PCF ID, Hierarchy ID, and Name
• These first three columns need to have non-empty values in all rows to be imported
To import the APQC framework into your workspace, follow these steps:
1. Download the framework as a Microsoft Excel spreadsheet from the APQC web site . Modify the
spreadsheet as required.
2. Open the explorer and choose Import/Export Import APQC Excel .
The Import APQC diagram structure from .xls file dialog opens.
3. Choose Choose File and select an APQC framework Excel spreadsheet.
4. Choose Import.
Note
The framework imports into the folder that is selected in the explorer.
Now, you are able to use the APQC framework as the beginning of your business process management
initiative in SAP Signavio Process Manager.
Learn how to import diagrams from ARIS Markup Language (AML) into your workspace.
Context
Note
Access to this feature depends on your workspace settings. For more information, contact your workspace
administrator.
The ARIS modeling interface uses AML to create the XML export format compatible with SAP Signavio Process
Manager. Using AML XML files, you can import the following diagrams types into your workspace:
Procedure
1. Open the explorer and choose Import /Export Import ARIS markup language .
Note
For more information, please contact our SAP Signavioservice experts from the SAP for Me portal .
You can import Visio diagrams into SAP Signavio Process Manager. The importer supports both BPMN 2.0 and
EPC diagrams.
Note
The importer supports VDX, VSD, VSDX files, and ZIP archives that contain such file types. Elements
that are not part of the BPMN 2.0 standard and not EPC-compliant are excluded.
4. Choose Import.
In SAP Signavio Process Manager you can upload documents and pictures into your SAP Signavio file storage.
These files can be linked to diagrams and, when published in SAP Signavio Process Collaboration Hub, are
available to team members who have read access.
Embedding images that are not accessible to all users can display as broken image links when viewed without
the necessary permissions or log-ins.
• As unlisted images (with hidden names and implicit authentication tokens, HTTPS only)
Example URL: https://external.domain.com/files/hidden-file-name-nobody-guesses?
possibleToken=123nekot321
Note
When you host images externally, be aware that these image can possibly be accessed by third parties.
Considerations
If the SAP Signavio file storage is enabled for your workspace, its size and the maximum upload file size
are displayed in the workspace configuration dialog accessible via the top drop-down menu of the Explorer in
the header Setup. To configure those limits according to your requirements, please contact our SAP Signavio
service experts from the SAP for Me portal .
If the file quota is exhausted or the size limit for a single file is exceeded, a warning displays.
In those cases, you can try to upload a smaller version of the file or delete unused pictures or documents from
your file storage. To increase your storage space, please contact your workspace administrator.
Note
• Take note that there must be enough free space left in your file storage to upload the whole file.
The total space for file storage is 10 GB.
• Make sure not to exceed the maximum single file size.
The maximum single file size is 32 MB.
• These file size limits cannot be adjusted.
To edit the name and description of a file after upload, follow these steps:
You can update a file in the SAP Signavio file storage by uploading a newer version of the file. Each link to this
file opens the updated version as well.
• doc
• docx
• ppt
• pptx
• xls
• xlsx
• odt
• ogg
• zip
• rar
• pdf
• audio/mpeg
• audio/ogg
• image/gif
• image/apng
• image/flif
• image/webp
• image/x-mng
• image/jpeg
• image/png
• multipart/form-data
• text/css
• text/csv
• text/php
• text/plain
• text/xml
You can import dictionary entries from Microsoft Excel files (XLS or XLSX) to add multiple entries at once or to
update existing entries. The import can't be used to delete existing entries from the dictionary.
In a workspace, it's not possible to perform multiple imports simultaneously. If you start an import while
another user is running one, the import tool shows a message and you have to wait until the other import is
finished.
The import is limited to 500 records per Excel spreadsheet. Importing a file with more than 500 records,
causes the import to fail. If you need to import more than 500 entries, you can distribute the data over
multiple sheets in one file or split up the data to create multiple files.
Column header The column header contains the dictionary attributes. You
can choose any name for the headers, as for the import
you map the columns to the dictionary attributes in SAP
Signavio Process Manager.
The import tool interprets the first row with text as the
header.
You must start your dictionary file with the first column and
fill in at least three columns. If you fill fewer columns with a
header or have empty columns in between, the import fails.
Rows Rows contain the actual dictionary entries and the informa-
tion you want to add, for example descriptions or statuses.
You can either create such a file or you export available dictionary entries and use the export file as a template.
Read more about exporting dictionary entries in the section Export dictionary entries [page 326].
Note
Related Information
Note
This feature is available on request. Contact SAP Signavio Customer Support for more details.
With the JAR import feature you can import Java classes as dictionary items and use them as data models in
the SAP Signavio Decision Manager.
The attributes and relationships of the classes are created as decision input/output data types.
Before importing a JAR file, make sure the target dictionary category supports data modeling.
The classes in your JAR file need to fulfill the following requirements:
Example
The following example displays a Java class that is valid for the import:
package sandbox.jarClasses;
import java.util.Set;
import
javax.xml.bind.annotation.XmlType;
@XmlType
public class Relationship {
private Fruit Apple;
private Fruit Orange;
private Set<Fruit> banana;
private boolean broken;
public Fruit getApple() {
return apple;
}
public void setApple(Fruit
Apple) {
this.apple = apple;
}
public Fruit getOrange() {
return orange;
}
public void setOrange(Fruit
Orange) {
this.orange = orange;
}
public Set<Fruit> getBanana()
{
return banana;
}
public void
setBanana(Set<Fruit> banana) {
this.banana = banana;
}
public boolean isBroken() {
return broken;
}
public void setBroken(boolean
broken) {
this.broken = broken;
}
This example can't be imported because the class lacks the @XmlType annotation:
package sandbox.jarClasses;
public class NotValid
extends Relationship {
private int
justANumber;
public int
getJustANumber() {
return justANumber;
}
public void
setJustANumber(int justANumber) {
this.justANumber =
justANumber;
}
}
The JAR's Java classes are available as dictionary items. Refresh your browser to see the imported items.
List of all export functions, for diagrams (export as PDF, export as image, export as SAP Signavio archive(SGX),
export as XML) and for dictionary entries.
In this section, it is described how to share diagrams and dictionary entries using the export functions:
For the import functions, read more in section Importing [page 312].
How to export all dictionary entries or a specific entry set from the dictionary to an Excel file.
You can export dictionary entries to an Excel file, for example to print them, for offline review, or for further
processing in third-party systems.
If you want to import dictionary entries from an Excel file to your workspace, read more in section Import
dictionary entries [page 321].
Partial Export
1. Before you start the export, select the entries you want to export in the dictionary
You can export the following entry sets:
• All entries in a category.
• All entries in a category that begin with a specific letter.
• All entries that are returned by a search.
2. Choose Import / Export Export Excel .
3. Select an export option. It depends on your previous selection which option is available:
• Export the entire dictionary
Completing Export
Note
In one Excel export you can export 300.000 dictionary items. If your complete dictionary contains more
than 300.000 entries, we recommend to split the export by exporting entries per dictionary category.
How to export one or more diagrams and folders as PDF to share with colleagues or keep track of the current
status.
With this function, you can export a diagram as a PDF file from the explorer.
You can either select a single diagram for export, or a folder. When selecting a folder, all diagrams contained are
combined into one PDF document.
1. In the explorer, select the diagram or the folder you want to export.
You can change your selection via the export options described below.
2. In the toolbar, choose Import / Export Export PDF .
The export configuration dialog opens.
3. Configure the export. Read more in section Export options [page 328].
4. If you want to save your export configuration as default for your workspace, enable Save as defaults at the
bottom of the dialog.
5. Choose Export.
The PDF is exported. The file is saved to your browser's download folder.
To export a diagram as PDF from the editor, use the print function in the toolbar. Read more in section Editor
toolbar and keyboard shortcuts [page 38].
Export options
• Language
If multiple languages are set up for the workspace, select the language for the diagram you want to export.
• Print in black and white
Specify whether to print the diagram in color or black and white.
• Show additional information
Enable this option if you want to add printing attributes to the PDF document, for example the author,
creation date, or page number. You can also add diagram attributes.
The preview area shows how many attributes you can add and where they are positioned.
To add diagram attributes, choose Own attribute and select up to 3 diagram attributes for each attribute
position.
• Paper size
Select a paper size for your PDF. The default is set to the international standard size A4.
• Stretch small diagrams to whole page
Specify whether small diagrams are enlarged to fit the full page.
• Logo
Add a custom logo. You can upload a new file or choose an image that already exists in your workspace.
The maximum size for a logo file is 5 MB.
• Use original size
Specify whether to use the original size of the image file.
• Landscape or Portrait
For the PDF pages, select landscape orientation or portrait orientation.
• Diagram rotation
Specify whether the diagram rotation is managed automatically or not.
With Automatic, the internal diagram rotation is used.
With Always, the diagram rotation you choose below is used.
With Never, the diagram isn't rotated.
• Diagram orientation
• Rule sets
Select which attributes should be visible.
How to export a diagram as an image in PNG or SVG format to share it with colleagues or embed it in
documents.
In the explorer, there are two export functions that transform diagrams into images: The PNG export creates
pixel graphics, the SVG export creates vector graphics.
If you want to embed the image of a diagram in web pages, which means the image updates automatically with
each change on the diagram, read more in section Embed a diagram as an image [page 343].
• Language
If multiple languages are set up for the workspace, select the language for the diagram you want to export.
• If different views exist for the diagram, select the view you want to export. By default, the original view is
selected.
How to export diagrams and folders to a SAP Signavio archive file, in SGX format, to exchange diagrams
between multiple workspaces.
Note
Access to this feature depends on your workspace settings. For more information, contact your workspace
administrator.
With this function, you can export one or more diagrams as a SAP Signavio archive from the explorer.
SAP Signavio archives, these are SGX files, allow you to exchange diagrams and folders between workspaces.
SGX is a SAP Signavio-specific file format, which can't be used by third-party systems.
We recommend to use the SGX export only to exchange diagrams between different workspaces. If users
are registered in the same workspace, use the shared documents folder and collaboration functions to work
together on diagrams. Read more in Working with folders and diagrams [page 28] and Collaboration [page
262].
How to export a BPMN 2.0 diagram as an XML file to exchange it between multiple workspaces.
Note
Access to this feature depends on your workspace settings. For more information, contact your workspace
administrator.
With this function, you can export a BPMN 2.0 diagram as an XML file from the explorer.
The BPMN 2.0 standard includes an XML notation which enables the platform-independent exchange of BPMN
2.0 diagrams. For more information about this XML standard or the BPMN 2.0 specifications, go to https://
www.bpmn.org .
You can export the following diagram types to BPMN 2.0 XML:
If you want to export diagrams of other modeling notations, use the XML export as described in section Export
a diagram as XML [page 332].
Export options
• Language
If multiple languages are set up for the workspace, select the language for the diagram you want to export.
• Include linked subprocesses
Specify whether to also export linked subprocesses.
• If different views exist for the diagram, select the view you want to export. By default, the original view is
selected.
Note
Access to this feature depends on your workspace settings. For more information, contact your workspace
administrator.
With this function, you can export a diagram as an XML file from the explorer, for example for further
processing in third-party systems.
Note
Use this export for diagrams of any modeling notation, except for BPMN 2.0 diagrams. If you want to export
BPMN 2.0 diagrams, use the BPMN 2.0 XML export as described in section Export a BPMN diagram as
XML [page 331].
The SAP Signavio-specific XML format produced by this export is a special form of RDF, the Resource
Description Framework which is used for conceptual description or modeling of information that is
implemented in web resources. You can use XML transformation tools to generate other XML formats from
the export file.
How to export a DMN 1.2 diagram as an XML file to exchange it between multiple workspaces.
Note
Access to this feature depends on your workspace settings. For more information, contact your workspace
administrator.
With this function, you can export a DMN 1.2 diagram as an XML file from the explorer.
The DMN 1.2 standard includes an XML notation. This notation enables the platform-independent exchange
of DMN 1.2 diagrams. For more information about this XML standard or the DMN 1.2 specifications, go to
https://www.omg.org/spec/DMN/1.2 .
Names of all elements in the exported file, like decisions, inputs, or input items, can only contain alphanumeric
characters (a-z, 0-9).
Other characters are automatically removed, for example underscores (_) and dashes (-).
If the removal of characters would create a duplicate name, a number is appended to the new name.
If dictionary entries are used as data input objects, you can add export names. This way, you can provide
domain-specific vocabulary when executing the exported XML file.
• To add an export name, specify a technical name for the dictionary entry.
The field Technical name is not available by default in the dictionary. An administrator must enable the use for
data modeling for the respective dictionary category. Read more in section Managing input and output data for
DMN Data Input elements.
The technical name is only used when exporting a DMN diagram as XML. In SAP Signavio Process Manager and
SAP Signavio Process Collaboration Hub, the standard dictionary name is always used.
The rules for permitted element names also apply to the Technical name.
Related Information
Note
Access to this feature depends on your workspace settings. For more information, contact your workspace
administrator.
You can either export multiple diagrams, one diagram, or just one decision table and its sub-decisions. The
Drools export supports four different export types: Production, Development, Test, and Cases. In contrast to
Production, Development adds additional comments and logging behavior.
Permissions for the Drools export can be limited to users of specific user groups.
To export decision logic to Drools, open the Explorer. Select one or multiple diagrams and go to Import/Export,
then Export Drools.
Now you can adjust your selection and set the following export properties:
• Export revision
You can choose whether to export the latest revision of the diagram that has been saved in the Editor or the
latest revision that was published in SAP Signavio Process Collaboration Hub.
• Export mode
• The option Production mode exports the decision logic to drools. It does not include comprehensive
comments, support for detailed logging, and test cases.
• Development mode provides additional comments and logging behavior.
• Development mode + test cases provides additional test cases in the form of .csv files (one .csv file for
each top level decision). The .csv files contain all combinations of all relevant sub-decisions.
Alternatively, you can export a decision table and its sub-decisions directly from the Editor.
In the Editor, open a decision table and choose Import/Export in the top-right corner of the dialog. There you
can chose between generating the Drools export or the test cases (as described above):
As soon as the files are generated, you can download them in you browser:
If dictionary entries are used as data input objects and data definitions, you can add information to export.
For that, an administrator must enable the use for data modeling for the respective dictionary category. Then,
the configuration dialog for dictionary entries has two fields more to specify the information:
• Technical name
• Class name
Note
If both names are set in one dictionary entry, only the class name is exported.
Both names are only used when exporting a DMN diagram as Drools rules. In SAP Signavio Process Manager
and SAP Signavio Process Collaboration Hub, the standard dictionary name is always used.
Read how to enable the fields in section Managing input and output data for DMN Data Input elements.
For dictionary entries that are used as data input objects, you can add export names. This way, you can provide
domain-specific vocabulary when executing the exported DRL file.
• To add an export name, specify a technical name for the dictionary entry.
For dictionary entries that are used as data definitions, you can reference existing java sources. This way, you
can integrate exported DMN Drools rules into existing execution environments.
• To add a reference, specify a class name for the dictionary entry, for example
com.signavio.dmn.example.DataDefinition. The exported DRL file then contains an import
statement, for example import com.signavio.dmn.example.DataDefinition.
Note
Access to this feature depends on your license. For more information, contact your workspace
administrator.
SAP Signavio allows you to export process and decision models directly to Red Hat Decision Manager projects
at GitHub. Like this, you can seamlessly integrate diagrams that have been modeled with SAP Signavio into
your Red Hat Decision Manager projects.
Process models are exported and uploaded as BPMN 2.0 XML files and all linked decision models are exported
and uploaded as DRL files.
1. To start an export, select a BPMN diagram in the explorer and choose Import/Export Export RedHat
files to GitHub .
2. You need to select exactly one diagram. The export will include all linked DMN and BPMN diagrams.
3. In case you haven't configured the GitHub integration yet, you need to authorize SAP Signavio to push to
your GitHub repositories.
Otherwise, proceed at section Pushing diagrams to Red Hat Decision Manager projects [page 337].
4. Choose Authorize.
5. You are forwarded to GitHub, where you need to grant SAP Signavio permission to push to your
repositories.
6. Re-enter your password to confirm. Upon successful authorization, the following page will be displayed.
Now you can go back to the explorer and export the diagrams to GitHub.
To start an export, select a BPMN diagram in the explorer and choose Import/Export Export RedHat files to
GitHub .
The files are pushed by your user to the default branch (for example main). The commit message is signavio
upload .
Export user-created content in your workspace, send it to translators and import the translated files.
Note
You can translate user-created content into all languages that are activated in your workspace.
You can translate content directly, as described in section Translating diagrams [page 282]. You can also export
the content to be translated outside of SAP Signavio Process Manager.
The source language for all translations is always the default language of the workspace.
You export the content and send it to translators. To make the translation available in your workspace, you
import the translated files.
Exported Files
Ensure that the original file names and the folder structure are maintained during translation.
Note
Note
Once the PO files are translated, you can import them to SAP Signavio Process Manager.
For each target language, you've can upload one translated PO file at a time. If you've more than one file for a
language, repeat the import. You can't upload PO files for the default language of the workspace.
Related Information
Note
Access to this feature depends on your workspace settings. For more information, contact your workspace
administrator.
With SAP Signavio Process Manager, you can publish single diagrams to any intranet or Internet website using
the embedding feature. This chapter describes how to embed a diagram into a blog post or web page.
You can embed diagrams in other systems that SAP Signavio Process Manager supports.
Note
You need the access right Publish to embed a diagram. Access rights are set by your workspace
administrator.
To embed a diagram in an external system, you have to explicitly allow the embedding. This can be reverted
later on - in this case, all existing integrations of SAP Signavio diagrams will be deactivated.
Several use cases for embedding are listed and explained in the following chapters.
Embeddings of diagrams can be disabled at any time by withdrawing read access for these diagrams. This can
also be set in the Embed diagram dialog. Select the link Stop sharing the diagram for read-only access :
Via this link all embeddings become inactive, so that your diagram are no longer viewed on pages which
previously have linked such a link.
How to embed a diagram as an image in web pages, whereby the image is automatically updated whenever the
diagram is changed.
You can embed diagrams as images in web pages and this way share the diagrams with users outside your
workspace. Users can see the diagram image, but can't edit or comment on it.
The embedded diagram image is automatically updated when a change is made to the diagram.
If you want to use a specific diagram version as an image which never changes, you can export the diagram in
PNG or SVG format and use it in any context. Read more in section Export a diagram as an image [page 329].
You can embed a diagram using a HTML code snippet in a website or blog as an interactive element. The
advantage of this method over a picture export is that the most current version of the diagram is always
available on your page.
The following paragraph explains how to embed diagrams as an HTML code snippet into a blog or a web page
like Blogger, TypePad, or WordPress.
4. Paste the copied snippet in the desired location of the HTML code of your page or blog posts.
5. If the diagram is not shared for read access yet, choose Share document for read-only access .
If you select Stop sharing the diagram for read-only access in the embedding menu, the diagram will not be
available on the web page and on any other pages it was embedded in.
6. See a list of Supported blog and content management systems [page 347] to get an overview of supported
systems.
The embedded diagram does not allow navigation to linked diagrams or linked documents. If you need
the viewers to be able to navigate to linked diagrams and documents, please use SAP Signavio Process
Collaboration Hub.
To embed your diagram optimally in your website, you have to option to alter the diagram's size and then to
check size and aspect ration in a preview.
1. Specify the desired Width and Height . By default, it is set to auto , so the size of the interactive element
adapts to the system it is embedded in.
2. Choose Preview to check the changes.
In the preview, HTML code is displayed in addition to the interactive element. A zoom slider and scrollbars are
added automatically.
You can embed SAP Signavio diagrams in all blog and content management systems that allow the embedding
of HTML snippets.
For example:
• Jira
• Confluence
You can also embed a diagram view of SAP Signavio Process Collaboration Hub in 3rd-party applications.
These applications includes any system that allows embedding of HTML iframes .
Administrator Profile
Workspace administrators have extensive rights and can make profound changes to the workspace. We
recommend to grant this role to users with solid IT skills who are familiar with both the SAP Signavio products
and BPMN.
Users need a license for SAP Signavio Process Manager to become administrators.
It is important to communicate and document changes in workspace settings among your administrative team,
so that all administrators are up to date and can give accurate responses to user queries.
Add Administrators
To add or remove administrator permissions, add or remove the user to or from the user group Administrators.
Read more in section Create workspace administrators.
Get Started
To get started as a workspace administrator, see section Prepare your workspace - overview.
You find an overview of the most popular integration scenarios at System integration scenarios.
An overview of the SAP Signavio Process Manager APIs is available in section API access to SAP Signavio
Process Manager.
You can learn how to view reports analyzing your workspace and process model usage in section Process
Model Dashboards.
Related Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.