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 deem 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 in the portal, you will now have the same experience of the main menu no matter where in the application you are working which will give a consistent experience.
As an editor working in the PIM you will now have the field sets to be ordered in a relevant way, so that you can more easily find the Field set that you want to select.
When you are a user with "Reader" permission rights you will now in a more clear way be able to distinguish between read-only fields and editable fields which give you a better user experience.
As a user in the portal setting up an Excel export you will now see the FieldTypeId of the fields together with the field name, which will make it more easy to select the correct field to be exported.
Based on the context and user - it’s sometimes more convenient to do the selection based on the "fieldtypeid" since fields can sometimes have the same name but different "fieldtypeid".
- As a user in the portal working with the "Details"-form in Enrich when editing or adding a new entity you will now get help to remove any leading or trailing spaces in a text that you copy into a string or local string field so that you don't get unintentional space characters in the value that is saved.
- As a user in Enrich working with a query result, you will now more easily be able to refresh the query with one click so that you can quickly get an updated result when you know that the preconditions have changed i.e. after updating an entity.
As a user in the portal when setting up a query in the query editor you will now see the FieldTypeId of the fields together with the field name, which will make it easier to select the correct field.
In some scenarios you need the FieldTypeId info to be able to select what field to work with.
As an editor of the PIM you will now be able to find entities where a created/updated date or date field value is less than 1, 2, 3, 4, 6, 9, and 12 months in the future and past (currently max 4 weeks)
For customers with the need of keeping track of documentation, photographs, etc, it is very useful to use the query editor to find entities that have an expiration date so action can be taken to produce updated or new documents/photos.