cancel
Showing results for 
Search instead for 
Did you mean: 

Workato Tips and Tricks

shivakumara
Executive Chef I
Executive Chef I

🔧 Workato Tip of the Day: Avoid XML Pitfalls with Reserved Keywords!

Did you know? In Workato, using <command> in an XML message template might show a red mark at the bottom. 🚩 This happens because command may be reserved keyword in Workato. ( image attached  #image_1: Before fixing the issue and ##Image_: After fixing the issue)

🛠️ Quick Fix:
Add a prefix or suffix, like <commands> or <name_command>, to avoid red mark.
Making this small tweak ensures smoother workflows and error-free integrations.

Stay ahead with these handy tips! 💡

This simple adjustment can make your XML integrations error-free and reliable. Keep this in mind for your next project! 🌟

before.jpgAfter.jpg

1 ACCEPTED SOLUTION

Hi @Prudvi,
Workato XML Processing Logic vs JSON Processing Logic:

XML: Workato's XML engine may enforce stricter validation rules or reserve certain tags for internal use due to XML's hierarchical structure and metadata handling. Tags like `command` could trigger errors during parsing if they conflict with system-defined keywords.

JSON: Workato treats JSON as a more flexible data structure and doesn’t enforce strict naming rules, allowing keys like command without issues.

This is my understanding on the JSON and XML parsing logic. Hope I have answered your question.

View solution in original post

5 REPLIES 5

Prudvi
Deputy Chef II
Deputy Chef II

Hi Shiva,
I have tried to create a message template using JSON format and I don't see the error message as mentioned in the above article.
Any reason why workato is only considering command as a reserved keyword for XML not for JSON.
Regards,
Siddhartha

Hi @Prudvi,
Workato XML Processing Logic vs JSON Processing Logic:

XML: Workato's XML engine may enforce stricter validation rules or reserve certain tags for internal use due to XML's hierarchical structure and metadata handling. Tags like `command` could trigger errors during parsing if they conflict with system-defined keywords.

JSON: Workato treats JSON as a more flexible data structure and doesn’t enforce strict naming rules, allowing keys like command without issues.

This is my understanding on the JSON and XML parsing logic. Hope I have answered your question.

Hi Shiva,
Thanks for the response.
wanted to confirm, all the components created in workato are internally converted to XML.
Regards,
Siddhartha

Hi Prudvi,
Not necessarily, it is purely depends on which component we are using.

  • JSON is Workato's primary internal format for processing and communication.
  • XML is supported where required, but it is typically converted into JSON internally for easier handling.
  • Workato’s architecture includes parsing, transformation, and output capabilities to manage both JSON and XML seamlessly.

    The issue arises not from JSON itself but from Workato's XML parsing logic and how certain keywords like command might conflict with its internal system architecture or processing rules.

    Thanks and Regards,
    Shivakumar A