Dear All,
I am new in ARIS, had a training but only on limited features.
I have a database with group of Models, i have copy one model from one location to another location for the purpose of keeping old copy for future reference, now having issue that model is not appear on ARIS Connect to Users, but while log in with system admin it is showing, Please advise.
I look forward to your response.
Thanks,
JD
Hello Mr. Jadoon,
Do the users who need access to the model have access privileges to the location (group) where the model is stored? In addition, objects of a model may be stored in a different group than the model. In this case, users may need to have access privileges to all these groups.
Best regards
Hi Mr. Fritz,
Thank you for your reply,
As i mentioned above that i am new to ARIS, there was a issue of privileges, but wonder how it was disappeared, i just copy and past to another location, after that it's disappeared from user.
Can you please advise while coping or moving the model from one location to another what steps should be considered, as we have 4 options while pasting.
We have two Groups in our database, 1 is for AS-IS process and 2nd is for TO-BE, if i would like to move process between what should i have to consider?
Thank you again for your help.
JJ.
Hi Mr. Jadoon,
When you move models, note that models can be saved in one group, while objects used in the models can be saved in another group. This can cause a user to have access to a model, but not to all objects used in the model. Conversely, models can be stored in a group to which a user has no access privileges, while objects are stored in a group to which the user has access.
This behavior makes it possible to build a very differentiated permission system.
If I have understood it correctly, you want all users to be able to access both groups. In this context, for example, you can assign read permission to all users of both groups. Please note that if you create a new group, you must assign the appropriate access privileges to the users for this group. If you create new users, you must also assign the corresponding access privileges to these users.
Once you move a model from one group to another, you can move it with or without the objects. If you have set up a differentiated permission system, you must ensure that a model and/or the objects are not moved to a group where users who need to access these items do not have access privileges.
Best regards
Thank you Very Much Mr. Fritz,
Another quesiton pls,
We have already Models prepared in ARIS, how we can control the revision?
If we make changes in the existing EPC, is it possible that orignal will remain same, and we can compare the Changes with Rev.01 to Rev.00 .
Please Advise!
Thank for your usual support.
J.
Hello J.,
for keeping old "versions" ARIS has the concept of "versioning". With that you can add an arbitrary number of models and objects to a "change list". This change list gets a number, which you may consider a version number. You can publish such a change list in the portal, e. g. you publish change list no. 5 in the portal. That means you can see any content that is part of any change list up to number 5 in the state it has in the youngest of those change lists. It's important that you fully understand this impact on the publishing features.
To be able to create change lists your database must have been created as a versionable database. And you must have the "version" permission on the groups with the artefacts you want to version and if I am not mistaken you also need the ARIS Architect client for that.
In ARIS Architect there are features to log in to the database with a change list number so you can see all change list contents as it would get published with that change list. And you can compare different versions of models as they were in different change lists. I would recommend to take the Advanced training to get started on these administrative features and understand the implications.
Because of the impact of versioning on the publication you should set up a governance concept, what shall be versioned and when (quality gate) and how things will be published and when (sign-off). There are different possible strategies you may follow. There are also strategies involving more than one database.
For very simple experimenting without the versioning feature you could tentatively do a definition copy of a model and experiment there. In ARIS architect you can also compare arbitrary models, so you could compare your changes with the original. But please: Throw away your new copies of objects and models and not the originals after you have made up your mind about the way to go. You should retain the identity of both models and objects over their whole lifecycle or you give up many advantages of modelling versus drawing. You will appreciate that with advancing maturity of your modelling initiative.
Best regards, M. Zschuckelt
Hello J,
one more remark: versioning is also available in ARIS Connect, if you have versioning permissions on a group.
If your database was not created as being versionable you can change that as follows:
1. Backup the database
2. Rename the database (all users must be logged off from the DB for this to work). Or just delete it (if you trust the backup).
3. Restore the backup checking the option to restore as a versionable database.
The database will have a slightly different icon in the explorer tree.
Best regards, M. Zschuckelt