This release contains an update to the Import Template creation process that focuses on the Jovix System ID for improved data accuracy when using the “Update” operation. Now, when users select the "Update" option, the Jovix System ID field will be visible for the primary entity, while it will not appear when the "Create" option is chosen. This distinction clarifies the purpose of each action.
When the Jovix System ID is selected, all other entity fields will automatically be disabled, allowing users to concentrate on this primary identifier. If users decide to de-select the Jovix System ID, previously disabled fields will be re-enabled, preserving any earlier selections. Additionally, once the Jovix System ID is selected and the user clicks "Next," it will auto-map as the primary identifier on the mapping screen, and this field cannot be removed to maintain data integrity.
These enhancements streamline the import template process, making it easier for users to manage accurate data within the Jovix system.
This release also introduces important updates to the management of Import Templates within the Jovix system, focusing on the back-end API functionality.
The groundwork has been completed to change the name of an existing import template, allowing for corrections of typos or alignment with updates. If a new Import Template name is provided, it will be updated in the system, while requests to change the name to one that already exists will be denied ensuring uniqueness. If no new name is given, the current name will remain unchanged.
Additionally, API work has been completed to support the ability to modify fields and adjust the Import Template's configuration without affecting the template name. If a request is made without including the name, it will not impact the existing name.
Looking ahead, further work will be done on the user interface to leverage these functionalities for a smoother experience. These updates lay the groundwork for more intuitive management of import templates in upcoming template editing feature development.
Last as it relates to Import Templates, we have also provided new external documentation to assist users in using the Import Template functionality effectively.
The documentation provides an overview of the Import Template builder, including primary entities, relationships, identifiers, advanced settings, and required fields. Visual aids are included for clarity, while execution details will be addressed separately.