I understand you question is addressed to IDS Scheer but let me just make two comments:
1. I find versioning in ARIS 7.1 very usefull. And it's very nice that it can be done at any level, not only DB.
2. I don't know what you mean by "After creating a version, there is no way to revert back to an earlier version" as you can choose any time which version to open and it's working both in opening and for publishing.
I have to admit I have no experience with RCM so may be the problem is with RCM integration.
Appreciate your quick response, Ivo.
My question is not only addressed to IDS but also to others on how it is being used. That way your response is valuable.
- Yes -- Opening older version is possible but only in Protected mode -- incase you want to revert back to an earlier version & make new changes over that earlier version... Is that possible?
- How do you publish an earlier version?
Thanks & Regards,
if you want to restore a old state you can backup the data base (until the changelist number you want to restore) . If you import the back upfile the old state is writeable again, but the new DB contains only the data until the restored changelist.
Appreciate your response, Thomas... But you are referring to restoring the entire database...
My query was whether restoring an earlier version of a model is possible... If possible, how can this be done?
Ivo has mentioned that earlier versions could even be published -- how do we get that done?
if you want to restore only one model than try this:
1. Open the DB login dialog and log in with the changelist that you want:
(in this case 1)
2. Navigate to your model in the explorer tree.
3. Login on a other db
3. Drag yout model to the database node of the other DB.
-> now you have the old state of your model (in a other DB)
If you want to restore a entire DB at a old state than try the Backup and Restore actions.
i'am also interested in versioning single models. For my understandig it is actually only possible to save the whole context. That doesn't make sense in a multiuser environment and even in a single user environment.
Thanks for sharing those steps -- had not tried this earlier.
But doesn't these steps also restore the model onto a different database and not to the same database? This will only be an overhead -- with the designer not having access to multiple databases but only to one development database.
Any other solutions / workarounds?
Also waiting to hear from Sebastian, Frank and other experts from IDS on this.... Guys -- Are you listening? :-)
if you want to restore the model in the same Db you can try this.
Select the model in the explorer tree.
Open the tab model revisions (in the table).
Rigth mouse click on the revision that you want to resore.
Select XML explort from the context menu and export the old model sate.
After that import the xml file again and override the exsiting model.
it is possible to versionize a single model in a revision, but if you login on the DB state of that change list you will see your model and all other model you have versionized before (but no other models). The reason for this is to support the RCM where a new version is based on the previous version.
Hi Thomas -- I'll try the option stated & get back.
Betw - didn't noticed that you are also from IDS, when I posted my earlier comment... Appreciate your prompt responses.
What you saying is correct we cant revert back the older version in the same database.
Even i have tried in many ways to revert the changes, but didnt work out.
The only way we can restore the entire database then its will revert back the older one.
Pls share your thoughts and experience.
I, too, am interested in versioning. Does anyone have BDPs for setting-up versioning? We are thinking of turning on versioning, but the documentation is a bit confusing.
I was investigating the same issue and went through all of your suggestions.
I cannot understand the essense of difference between variants and versions (I understand these are different functionalities, but what the main difference of usage).
Could anyone help with this?
the difference between a variant and versioning is simple. If you create a variant of a model you just create a new model. This model is a normal model you can edit like the original model. The only benefit is that you can compare the variant model with the original model. If you use versioning feature and you create a verion of a model (or a group or the entire DB) than a copy of the model (or the group or the entire DB) is created and stored in the DB. You can not see the versionized data in the normal tree (except you logout from the DB and login again with the vrersion state (third page at the login wizard)). At a normal login you can see the versions of a model if you select the model in the explorer tree (explorer module). You can now switch in the table to the tab (versions (third tab)). In this table you can see all versions of the model and you can compare them. The other main diffrent to variants is that version are read only and variants can be changed.
To cut a long story short if you want to change your new created models and compare both models use variants. If you wan to save some states of a model and compare them use versioning.
Thanks Thomas ... this is great information! I did do a test with a copy of our DB and when versioning was turned on, it immediately more than doubled the size of the DB and ARIS performance decreased. We are currently using v.7.1 SR1. Could that possibly be a problem? Does versioning work better in SR5? Darlene
to use versioning you need:
1. Aris 7.1 (Client/Server)
2. You need to create a new DB (and check the option versionable in the create dialog) or you need to back up your exsiting DB and restore the DB as a versionable DB.
Now you can start the versioning at a model or a group.
Thank you for the information. I have now a clearer picture in my mind.
If you create the first version of the entire DB than it is clear that the database size will double. Because the entire database content is saved in the versioning repository of the database. If you use the versioning for the second time than only the differences to the last version will be saved. Regarding the performance problem, you should try the versioning feature with SR05 we have increased performance for some features.(You need to update the client and the server.)
Many people say that only versions or variants of a model can be compared. There is another scenario i stumbled upon: any two models of the same type and in the same group can be compared. Using explorer module, multi-select the two models (CTRL+Click in the tabbed/list view, not in the treeview). Then, right-click and choose 'compare model...'. I have not found a way to compare across groups, but surely there is no technical barrier. Hope this helps.
I am exploring the use of Versioning and all the above comments are very useful indeed. However it would be very useful to be able to run reports of change information out to documents, as far as I can see it is only possible to do on-screen comparisons. How would I generate a summary report of changes between two versions? Does anyone have any ideas, or perhaps has a script?
Martin - thank you for this information, Rob's report looks very powerful.
However, maybe I was not clear enough in what I required. The summary I am looking for is not at this detailed level per model, but rather to compare two versions of a complete folder structure (or indeed a database) and get a summary listing of all the models where there are differences. You might say that it is a "first pass" report.
Once I have this, I can then choose to do selective reporting using a report such as the ones you mention.
Any ideas are welcome.
Do you have detailed instructions (or screen shots) for setting-up and executing versioning. I am now using v.7.1 SR8 and want to ensure that I am setting up everything properly. The instructions in ARIS Help are very sketchy!
To similar problem, here my approach. the usage scenario of Mr. Shankar Ganesh is similar to continuous integration scenario (cf http://en.wikipedia.org/wiki/Continuous_integration ).
Currently it's not possible to have like Source Version Control features within ARIS tools: versioning is simply timeline tag the models).
Meanwhile an Manual Workaround exist.
Currently as ARIS BPM plateform i use these environments
* Development, for development and maintenance of the models.
* MCV (Model Control Versioning) Repository to version the Models (the simpliest way is to use a SCV with the backup script)
* Testing, for reviewing the models with the BPM quality Manager, Business Manger.
* Acceptance, for reviewing by the all the impacted business side
* Publication, for publishing the models on the intranet of the company.
The "check in "/ "check out" (or commit/update/merge) will be made via the use a SCV with the backup script, + compare model version. Idem for deployments between envs
Hope in Future version of ARIS the versioning feature will be improved
I am very interested in your environment architecture. I am in charge of defining the best deploy of ARIS Business Servers for various customers and do it compatible with a optimal management of scripts (reports/macros) complemented probably with the use of a Subversion, CVS, or whatever.
Could you please provide me/us with a more detailed map of your environments?
Does any one know a reference for this issue in the ARIS literature?
you can contact me via linkedin djebar hammouche
I wanted to publish multiple versions of a model, is this possible in ARIS 7.1. Please let me know.
Can anyone please guide how to copy my EPC models from ARIS Express to ARIS IT Designer 7.2. I have done initial learning and modeling on freeware but wish to copy someof the work on ARIS IT Designer 7.2. I need someone to guide me if there is any possibility because at presents the models are getting copied as images.
Attached is a document on importing ARIS Express into ARIS
Thank you for your help and support.
The problem I am facing here is that the Import function provides only graphic option and there is no option to import .adf files when i right click on the explorer tree.
Please let me know how may I proceed.
If you are using a Designer license you won't be able to import, you will need an Architect license