Fixes July 2021

In this version, we've fixed the following issues:

Manager

  • In a specific scenario, the following error message was shown when selecting a topic in the Mavim database: "System.NullReferenceException: Object reference not set to an instance of an object." This has now been resolved.
  • In a specific scenario and closing Mavim Manager, the following error could be shown: "System.NullReferenceException: Object reference not set to an instance of an object." This has now been resolved.
  • When changing the topic type and or icon in the options screen so that it matches with a template configuration, and selecting a different topic without pressing OK first, the template was not applied to the description. This has now been resolved.
  • When importing i-Navigator, the roleType ID was not imported correctly. After updating the import, the following error was shown: “System.NullReferenceException: Object reference not set to an instance of an object“. This has now been resolved.

Visio

  • It was not possible to export simulation in the Mavim Online Environment.
  • For Cross Functional Flowcharts, the weight and probability simulation attributes were wrongly displayed as custom, or user defined attributes.
  • Importing a .vsdx file as a Generic Chart failed.
  • Moving a connector in a Cross Functional Flowchart did not activate the Save button.
  • Graphical traces of shapes were sometimes left behind when:
    • Deleting a shared activity in Cross Functional Flowcharts.
    • Deleting a data association in a BPMN model.
    • Creating a group in an ArchiMate chart.
  • The page sometimes briefly recentered when:
    • Deleting a lane in a Cross Functional Flowchart.
    • Adding a related topic in a Cross Functional Flowchart.
    • Dropping a shape outside of the page area.
  • When converting an ArchiMate 2.1 chart to 3.1, older versions of shapes were instantiated when added from the stencil.
  • Shapes that were not properly connected to the Mavim database produced a crash when opening a ArchiMate chart.
  • Adding a pool in a BPMN collaboration, incorrectly triggered a full layout.
  • Shared flow step in a BPMN pool was inadvertently converted to a BPMN type.
  • In BPMN Stand-alone charts, the model explorer showed the menu for a full model.
  • The "Convert to BPMN type" menu for a pool incorrectly triggered the conversion for all the pools in the collaboration.
  • When changing the Lane topic for a BPMN pool, the tree dialog showed duplicate topics.

Mavim Process Mining

  • When duplicate column headers are present in the event log csv the uploading and transforming of the event log threw an exception. This has now been fixed.