Blue Prism 6.5浏览器自动化功能缺失及Chrome相关功能咨询

Hey there! Let's tackle your Blue Prism questions one by one, since they're both tied to browser automation waiting behaviors:

Yes, Blue Prism does support this functionality for Chrome, but it varies based on the automation mode you're using:

• In the legacy HTML Mode, the "Wait for Document Loaded" action is directly available as a built-in option for browser elements—it waits until the main DOM is fully loaded and ready for interaction.
• In the newer Browser Automation Mode (like the one you're using in 6.5), there's no direct out-of-the-box action for this, but we can replicate the behavior with workarounds (which we'll dive into for your second question).

First off—you're not making a mistake here! This is a known limitation of the early Browser Automation Mode in Blue Prism 6.5. The mode was built to be more streamlined for modern browser interactions, but it did leave behind some of the legacy HTML Mode's targeted waiting actions, including "Wait for Parent Document Loaded".

That said, there are solid workarounds tailored to the specific scenarios you mentioned where Check Exists falls short:

Targeted Fixes for Your Use Cases #

• Dropdown selection triggering page refresh:
  Instead of a generic document wait, combine two actions:
  1. Use Wait for Element State on a critical element that definitely changes after the refresh (e.g., a new page title element, a unique section header, or a button that only appears post-refresh). Set the state to "Visible" or "Exists" with a reasonable timeout.
  2. If the refresh navigates to a new URL, use the Wait for Navigation action (built into Browser Automation Mode)—it waits until the browser finishes loading the new page address.
• Clicking "Next Page" in pagination:
  Focus on an element that updates with each page, like the current page number text. Use the Wait for Element Text to Change action to wait until the text updates to the expected page number. This is way more reliable than Check Exists because it directly monitors the value that changes with pagination.
• Reading HTML tables where most objects stay the same:
  • If the table content updates, use Wait for Element Attribute to Change on the table's innerHTML or textContent attribute. This will trigger as soon as the table's content refreshes.
  • Alternatively, set up a loop that checks the table's row count at short intervals until it stops changing (or matches an expected count, if you know it). This ensures you wait until the table is fully populated.

General-Purpose Document Load Workaround #

For scenarios where you just need to wait for the entire page to be fully loaded, you can run a simple JavaScript snippet via the Run JavaScript action:

return document.readyState === 'complete';

Wrap this in a loop that runs the script repeatedly until it returns true, with a timeout to avoid infinite loops. This mimics the "Wait for Document Loaded" behavior by checking the browser's official ready state.

内容的提问来源于stack exchange，提问作者Michał Plich