Update Production API server
Introduction
This release updates the Production API Server to a newer backend version focused on improving the performance and stability of Linked Record operations. The update removes unused portions of the API response that were previously generated but not required by the platform. By eliminating this unnecessary processing, the API now returns a smaller response payload and reduces the time taken to load linked fields inside a checklist.
No functional behaviour has been changed as part of this update; all linked field and embedded field workflows are expected to operate exactly as before.
Release Scope
Updated the API server to v5.15.43, which is a newer, optimised version.
Removed unused embedded-field data previously fetched from the API to get the linked field value.
Improved API response payloads for embedded fields to reduce load time.
Ensured no functional behaviour changes in how embedded fields are selected, displayed, edited, or updated.
Validated complete UI flow for:
Checklist UI with embedded fields
Linked Record field display
Embedded field visibility and ordering
Embedded field deletion and updates
Verified that checklist conditions dependent on embedded fields continue working as expected.
Confirmed performance improvement in loading embedded fields within Linked Records.
Before vs After
API Behaviour
API returned additional unused details while fetching embedded field values.
API returns only required data → lighter payload and faster processing.
Embedded Field Loading
Slower loading time, especially for Linked Records with multiple embedded fields.
Noticeably improved loading speed for embedded fields.
Checklist UI Behaviour
Fully functional but dependent on heavier database queries.
Functional behaviour unchanged, but with optimised backend queries.
Ordering & Visibility
Reordering and visibility changes worked but were slower to reflect.
Reordering, visibility, and deletion flow remain the same but respond faster.
For more details about Unifize APIs, check out the complete API documentation here.
Last updated