Generative AI-based fallback
- 最終更新日2024/07/22
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.
- From the Bot editor, navigate to .
- In the Use Generative AI-based
fallback option.
- 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.
- Ensure that you use at least one action in the bot to load the Recorder package specific settings.
Automatically update DOMXpath values in the 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.
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.
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.