Best practice for maintaining a Process ID in Signavio Process Explorer?

[anna_henke28]

Hi,

I am looking for a best practice on how to maintain a unique identifier for processes managed within SAP Signavio. By this I don't mean the internal ID, but an identifier that serves as a "memorable" ID. I understand that we can maintain an ID value manually in an attribute, but I have not been able to configure such field to ensure that the value is indeed unique and immutable.

I believe that the name of a process must be unique within a workspace, but to reference a process from e.g. outside of Signavio I want to something else than the name, as it may change in the the course of its lifetime.

Has anyone come up with a solution to this?

Thank you,

Anna

[danielschoeneck · Accepted solution]

Hi Anna,

we are using a scheme of steps in 10 for our process IDs, so we are able to split processes or to insert a new process in between, without re-numbering all the following processes. And we have an according attribute for this for each diagram. See example attached.

[anna_henke28 · Accepted solution]

Hi danielschoeneck2 , I like the approach of showing the ID as an overlay, thank you!

Have you implemented a rule that checks the uniqueness of that attribute?

[danielschoeneck · Accepted solution]

No, and I think there is no standard solution for that...

As only the Signavio admins are defining and entering the process IDs (in the approval workflow) we can manage that all process IDs are unique.

[rkesireddy]

@danielschoeneck, could you please advise the steps/configure the below changes you explained?

[DanielLerch20]

We do it a little bit different 🙂

We defined the hirachie corresponding to the departemnt which is in charge of the process. After that it is followed by a flowing number which exist only once in combination with the letters before.

example:

Process Describtion - Department 1 - Group A - Team B - 23

PD-D1-GA-TB-23

Process Describtion - Department 2 - Group B - Team A - 23

PD-D2-GB-TA-23

If we have to add a process between process 22 and process 23 and the last number at this Team is 121 than the new process ist process 122.

with this ID all user can search for every process corresponding to a team they know. Otherwise they search in our Landscape.

Let me know what you think about this.

[anna_henke28]

daniellerch - gotcha. This solution also relies on a manual process to create unique IDs, but I guess this is just something that we currently have to deal with. Your solution is smart in regards to that you can already see from the ID itself where the process is located at. We are currently heading for a solution that combines the approaches here in the forum.

[marc-werner]

Hi Anna,

we are also struggling with this topic.

Currently we are using a numbering like this:

1.main level

1.1 2nd level

1.1.1 3rd level

In addition with the naming of the object it is more or less unique.

Within Modeling Rules it is also possibel to implement a check, but the logic is not well explained.
(1.3 Usage of a numbering schema in diagram names)2023-12-18-14-39-04-window.jpg

kind regards

Marc

[anna_henke28]

Thank you, marc-werner - this is something we also considered.

I see some drawbacks in this solution as well (like lack of inmutability), but as Signavio does the ordering in a folder according to the name, it would become noticable when an ID is used twice.

But maybe it is the most pragmatic approach so far.