Dashboard migration

This tool transcodes the version 6 portal associated with a user or a trade code and generates a set of dashboards with the same contents.

The query page

When opening the page, a query displays the list of trade codes and/or users for which the portal can be generated. The following information appears on the list:

• The Type can be either Trade Code or User.
• The Code identifies the user or trade code.
• The Description provides a longer description.

From this query page, two links are available on the lines:

• The first link points to the detail page (but no additional information is available).
• The second link triggers the generation process that generates a log file where eventual errors will appear in the upper panel.

Initiating the generation

The initiation is activated by using the second link called Dashboard Import on the corresponding line. The generation is carried out in two successive steps:

• The analysis of the dictionary to build a JSON file describing the administration data (menu items, portlets, and dashboards) that need to be created or updated.
• The call of the import tool that will update the mongodb database and create a journal of the modifications. This journal can be used to undo the operation, which is described in the Administration reference Import Session.

Operation finished in xx.yyy secondsN menu items, M portlets, and P dashboards created or updated

Parameters

A supervisor parameter called ACONVONLY can be set up at the user level to define how the generation must be done on Sage X3 People "objects" functions:

• If the value of ACONVOLY is set to Yes, the link on Sage X3 People object functions is always a Classic link, even if a representation exists.
• If the value is set to No, which is the default value, the links from the menu will be read-only pages links if a representation is available for the Sage X3 People object.