Generative AI-based fallback

If the object on which you want to execute an action is not detected within the specified time-out, you can leverage generative AI based fallback to automate the specific dynamic webpages, decreasing the possibility of the Recorder action failure in the bot due to UI element changes or dynamic properties.

Once the Generative Recorder verifies that a fallback DOMXPath can uniquely identify the target UI element, it conducts an additional validation step. This involves comparing other properties of the UI element. For instance, if the automated action involves data entry, the Generative Recorder ensures that the automation proceeds only if the fallback DOMXPath corresponds to a data entry input, such as a text box, and not to buttons or labels.

To enable the generative AI capability:
  1. From the Bot editor, navigate to Advanced settings > Package settings.

    Navigate to Advanced settings

  2. In the Package settings > Recorder, enable the Use Generative AI-based fallback option.

    Enable GenAI capability

Note:
  • These are bot level settings. Hence, when you enable generative AI-based fallback, all the capture actions occurring in that specific bot will use these same settings with a time out of 30 seconds.
  • Starting from Recorder package (version 3.1.5 and later), the Generative Recorder configuration settings will be visible regardless of whether a Recorder action is added in the Bot editor. To save the configuration settings, ensure that you use at least one Recorder > Capture action in your automation.

Automatically update DOMXpath values in the debug mode

Generative Recorder offers recommendations, to automatically update automations to make those more resilient. When you run your automations in Run or Debug mode, you will receive recommendations to automatically update the DOMXPath (UI element path) with the value used in successful fallback enabling to make your automations more resilient.
Note: You will not be able to update the DOMXPath value in Run mode.
The fallback notification dialogue window will not appear for unattended automations whenever a fallback happens. This will ensure a smooth automation process.
Note: The fallback notification dialogue window is displayed only to Citizen and Professional developers.

Recommendations when running automations in Run or Debug mode

To update these values at runtime, run your automations in Debug mode. You can choose to update your DOMXPath with the recommended value or to skip it. When you select the Stop automation option, the bot execution will be stopped.

Update DOMXPath values during runtime in Debug mode

When you update your DOMXPath with the recommended value, ensure that you deselect other invalid or dynamic properties in your search criteria before running your automations again. If these dynamic properties remain selected and are combined with the new DOMXPath, the Recorder fails and fallback is triggered again.

You can also move the fallback notification dialogue window at the desired location on the screen according to your needs and preferences thus improving the visibility of your business application and the fallback.

Note: When you run a parent bot, you will have an option to update the DOMXPath value whereas for the child bot, the update option is not available.

Caching of successful Generative AI responses

The Generative AI calls made during successful Generative AI-based fallbacks are now cached in the system memory and the region-based service which are then reused for subsequent executions of the same automation. This reduces the time taken for subsequent executions of the same automation significantly thus improving performance.