Sections in the article
inriver is moving towards more incremental, smaller releases to accommodate our customers better and faster. 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:
Print 2.0
- It has been implemented that Print 2.0 now supports exporting tenants with large print configurations. Previously blocked exports due to size limitations are now resolved, enabling seamless and reliable export of all print settings.
- It has been implemented that Print 2.0 includes database cleanup optimization, delivering performance improvements that reduce resource consumption and enhance overall efficiency.
Table View
- It has been implemented that the Table View now loads without media details by default, significantly improving initial load performance. Media details are retrieved only when required, optimizing resource usage and responsiveness.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that deleting a field type via Remoting or REST also clears the associated DisplayName and DisplayDescription field types.
- We have applied a solution to ensure that, in the Remoting API, users can no longer switch CVL fields from multi-value to single-value when existing entities contain multiple values for that field.
- We have applied a solution to ensure that when a static Locale String CVL with defined CVL values is converted into a custom CVL via Remoting, the custom values are now correctly returned by the GetCVLValuesForCVL operation. This resolves the issue where custom CVL values were not displayed as expected.
- We have applied a solution to ensure that regular expression validation is consistently enforced across all Add and Update Entity methods in the Remoting API. Previously, certain entity fields were not properly validated against their defined regular expressions, resulting in data inconsistencies.
- We have applied a solution to ensure that the UtilityService.GetHtmlTemplatesByTypes method correctly returns the content property of HTML templates. Previously, due to a bug, the method returned template properties instead of the actual HTML content.
- We have applied a solution to ensure that a timeout is implemented in the regex matching process during Add and Update Entity operations in the Remoting API.
- We have applied a solution to ensure that the correct username is applied to listener extensions in the context during simultaneous updates.
Print 2.0
- We have applied a solution to ensure that Print 2.0 consistently retains the parent entity in print results. In rare scenarios where the same print was repeatedly added and removed, the parent data could be missing.
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.