Skip to main content

[wish] Prevent information on BPMN-objects to change when published

Not planned
Roland Kaijen
Edited

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).

Wish

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.

Why

Changed information on objects in published BPMN-worksets will not be available in the base for future changes and therefore poses a risk.

Workaround

Create and communicate a way of working where users will not make changes in published BPMN-worksets…

Possible Solution

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.

0

Comments

6 comments

Date Votes
  • Official comment
    Ameya Sapre

    Hello all,

    We are closing this as not planned due to lack of upvotes.

    Thanks,

    Team ValueBlue

  • MG || Gemeente Tilburg

    If you imply that the name of referenced objects cannot be altered, I would not agree with this wish. This would make working with BD more cumbersome.

    I agree though that a published BPMN view should remain unaltered. This wish was suggested a while ago, to keep the changes to a minimum and re-using objects that are just slightly different easier:
    https://valueblue.zendesk.com/hc/en-us/community/posts/360010118219-Different-object-name-in-view

    0
  • Roland Kaijen

    I'm not sure I understand you correctly, because changing the name of a BPMN-object (e.g. a Task) is not possible in a published BPMN-workset (however, changing the name of an ArchiMate-object from an published ArchiMate-workset is possible) - I think your wish is related to ArchiMate objects and views?

    I have created a questionnaire to add user or system instructions to the BPMN-tasks. These instructions can be changed from a published BPMN-workset, but don't 'travel back' to the base-workset used for future changes. There is a different approach to objects in ArchiMate and BPMN, resulting in this unwanted behavior from a BPMN perspective.

    0
  • MG || Gemeente Tilburg

    Ah, sorry, I though you meant changing the names of Business Objects or Application Components or Roles that also show on your published BPMN views. Never mind then :)

    The wish I referred to was for Archimate views - but can just as well be extended to BPMN views (for the objects I just mentioned).

    0
  • Roland Kaijen

    No worries - always good to see people in the community taking time to read and reflect on each others wishes!

    0
  • BOFH

    This I think could be solved by enabling staging/LCM, see https://valueblue.zendesk.com/hc/en-us/community/posts/5884480006674-Introduceer-staging-DEV-ACC-PRD-ie-versioning-LCM

    All of PRD would be readonly, modify objects in ACC by demoting or archiving and promoting ACC>PRD

    0

Post is closed for comments.

Didn't find what you were looking for?

New post