Release Notes - Jovix 2024.12 - Jovix - Release Notes

Import Templates

Now available under Data & Reporting, this release removes the feature flag for primary entity import templates, streamlining the creation process with several enhancements. Users can now seamlessly create import templates specifically designed for primary entity data without encountering feature flag restrictions. The Advanced Settings button has been hidden on both the field mapping and summary pages of the import template creation workflow, simplifying the user interface, and focusing attention on essential tasks.

Once an Import Template is created, it will then be able to be accessible to use in Import under Data & Reporting.

Although Advanced Settings remains hidden behind a feature flag, this release addresses an edge case within the Advanced Settings dialog of import templates where parent entities shared by multiple child entities were not consistently displayed when child entities were toggled. The issue arose from inconsistencies in how reference data between parent and child entities was handled, causing the parent entity to disappear from the dialog when one of the shared child entities was unchecked, even if another child entity remained checked. With this update, we have improved the visibility logic in the Advanced Settings dialog to ensure that parent entities remain visible as long as at least one related child entity is selected. Users can now manage import templates more effectively, ensuring all intended parent and related child entities are correctly displayed and selectable within the dialog, thereby improving workflow reliability and user experience. This enhancement provides a more robust solution for managing complex entity relationships in Jovix.

Inspection Templates

This update enhances the Inspection Templates API by adding paging functionality, enabling developers to retrieve inspection template data efficiently for front-end display. With this enhancement, developers can specify the amount of data per page and ensure that subsequent requests for additional pages return the next set of inspection templates in the specified size. Crucially, the data remains sorted alphabetically by Name as required. This improvement simplifies the process of handling large datasets, ensuring all templates are accessible without duplicates across pages and maintaining consistent sorting integrity.

This update also enables Jovix System Administrators to create or update roles with inspection template permissions via the API. Administrators can now assign permissions for creating, reading, updating, or deleting inspection templates to roles associated with specific projects, enhancing role management flexibility. The API supports the successful creation and updating of these roles, empowering administrators to define comprehensive access controls. Non-administrator attempts to modify roles with these permissions are appropriately restricted with a 403 (forbidden) response, ensuring security and access integrity. The impact of this feature is that System Administrators can now efficiently manage inspection template permissions, facilitating customized access controls within Jovix.

Web Notifications

This release enhances the Jovix web interface by integrating failed data calls into the workflow notification card's completed count, providing users with a more comprehensive view of workflow statuses. Previously, only successful requests were reflected in the completion count, which could be misleading during workflows with errors. With this update, users can now accurately track both successful and failed data calls within the notification card's Items Process block. For instance, workflows where all post calls fail due to naming collisions now correctly display a count reflecting both successful and failed operations under "Complete with Errors". This improvement ensures transparency in workflow outcomes, enhancing user understanding and decision-making. The impact is that users benefit from improved notification clarity, encompassing both successful and failed data call counts within workflow statuses.