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 be able to identify and mitigate any erroneous behavior that may be caused by the release much faster. Please note that larger features and/or changes that are deemed to have a strong impact on customers and partners will of course be communicated in advance.
Please see below for the deployed features and improvements:
- As a user logging into Contribute, Content Store, and/or Supplier Onboarding, there is now an informative text showing a link to the inriver privacy policy when a user logging in to Contribute so that I can get an understanding of how inriver is managing user information according to the guidelines set by GDPR.
-
As a user in Syndicate, it is now possible to see which syndications are scheduled on the syndication card. This is visualized by a clock icon in the upper right corner of the syndication card. When clicked, the user is taken to the schedule step of the syndication wizard.
Please see below for the deployed bug fixes:
-
It has now been corrected so that when enabling the configuration setting "Searchable Field Types " in the Control Center using the QUICK_SEARCH_MAX_RESULT the results will not be capped at 100 but reflect the set value.
- It has now been corrected so that the preview of entities in the "Imports" tab of Supplier Onboarding will exist for the selected entities to be imported.
- It is now corrected so that the "Display Last Modified" date for items/products in a query will be shown local date/time and not in UTC.
- It is now corrected so that a user of the Supplier Onboarding will never see entities that do not pass the Supplier filters applied.
- It is now corrected so that items in the left side panel of Enrich will provide a highlighting effect to indicate the selected or active item.
Comments
1 comment
Hi,
Could you please explain this point a bit more:
"It has now been corrected so that when enabling the configuration setting "Searchable Field Types " in the Control Center using the QUICK_SEARCH_MAX_RESULT the results will not be capped at 100 but reflect the set value."
I can't find this "Searchable Field Types" in Control Center? Are you referring to "Searchable Field Types" in the content store setup? What does this have to do with QUICK_SEARCH_MAX_RESULT since I thought that only affected the Enrich app and not content store.
I also saw QUICK_SEARCH_MAX_RESULT isn't listed here:
https://community.inriver.com/hc/en-us/articles/360012111314
Please sign in to leave a comment.