[wish] Prevent information on BPMN-objects to change when publishedNot planned
Before I make a BPMN-workset official I publish the BPMN-workset to create a clear version that can be checked and accepted (and then made into the offical version).
I want to avoid users to change information on objects in a published BPMN-workset. Or, if people are able to change information on the objects (like in ArchiMate-worksets), these changes can be seen on the objects in the workset that is the base for future changes.
Changed information on objects in published BPMN-worksets will not be available in the base for future changes and therefore poses a risk.
Create and communicate a way of working where users will not make changes in published BPMN-worksets…
If BPMN-objects could live outside a workset (in a repository) the way of working would be similar to ArchiMate and changes would be visible in the base for future change (this would also could help in solving this wish: [wish] relate BPMN intermediate events: connect throw to catch).
Another approach could be to prevent information on object to be changed if a workset is published.
Post is closed for comments.