Release notes: February 24th - February 25th, 2024

inriver is moving towards more incremental, smaller releases to be able to accommodate our customers in a better and faster way. With smaller, more frequent releases, inriver will be able to increase the quality and transparency of the releases and be able to identify and mitigate any erroneous behavior that may be caused by the release much faster. Please note that larger features and/or changes that are deemed to have a strong impact on customers and partners will of course be communicated in advance.

Please see below for the deployed features and improvements:

• Extensive work has been implemented with our Connect event filtering for Server Extension. When a filter is configured for a server extension, each time that server extension is supposed to be triggered, the filter will be checked, and depending on the filter, either run the extension or don't run the extension. Extensions do not use any queuing, instead they are part of the add/update entity process directly. Since the server extension execution is always an overhead in any save operation, due to the synchronous way it is currently being executed. So being able to filter scenarios where the extension should not be run would be an instant performance increase for many customers that use server extensions.
  • Supported filter types are:
    • Action
    • EntityType
    • LinkType

Additional information:
https://community.inriver.com/hc/en-us/articles/10495170246428-Event-filtering-for-extensions

Please see below for the deployed bug fixes:

• • We have applied a solution to ensure that when working as a user in Control Center, and adding or checking the existing extensions, the "Extension Description" is now properly placed.