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 behaviour 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, within the Remoting API and extension management, the setting of deactivated CVL values during entity updates is now prevented.
It has been implemented so that, in the Remoting API and extension management, UtilityService.UpdateSharedWorkAreaQuery and UtilityService.UpdatePersonalWorkAreaQuery now validates ComplexQuery values before update execution. A new validator enforces the existence and consistency of entity types, field sets, fields, and link types; validates operator compatibility with field data types and CVL configurations; enforces operator-specific value requirements; validates value data types; and applies language constraints correctly, including full validation of source and target criteria in LinkQuery.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that, in extension management, Context.Username now reflects the actual username of the user who performed channel-related events, including UpdateEntity, AddLink, DeleteLink, UpdateLink, InactivateLink, ActivateLink, and DeleteEntityFromChannels, instead of displaying "system". Changes executed by extensions and DeleteEntityFromChannels actions initiated from the Portal will continue to display as system.
We have applied a solution to ensure that REST & Remoting APIs handle FieldType IDs consistently. FieldType IDs are now case-insensitive, and the system stores and returns them using the canonical database casing. This resolves inconsistencies and prevents potential downstream errors caused by varying input casing.
We have applied a solution to ensure that RemoteManager.DataService.UpdateSpecificationField(SpecificationField specificationField) now supports assigning null values, allowing proper clearing or resetting of specification fields where applicable.
We have applied a solution to ensure that the CategoryId specified in SpecificationFieldType is validated against existing SpecificationCategory records in the database before add or update operations.
We have applied a solution to ensure that GetAllCVLValues for Custom CVLs returns unique entries. This was achieved by updating the underlying SQL query with an additional WHERE clause to prevent duplicate CVL values.
We have applied a solution to ensure that, in the Portal Import process, the media upload dialog correctly displays the segment selection dropdown.
We have applied a solution to ensure that, in the Portal, clicking the History item on the Enrich homepage correctly opens the History view.
We have applied a solution to ensure that, in Plan & Release, removing an entity from one link type does not incorrectly grey out the entity card when the entity still exists in another link type.
Expression Engine
We have applied a solution to ensure that, in Remoting, entity versioning and history retrieval functions operate correctly for fields with expression support and change tracking enabled.
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.