AS

Hi to all,

in an older post I read that:

"You are in a model and you like to version it. You open the version window and automatically your version activity gets a change list number assigned (the next available).

You enter a comment (the change list comment) and you press enter.

The versioning mechanism is now looking for all objects used by and all models linked to your current model (if requested) and will activate a new version."

This means that when I select a model to be versioned in a particular group (folder), all linked diagrams (even if they are in other groups (folders)) are revisioned, and are revisioned all the objects that are linked to it: it's right?

Are the models that are not linked to the selected one, but also contain copies of objects that are present in the selected models versioned?

Thanks,

Anna.

by Sere Le
Posted on Thu, 06/29/2017 - 16:06

Hi, I think the answer to both these questions is ‘Yes’.

For example, considering a DB composed by:

  • a folder containing objects libraries (divided into Organizational, Application Systems, etc.);
  • a folder with the company process map, containing also sub-models classified into Management and Core processes folders (and these folders containing other sub-folders, with two or three levels below).
  1. If I create the version of model A, located in the 1° level of core process and assigned with: sub-processes on 2° level (models: A.1, A.2), and other models at the 1° level of management processes (for example model B), setting as level of assignments = 1, the change list obtained includes versioning of models A.1, A.2 and also the versioning of model B. How can I block the versioning of model B?
  2. If model A contains object C in occurence, and object C is also in an other model (model B), renaming object C in “D”, saving changes and versioning model A, what's happen to this object? Selecting in versioning wizard “level of assignments = 0”, is model B also versioned? ... In my versioning tests I see object C renamed in “D” also in model A and in model B, is it correct?

Finally, I’m not sure what’s happen in ARIS with versioning: does ARIS make a copy of models (and objects) selected in versioning? And, If I create a version of the ‘main group’ of my DB, does ARIS duplicate the entire DB ?

Thanks in advance for answers!

S.

0
by Tony Iliev
Posted on Mon, 07/03/2017 - 14:07

Hello,

The versioning process is a bit more complicated than it looks. The answer to the question "Are the models that are not linked to the selected one, but also contain copies of objects that are present in the selected models versioned?" is "No". Versioning is applicable to models and affects models, but please do not forget the object's definition-occurrence condition: if you change an attribute in one of its occurrences then the change would take effect on all of its occurrences. This is because you're making changes in the object's definition.

"Finally, I’m not sure what’s happen in ARIS with versioning: does ARIS make a copy of models (and objects) selected in versioning? And, If I create a version of the ‘main group’ of my DB, does ARIS duplicate the entire DB ?"

You're almost correct. ARIS would create copies of the model's content, although they are not editable and not visible as separate items. Pretty much like a snapshot, but quite heavy one as it carries all of the item's information. In theory, if you version all of your models, the db (if clear) will double its size.

In my everyday work I would say that less change lists create less problems. It is a good idea to create one change list for a large number of models (if possible of course), instead of version models one by one, especially when they are subject of one and the same review.

Regards

Tony

0

Featured achievement

Rookie
Say hello to the ARIS Community! Personalize your community experience by following forums or tags, liking a post or uploading a profile picture.
Recent Unlocks

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock