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 bug fixes:
-
We have applied a solution to ensure that Excel file uploads no longer result in internal server errors, allowing successful uploads irrespective of file modifications.
- We have applied a solution to ensure that users get a proper and clear error message, displaying "Value cannot contain scripting" when importing entities with scripts into Contribute.
- We have applied a solution to ensure that zip file creation in the Content Store is filtered based on resource format, allowing users to download only the required files.
- We have applied a solution to ensure that in the Query Editor, when changing from "not equal" to "equal", the second condition now displays properly, resolving the issue where the second condition was not displaying correctly after this change.
- We have applied a solution to ensure that the details view tools row no longer overlaps the user details modal window, allowing the modal window to be fully visible as expected.
- We have applied a solution to ensure that when adding and linking entities in the PIM, users can view the ServerExtension in the logs, facilitating validation of whether the ServerExtension is being called.
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
0 comments
Please sign in to leave a comment.