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

Was this article helpful?

Still need help? contact us

Comments

19 comments

  • Avatar
    Per Bolmstedt | Kodexe ☕

    https://community.inriver.com/hc/en-us/articles/8686669024156 seems unavailable. Or is it just me? :)

    3
  • Avatar
    Tomas Bylander

    Hi,

    Apologize for this, can you please try again?

    2
  • Avatar
    Micah Jank
    • Please note that input validation for HTML templates is enforced - restricted strings are system.iowwroot 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
  • Avatar
    Tomas Bylander

    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
  • Avatar
    Karin Björnbäck
    First Responder

    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
  • Avatar
    David Kraft
    PIMpoint 2023 Americas

    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
  • Avatar
    Tomas Bylander

    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
  • Avatar
    Henrik Grönvold

    Tomas Bylander
    Now we're good! :)

    0
  • Avatar
    Erik Strandberg
    Conversation Starter

    Hey Tomas,

    Much appreciated and cheers for the fast follow-up!

    0
  • Avatar
    Henrik Grönvold

    Me neither :/

    0
  • Avatar
    Cindy Van De Water

    Nope, Same here. Can't read it.

    0
  • Avatar
    Tomas Bylander

    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
  • Avatar
    Tomas Bylander

    Thank you for fast feedback!

    0
  • Avatar
    David Kraft
    PIMpoint 2023 Americas

    Great, thanks for the update Tomas!

    0
  • Avatar
    Cindy Van De Water

    It works. Thanks

    0
  • Avatar
    Frank Hancock

    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"]
               ]
             }
           ]
         }
       ]
    }
    ]
    0
  • Avatar
    Frank Hancock

    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
  • Avatar
    Tomas Bylander

    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
  • Avatar
    Erik Strandberg
    Conversation Starter

    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

Please sign in to leave a comment.