Plex 2E

  • 1.  Level Consolidation

    Posted Dec 14, 2011 04:53 AM
    Migrating up to r7 would seem to provide an ideal opportunity to consolidate all existing levels into a single new base level. Do any tools exist for this purpose?


  • 2.  RE: Level Consolidation

    Posted Dec 14, 2011 05:07 AM
    No tools to speak of but one of the limitations (not for you in this case) of the Model Export is it does not cater for levels and versions just exports a snap shot of the local model at that current configuartion.

    So you could simply export a local and import it into a brand new group model and there you have it.


  • 3.  RE: Level Consolidation

    Posted Dec 16, 2011 08:12 AM
    looking in Knowledge Base Article for something else but came across the following

    XML IMPORT INTO ATTACHED LIBRARY

    Please note the following is in Plex help under Exporting an Object which I assume (assumptions kill projects..) would be part of the Exporting a Model and would prove a problem
    Note: Local overrides on the parameter mappings inherited function and API calls are not exported.
    I would test for this does not occur in the "Export a Model" process, if it does then my opinion it is a show stopper and you are still asking around for a tool


  • 4.  RE: Level Consolidation

    Posted Jan 18, 2012 04:56 PM
    Any help dave or have you found a tool to do this?


  • 5.  RE: Level Consolidation
    Best Answer

    Posted Jan 26, 2012 04:30 AM
    George, no progress on this one. Given the size/complexity of the application it looks like we will have to retain the current levels. Dave.


  • 6.  RE: Level Consolidation

    Posted Mar 10, 2014 04:12 PM

    Reading Plex Help of an evening as you do...

     

    Model Object Export/Import

    The Model Object Export/Import enables the copying of object definitions between CA Plex models. A simple import/export facility allows easy copying of objects between models, both within a customer development department and between customers. The information is contained in XML (eXtensible Markup Language) documents.

    If you are editing a local model, you can export the entire model or export just a number of objects selected in an open Object Browser, Inheritance Browser, or Dependency Browser. Or, you can also elect to import the contents of an XML file.

    Both import and export are operationally long running processes. Therefore, each process provides an update regarding progress via the dialog, with the ability to cancel the process at any stage. Canceling an import just stops the import process; it does not roll back any changes made to a model as a result of running the import.

    Uses

    The most obvious use of this feature is to copy information between local models.

    The next obvious use is as an alternative to library models. You can publish and distribute patterns for which no licensing is required.

    There are also opportunities for group model housekeeping. First, by copying only what is to be retained to new local and group models. Second, version levels can be compacted. This can be done by:

    1. Taking model snapshots at the configurations to be retained.

    2. Setting the first configuration and importing with duplicate action 'Clear.'

    3. Setting the remaining configurations and importing with duplicate action 'Merge.'

     

    Now CA  have never brought this up in the many previous discussions about compressing levels and or versions so beware I guess.