3 weeks ago
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.
I eagerly await your response. Thank you for your time and consideration.
Kind regards,
Vladimir
Request clarification before answering.
Hi Vladimir,
Wishing you and your team a very Happy New Year! 🎉
Thank you for reaching out with such a detailed and thoughtful question about SAP Signavio Process Manager. It’s a great topic to discuss, and I’m happy to share how we’ve approached similar challenges.
In our setup, we usually create separate rules for each mandatory attribute instead of grouping them together. While it might seem like extra work, this method has worked better for us because:
That said, we occasionally combine related attributes (like diagram metadata) into a single rule when it makes sense, as long as it doesn’t compromise clarity for the team.
We’ve learned a lot from listening to our modelers about error messages. Here’s what’s worked well for us:
By focusing on clarity and guidance, we’ve been able to reduce frustration and speed up issue resolution.
Yes, we’ve definitely changed how we enforce mandatory attributes over the years! Here’s why:
These changes weren’t always big, but they’ve made a meaningful difference in how smoothly things run.
I hope this gives you some useful insights into how we’ve tackled these challenges. The key for us has been balancing clear rules with flexibility, and always listening to the team for feedback.
If you’d like to dive deeper into any of this or compare notes, I’d be happy to chat more.
Br,
Rahul Aryan
Albatha Holdings LLC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Rahul,
your response is highly appreciated.
My thinking was along similar lines so it's great to a confirmation. (I hope there is no confirmation bias here.)
I was wondering whether you could elaborate a bit more on how you include simple steps for resolving the issue to making Error messages actionable.
Kind regards,
Vladimir
User | Count |
---|---|
52 | |
8 | |
5 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.