<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Workato Tips and Tricks in Workato Pros Discussion Board</title>
    <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8330#M3479</link>
    <description>&lt;P&gt;Hi Shiva,&lt;BR /&gt;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.&lt;BR /&gt;Any reason why workato is only considering command as a reserved keyword for XML not for JSON.&lt;BR /&gt;Regards,&lt;BR /&gt;Siddhartha&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Dec 2024 12:26:12 GMT</pubDate>
    <dc:creator>Prudvi</dc:creator>
    <dc:date>2024-12-17T12:26:12Z</dc:date>
    <item>
      <title>Workato Tips and Tricks</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8311#M3471</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;span class="lia-unicode-emoji" title=":wrench:"&gt;🔧&lt;/span&gt; Workato Tip of the Day: Avoid XML Pitfalls with Reserved Keywords!&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Did you know? In Workato, using &amp;lt;command&amp;gt; in an XML message template might show a red mark at the bottom. &lt;span class="lia-unicode-emoji" title=":triangular_flag:"&gt;🚩&lt;/span&gt; This happens because command may be reserved keyword in Workato. (&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN&gt;image attached&lt;/SPAN&gt; &lt;A class="" href="https://www.linkedin.com/feed/hashtag/?keywords=image_1&amp;amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7264305883604557824" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp;#&lt;/SPAN&gt;image_1&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt;: Before fixing the issue and&lt;/SPAN&gt; &lt;A class="" href="https://www.linkedin.com/feed/hashtag/?keywords=image_2&amp;amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7264305883604557824" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;##Image_&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt;: After fixing the issue)&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;span class="lia-unicode-emoji" title=":hammer_and_wrench:"&gt;🛠&lt;/span&gt;️ Quick Fix:&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Add a prefix or suffix, like &amp;lt;commands&amp;gt; or &amp;lt;name_command&amp;gt;, to avoid red mark.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; Making this small tweak ensures smoother workflows and error-free integrations.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Stay ahead with these handy tips! &lt;span class="lia-unicode-emoji" title=":light_bulb:"&gt;💡&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":sparkles:"&gt;✨&lt;/span&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;This simple adjustment can make your XML integrations error-free and reliable. Keep this in mind for your next project! &lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="before.jpg" style="width: 999px;"&gt;&lt;img src="https://systematic.workato.com/t5/image/serverpage/image-id/1692i8A41E4A02E7962A9/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="before.jpg" alt="before.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="After.jpg" style="width: 999px;"&gt;&lt;img src="https://systematic.workato.com/t5/image/serverpage/image-id/1693i3E5386D0A0B3E431/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="After.jpg" alt="After.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Dec 2024 05:50:56 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8311#M3471</guid>
      <dc:creator>shivakumara</dc:creator>
      <dc:date>2024-12-10T05:50:56Z</dc:date>
    </item>
    <item>
      <title>Re: Workato Tips and Tricks</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8330#M3479</link>
      <description>&lt;P&gt;Hi Shiva,&lt;BR /&gt;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.&lt;BR /&gt;Any reason why workato is only considering command as a reserved keyword for XML not for JSON.&lt;BR /&gt;Regards,&lt;BR /&gt;Siddhartha&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 12:26:12 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8330#M3479</guid>
      <dc:creator>Prudvi</dc:creator>
      <dc:date>2024-12-17T12:26:12Z</dc:date>
    </item>
    <item>
      <title>Re: Workato Tips and Tricks</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8335#M3481</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/11321"&gt;@Prudvi&lt;/a&gt;,&lt;BR /&gt;&lt;STRONG&gt;Workato XML Processing Logic vs JSON Processing Logic:&lt;BR /&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;XML&lt;/STRONG&gt;:&amp;nbsp;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.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;JSON&lt;/STRONG&gt;: Workato treats JSON as a more flexible data structure and doesn’t enforce strict naming rules, allowing keys like command without issues.&lt;BR /&gt;&lt;BR /&gt;This is my understanding on the JSON and XML parsing logic. Hope I have answered your question.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 15:17:05 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8335#M3481</guid>
      <dc:creator>shivakumara</dc:creator>
      <dc:date>2024-12-17T15:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: Workato Tips and Tricks</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8336#M3482</link>
      <description>&lt;P&gt;Hi Shiva,&lt;BR /&gt;Thanks for the response.&lt;BR /&gt;wanted to confirm, all the components created in workato are internally converted to XML.&lt;BR /&gt;Regards,&lt;BR /&gt;Siddhartha&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 15:50:14 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8336#M3482</guid>
      <dc:creator>Prudvi</dc:creator>
      <dc:date>2024-12-17T15:50:14Z</dc:date>
    </item>
    <item>
      <title>Re: Workato Tips and Tricks</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8337#M3483</link>
      <description>&lt;P&gt;Hi Prudvi,&lt;BR /&gt;Not necessarily, it is purely depends on which component we are using.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;JSON is Workato's primary internal format for processing and communication.&lt;/LI&gt;&lt;LI&gt;XML is supported where required, but it is typically converted into JSON internally for easier handling.&lt;/LI&gt;&lt;LI&gt;Workato’s architecture includes parsing, transformation, and output capabilities to manage both JSON and XML seamlessly.&lt;BR /&gt;&lt;BR /&gt;The issue arises not from JSON itself but from &lt;STRONG&gt;Workato's XML parsing logic&lt;/STRONG&gt; and how certain keywords like command might conflict with its &lt;STRONG&gt;internal system architecture&lt;/STRONG&gt; or processing rules.&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards,&lt;BR /&gt;Shivakumar A&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Tue, 17 Dec 2024 16:07:45 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8337#M3483</guid>
      <dc:creator>shivakumara</dc:creator>
      <dc:date>2024-12-17T16:07:45Z</dc:date>
    </item>
    <item>
      <title>Re: Workato Tips and Tricks</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8338#M3484</link>
      <description>&lt;P&gt;Hi Shiva,&lt;BR /&gt;Thanks once again, now it clarifies my understand of these components.&lt;BR /&gt;Regards,&lt;BR /&gt;Siddhartha&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 16:14:14 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/workato-tips-and-tricks/m-p/8338#M3484</guid>
      <dc:creator>Prudvi</dc:creator>
      <dc:date>2024-12-17T16:14:14Z</dc:date>
    </item>
  </channel>
</rss>

