Learn what is new, and what has been improved and fixed.
New
New
-
BPMN structure can now be extracted from user Visio drawings. The feature is available via Mavim Manager ribbon menu: “Import\BPMN from Visio drawing ...”.
-
For BMPN Collaborations, a warning is now displayed in Visio when empty Lanes are found.
Improved
Improved
-
Copy-Paste of texts in Visio shapes is now available for all chart types.
-
When versions are copied, “BPMN Catalogs” folders are now joined in a single topic.
Fixed
Fixed
- When opening a BPMN chart created with a previous version of Mavim Manger, Data Objects were displayed with no text.
- When opening specific BPMN Collaborations, existing lanes in the chart were removed. This was due to the fact that the Who relationships were not properly saved in the database. Opening the chart now and saving it will correct the issue.
- When opening BPMN Collaborations with a restricted characteristic range and process steps shown in one lane, sometimes empty Lanes were displayed.
- Importing Flowchart drawings exported with older Mavim Manager versions, led to undesired visual effects.
- When checking charts from Mavim Manager, the status of checked charts was sometimes not displayed.
- When versions are copied, special BPMN and ArchiMate characteristics are now consolidated in a single occurrence.
New
-
BPMN structure can now be extracted from user Visio drawings. The feature is available via Mavim Manager ribbon menu: “Import\BPMN from Visio drawing ...”.
-
For BMPN Collaborations, a warning is now displayed in Visio when empty Lanes are found.
Improved
-
Copy-Paste of texts in Visio shapes is now available for all chart types.
-
When versions are copied, “BPMN Catalogs” folders are now joined in a single topic.
Fixed
- When opening a BPMN chart created with a previous version of Mavim Manger, Data Objects were displayed with no text.
- When opening specific BPMN Collaborations, existing lanes in the chart were removed. This was due to the fact that the Who relationships were not properly saved in the database. Opening the chart now and saving it will correct the issue.
- When opening BPMN Collaborations with a restricted characteristic range and process steps shown in one lane, sometimes empty Lanes were displayed.
- Importing Flowchart drawings exported with older Mavim Manager versions, led to undesired visual effects.
- When checking charts from Mavim Manager, the status of checked charts was sometimes not displayed.
- When versions are copied, special BPMN and ArchiMate characteristics are now consolidated in a single occurrence.
Learn what is new, and what has been improved and fixed.
Fixed
Fixed
- When consistency was checked in a BPMN chart, warnings that collapsed sub-processes are empty were wrongly displayed.
- When a Task was changed in Mavim Manager to a Sub-process, when opening the BPMN chart, the corresponding shape was not changed to the desired type, and it was also not possible to change the shape type in Visio.
- When a Task was changed in Mavim Manager to a Sub-process, when opening the BPMN chart, some sequence flows links were shown disconnected from the Activities and they were also marked as modified with color code "purple".
- When a lane Topic was replaced, when opening some BPMN charts, the lane was not replaced in the drawing. Sometimes the process steps where shown as unassigned.
- When a lane Topic was deleted in Mavim Manager, when opening the BPMN chart, the flow steps were shown correctly as unassigned, but with a too wide layout.
- Opening a specific configuration with Lanes and Data Stores representing the same Topic, adding a new Data Store led to a crash.
- For some newly dropped shapes, the "green" color code exhibited unwanted variations (e.g. Data Stores).
- For a BPMN Custom Stencil, setting the Text Background as None for Sequence Flows was reverted to Solid when used in a chart.
Fixed
- When consistency was checked in a BPMN chart, warnings that collapsed sub-processes are empty were wrongly displayed.
- When a Task was changed in Mavim Manager to a Sub-process, when opening the BPMN chart, the corresponding shape was not changed to the desired type, and it was also not possible to change the shape type in Visio.
- When a Task was changed in Mavim Manager to a Sub-process, when opening the BPMN chart, some sequence flows links were shown disconnected from the Activities and they were also marked as modified with color code "purple".
- When a lane Topic was replaced, when opening some BPMN charts, the lane was not replaced in the drawing. Sometimes the process steps where shown as unassigned.
- When a lane Topic was deleted in Mavim Manager, when opening the BPMN chart, the flow steps were shown correctly as unassigned, but with a too wide layout.
- Opening a specific configuration with Lanes and Data Stores representing the same Topic, adding a new Data Store led to a crash.
- For some newly dropped shapes, the "green" color code exhibited unwanted variations (e.g. Data Stores).
- For a BPMN Custom Stencil, setting the Text Background as None for Sequence Flows was reverted to Solid when used in a chart.
Learn what is new, and what has been improved and fixed.
Fixed
Fixed
- When a Visio document was closed and Visio was left open, that chart could no longer be re-opened without restarting Mavim Manager.
- Some charts exported from Mavim Manager and then re-imported could unexpectedly have some visual styles changed.
- In Relationship Network chart it was not possible to apply the standard stencil. The classic stencil was always incorrectly shown.
- In some situations, dropping a shape would result in an unexpected font which was different from the font in the master shape.
- For Flowcharts, CFF and EPC with the “Save all implicit flow relationships” option enabled, changes of types from Activity to Stop for instance, were still incorrectly applied.
Fixed
- When a Visio document was closed and Visio was left open, that chart could no longer be re-opened without restarting Mavim Manager.
- Some charts exported from Mavim Manager and then re-imported could unexpectedly have some visual styles changed.
- In Relationship Network chart it was not possible to apply the standard stencil. The classic stencil was always incorrectly shown.
- In some situations, dropping a shape would result in an unexpected font which was different from the font in the master shape.
- For Flowcharts, CFF and EPC with the “Save all implicit flow relationships” option enabled, changes of types from Activity to Stop for instance, were still incorrectly applied.
Learn what is new, and what has been improved and fixed.
Improved
Improved
- When importing a Flowchart you are now able to differentiate the Flow steps instead of just specifying “Topic". The shape type is also pre-determined by the relationships of the shape.
- Call outs inserted from the Visio Ribbon are now directly created as free shapes.
Fixed
Fixed
-
When importing a Flowchart, the Mark Shapes form did not select the Start shapes.
-
When opening a copy of a model in selective mode and saving it, if the full model was opened after saving, views that were initially not opened were inadvertently recreated on the fly.
-
When saving a BPMN chart, "Glossaries” and "Milestones” topics were placed in the Recycle Bin.
-
Inserting a new flow step on a relationship after a Call-out shape was added from the Visio Ribbon, resulted in disconnected relationships. This happened for Flowcharts, BPMN, EPC and Crossfunctional Flowcharts.
Improved
- When importing a Flowchart you are now able to differentiate the Flow steps instead of just specifying “Topic". The shape type is also pre-determined by the relationships of the shape.
- Call outs inserted from the Visio Ribbon are now directly created as free shapes.
Fixed
-
When importing a Flowchart, the Mark Shapes form did not select the Start shapes.
-
When opening a copy of a model in selective mode and saving it, if the full model was opened after saving, views that were initially not opened were inadvertently recreated on the fly.
-
When saving a BPMN chart, "Glossaries” and "Milestones” topics were placed in the Recycle Bin.
-
Inserting a new flow step on a relationship after a Call-out shape was added from the Visio Ribbon, resulted in disconnected relationships. This happened for Flowcharts, BPMN, EPC and Crossfunctional Flowcharts.
Learn what is new, and what has been improved and fixed.
New
Creating or recreating an ArchiMate model with many views
Why it was developed? The speed of creating or recreating ArchiMate models with many views has been improved. This improvement was implemented to increase efficiency when setting up and adjusting complex models.
Added value: Efficiency > With the accelerated creation and recreation of ArchiMate models, users can set up and adjust their models more quickly.
Use case scenario: When an organization uses ArchiMate models to visualize its enterprise architecture. With the improved speed of creating and recreating models, architects can respond more quickly to changes in the organization and adjust the corresponding models.
Improved
Improved
Creating or recreating an ArchiMate model with many views underneath is now faster.
Fixed
Fixed
- In limited instances, double Subchart relationships were shown on the same ArchiMate View Topic. When opening now the affected View(s) or the full model, a patch is applied. The existing shapes are kept in the same page, and new View Topics are created on saving. Provisionally, the names of the new Topics are the initial name, prefixed with “[variant]-”.
- When exporting an ArchiMate model, an error was displayed, and Visio was closed. Nevertheless, the export was completed successfully. The error is now removed.
Creating or recreating an ArchiMate model with many views
Why it was developed? The speed of creating or recreating ArchiMate models with many views has been improved. This improvement was implemented to increase efficiency when setting up and adjusting complex models.
Added value: Efficiency > With the accelerated creation and recreation of ArchiMate models, users can set up and adjust their models more quickly.
Use case scenario: When an organization uses ArchiMate models to visualize its enterprise architecture. With the improved speed of creating and recreating models, architects can respond more quickly to changes in the organization and adjust the corresponding models.
Improved
Creating or recreating an ArchiMate model with many views underneath is now faster.
Fixed
- In limited instances, double Subchart relationships were shown on the same ArchiMate View Topic. When opening now the affected View(s) or the full model, a patch is applied. The existing shapes are kept in the same page, and new View Topics are created on saving. Provisionally, the names of the new Topics are the initial name, prefixed with “[variant]-”.
- When exporting an ArchiMate model, an error was displayed, and Visio was closed. Nevertheless, the export was completed successfully. The error is now removed.