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:
- We have applied a solution to ensure that in Content Store, bookmarked or direct links redirect to the login page.
- A solution has been implemented for users of Remoting API, adding validation for incorrect settings keys or null setting values. This enhancement aims to lessen troubleshooting time.
Please see below for the deployed bug fixes:
- We have applied a solution to ensure that, in 3DL, when deleting a FieldType, associated Fields marked as Unique are also deleted. This prevents issues when a FieldType is deleted and then remade with the same name.
- We have applied a solution to ensure that, in 3DL, deleting a value from a CVL assigned to a Field type no longer causes an error.
- We have applied a solution to ensure that users of Remoting API, working with Data Service, can now identify fields returning invalid values in the logs when updating entities. This will lessen troubleshooting time.
- We have applied a solution to ensure that for users of Remoting API, the query for the GetAllChannelStructureEntitiesForType method is optimized. Additionally, we introduced the GetAllChannelStructureEntitiesForTypePaged method to enable pagination for large datasets. This fixes the timeout error experienced by extensions and other integrations using the Remoting API.
- We have applied a solution to ensure that users of Extensions, the saving of Field History is fixed when updating LocaleString Field Data Types via Connect Extensions. This is to maintain customer data integrity.
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
2 comments
Thank you inriver champions for providing the Remoting API improvements!
Do we have more specific information about what is fixed regarding this?
Please sign in to leave a comment.