Versioning of Models

Victoria Longman
Victoria Longman
in AppWorks #1

Part of the work that I do is to input data into Provision and create a version of a particular model. I am coming to the conclusion that archiving the previous models would be a worth while thing to do so all i am left with is the most current of data.

 

However i have been wondering if there would be any particular benefits from leaving all the versions in the one place. Any ideas?

 

Ex.

Goal Model

             Jan 2009

             Feb 2009

             Mar 2009

So On.....

Tagged:

Comments

  • Gerry_Victoria
    Gerry_Victoria
    #2

    Hi Victoria:

     

    Based on your example you might want to consider dimensioning your models.  This will allow you to have for example multiple Goal models i.e.. Jan 2010, February 2010 in the same notebook.  Then you can easily view them and visually see the differences.  In addition, as you dimension an object you can change its properties etc. and it will not change the properties in the original object.  In ProVision you are always working within the confines of a Notebook and when you change an object the change is dynamic for the instantiation of the object within it's notebook. 

    You can start by selecting the object Inventory and create a Dimension Type called Version then you will select the Object type called Dimensions and create your various Dimensions such as January 2010 etc.  Once you create your Dimensions you can apply them to a model or a single object by a right mouse click  and select Dimensions. Next you will need to understand the difference between create a projection, substitute a projection and Configure.  Without going into immense detail in this post you can read context sensitive help on each of these types of Dimensions.

     

    Regards,

    Gerry

  • Gabriele Beretti
    Gabriele Beretti
    #3

    Hi all,

    this topic is very interesting.

    I wonder how use the “version” feature at best in a corporate environment using Knowledge Exchange(6.2.1). What is the best practice to leverage this useful feature?
    For example, how can I compare 2 or more versions of the same model/notebook ?

     

    A way I found to do this is to check-out (by copy)  a version of the notebook in a new notebook and then check-out (by copy) another version of the notebook in another. Then, I compare the 2 notebooks with the compare functionality.

     

    Is this way the best?

     

    Thanks in advance

    Gabriele

  • Michael_Langford
    Michael_Langford
    #4

    I have found that using the dimension feature to identify which objects, e.g..: activity usage, were added or updated for a version of any model to be a good solution. 

     

    To do this, you must first version the subject and create a blank model, then copy in the old version.  Update and add using the dimension substitution function.  If you delete, keep track and identify in the model detail description for those wishing to track in the future.  Without having to use the compare feature, you can find the "current" changes quickly and easily.  Also change the version ID in the model details.  Remember to update any upstream process and/or workflow models to reflect the newer version of the subject object - use dimension substitution. 

     

    A helpful document can be found on the ProVision support documentation site.  Download the .pdf for Metastorm ProVision Dimensions.

     

    Regards,

    Michael Langford

  • Victoria Longman
    Victoria Longman
    #5

    I see where your going with this Gerry but I am still trying to assertain what advantages would be got from leaving all the models in one notebook. Other than running a report for the current month the data isnt used, its just a holding place. 12 months in a year = 12 models and I have been doing this for 3 years!

     

    Thanks for all the feedback

    Victoria

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform