Import

This function can only be used with a DUAS V5 node.

Fill in all fields and:

• Click Simulate to list all the objects that may be imported in the local environment.
• Click Cancel to quit the import feature.
• Click OK to import the BV and/or its objects to the local Dollar Universe environment.

If an object is imported (with the overwrite setting) and it already exists, if its definition changes (Uproc or execution context for a Session, user for a Task, etc.) a message will be displayed to the user.

General

• File

  Enter the full file name (including the path) or click on the button to select it with the browser.

• Business View

  Displays the Business View name in the file.

• Import Business View Definition

  Check the box if you want to create the Business View in Dollar Universe.

• Import Referenced Objects

  Check the box if you want to create the Business View objects during the import. If the Business View contains a Task, you can change the Submission Account during the import. Add the corresponding user in the "Mapping User" section.

• Select a version

  If the import targets an Area with Uproc versions or Session versions and if the objects were exported without version numbers, enter their new version on three digits.

• Overwrite if object already exists

  If the file contains the objects, if you checked the "Import objects…" box above and if the objects already exist in the target environment. Check this box to replace their present definition with the imported one. In this case, you can be sure that the BV object definitions match the object definitions in Dollar Universe. In case of conflict, a message is displayed to the user.

Mapping MU

If a Session in the Business View contains a specific execution Management Unit, it can be changed automatically during the import.

For example, if the Session references the Management Unit "SATURN", you can replace it by "TEST" by adding the following map: "SATURN TEST".

Click Add to add a new MU map:

• Select the MU to map: click on the arrow to display the MU referenced in the BV (as a Session execution context) and select one from the list (for example SATURN).
• Select the new MU: click on the arrow to display the local MUs and select the new one from the list (for example TEST).

Click OK to confirm. The new map is displayed in the list.

In the example, the "SATURN" Management Unit will be replaced in the imported Business View Session by the "TEST" Management Unit.

If the Session already exists in this environment, it will be updated as well (if the overwrite parameter is used in the Import).

Click on Export File to export all the correspondences of this list into a file (for import later).

• Select the directory and enter the file name that contains the Management Unit correspondence.
• Click on Save to create the file.

Click on Import File to import the correspondence (defined in a file created by an export) in the list of existing correspondence. If the correspondence already exists, it will not be deleted, even if there are duplicates.

• Select the directory and the file that contains the Management Unit correspondence.
• Click on Open to import the correspondence in the list.

User Mapping

If the Business View contains a Task, you can automatically change its Submission Account during the import.

For example, if the Submission Account is "prod" in the Task, you can replace it by "eca" adding the following map: "prod eca".

Click Add to add a new User map:

• Select the User to map: click on the arrow to display the users referenced in the BV (as Submission Accounts in a Task) and select one from the list (for example "prod”).
• Select the new User: click on the arrow to display the local users and select the new one from the list (for example "eca").

Click OK to confirm. The new map is displayed in the list.

In the example, the "prod" submission account will be replaced in the imported Business View Task by the "eca" Submission Account.

If the Task already exists in this environment, it will be updated too (if the overwrite parameter is used in the Import).

Click on Export File to export all the correspondence of this list into a file (for import later).

• Select the directory and enter the file name that contains the user’s correspondence.
• Click on Save to create the file.

Click on Import File to import the correspondence (defined in a file created by an export) in the list of existing correspondence. If the correspondence already exists, it will not be deleted, even if they are duplicated.

• Select the directory and the file that contains user’s correspondence.
• Click on Open to import the correspondence in the list.