Download as pdf or txt
Download as pdf or txt
You are on page 1of 14

SAP Signavio business process model

connector

Troubleshooting Guide
Contents
1: Unable to add SAP Signavio System when creating a new Sync Project ................ 3
Error Message ............................................................................................................................... 3
Root Cause .................................................................................................................................... 3
Customer Resolution / Workaround ............................................................................................ 3
2: Unable to add SAP Solution Manager systems when creating a new Sync Project 4
Error Message ............................................................................................................................... 4
Root Cause .................................................................................................................................... 4
Customer Resolution / Workaround ............................................................................................ 4
3: BPMN 2.0 or other diagrams are located in SAP Signavio top-root folder ............... 5
Error Message ............................................................................................................................... 5
Root Cause .................................................................................................................................... 5
Customer Resolution / Workaround ............................................................................................ 5
4: Error running a diagram sync from SAP Solution Manager to SAP Signavio.......... 6
Error Message ............................................................................................................................... 6
Root Cause .................................................................................................................................... 7
Customer Resolution / Workaround ............................................................................................ 7
5: Attribute Mismatch (Inconsistent Behavior) ............................................................. 10
Error Message ............................................................................................................................. 10
Root Cause .................................................................................................................................. 10
Customer Resolution / Workaround .......................................................................................... 11
6: Element Locked ........................................................................................................... 11
Error Message ............................................................................................................................. 11
Root Cause .................................................................................................................................. 11
Customer Resolution / Workaround .......................................................................................... 12
Need to identify the user/users who are locking the branch and ensure the branch is
not being edited as we run the synchronization. .......................................................... 12
7: Known Issues .............................................................................................................. 12
Warning when Tasks are not linked to the correct Dictionary category. ................................ 13

2 / 14
1: Unable to add SAP Signavio System when creating a new
Sync Project

Error Message
Unable to fetch data from your systems. Please check your system details.

Root Cause
The created system details may be incorrect.

Customer Resolution / Workaround


Edit Connected System with correct system details.

3 / 14
2: Unable to add SAP Solution Manager systems when
creating a new Sync Project

Error Message
Unable to fetch data from your systems. Please check your system details.

Root Cause
SID, Client, hostname / workspace combination may have been entered incorrectly for Connected
System.
Username / password may have been entered incorrectly for Connected System.
Cloud Connector may have a Location ID which was not provided for Connected System.
Service User may not have correct roles assigned.
Relevant services may not be active in Solution Manager.

Customer Resolution / Workaround


Edit Connected System with correct system details.
Edit Connected System with correct username/password.
Verify if Cloud Connector contains a Location ID and update Connected System with the same value.
Verify if destination can be reached in BTP.
Ensure that the Service User being used has been given the appropriate roles in SU01. The list of
required roles is detailed here:
https://help.sap.com/docs/signavio-process-manager/workspace-admin-guide/configure-solman7-
2?locale=en-US

Use transaction SU53 to see if failed authorization check.


Ensure that the relevant services have been activated in transaction SICF.

4 / 14
3: BPMN 2.0 or other diagrams are located in SAP Signavio
top-root folder

Error Message
Sync errored for ObjectType: FOLDER with error: BPMN model can't be stored in the Folder that was
nominated to be Top Root Folder in the Sync Project settings with name Folder 2 and ID
eed78addab9b4b43a49a4612

Root Cause
BPMN 2.0 or other diagrams are located in SAP Signavio top-root folder (Shared Documents) or outside
synchronized Folder (Scenario).

Customer Resolution / Workaround


The issue will block any follow up synchronization. While the issue is being resolved by the product team,
customers can do the following to prevent or unblock the synchronization:

o Do not store any models at the top root folder whether it’s SAP Signavio Shared Folders to a
nominated Custom root folder.
o Do not store models in the sub-folders that are not Folder (Scenario) in SAP Signavio.
o If the issue happened for a test project that could be abandoned, then remove the Diagrams
from the top root folder and/or sub-folder. Create a new sync project and synchronize again.
o If the issue happened for a productive project, then remove the Diagrams from the top root
folder and / or sub-folder and contact SAP Support by opening an incident under BPI-SIG-
CA-BMB component.

5 / 14
4: Error running a diagram sync from SAP Solution Manager
to SAP Signavio

Error Message

When running an initial sync from SAP Solution Manager to SAP Signavio containing diagram elements
we can see errors such as the one above.

SOL-SIG Sync errored for ObjectType: DIAGRAM with error: Map internal to external failed for direction:
SOLMAN2SPM with error: TypeError: Cannot read properties of undefined (reading 'systemAObjectID')
with name and ID.

Variants of this error include:


Error 1
TypeError: Cannot read properties of undefined (reading 'ATTRIBUTES') with name and ID.

Error 2
TypeError: Cannot read properties of undefined (reading 'DATA') with name and ID.

Error 3
TypeError: Cannot read properties of undefined (reading 'systemAObjectID') with name and ID.

6 / 14
Root Cause
Error 1
The Diagram is empty and does not contain any object inside the diagram, e.g. empty diagram.

Error 2
The Diagram is missing BPMN Interchange XML for the connector to export the diagram to SAP Signavio.
This can happen if the diagram was imported to SAP Solution Manager from an external source and the
xml wasn't generated by SAP Solution Manager, therefore it will not be available in the API to pass to the
connector.

Error 3
The Diagram contains objects (tasks/process steps) that have been deleted or not inside the current
process model. Therefore, the connector cannot find the reference objects.

Customer Resolution / Workaround


Error 1
Syncing of empty diagrams (diagrams containing no PS Ref) is not supported. Customers should remove
any empty diagrams before syncing from SAP Solution Manager to SAP Signavio.

Error 2
Customer to retry importing objects (e.g. diagrams) from external source to Solution Manager. If
that does not work, then the customer will need to generate a Process Document. To run this the
following steps need to be performed:

1) Start Solution Documentation in SAP Solution Manager

7 / 14
2) Select a scope (if required)

3) From the Global Functions menu access the Process Document option

8 / 14
4) Select the relevant options and press the “OK” button

This is detailed in further detail in the following link:


https://help.sap.com/docs/SAP_Solution_Manager/60943adf3ff44893b62c568bb8a87d17/b3ad5557e03f9
067e10000000a4450e5.html?locale=en-US
Once the Process Document has been generated containing the diagrams, users should be able to repeat
synchronization using the same sync Project and import these diagrams to SAP Signavio.

9 / 14
Error 3
Customer to review all diagrams before syncing from SAP Solution Manager to SIG, to ensure that
diagrams contain PS Ref (Tasks) which have not been deleted.

5: Attribute Mismatch (Inconsistent Behavior)

Error Message

When doing a synchronization, an error such as the one below or the one above can occur
Sync errored for ObjectType: PROCESSMODEL with error: INVALID ATTRIBUTE TYPE
CARDINALITY_FOR:ID=0278129df9f78cfddb766c;TYPE=PROC;ATTR=Z_INFORMATION_ELEMENT_U
SED. with name and ID

Sync errored for ObjectType: PROCSTEP with error:


00cb56564f94acae3258d_CONTENT_OFF_ATTR_TEAMMEMBERID_TO_LONG. with name and ID

Root Cause
The attribute type or properties of the SAP Signavio custom attribute do not match the type or properties
of the SAP Solution Manager custom attribute. For example, the SAP Signavio custom attribute may be
single-value and the SAP Solution Manager custom attribute may be multi-value.

10 / 14
Customer Resolution / Workaround
Need to ensure that the customer attributes match attribute type.

6: Element Locked

Error Message

When doing a synchronization from SAP Signavio to SAP Solution Manager, we can come across an error
such as the below or the one above.

Root Cause
This could occur if a user is editing the Solution Documentation branch as the synchronization is trying to
run.

11 / 14
Customer Resolution / Workaround

Need to identify the user/users who are locking the branch and ensure the branch is not being edited as
we run the synchronization.

7: Known Issues
Please note that the following exceptions still exist in the current GA release of the connector delivered
under version 1.1.0 R23Q2

• SAP Signavio to SAP Solution Manager synchronization: import runs into an error if BPMN
2.0 or other diagrams are stored in the top root folder or outside a scenario, as described
above in known errors.
• For SAP Signavio to SAP Solution Manager update sync, if the folders and/or diagrams were
not included in the initial synchronization, then they are still not transferred to SAP Solution
Manager in the update sync run, even if they meet all prerequisites for being included. The
folder or diagram might have been skipped in the initial sync run due to folders being empty
and/or diagrams being in the wrong part of the process structure. Folders, scenarios and
diagrams that were initially synchronized successfully could be moved and all changes are
passed to SAP Solution Manager correctly. The folders that were ignored would need to be
recreated again in SAP Signavio if they are required.
• Incorrect number of logs for the update sync run from SAP Signavio to SAP Solution
Manager. After successful update synchronization from SAP Signavio to SAP Solution
Manager, the number of logs for transferred objects is higher than expected. It might extend
synchronization time, but this issue has no impact on consistency or correctness of the
synchronized data.
• For SAP Signavio to SAP Solution Manager synchronization, moving tasks from one BPMN
2.0 diagram to another is not reflected correctly after update sync run. If Task is moved to a
different diagram using cut and paste function in SAP Signavio, the changes are not reflected
in SAP Solution Manager.
• If a sync project which has been activated needs to be deleted, please contact SAP Support
by opening an incident under BPI-SIG-CA-BMB component. Users can create another project
without deleting any previous projects.

If we want folders to be synced, we need to ensure that they contain some content. Considering that an
empty folder might be updated with a BPMN 2.0 diagram or another folder, the connector will assign a
specific type to it either considering it a Folder or a Scenario. In SAP Solution Manager it’s not possible to
convert folders to scenarios and thus the connector needs to know the type of Folder before the
synchronization.

12 / 14
Currently, it is not possible to sync diagram changes from SAP Signavio. Diagram and process are two
separate object types in SAP Solution Manager. Synchronization of the updates to SAP Solution Manager
BPMN 2.0 diagrams is not yet supported by the connector.

Warning when Tasks are not linked to the correct Dictionary category.

The connector will skip those for tasks that are not stored in the right mapped Dictionary or not stored/linked
to a Dictionary category (Activity) at all and continue with synchronization of other objects. If the user
corrects those Tasks and moves and/or links them to the right, mapped in the sync project, Dictionary
Category, the Tasks will be imported to SAP Solution Manager via the next update synchronization run.

13 / 14
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
See Legal Notice on www.sap.com/legal-notice for use terms,
disclaimers, disclosures, or restrictions related to SAP Materials
for general audiences.

You might also like