Release notes: Jun 14th - Jun 15th, 2025

Avatar
Helena Gerebro
  • Updated

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:  

    General

    • It has been implemented to add filtering to the download media options sub-menu, ensuring that only applicable media transformations are displayed. This enhancement enhances the user experience by presenting relevant options tailored to the media context.
    • It has been implemented that two new columns, CreatedBy and ModifiedBy, have been added to the Packages page in ControlCenter. This enhancement provides greater transparency and traceability by displaying the user information associated with the creation and last modification of each package.
    • It has been implemented that new columns have been added to the Extensions table in Control Center, specifically: Created (date), Modified (date), Created by (user), and Modified by (user). These additions enhance auditability and provide improved visibility into the lifecycle and ownership of each extension.

    • It has been implemented that widget visibility on the Portal Dashboard can now be toggled on or off via a configurable server setting in Control Center. The new setting, DASHBOARD_WIDGETS_DISABLED, allows administrators to specify which widgets should be hidden by providing a comma-separated list of WidgetType values.
       

      Example Configuration:

      • Setting Key: DASHBOARD_WIDGETS_DISABLED
      • Setting Value: Jobs, Queries, Custom
      • Effect: Hides the Jobs, Queries, and Custom widgets from the dashboard.

      Supported Widget Types include:

      • Entities
      • EntitiesOverview
      • Channels
      • Queries
      • ProductStatus
      • WorkAreas
      • Jobs
      • Extensions
      • Publications
      • AddedResources
      • Custom

    Expression Engine

    • It has been implemented that several UI improvements have been made to the Expression Engine in Control Center, including the following enhancements:

      • The "Apply on existing..." option is now only enabled when the entered value is a valid expression.
      • The "Overwrite options" radio buttons have been indented for improved visual hierarchy and clarity.
      • Users are notified when the entered value is not recognized as a valid expression.
      • In the Field Type list, field types that support expressions are now explicitly indicated.

      These improvements enhance usability, reduce input errors, and provide clearer guidance when configuring expression-based values.

    • It has been implemented that a new Completeness rule type—Expression—is now available in the Expression Engine. This rule allows users to define Expressions that evaluate entity completeness, either by returning a value between 0–100 to indicate the degree of completeness, or a boolean TRUE/FALSE to signify whether the entity is fully complete or incomplete.

      For more information: https://community.inriver.com/hc/en-us/articles/360012112414-Setting-up-completeness-levels 

    Inspire

    • It has been implemented that a loading notification with a progress indicator is now displayed when inspiring cells via the new Dynamic Table View in Inspire. This enhancement provides users with real-time feedback on the operation’s progress.
    • It has been implemented that the token count on the Inspire tab now updates immediately following any action that affects it. This enhancement ensures real-time accuracy of usage information.


    Please see below for the deployed bug fixes: 

    General

    • We have applied a solution to ensure that entities can now be successfully saved in Enrich, even when a LocaleString exceeds 2,097,152 characters. This resolves a JavaScriptSerializer validation error that previously occurred due to the character limit.
    • We have applied a solution to ensure that the Enable/Disable button in Control Center – Extension Configuration accurately reflects the extension’s state after clicking "Load Default Settings." This resolves a UI inconsistency that previously misrepresented the extension status, ensuring clear and reliable configuration behavior.
    • We have applied a solution to ensure that work areas opened in non-active panels within split view open exclusively on their designated side. This fix prevents work areas from inadvertently shifting focus, maintaining a consistent and predictable user interface layout.
    • We have applied a solution to ensure that in Enrich Excel Export, Double-type fields from related entities are correctly exported with numeric formatting rather than as strings in exponential notation.
    • We have applied a solution to ensure that in Enrich Excel Import, updating a locale string field assigned as the Display Name no longer clears the Display Name when the master language is excluded from the import. This fix preserves the Display Name integrity across localized data imports.
    • We have applied a solution to ensure that the spinner in the Enrich Workarea no longer loads indefinitely when there are no entities to display. This fix improves user experience by accurately reflecting the loading state and preventing unnecessary wait times.

    Expression Engine

    • We have applied a solution to ensure that Expression Support configurations are persisted before a template is added in the CC module of Expression Engine.
    • We have applied a solution to ensure that multiple "Apply Expression" jobs can now be executed concurrently in Expression Engine. This enhancement enables parallel processing of expression evaluations.

    Inspire

    • We have applied a solution to ensure that the Inspire button in the context menu of the Table View, as well as the Inspire batch button in the Entity Details tab, are appropriately disabled when Inspire is not applicable. This prevents unintended user actions and ensures alignment with the configured Inspire-enabled entity types.

    Table View

    • We have applied a solution to ensure that the Table View updates immediately after locking or unlocking an entity in the Details tab. This improvement enhances data consistency and user experience by providing real-time visual feedback.
    • We have applied a solution to ensure that child CVL values not explicitly mapped to a parent CVL value are now correctly displayed in the Table View when any parent CVL value is selected. This fix improves data visibility and ensures consistent representation of CVL hierarchies within the user interface.

    Print 1.0

    • We have applied a solution to ensure that all Print Objects in Print 1.0 now render correctly when using Swedish or other special Latin characters. This update addresses character encoding issues, enabling accurate display and improved localization support across all relevant print outputs.


    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

    Was this article helpful?

    Still need help? contact us

    Related articles

    Comments

    0 comments

    Please sign in to leave a comment.