May 6th - May 7th, 2023 / Release notes

June 01, 2023 09:19
Updated

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.

Honorable mentions

Before the list of deliverables is presented, we have some honorable mentions in the release that needs some special attention here in the release notes :)

We are happy to say that we have now included Inspire in inriver PIM. Inspire, featuring ChatGPT AI, offers a solution for generating product descriptions, social media posts, and SEO keywords. This tool utilizes structured data from inriver to create precise, compelling, and original product text with minimal effort. The technology behind this solution is AI-driven, offering an innovative and efficient approach to content creation. If you want to know more about the feature and activation of such feature, please check the page https://community.inriver.com/hc/en-us/articles/8686669024156.

Further on, the query editor in Enrich has now been upgraded to also support OR between the field conditions for the entity type. This upgrade comes with the limitation that you can either have OR between all field conditions or AND between all field conditions, it's not possible to have combinations within the field conditions. The support for OR has been added to field conditions only-not when adding a condition for related entity type or between any other types of conditions. There you will instead see a fixed AND operator.

We have also added the possibility for the Enrich user to cancel on-going jobs. This has been a very-much sought-after feature to prevent the user from being blocked if e.g. a misconfigured job has been triggered and forcing the user to wait for the job to finish before the work can be resumed.

We have also included in this release execution metrics of the environments extensions visible in Control Center. The metrics show the response time, number of successes and failures, and information split per service. Please note that a more in-depth article explaining the metrics visible in Control Center will come soon.

Last but definitely not least in the honorable mentions, we have now added support for upsert in REST API. As a user of REST API, I want to be able to insert or update (upsert) entities and links in batch via POST /api/v1.0.0/entities:upsert. The API client does not need to be aware of system/entity id's since any field value may be used a key to identify existing entities. It's possible to upsert multiple layers of linked entities in one go (with optional deletion of stale links). Furthermore, the upsert endpoint also lets the client set specification data, field set and segment.

Request body example:

Improvements and/or enhancements for Enrich:

As an Enrich user working with an entity on the Details tab, I want a toggle to hide the read-only fields from the details view so that I can more easily find the fields that I’m able to edit. https://community.inriver.com/hc/en-us/community/posts/360008990180-Filter-to-hide-ReadOnly-fields-from-Details-view-
As an Enrich user, I want to open the Query Editor directly from the Dashboard so that I can save an extra click going to Enrich. https://community.inriver.com/hc/en-us/community/posts/8479226710044-Add-Create-new-entity-and-Query-editor-icons-on-the-Dashboard-of-inriver?page=1#community_comment_8479534998940
As an Enrich user, I want to have a view of the linked entities on the "Includes" and "Included in" tabs as a top-to-bottom list So that I more easily can sort them in my preferred order
Correction for after changing the data on a display name field in Enrich (example from blue to red), the new data (red) is not searchable until the Rebuild job is run

Improvements and/or enhancements for REST API:

As a user of REST API, I want to have endpoints to be able to access model-specific endpoints like:
- GET/POST/PUT/DELETE EntityTypes
- GET/PUT FieldTypes
- POST/PUT/DELETE Languages
- POST/PUT/DELETE Fieldsets
- GET/POST/PUT/DELETE Categories
- GET/POST/PUT/DELETE CVL
- GET/POST/PUT/DELETE Completeness
- GET/POST/PUT/DELETE Restricted Fields
As a user of REST API, I want to have endpoints for ChannelMessages and ConnectMessages to be able to track the messages.
Correction by creating a new endpoint v1.0.1/entities:createnew for fixing issues with:
- If the user isn't assigned to segment 0 (default segment) it's not possible to create the entity in another segment
- If segmentId is omitted an error is returned (unless the user is assigned to segment 0)
  When supplying segmentId a Connect event (EntitySegmentationChanged) is fired - which is wrong
Correction for documentation regarding user provisioning for only provision roles and permissions in an SSO scenario (and only in that scenario).
Correction for If you send a request to v1.0.0/query (REST API, in an NDL environment) with a DataCriteria that contains a FieldTypeId that links to an integer field and operator is equal to "IsNotEmpty" you won't find entities that have the value 0. If you do the same request in an ODL environment you will find the entity.
Correction for documentation:
- Changed 'ProducesResponseType' CreateComment` from list to single 'CommentModel' (this only effect swagger documentation)
- Changed 'ProducesResponseType' on 'GetImageConfigurationDetails' from single `ImageConfigurationDetailsModel' to list (this only effect swagger documentation)
- Renamed 'GetFields' to `UpdateSpecificationValues'
- Turned all fields in 'EntityBundleModel', 'LinkCriterionModel', 'FetchLinkObjecsModel' to properties

Improvements and/or enhancements for Control Center:

As a user of Control Center, I want REST API Extension actions to be logged in Control Center logs
As a Control Center user working with the fields of an entity in the model, I want the ability to see the FieldTypeId parameter in the list of fields so that I can more easily understand what field to work with.
Correction for Control Center when the user is unable to save more than one row of name and description for a FieldSet after first save
Please note that input validation for HTML templates is enforced - restricted strings are system.io, wwroot and stacktrace. Uploading an HTML template containing these strings will trigger a "Not Acceptable" error. This validation will be enforced via Remoting API soon as well.

Improvements and/or enhancements for Syndicate:

As a user, I want Coalesce to allow me to add the same field multiple times, So I can have another language as a backup. Read more about Coalesce function here.
As a user, I want to schedule my syndications inside Syndicate, so I don't have to go to control center to do so. Read more here.
As a user, I would like to be able to get the resources set order in Enrich, so I can use my own sort order to prioritize my images in syndications. Read more here.

Improvements and/or enhancements for Plan & Release:

Correction for Items in Plan & Release that are excluded from Node should be greyed out and marked as "excluded".

Improvements and/or enhancements for Planner:

Correction for corner-case when the exported file contains headers but no values.

Comments

19 comments

Per Bolmstedt | Kodexe ☕

May 09, 2023 06:07
https://community.inriver.com/hc/en-us/articles/8686669024156 seems unavailable. Or is it just me? :)
3
Tomas Bylander

May 09, 2023 07:16
Hi,

Apologize for this, can you please try again?
2
Micah Jank

May 19, 2023 20:07

Edited
Please note that input validation for HTML templates is enforced - restricted strings are system.io, wwroot and stacktrace. Uploading an HTML template containing these strings will trigger a "Not Acceptable" error. This validation will be enforced via Remoting API soon as well.
Can you explain the reasoning behind this? We have React builds that are output as single html files and contain "prepareStackTrace" references in the final output. This causes the html templates to give the validation error.
1
Tomas Bylander

May 10, 2023 04:18
Hi David!

The implementation of the extension message filtering is done but due to the high-risk nature of such a feature and since the implementation of this feature has corresponding changes in multiple parts of the service, the complete roll-out will take several weeks. This release contained some parts of the implementation, the next release will be contain some parts and so on. More information will come.
1
Karin Björnbäck

May 12, 2023 09:50

Edited
Hi Frank Hancock,
I asked one of our developers behind this new functionality and this was the guidance from him:

Linked entities should be grouped per link type. Please modify the request body to something like this:

Hope this will help you!
1
David Kraft

May 10, 2023 14:16
Great, thanks for the update Tomas!
0
Erik Strandberg

May 30, 2023 22:35
Hey Tomas,

Much appreciated and cheers for the fast follow-up!
0
Tomas Bylander

May 29, 2023 06:09
Hi Erik,

Since there has been push-back on this from several customers, I have gone ahead and reverted the initial change and will leave it like this during the investigation to determine at which level we can realistically restrict the use of certain keywords in the templates.
0
Erik Strandberg

May 26, 2023 12:41
Have to chime in that we're having the exact same issue with basically all of our templates delivered to customers, we're currently unable to redeploy those with fixes, they're all having issues with the stacktrace word blacklisting which seems... a bit silly.

We have another html template under development that will reference the word "Stacktrace" not just in code but in the GUI as part of a troubleshooting step / developer contact card.

Nevertheless happy to see that it's being re-evaluated and am hoping for an update soon...
0
Tomas Bylander

May 20, 2023 05:47
Micah Jank Hi, we have learned that this change caused some problems for a small subset of HTML templates with minified code with references to stacktrace and we are reevaluating this change.
0
Tomas Bylander

May 16, 2023 10:06
Further guidance from our developer:

If you want to unlink "Item Test ID 2" you should simply omit it from the entities array for the ItemResource link type. The setting "staleLinkAction": "Unlink" will unlink any existing link that is NOT supplied in the entities array.
0
Frank Hancock

May 12, 2023 13:48
Hi Karin Björnbäck,

My questioned pertained to doing a link AND unlink of the same link type for the same entity under a single request. It appears that it's not possible at the moment. So for now, I will relegate it to two separate requests.

The grouping advice is helpful, I'll be sure to follow that form when submitting future payloads.

Thanks!
0

Frank Hancock

May 11, 2023 20:57
Edited

The REST Upsert addition is a tremendous addition. One question I have, I noticed this while testing.

When performing links, are you able to perform linking and unlinking action under the same entity?
When trying this out, neither linking nor unlinking was performed when including both actions, but still receive a 200 response:

[
  {
    "entityTypeId": "Resource",
    "keyFieldTypeIds": [
      "ResourceFilename"
    ],
    "fieldValues": [
      [
        "ResourceFilename", "test.jpg"
      ]
    ],
    "links": [
      {
        "linkTypeId": "ItemResource",
        "entities": [
          {
            "entityTypeId": "Item",
            "keyFieldTypeIds": [
              "ItemID"
            ],
            "fieldValues": [
              ["ItemID", "Item Test ID 1"]
            ]
          }
        ]
      },
      {
       "linkTypeId": "ItemResource",
       "staleLinkAction": "Unlink",
       "entities": [
         {
           "entityTypeId": "Item",
           "keyFieldTypeIds": [
             "ItemID"
           ],
           "fieldValues": [
             ["ItemID", "Item Test ID 2"]
           ]
         }
       ]
     }
    ]
  }
]

David Kraft

May 09, 2023 14:06
Any word on whether Extension Message Filtering will be included, or has this been pushed out further? It was mentioned in Chicago that this would be part of this release.
0
Cindy Van De Water

May 09, 2023 07:21
It works. Thanks
0
Tomas Bylander

May 09, 2023 07:19
Thank you for fast feedback!
0
Henrik Grönvold

May 09, 2023 07:17
Tomas Bylander
Now we're good! :)
0
Henrik Grönvold

May 09, 2023 07:13
Me neither :/
0
Cindy Van De Water

May 09, 2023 06:24
Nope, Same here. Can't read it.
0

Please sign in to leave a comment.

Join the Easter Challenge!