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 behavior 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 that the Workflows application now follows the user's configured Portal interface language, with full French, Spanish, and German translations.
- A new role-based language access system feature is now available in Control Center, where you can assign a language role that gives a user on Portal specific read/write access to languages.
-
We've implemented filtering for calls to Server extensions based on how the corresponding Rest API call is authenticated.
The new filter, Initiator, supports the values User and/or Integration. When a Rest API call is authenticated using an API key, the initiator is classified as an Integration. All other authentication methods classify the initiator as a User.
By configuring the event filter for Server extensions, it is therefore possible to specify which events should be processed based on their Initiator. This enables Server extensions to handle events selectively depending on whether they originate from a user or an integration.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that notification emails sent by completeness trigger actions no longer show a stray "/n/r" string in the message body. Line breaks in the message now render correctly.
- We have applied a solution to ensure that, in the Includes and Included in tabs of an entity, users only see linked entities that belong to content segments they have access to. Previously, users with restricted content-segment access could see linked entities from segments they were not permitted to access.
- We have applied a solution to ensure that users with read-only language permissions can select those languages as the source data for Inspire Translate.
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
Nice to see about the new filtering options for server extension! I would like to double check, when an extension is hosted by you and it is using the remoting api (system user), will that also count as initiator "integration"? Or is it only the rest api?
Please sign in to leave a comment.