October 1th - October 2th, 2022 / Release notes

Avatar
Tomas Bylander
  • 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 into the releases and be able to identify and mitigate any erroneous behaviour 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.

     

    On October 1th - October 2th, the following patches were deployed to all stacks:

    Improvements and/or enhancements for REST API:

    • Update Swagger documentation for Extension / package management to reflect the documentation in https://community.inriver.com/hc/en-us/articles/4406998024594-Manage-extensions-and-packages-via-REST-API
    • As a user, it should not be possible to to add an extension with illegal chars in the extension id through the extension REST API. 
    • As a user, it should be possible to download an extension package via REST API
    • As a user, it should be possible to set the state of the extension when it is uploaded via the REST API, e.g. when uploading a scheduled extension since they start running right way. The default behaviour, if omitting the new isEnabled field, is that the extension is enabled. If users want to disable the extension, property needs to explicitly be set isEnabled = false.
    • Correction for when updating specification values via REST API, the process should not stop on invalid values but instead continue processing the valid ones and presents the overall information to the client
    • Correction for when a user tried a second attempt on PUT /api/v1.0.0/workareafolder/{workareaFolderId}/entityIds and the workarea becomes cleaned out
    • Correction for when attempting to retrieve AddtionalData from specification values via below  endpoints according to the documentation https://community.inriver.com/hc/en-us/articles/360012237694-Specification-Additional-Data-Column
    • Correction for when duplicate links exist even if the Link Rule Definition Job is set to Enabled
    • Correction for output format when accessing endpoint GET /api/v1.0.0/syndications
    • Correction for when setting link.inactive property with the REST API.
    • Correction for documented response type to reflect actual response in:
      • Channel:
        • GET v1.0.0/channels/{channelId}/entities/{entityId}/links
          GET v1.0.0/channels/{channelId}/nodes
      • Entity:
        • PUT v1.0.0/entities:upsert
        • POST v1.0.0/entities:mapuniquevalues
        • GET v1.0.0/entities/{entityId}/completenessdetails
        • GET v1.0.0/entities/{entityId}/fieldvalues/{fieldTypeId}/revision
        • GET v1.0.0/entities/{entityId}/media
        • POST v1.0.0/entities/{entityId}/comments
      • Extensions: 
        • GET v1.0.0/extensions/{extensionId}/statistics
        • POST v1.0.0/extensions/{extensionId}/settings:applydefaults
      • System:
        • GET v1.0.0/system/assetconfigurationdetails
        • GET v1.0.0/system/support/internal/retrylog
      • WorkArea:
        • PUT v1.0.0/workareafolder/{workareaFolderId}/query
    • BETA: As an admin, when integrating an external IDP with inRiver PIM, it will simplify the implementation if users can be created, deleted and updated using REST API and ControlCenter permission APIManageUsers.
      • System:
        • GET /api/v1.0.0/system/users - Get list of users
        • POST /api/v1.0.0/system/users:provision - Provision user
        • DELETE /api/v1.0.0/system/users/{username} - Delete user
        • GET /api/v1.0.0/system/users/{username} - Get user
        • PUT /api/v1.0.0/system/users/{username} - Update user

    Improvements and/or enhancements for Syndicate:

    • Popup menu for Mappings(Formats) doesn't fit for the browser window
    • Correction for 'Could not process server request : Invalid work area.' preventing Syndicate to function properly when work area has been deleted.

    Improvements and/or enhancements for Content store:

    • Improvement for loading time for filters
    • Correction for when a user doesn't have any content store linked, no content store boxes should be visible when logging in
    • Correction for when renaming images, naming should be displayed incorrectly in the table
    • Correction for error message when setting user friendly name for a content store
    • Correction for when user clears the excluded field type in Content Store , it should clear the 4 fields -ExcludeFieldTypes,SearchableFieldTypes, MultisearchFields and Filterfields as it has an impact on the Excluded Link type filter selection

    Improvements and/or enhancements for Contribute:

    • When CVL fields are marked as non editable, it should remain as non-editable.

    Was this article helpful?

    Still need help? contact us

    Related articles

    Comments

    12 comments

    Sort by Date Votes
    • Avatar
      Tobias Månsson
      inriver champion
      PIMpoint 2023 Europe
      Easter 2023
      Top Contributor
      First Responder
      +2 more

      Breaking change in the deploy.

      If you used version 1.0.1 of the POST fetchdata method, you need to downgrade again to 1.0.0 

      Not working: https://<cluster-specific-url>.productmarketingcloud.com/api/v1.0.1/entities:fetchdata 

      Working: https://<cluster-specific-url>.productmarketingcloud.com/api/v1.0.0/entities:fetchdata 

      0
    • Avatar
      Srini Kaila
      • Edited

      Is BETA change to support user creation using Rest API available for everyone? What should we to participate in that if it is not open.

      Is there any documentation available?

      1
    • Avatar
      Mark Stuart-Walker
      Feedback Guru
      Community Star
      Mentor
      Curious Master
      +3 more

      There is mention about about v1.0.1 above yet the website shows v1.0.0. Is 1.0.1 in BETA release?

       

      Swagger https://api-prod1a-euw.productmarketingcloud.com/swagger/ui/index#/Channel 

      0
    • Avatar
      Srini Kaila

      I managed to setup new permission for User Provision and use API call to add user.

      However, when I add user using the API, I do not see that user added to Control Center and user is also unable to unable to logon.

      0
    • Avatar
      Emilia Nilsson
      business solutions architect
      PIMpoint 2023 Europe
      Engagement Champion
      Mentor
      Top Contributor
      +2 more

      Hi Srini Kaila,

      The API for User is to provision a user in order to synchronize SAML accounts across systems, and not add an actual user to inriver. The use case for this is to provision users in a single sign-on situation, where it otherwise would get the default role only once they log in and role re-assignment would be done ad-hoc.

      The Swagger documentation will give you a bit more insight into what it does: https://api-prod1a-euw.productmarketingcloud.com/swagger/ui/index#!/System/System_ProvisionUser 

      Kind regards,
      Emilia

      0
    • Avatar
      Srini Kaila
      • Edited

      Hi Emilia Nilsson, we have SSO activated and the user is authenticating through SSO when trying to logging in to inriver. However, they see "Unexpected Error". They are not seeing the access of "default" role.

      When I used Provision User method, I also supplied the Segment ID and the Role name that is supposed to be assigned to that user.

      Now, if I call GET method to inquire on that user, I see inriver response with correct Segment ID and Role Name (as I gave in Provision User call originally). 

      0
    • Avatar
      Emilia Nilsson
      business solutions architect
      PIMpoint 2023 Europe
      Engagement Champion
      Mentor
      Top Contributor
      +2 more

      Hi Srini Kaila, 

      This seems like an issue that would require further investigation - may I ask you to create a support ticket and provide the customer name and details in it?

      Kind regards,
      Emilia

      1
    • Avatar
      Srini Kaila

      Thanks Emilia Nilsson
      I submitted a ticket already (#50568) after my initial comment. 

      0
    • Avatar
      Marcus Jacobsson

      Is the swagger docs really updated with the manage extensions / packages methods? I cant seem to find them.

      https://api-prod1a-euw.productmarketingcloud.com/swagger/ui/index#/

      1
    • Avatar
      Pål Christian Odlo
      Conversation Starter

      Its stated that the beta docs are only in PDF format and as a Postman collection

      https://community.inriver.com/hc/en-us/articles/4406998024594-Manage-extensions-and-packages-via-REST-API

      0
    • Avatar
      Marcus Jacobsson

      And these release notes states that the swagger docs should have been updated with that information, hence my question

      1
    • Avatar
      Steve Vink
      business solutions architect
      Word Weaver
      PIMpoint 2023 Americas
      First Responder

      Hi Marcus,

      I will forward your comment to the development team, and see if we can include these in the Swagger documentation.

       

      Regards,

      Steve Vink
      Principal Business Solutions Architect

      0

    Please sign in to leave a comment.