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 the releases and identify and mitigate any erroneous behavior that may be caused by the release 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 stronger validations are now enforced on the endpoint /api/v1.0.0/workareafolder/{workareaFolderId/query, ensuring all query parameters are valid and aligned with the data model. These include:
- Validating systemCriteria.EntityTypeId and systemCriteria.FieldSetId against known Entity Types and Fieldsets.
- Confirming each dataCriteria.fieldTypeId matches the expected Data Type of dataCriteria.value.
- Ensuring dataCriteria.fieldTypeId belongs to the specified systemCriteria.EntityTypeId.
- For link criteria: verifying field ownership based on link direction (Outbound → TargetEntityType, Inbound → SourceEntityType).
- These checks prevent invalid queries and enforce strict data model consistency.
Brand Store v2
It has been implemented so that PDF preview performance in Brand Store v2 is significantly improved when displaying the preview of a selected template prior to downloading the PDF catalog, resulting in faster load times and a smoother user experience.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that when an entity is removed from a LinkType relationship, and that same entity still exists in another LinkType relationship, its entity card remains active and is no longer incorrectly greyed out in the Plan and Release views.
We have applied a solution to ensure that FieldType IDs are handled consistently across both REST and Remoting APIs. This fix normalizes input casing, allowing FieldType IDs to be provided in a case-insensitive manner (e.g., fieldid, FieldId, FIELDID) while the system continues to store and return them using the correct canonical casing defined in the database. This eliminates prior inconsistencies, preventing confusion and avoiding downstream processing errors.
Table View
We have applied a solution to ensure that Table View fully supports expression fields within selected cells, and that associated context menu messages are updated accordingly for clarity and correct functionality.
Brand Store v2
We have applied a solution to ensure that when downloading Media resources as files in Brand Store v2, only the appropriate media assets are included. Media files are now added to the download package exclusively when their original file format matches one of the selected Asset formats, preventing unnecessary or excessive media content from being bundled.
We have applied a solution to ensure that Brand Store v2 correctly displays all categories and fields defined in a specification template, even when multiple categories are included. All specification data is now fully visible and properly represented when sharing fields from the template.
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
1 comment
On this item
It has been implemented so that stronger validations are now enforced on the endpoint /api/v1.0.0/workareafolder/{workareaFolderId/query, ensuring all query parameters are valid and aligned with the data model.
Will the user be given a error message? Is there a log message that we should be looking for?
Please sign in to leave a comment.