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:
Expression Engine
- It has been implemented that the Expression Engine is now supported in Excel Import/Export jobs. On export, fields with expressions generate an additional column named {fieldTypeId}_Expression, indicating a calculated value.
- It has been implemented that the Expression Engine introduces a new endpoint:
GET /api/v1.0.1/model/entitytypes/{entityTypeId}/expressions
This endpoint returns the field set and segment expressions configured for the specified entity type. - It has been implemented that the Expression Engine includes a new endpoint:
PUT /api/v1.0.1/model/entitytypes/{entityTypeId}/expressions
This endpoint allows setting field set and segment expressions for the specified entity type.
- It has been implemented that, to discourage misuse of the Expression Engine and to manage database storage efficiently, only expressions with a length of less than 100,000 characters will be accepted.
- It has been implemented that the Expression Engine update to the endpoint GET /api/v1.0.0/entities/{entityId}/summary/fields adds an expression property to each field in the response.
- It has been implemented that the Expression Engine endpoint POST /api/v1.0.1/entities:fetchdata has been updated to support requesting entity expressions by specifying "Expressions" in the objects property.
Example: "objects": "FieldValues, Expressions"
- It has been implemented that the Expression Engine endpoint POST /api/v1.0.1/entities:fetchdata has been updated to include an expression property in each field summary when "FieldsSummary" is specified in the objects property.
Example: "objects": "FieldsSummary"
Remoting
- Remoting nuget 8.21.0 has been published to nuget.org:
https://www.nuget.org/packages/inRiver.Remoting.iPMC/8.21.0
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that the query editor now correctly includes null and empty values when using the 'NotContains' operator.
- We have applied a solution to ensure that in Enrich Export, restricted fields and categories are now properly hidden from users, preventing them from being included in Excel exports.
- We have applied a solution to ensure that the sort order is preserved when changing a fieldset in the entity view and that fields and categories appear in the correct order.
- We have applied a solution to ensure that the Custom List View button functions correctly during mass updates for Locale Strings. Previously, the button failed to display the list of available languages, which prevented users from selecting and updating multiple languages efficiently.
- We have applied a solution to ensure that in the RESTAPI, field updates are now validated to confirm they conform to the associated regular expression, similar to the behavior in Portal and Excel Import.
- We have applied a solution to ensure that the model cache for extensions now updates when changes occur in the model, without the need to restart the service. The model cache update is now performed with a delay of approximately 10 seconds.
- We have applied a solution to ensure that during the Excel import, a warning message is displayed when field and segment field restrictions are applied. These restrictions will now be checked per entity during the import process.
Table View
- We have applied a solution to ensure that in Table View, the '404 Not Found' error message no longer appears in the browser console when a user has no workspaces.
- We have applied a solution to ensure that when opening an entity from Table View in a new tab, the left-side board is correctly displayed, matching the view when opened from card view.
Inriver Integration Framework
- We have applied a solution to ensure that the unused System.Identity reference has been removed from DeltaChannelListener in IIF.
- We have applied a solution to ensure that the bug in retrieving Value Lists using the fetching strategy in IIF has been fixed.
- We have applied a solution to ensure that IIF handles errors properly when a field is not found in the Connect model cache due to a race condition, preventing critical errors that could cause the export to crash.
Separate release notes related to IIF can be found here: https://community.inriver.com/hc/en-us/articles/360016869900-Integration-framework-Release-notes
Remoting
- We have applied a solution to ensure that in Remoting, LocalString serialization is removed from the CVLValue object. Starting from .NET Core and in later versions, the default binary serialization mechanism has been deprecated due to security and performance concerns, affecting the serialization of several types, including CultureInfo.
- We have applied a solution to ensure that in Remoting, the error in the GETUserByUsernam() method is resolved when used in a .NET 8 C# project with the inriver.Remoting.iPMC package. The method now utilizes new DTOs that do not reference the CultureInfo class.
inriver Implementation Standards
inriver's ambition is to collaborate with our partners in providing our customers with as safe and secure a PIM system as 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.