Apty Element Selection - Advanced

To ensure an accurate selection of elements when setting up workflows for the Host application, an advanced Control Panel enhancement has been integrated into the Admin Console.

PATH: Admin Console > Select the Application from the left sidebar > Click on the Settings Icon> General Settings > Advanced > Advanced Options page appears  

Inside the page for Advanced Options, the user can create conditions to ignore specific selectors by clicking the Add Condition button. Any created conditions will ignore the dynamic selectors thereby allowing precise selection.

Dynamic Selectors

A dynamic selector uses a variable or an argument as a property for the attribute of your target tag. This allows the selector to easily identify a target element based on the value of the variable or argument, and not an exact string, which might change, depending on interactions inside our application. As such, the variable or argument can be changed to interact with a different element, without changing the selector itself.

Once clicked, conditions can be created as listed:

  1. A dropdown button appears against the IF/OR IF condition where the user can select the desired selectors. Apty provides the following selectors:                        
  2. Select the operator. Apty provides the following operators to choose from: 
  3. Enter the value to be ignored.                                               

More conditions can be added by clicking the plus button. Similarly, the added conditions can be removed by clicking the minus button.

ignore dom eventsignore selector condpartial selector cond

Attribute Priority

The user can set the priority for defining the selector inside the Attribute Property field.

NOTE: The user can add the selectors separated by a comma inside the Attribute Priority field;
For Ex: if id, class, and href are entered inside the field then id will be given the highest priority and href will have the least priority.
A selector that remains unique and consistent during the selection of elements can be given higher priority

Container Score Threshold

Defines the accuracy of the selector; as per the defined threshold, element selection can be made more precise. Inside the Container Score Threshold field, the user can set the threshold value, any selector below the threshold value will be ignored.

Max Z-Index

The user can set the maximum Z-index for content displayed on the application inside the Max Z-index field. The Z-index value ensures that the element is always on top.

Additional Functionalities:

additional func

Apty’s advanced settings also offer additional functionalities to improve workflow performance and element selection:

  • Detect Top Window and Iframe DOM Changes: Monitors changes within iframes or the top window to ensure workflows adapt to dynamic content.
  • Enable Shadow DOM Support: Adds support for applications built with Shadow DOM, solving common element selection issues.
  • Reduce Workflow Auto-Scroll Animation: Streamlines the user experience by minimizing automatic scrolling.
  • Ignore Selector Conditions: Customize conditions to ignore specific selectors, preventing them from interfering with workflows.
  • Ignore DOM Events: Set conditions to ignore certain DOM events, reducing unnecessary workflow triggers.
  • Partial Selector Conditions: Configure partial conditions for selector targeting, allowing more nuanced selection.
  • Debounce DOM Change: Set a debounce time to optimize performance when continuous DOM changes occur.
  • Render Client Widget: Choose where to render the client widget, with options like HTML or Body.
  • Workflow Click Element Advance On Behavior: Customize how workflows advance based on user interactions (e.g., mousedown, click, mouseup).
  • Metadata Tracking Depth: Adjust the tracking depth for metadata to improve performance in complex DOM environments (default value: 10).
  • Configurable Workflow Failure Wait Time

    This enhancement allows users to configure a custom wait time for triggering workflow failures based on application loading time. Previously, workflows would fail if an element took longer than 15 seconds to load. With this update, users can adjust the wait time to match the application’s performance, ensuring workflows are not interrupted by slower loading times.
    The default is 15 seconds, but you can customize it to suit the specific application loading time.

    wait time config (1)