Sections in the article
Inriver is moving toward smaller, more incremental releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver can improve release quality and transparency and identify and mitigate erroneous behavior much faster.
NB! To receive notifications when new release notes are published, please ensure you follow this page by clicking the "follow" button above.
Please see below for the deployed features and improvements:
General
- It has been implemented that extension settings in Control Center can be configured with a visibility option that controls how the setting value is displayed. When adding or editing an extension setting, you can now choose to keep the value always visible, display a masked value that can be temporarily revealed using an eye icon, or set the value as never visible. Revealing a masked value is logged for traceability, and every create, change, and delete of an extension setting is recorded in the audit log. A value that is set to never visible cannot be edited afterwards and must be deleted and recreated if changes are needed.
- It has been implemented that the clickable fields are more distinguishable by the "pointer" cursor on hover on said fields.
- It has been implemented that copy/paste handling for not-found items is improved, allowing item numbers to be copied from Excel and pasted directly into Quick Search for multi-search without manually adding separators.
It has been implemented that users can click the search string in Quick Search and multi-search result tab headers to reopen and edit the query in the Query Editor without re-entering values or opening a new tab.
- It has been implemented that deleting a Language Role through the REST API (DELETE /api/v1.0.0/system/languageroles/{id}) is now rejected with a 400 Bad Request when the Language Role is still assigned to a Role, in the same way as when it is assigned to a user. The error message states that at least one role is assigned to it, and the Language Role is not deleted. The Language Role can be deleted once it has been removed from all Roles in Control Center.
- It has been implemented that, when Language Access is enabled, the REST API shows and sets the Language Roles assigned to a Role. The Roles returned by GET /api/v10.0/system/roles and by GET /api/v1.0.0/system/segments now include a languageRoles list (id, name, and description). A new GET /api/v1.0.0/system/roles/{id}/languageroles returns the Language Roles assigned to a Role, and PUT /api/v1.0.0/system/roles/{id}/languageroles with a list of Language Role IDs replaces them (an empty list removes all of them). Both new endpoints require the Manage Users API permission and return 403 when Language Access is not enabled, 404 when the Role does not exist, and 400 when a Language Role ID is invalid. Language Roles assigned to a Role apply only to users with that Role who have no Language Role assigned directly. When Language Access is not enabled, the responses of the existing roles and segments endpoints are unchanged.
-
It has been implemented that the REST API endpoint entities:upsert returns a descriptive error message for each failed bundle instead of the generic "Internal server error". Depending on the cause, the message now tells the caller that the request timed out or conflicted with another change and can be retried, that a required value is missing, that a value is too long, in an invalid format or out of range, that the change conflicts with related data, or that evaluating the entity's expressions failed. Other unexpected errors return "An unexpected error occurred." together with the processing step that failed and a reference id that inriver Support can use to find the error. Internal system details are no longer included in upsert error messages.
Please note! Some data errors that previously returned the error code invalid_input with an internal description now return one of the messages above, and may use a different error code (for example internal_server_error or duplicate).
Syndicate Advance
- It has been implemented that the Default Locale dropdown in the Syndicate Advance mapping editor now supports search functionality, allowing users to quickly locate and select the required locale.
- It has been implemented that all standard functions in the Syndicate Advance mapping editor are grouped under a single Standard category, displayed first, followed by custom categories in alphabetical order. Custom categories named Standard remain separate from the built-in category.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that deleting an Entity Type in Control Center that is still in use now shows a clear message naming what still references it.
- We have applied a solution to ensure that multi-value CVL fields can be updated via the REST API and RemoteManager when the field already contains a value that was deactivated after it was selected. Previously this failed with a "CVL key that is deactivated" error; you no longer need to remove the deactivated value first. Adding a new deactivated value is still not permitted, matching the Portal.
- We have applied a solution to ensure that CVL values are no longer returned for languages that have been deleted from the system, when retrieving values for a single value list or for all value lists. This aligns the behavior across all retrieval methods with how the system already handles this elsewhere.
- We have applied a solution to ensure that user permissions are refreshed immediately after a successful role change made through extensions.
- We have applied a solution to ensure that deleting a field type in Control Center no longer freezes the page. The delete now runs in the background, a message tells you that it continues in the background, and you can keep working while it completes. If the delete cannot be completed, the error is shown the next time you open the field type. A field type that is still used by a work area, a notification or Print is now rejected immediately with a message, and nothing is deleted. Please note! While a delete is running, entities can show the field type with an empty value.
-
We have applied a solution to ensure that deleting an entity type through the Remoting API returns a clear error when the entity type is still in use. The message now names what still refers to it, for example field types, link types, entities, field sets, restricted field permissions, search hints or print display information, and explains how to remove it.
Old entity version data no longer prevents an entity type from being deleted once all its entities are removed.
Inriver Implementation Standards
Inriver's ambition is to collaborate with our partners in providing our customers with the safest and most secure PIM system 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.