cancel
Showing results for 
Search instead for 
Did you mean: 

Mandatory attributes and Convention checks in Signavio Process Manager

vp_nbn
Explorer
0 Kudos
219

Hi team and a happy New Year to everyone 🎆!

In our SAP Signavio Process Manager setup/ configuration, we have defined a number of main properties and custom attributes as mandatory, primarily at the diagram level. To enforce their usage, we’ve implemented a custom modeling convention. Section 2.2. of the convention (Definition of mandatory attributes) contains the rules for populating these mandatory attributes. Diagrams that violate modelling conventions (i.e. contain errors) cannot be published (to the Signavio Collaboration Hub)

For instance, in the screenshot provided you can see an example from our workspace. The diagram-level attribute Publisher is not populated, which triggers an error when the Convention check is triggered.

I’m curious to know your practice in this regard.

  1. Do you apply a separate rule for each attribute, or do you cover multiple attributes with a single rule? Could you please share your rationale behind this choice?
  2. Have you received feedback from your modellers regarding the error messages, particularly their clarity in helping the modellers identify and rectify the errors?
  3. Over the years of using Signavio, have you changed your approach to enforcing mandatory attributes? If yes, what factors led to this change?

I eagerly await your response. Thank you for your time and consideration.

Kind regards,

 

Vladimir

View Entire Topic

Hello Vladimir,

1. we also use mandatory attributes for example for the information of authorization data. 

We created one rule for our specific mandatory attributes and included those which should give an error. I think an additional rule is only required if you want to control the level of error/warning/information.

2. feedback is mixed, of course a mandatory attribute always leads to additional effort especially if the content is not (yet) known and you have to put something like "n.a." or "not known". This will always be a kind of downside if you make an entry mandatory. so it should be chosen wisely and with purpose.

From a management perspective though you have then a nice opportunity to identify areas which are unclear

3. we did not make any changes so far but it depends on the overall strategy we want to follow in regards of a tansformation platform and reusing data from the process design in signavio process manager.

Hope this helps.

Best

Christian

vp_nbn
Explorer
0 Kudos

Thank you Christian. Much appreciated.

Kind regards.

 

Vladimir