Hi @aritchie​ ,

Just to confirm, the adaptive card format and the square brackets worked prior to the upgrade? If you use it without the adaptive card, it works fine? Have you tried the square brackets work in the Logger Action? What is the content-type parameter set to in the external action, HTTP Request? Would be you able to share the automation log for me to take a look?

 

Thanks,

Kezia

Hi Kezia,

• Yes, the adaptive card format, with square brackets worked prior to the upgrade.
• If I send a plain json message, it works fine.
• Using square brackets and an automation parameter in the Logger works
• Content-Type  is set to JSON
• Automation log, including my log actions (HTTP Body response, followed by simple log message).

 

This examples uses an extremely basic adaptive card in the HTTP Body:

{
    "type":"message",
 
"attachments":>
       {
          "contentType":"application/vnd.microsoft.card.adaptive",
          "contentUrl":null,
          "content":{
             "$schema":"http://adaptivecards.io/schemas/adaptive-card.json",
             "type":"AdaptiveCard",
             "version":"1.2",
             "body":c
                 {
                 "type": "TextBlock",
                 "text": "{automation.name}, see Âhttps://adaptivecards.io/samples" target="_blank">https://adaptivecards.io/samples](https://adaptivecards.io/samples)"
                 }
             ]
          }
       }
    ]
 }

 

{
    "type":"message",
 
"attachments":>
       {
          "contentType":"application/vnd.microsoft.card.adaptive",
          "contentUrl":null,
          "content":{
             "$schema":"http://adaptivecards.io/schemas/adaptive-card.json",
             "type":"AdaptiveCard",
             "version":"1.2",
             "body":c
                 {
                 "type": "TextBlock",
                 "text": "{automation.name}, see Âhttps://adaptivecards.io/samples" target="_blank">https://adaptivecards.io/samples](https://adaptivecards.io/samples)"
                 }
             ]
          }
       }
    ]
 }

Hi @aritchie​ ,

 

Thank you for the log and additional information. I tested the square and curly brackets for the Logger in 2021 vs 2022. I see that the behaviour has changed. The logger action may have more issues with the curly brackets in 2022 and perhaps the HTTPCaller with the square brackets.

I'll file a ticket to get this looked into. 

 

I also found this idea on FME Community that you may be interested in upvoting or including your use case. 

Thanks,

Kezia

Hi @aritchie​ ,

As an update, we've filed an issue for this bug and have included it in our Known Issues 2022.x article under FMESERVER-19612. This should be resolved in 2022.2.3.

Apologies for the inconvenience and thank you for reporting this.

-Kezia