Release notes: November 2nd - November 3rd, 2024

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. 

Please see below for the deployed features and improvements:

General

• It has been implemented that validation has been added to prevent duplicate links when adding a new link. This ensures that unique links are allowed, enhancing data consistency and preventing redundancy within the system.

Brand Store

• It has been implemented that the Brand Store now includes functionality allowing administrators to send email invitations to all or selected users, as well as remove all or specific users from the user list. This enhancement improves user experience by enabling bulk email invitations, streamlining the invitation process for multiple users simultaneously. Additionally, the new option to remove all or selected users from the user list offers greater control and efficiency in user management, ensuring a more flexible and intuitive experience for Brand Store administrators.

• It has been implemented that a delete confirmation prompt is triggered when attempting to remove a PDF template currently in use by a Brand Store. This added validation ensures that administrators are alerted before proceeding with deletion, reducing the risk of unintended disruptions and maintaining template integrity across active brand configurations.

Remoting

• It has been implemented that restrictions are now in place to prevent adding or removing the Administrator role from any user via the remoting API. This change is designed to prevent unauthorized role escalation and safeguard against potential account takeovers, ensuring that the Administrator permissions cannot be modified externally through the API.

  Updated the rules according to the following:

Please see below for the deployed bug fixes:

Brand Store

• We have applied a solution to ensure that duplicate Brand Store names cannot be created through Brand Store templates. A validation has been added to the Brand Store creation process from templates, preventing duplicate names and maintaining unique identifiers across Brand Stores for consistency and improved data integrity.

• We have applied a solution to ensure that products added to the cart in the Brand Store are retained even after refreshing the page. Additionally, carts are now saved on a per-store basis, allowing users to seamlessly transfer to another store without losing their cart contents from the original store. This fix provides a consistent and reliable shopping experience, preserving user selections and supporting efficient multi-store navigation.

• We have applied a solution to ensure that the Brand Store no longer relies on AccessControl for user validation. Instead, users are now verified directly against the Creator and Invitees lists. This adjustment was implemented to enhance data integrity, providing a more accurate and streamlined approach to access management within the Brand Store environment.

• We have applied a solution to ensure that full-text searching functions correctly on fields containing dashes within the Brand Store. Unique IDs are now indexed by default for full-text search, improving search accuracy and performance. For this update to take effect on existing datasets, a data resync will be required. This fix enhances search reliability and ensures consistency across all indexed fields.

• We have applied a solution to ensure that email invitations are successfully sent during the Brand Store publishing process, addressing previous issues with invitation delivery. Additionally, we resolved an issue with missing IDs in invitees after publishing, which now guarantees that all invitees are properly tracked.

Syndicate Plus

• We have applied a solution to ensure that users of Syndicate Plus can now seamlessly view historical outbox entries without encountering errors. This fix addresses the previously reported bug, allowing uninterrupted access to past entries in the outbox.

Remoting

• We have applied a solution to ensure that, as a user in the remoting environment working with DataService.GetAllFieldsByFieldType in ODL environments, you can now accurately retrieve the correct last modified date specific to a FieldType. This fix addresses instances where the last modified date of a FieldType may differ from that of the associated entity, providing more precise and reliable data for field modifications.
  

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