sections in the article
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 identify and mitigate any erroneous behavior that may be caused by the release much faster.
Please see below for the deployed features and improvements:
- A new version, 1.16.0, of the integration framework (IIF) has been released and for detailed information on this please see: Integration framework: Release notes
- In the Control Center, we have introduced a user-friendly shortcut, Ctrl + Alt + [1-0], facilitating efficient configuration of auto log refresh periods. This feature is complemented by automatic 10-second log refresh intervals, ensuring timely updates of data. For example:
- - Ctrl+Alt+1: 1 minute
- - Ctrl+Alt+6: 6 minutes
- - Ctrl+Alt+0: 10 minutes
- HTML templates are now supported in the REST API, allowing users to perform POST, PUT, GET, and DELETE operations for HTML templates.
- In the Control Center, users are now prevented from adding duplicate completeness rules within the same entity type and prevented from adding a rule with a null setting value.
- The extension deletion dialog within the extension list has been enhanced for improved consistency. Whether deleting from the list or within the extension view, its behavior remains uniform.
Please see below for the deployed bug fixes:
- For the Print users, we have applied a solution so that it is now possible to add a name to the Attribute, and it remains as per what the user has added after selecting a type.
- For the Print users, we have applied a solution so that it is now possible to add a Space value in the Delimiter.
- We have applied a solution so that, in PIM, exported Excel files will no longer displace data in the columns. This enhancement will facilitate users in properly reading the data within the exported Excel files.
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
1 comment
Hi! I don't understand the change "In the Control Center, users are now prevented from adding duplicate completeness rules within the same entity". Why is that change made? Personally it would make sense to allow it. Imagine you have a "Website completeness" rule group with the rule that description needs to exist. Then imagine you want to add a group for print as well, description might be a requirement for print as well.
I assume it is done for performance reasons as calculating it more than once is unnecessary. However this messes a bit with the rule "relations group complete" does it not? Now a rule can't check if an entity is relations group complete for "website" and "print" reliably.
Please sign in to leave a comment.