Fixed · Custom Portal

Fixed March 2022

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

In a specific situation, editing a report with a certain field set showed the error message: "Item has already been added. Key in dictionary".
When using the Batch Configuration to create and publish a version, the Batch Configuration did not stop after an error while creating a version but instead continued and published the existing version.
When a coupled copied field was removed from its coupled copied field set and then placed back, updating the coupled copied field set resulted in a problematic state causing errors like: "Item has already been added. Key in dictionary" or "Sequence contains more than one matching element" when the field set was read.
When publishing to Word, in some cases the Word publication placed all topics in the TOC instead of following the Word Theme settings.
When publishing to SharePoint, in some cases the value of a field type Yes/No was not visible.
When using the SharePoint App, it was not possible to close the print dialog after opening.
When using the SharePoint App, it was not possible to select a topic without a name.
When using the SharePoint App, some ArchiMate types did not show the correct icon.

When dropping specific complex shapes in a generic chart, there was a delay before Visio displayed the shape on the page. This delay increased as more shapes were added to the chart.
Generic charts that included embedded pictures would cause an error message when publishing to the Mavim Portal resulting in the chart not being visible in the publication.
When a page in a Generic chart used another page as a background, the published chart did not include the background.
In ArchiMate, all relationships to/from Junction shapes were reported as incorrect. Now the correct rules based on ArchiMate Specification are applied.
Copying and pasting a shape in a Generic chart inadvertently connected the new shape to the currently selected topic in Mavim Manager.
Visio callouts and annotations were displaced during the publication of BPMN collaborations to the Mavim Portal.
In flowcharts, when relationships with dispatch instructions or dispatches were added via "Show" context menus, characteristics unexpectedly moved to original positions.