Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

1         Auto Data Marking

Vienna Advantage has enhanced the functionality of Auto Data Marking, allowing users to easily import bulk data from one instance to another using the Auto Data Marking tool.

1.1    Enable Auto Data Marking

To enable “Auto Data Marking”, one role must be configured for users.  This role should have the “Auto Data Marking” setting checked on the Role screen, as shown in the image below:

For users assigned to roles with "Auto Data Marking" enabled, they will have access to all screens. However, automatic data marking will only occur for screens labeled as ‘Maintain’ in the screen configuration and having table type of ‘Master’ under the Database Schema. For other types of screens, if a user can open the screen and create the record but system will not consider those screens for auto data marking.

 Users who log in with roles not marked as "Auto Data Marking" will not have automatic data marking on record save or update.

To map a role with a tenant, a user has two options: they can either create a new tenant or assign the role to an existing one. To create a new tenant, follow the steps below:

1.1.1        Creating a new tenant

  1. Log in as the Superuser (System Admin)

  2. Go to menu and search for “Initial Tenant Setup”

  1. Create a Tenant by updating the details within the form.

  1. Enter the details for creating a Tenant.

  2. Click on the  “Done” button

1.1.2        Creating a New Role

To create a new role mapped with the tenant, follow these steps:

  1. Navigate to the ‘Role’ window from the menu.

 

  1. Open the Role window.

  2. Enter the details into the Role window & save the record

  1. Mark the “ Auto Data Marking” check box under the Role window as true.

1.1.3        Mapping Roles to Created Tenants (User)

  1. Navigate to the User window from the menu.

  1. Open the User window.

  2. Navigate to the user record.

  3. Open the record and proceed to the “User Roles” tab

  4. Map the role to the respective user within this window

2         Marking Data

When new records are saved or updated by login users with this role, all configurations will be automatically marked with the “Auto Data Marking” module.

Let’s illustrate this with the example of the “Tax Rate”.

To open the window, navigate to the menu, type “Tax Rate” and select it as shown in the screenshot below:

 

  1. Tax Rate screen will be opened.

  2. Click “New record” to create a record in the Tax Rate header

 

  1. Users can check the marking by clicking on the “tick icon” in the action panel, as shown below.

  1. A pop – up window will open on the screen.

  1. By default, the "Beta Auto Data Marking" checkbox is set to true, and the user cannot uncheck it.

3         Generating XML Files

After all the marking is done, user has to generate the XML files so that the configurations can be moved to another instance. To do this,

  1.  There is a job in the menu with the name “Generate Configuration Files”, which users has to run from the tenant where the marking is done.

  1. On this screens, there are two buttons displayed i.e.

Ø  Generate: By Clicking on the Generate button, new XML Configuration files will be generated and then user can download newly generated file.

Ø  Download: Users can download the previous generated files, if new files are generated.

  1. This job will pick all the markings done by the user and will generate XML files

  2. A .rar file should be downloaded with name “VA093_”

  3. Users can verify their record data within the respective module files.

4         Import Configurations

To import configurations on another link, please ensure that the ‘Auto Data Marking’ module should be installed.

  1. Users should login with different user on another link where the configuration needs to be imported.

  2. Check if there is a page/form available in the menu named “Import Configurations” as shown in the image below.

  1. This will open the import module form/page, where the user has to select “.rar” files that were exported from the configuration link.

  2. This page contains three fields, as displayed in the image below:

4.1  Select File: Users need to choose the exported XML files, and it will accept “.zip” files only.

4.2  Import Data: This field is mandatory. Users must select one of the following options:

4.2.1        Insert Only: This option is used to import only newly created master data.

4.2.2        Insert and Update: This option is used to import new records and existing records based on specific criteria (Export_ID, Unique columns, Search Key columns) following the market logic of “Other Customization” or already updated record to be skipped.

4.3  Import Button: Clicking this button initiates the import configuration process. The configurations found in the selected XML files will be imported into the tenant where the user is logged in. After completion, the user will be presented with a log file similar to the one displayed at the end of module installation. This log file allows the user to verify whether everything was imported successfully.

User must select either “Insert Only” or “Insert and Update”, to enable “Import” button.

4.1    “Insert Only” for the Import Process

Certainly, here’s an explanation of how to import a file using the “Insert Only” option in the import process:

  1. Select the file by browsing from the system

  2. Select the ‘Insert Only’ option under Import Data to specifically import new records.

  3. Click on the Import button

  4. The Import Configurations process is started.

  1. After completing the process , a pop- up window will appear.

  1. Here, we can download the log  & server log files to check if the record data was imported successfully

  2. Close the pop-up window & exit the Import configuration page.

  3. Now, navigate to the Tax Rate window, to verify that the record is displayed.

  1. Newly created records are updated and displayed under the Tax Rate window.

10.   User should verify that the same record has been updated under the destination link.

11.   Data under the destination link should be updated with the same values as the configuration link for all fields.

4.2    “Insert and update” for the Import Process

Certainly, here’s an explanation of how to import a file using the “Insert and Update” option in the import process:

  1. Select the file by browsing from the system

  2. Select the ’Insert and Update’ option under Import Data, which allows user to import new records and updated (existing) records based on specific criteria like Export _ID, Unique columns and Search key columns.

  3. Click on the Import button

  4. The Import Configurations process will be started.

  1. After completing the process, a pop- up window will appear.

  1. User can download the log  & server log files to check if the record data is imported successfully or not.

  2. Close the pop-up window & exit the Import configuration page.

  3. Navigate to the Tax Rate window, to verify that the record is displayed.

  1. Newly created records are updated and displayed under the Tax Rate window.

  1. Go back to the Tax rate window, reopen the previously updated record.

  1. User should verify that whether the same record has been updated under the destination link or not.

  2. Data under the destination link should be updated with the same values as the configuration link for all fields.

              

This would be working in a same way for the other master screens as well whether they have a single tab or multiple tabs.

 The Configuration import logic follows a prioritized order as define in the code: 

Ø  Firstly, the system checks for the presence of an Export_ID. It compares the Export_ID in the XML file with records in the production link. If a matching Export_ID is found, the system updates the corresponding record; otherwise, it inserts a new record into the production link.

Ø  The second priority is given to unique columns within the production link where the configuration is being imported. If imported data matches existing data in these unique columns, the system updates the record. If no match is found, it proceeds to the third priority.

The third priority involves the search key column in the table. If the value in the production link matches the value in the XML files, the system updates the record. However, there is an exception when the “Search Key” column is not unique. In cases where multiple records share the same search key in the production link, the decision to insert or update

  • No labels