Simplifying the creation of an "Official BPMN"
Gepland
What is your wish?
As an admin, I want to be able to make BPMNs official with 1 press of a button.
Why do you want this wish?
Keeping different versions of BPMN is not something everyone wants. It reduces the management activities for an admin.
It simplifies the official making process.
With less chance of errors.
Do you have a workaround? And if so, what is it?
Manual removal of views.
With a chance of deleting the wrong view.
How would you ideally solve the problem?
If a process already has an official version it should automatically be dropped.
The name of an official BPMN should be taken from the view it is based on to start with.
If the name already exists it should be able to be overwritten.
The result, of course, would be the deletion of a published version of the view.
How big is the wish on a scale from 1 to 5? (1 = it would be nice, but definitely not necessary, and 5 = I cannot work another day without it).
4
-
Hi,
I am going to discuss this in our next feedback session. I'll let you know.
0 -
Eric Arts "If a process already has an official version it should automatically be dropped" should already be possible (it will become a published view, which is not the same as an official view)
0 -
We will work on this when we proceed with RBAC in 2022 / 2023! Please keep an eye on the release channel.
0 -
Rob Korving In your answer you say the "automatic dropping" is already possible, but that is not true when you want to keep the name of the view identical (which you'll want for usability and governing purposes). I guess versioning of views will solve this issue, as it is quite the hassle to work with.
0
U moet u aanmelden om een opmerking te plaatsen.
Opmerkingen
4 opmerkingen