<?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: New Release Announcement: Unveiling the Newest Automation Accelerators (May 2024) in Workato Pros Discussion Board</title>
    <link>https://systematic.workato.com/t5/workato-pros-discussion-board/new-release-announcement-unveiling-the-newest-automation/m-p/9801#M3989</link>
    <description>&lt;P&gt;I’m currently implementing the &lt;STRONG&gt;Autonomous Operations Framework (AOF)&lt;/STRONG&gt; from the Workato Academy, which is designed to standardize error handling, logging, and recovery using sub-recipes like error logging and job recovery. While testing the setup provided in the Academy package, I observed that the &lt;STRONG&gt;Job Recovery recipe is not being triggered&lt;/STRONG&gt;, even though the conditional block in the orchestrator recipe explicitly passes "Yes" to invoke the recovery sub-recipe. I’ve confirmed that the orchestrator recipe calls the job recovery step as per the framework design, and the test scenario simulates a recipe failure, but the job recovery recipe still doesn’t appear in the dashboard or get executed. I’ve followed the AOF accelerator implementation without any customization, and all recipes are published and accessible. This seems to contradict the framework’s expected behavior, where job recovery should be automated once an error is encountered&lt;/P&gt;</description>
    <pubDate>Wed, 07 May 2025 09:27:36 GMT</pubDate>
    <dc:creator>Patel0786</dc:creator>
    <dc:date>2025-05-07T09:27:36Z</dc:date>
    <item>
      <title>New Release Announcement: Unveiling the Newest Automation Accelerators (May 2024)</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/new-release-announcement-unveiling-the-newest-automation/m-p/6701#M2907</link>
      <description>&lt;P&gt;Based on the feedback from the customers and pain points that we heard from the partners, we have released the below 2 new platform accelerators:&lt;/P&gt;&lt;OL class=""&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;&lt;SPAN&gt;Autonomous Operations Framework (AHQ)&lt;/SPAN&gt;:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;&amp;nbsp;The&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;Autonomous Operations Framework (&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;AOF&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;) Accelerator was built to provide our customers with a standardized approach for error handling and recovery across all of their recipes&lt;/SPAN&gt;.&amp;nbsp;&lt;SPAN&gt;While the product contains many features to handle errors, organizations often wish to ensure a standard approach is used for all recipe builders to save time and also ensure that the teams supporting the integrations/automation know exactly what will happen when an error is encountered in a recipe.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;For example, it might include a ticket being created in ServiceNow, a message being logged in a database, and automatic retries of the recipe every 10 minutes. The operations team can configure the settings in the AOF, and then all developers simply send their errors to the framework and all notifications, logging, and retries will be handled automatically&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;&lt;SPAN&gt;Automation Quality &amp;amp; Security (AHQ)&lt;/SPAN&gt;:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;Workato’s Automation Quality &amp;amp; Security &lt;SPAN&gt;&lt;SPAN class=""&gt;AHQ&lt;/SPAN&gt;&lt;/SPAN&gt; Accelerator provides a framework to&amp;nbsp;standardize&amp;nbsp;recipe development&amp;nbsp;best practices&amp;nbsp;and report on the non-adherence of recipes/deployment packages concerning the defined best practices. This accelerator solves some of the compliance check problems as there is:&lt;UL class=""&gt;&lt;LI&gt;&lt;P&gt;No easy way for &lt;SPAN&gt;IT&lt;/SPAN&gt; to check adherence to best practices.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;No metrics to identify non-adherence to best practices.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;No easy way for recipe builders to know whether they are adhering to internal best practices set by &lt;SPAN&gt;IT&lt;/SPAN&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The Latest Version of &lt;SPAN&gt;&lt;SPAN class=""&gt;AQS&lt;/SPAN&gt;&lt;/SPAN&gt; has a Completely Redesigned Rules Engine to Perform Quality Checks &amp;amp; Compile Quality Scores from an &lt;SPAN&gt;&lt;SPAN class=""&gt;SDK&lt;/SPAN&gt;&lt;/SPAN&gt; for all the Rules to Reduce Execution Time &amp;amp; Task Consumption by the Accelerator. Additionally, &lt;SPAN&gt;AQS&lt;/SPAN&gt; has unveiled a new &lt;SPAN&gt;SDK&lt;/SPAN&gt; designed for Task Optimization Assessment. This &lt;SPAN&gt;SDK&lt;/SPAN&gt; can systematically compile recommendations by leveraging insights derived from its predefined rules and core logic, ultimately reducing your task utilization. It significantly accelerates quality check time by 95% while reducing task consumption by 81%.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN&gt;Would you like to see a demo for any of the accelerators? Get in touch with us through&amp;nbsp;&lt;/SPAN&gt;&lt;A href="mailto:accelerators.feedback@workato.com" target="_blank" rel="noopener nofollow noreferrer"&gt;accelerators.feedback@workato.com&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2024 14:23:20 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/new-release-announcement-unveiling-the-newest-automation/m-p/6701#M2907</guid>
      <dc:creator>manoj-gaddam</dc:creator>
      <dc:date>2024-05-15T14:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: New Release Announcement: Unveiling the Newest Automation Accelerators (May 2024)</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/new-release-announcement-unveiling-the-newest-automation/m-p/9801#M3989</link>
      <description>&lt;P&gt;I’m currently implementing the &lt;STRONG&gt;Autonomous Operations Framework (AOF)&lt;/STRONG&gt; from the Workato Academy, which is designed to standardize error handling, logging, and recovery using sub-recipes like error logging and job recovery. While testing the setup provided in the Academy package, I observed that the &lt;STRONG&gt;Job Recovery recipe is not being triggered&lt;/STRONG&gt;, even though the conditional block in the orchestrator recipe explicitly passes "Yes" to invoke the recovery sub-recipe. I’ve confirmed that the orchestrator recipe calls the job recovery step as per the framework design, and the test scenario simulates a recipe failure, but the job recovery recipe still doesn’t appear in the dashboard or get executed. I’ve followed the AOF accelerator implementation without any customization, and all recipes are published and accessible. This seems to contradict the framework’s expected behavior, where job recovery should be automated once an error is encountered&lt;/P&gt;</description>
      <pubDate>Wed, 07 May 2025 09:27:36 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/new-release-announcement-unveiling-the-newest-automation/m-p/9801#M3989</guid>
      <dc:creator>Patel0786</dc:creator>
      <dc:date>2025-05-07T09:27:36Z</dc:date>
    </item>
  </channel>
</rss>

