Profile picture for user VC_Bakker

Hello,

We've been cleaning up our 2 library models concerning roles.

This involved some consolidation of certain roles.

In essence this would come down to the following action in DEV;

Pick objects;

Object A - GUID A ( 1 occurrence processes A)

Object B - GUID B (2 occurrences process B, C)

Both will become 'Object A', with GUID A,  for I have chosen this object as the 'Master' in the consolidation functionality.

If I now look into the occurrences of Object A in the DEV database, it would have 3 occurrences in the DEV database. (A,B,C)

If I then merge the library towards the PUB database, my library models are updated, but not the number of occurrences.

Object B now resides in the model folder (moved?), not in the library folder anymore, but still exists in process A.

Object B still only has 2 occurrences. 

How can I ensure that the library also pushes these 'complicated' changes, without changing the model itself?

I've tried all settings concerning merges, nothing seems to work.

Thanks for your time,

BR,

Vincent

by M. Zschuckelt
Posted on Wed, 01/31/2024 - 14:29

Hello Vincent,

what you are publishing in Change lists is always models. So for processes B and C not to contain Object B any more you have to publish them. This behaviour makes sense, because the role library owner is (normally) different from the process owner and the process owner is responsible for the usage of roles in his process. You are not publishing the consolidation operation but copying/merging certain content from one DB to another.

Since you did not publish processes B and C to the PUB and object B was not contained in the role library group any more (probably you merged the library group to PUB database), ARIS had to find a way to provide that object to these models and resorted to moving it to one of the groups of those.

BR,

 M. Zschuckelt

1
by Vincent Bakker Author
Posted on Wed, 02/07/2024 - 12:00

Hello,

Thanks for the answer!

Although it is a logical one, I am still under the impression that 'pushing' those library changes towards a model would be 'a win'. 

BR,

Vincent

0
by M. Zschuckelt
Posted on Mon, 02/12/2024 - 14:11

In reply to by VC_Bakker

The common thing to do is starting some governance in your DEV database to have the process owners update their processes with the new objects.

0
by Vincent Bakker Author
Posted on Thu, 03/07/2024 - 07:59

Hello,

Thanks for the answer, we're now 'repairing' both DEV and PUB in the exact same manner with the 'consolidation' functionality, it works for our 'problem' at hand.

BR,

Vincent

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