Release notes: October 28th - October 29th, 2023

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:

• Enhancements have been made to the "Save" and "Undo" buttons on the details form in Enrich, as well as in Plan & Release, to give a better user experience and to let users confirm when clicking "Undo" not to lose changes without the intention to do so. 
  
  
• As a Portal user working with the query editor and searching by Created by/Modified by the user names in the dropdown will now be easier to find with a filter.
  
  
• Enhancements have been made to the text on the browser tab and it now shows which entity is opened, so that it's possible to differentiate what is showing on the page when having multiple browser tabs open simultaneously. The information is shown according to the formula:
  
  [EntityDisplayName] + "-" + [EntityType] + " | Enrich: inriver"
  
  
• Enhancements have been made to the text on the browser tab and it now shows which query is opened, so that it's possible to differentiate what is showing on the page when having multiple browser tabs open simultaneously. The information is shown according to the formula:
  
  [QueryName] + "-" + "Query" + " | Enrich: inriver" 
  
  
• Enhancements have been made to the text on the browser tab and it now shows which work area is opened, so that it's possible to differentiate what is showing on the page when having multiple browser tabs open simultaneously. The information is shown according to the formula:
  
  [WorkareaName] + "-" + "Work area" +" | Enrich: inriver"
  
• Enhancements have been made to the "Save" and "Undo" buttons on the specifications tab in Enrich, to give a better user experience and to let users confirm when clicking "Undo" not to lose changes without the intention to do so. 
  
  
• As an API user, I will now be able to access/change server settings via REST API. The new endpoint must be protected by a new permission ManageServerSettings, so only users having this permission can upsert server settings. 

Please see below for the deployed bug fixes:

• It has now been corrected so that the date & time have the correct date format on the Overview Tab based on the browser's language setting in the same way as when showing the date field on the Details tab. 
  
  
• It has now been corrected so that the user of Supplier should never see entities that do not pass the Supplier filters applied in the Supplier Onboarding application.
  
  
• It has now been corrected so that in the Contribute organization settings field filters are now reset and working as expected when the entity type is deselected/unchecked.
  
  
• It has now been corrected so that when using the REST API and trying to add a non-valid language the response states that this is i non-valid language code.
  
  
• It has now been corrected so that when using the REST API and working with multi-select CVL the user will now get back a separate list of the CVL values.
  
  
• It has now been corrected so that when working with the [REST] delete /api/v1.0.0/model/fieldsets/{fieldsetId}/{fieldTypeId} with invalid fieldsetId nad/or fieldTypeId it will return a proper error response 404.
  
  
• It has now been corrected so that when working with the [REST] delete /api/v1.0.0/model/fieldsets/{fieldsetId} it will return a proper error response 404.
  
  
• It has now been corrected so that when working with the [REST] doing a GET /api/v1.0.0/model/restrictedfields/{restrictedFieldId} with a non-existing restrictedFieldId will give a proper error message. 
  
• It has now been corrected so that when working with the REST API GET /cvls/{cvlId} Requesting will result in an expected 404 Error.