Sections in the article
Inriver is moving towards more incremental, smaller releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver will be able to increase the quality and transparency of releases and identify and mitigate any erroneous behaviour much faster.
NB! To receive notifications when new release notes are published, please ensure you follow this page by clicking the "follow" button above.
Please see below for the deployed features and improvements:
General
- It has been implemented so that uploading large glossary files no longer times out. The file size limit has been increased from 5 MB to 20 MB, and the upload process has been significantly optimized to improve performance, reliability, and stability when handling large files.
- It has been implemented so that glossary term searches are now significantly faster, particularly for large glossaries. Previously, searches within large glossaries could be slow and result in delayed responses.
- It has been implemented that the AI-powered text generation in Inspire Table View now matches CVL (dropdown) option values more reliably. Previously, minor formatting differences in AI responses could prevent the correct option from being selected. The system now applies normalization to handle these differences and select the correct CVL option where possible. If no reliable match is found, the system gracefully avoids selecting an incorrect option.
Shopify Adapter
It has been implemented so that select inventory item fields are now supported, enabling more flexible and granular data handling for inventory-related attributes.
It has been implemented so that product option names can now be mapped, allowing improved consistency and control over option labelling across systems.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that CVL field styling behaves consistently across the UI. The update introduces class-based handling for border rendering, providing controlled removal of borders where appropriate and improving visual consistency.
- We have applied a solution to ensure that the Save button in Entity Details remains disabled when an entity is initially opened and is enabled only after a user makes a genuine modification to a field.
- We have applied a solution to ensure that the entities: upsert endpoint with staleLinkAction "UnlinkAndDeleteOrphans" and an empty entities array no longer returns an internal server error. Orphaned entities are correctly deleted as expected.
- We have applied a solution to ensure that the specification summary endpoint correctly resolves formatted fields (e.g., "Product Dimensions") by fetching values from their source fields, instead of entering an infinite loop that caused request timeouts.
- We have applied a solution to ensure that the error "Failed to execute ReloadContributeOrganizationJobActor for supplier" in the Control Center no longer occurs when multiple reload requests for the same supplier are triggered at the same time. Previously, simultaneous reload operations for the same supplier could interfere with each other, causing the operation to fail. The supplier reload operation now correctly prevents duplicate jobs from running concurrently, so the reload completes successfully without errors.
- We have applied a solution to ensure that personal workspaces created in Portal Enrich are correctly displayed in the workspace selection dropdown, regardless of username letter casing. Previously, the workspace selection filter performed a case-sensitive comparison, which could result in a mismatch between the stored username and the workspace owner lookup when usernames contained uppercase characters.
Shopify Adapter
We have applied a solution to ensure that GID updates are correctly processed and consistently reflected across the system, resolving inconsistencies in identifier synchronization.
We have applied a solution to ensure that one-level IIF products correctly persist fields at the variant level when such behaviour is configured, ensuring expected data inheritance and storage.
We have applied a solution to ensure that products with a single variation and no overridden fields are correctly handled when sending the variant as a product, preventing incorrect mapping or data loss.
We have applied a solution to ensure that products with no variants are properly processed when no product variant behaviour is defined, ensuring stable handling of edge-case product configurations.
We have applied a solution to ensure that variant metafields are correctly populated upon creation, resolving an issue where initial metadata assignment was previously not applied.
- Inriver Implementation Standards
Inriver's ambition is to collaborate with our partners in providing our customers with the safest and most secure PIM system possible. With that in mind, Inriver is improving the information on our Community to help implementation partners ensure quality, optimize implementations, and avoid pitfalls.
Read more about Inriver Implementation Standards
Comments
0 comments
Please sign in to leave a comment.