Navigation and interaction

Working with Navigation and Interaction Components in Afina

The Navigation and Interaction components are the central hub of Afina script-side page control. They are the place where every page open, hover, click, and selector lookup finds a home inside automation scripts. Users get a smooth experience to drive page navigation, hover over elements, perform single or double clicks, and pick elements through CSS selectors or XPath whenever needed. Furthermore, the toolkit offers reliable management of timing windows, comparison rules, save targets, descriptions, and the interaction data attached to each step.

Once interaction components are loaded into a script, the canvas presents the entire flow on display. The best part is the convenience: a user can monitor each navigation step, locate any specific component in seconds with the matching label, and trigger interactions across many scenarios in a single click.

Benefits of Navigation and Interaction Components

• A wide list of interaction types is available in the Navigation and Interaction group for every business need.
• Users can configure each step through proper timing windows and saved targets.
• Downstream automation scenarios easily reach into a result through the saved-variable reference.
• The components support both single page visits and full multi-step navigation pipelines at any moment.
• Any user can have a smooth experience while building page-level logic with a unique configuration.

Once an interaction component is saved, the freshly-placed step joins the rest of the entries inside the script canvas. From this point, a user can run the scenario, edit each component, attach the step to a pipeline, mark older entries for cleanup, link the right selector to a transition, and send the script into automation tasks. Thus, every newly-placed component becomes immediately operational.

Visit Website

A wide list of reasons exists to use the Visit Website component in Afina. To start with, it offers brilliant speed for fresh page loads. Then a user can shift focus to the reliability with already-prepared link data. The component is totally effective for setting up a working environment, deploying a large batch of page visits at once, or restoring a known good navigation flow after a workflow change.

Furthermore, the Link field at the top of the component panel provides uninterrupted access to the destination URL. A user picks the link flavor and points at the matching variable. The platform takes care of the rest.

Moreover, the component supports a connected Wait time value. So, a user can pull a custom load timeout straight from the script context whenever the page demands extra patience. After the load wraps, the freshly-fetched page settles into the browser and becomes immediately ready for launching, configuration, and use inside scripts.

Hover and Click

Different interaction scenarios are available for various business needs. Users can drop a single hover at a time, or chain a stack of clicks inside one workflow. For routine selection, a user picks the matching Selection method: Selector for CSS selectors, XPath for XPath expressions, or Saved object for a previously-saved element. The bulk option is located inside the component panel at the top of the script editor.

Before an interaction clicks through, a user should check that the targeted element is no longer wired into an active job, a script, or a workflow that is currently running. The reason is simple: an interaction operation pulls related script references, tasks, page state, and work history along with the action. Thus, an unintended interaction may bring extra losses.

On the other hand, full element replacement is not always the right move. Many users prefer to keep an older selector around, shift its index, swap its element order, or switch the variable to a fresh saved object. The positive part is that the selector simply sits on the bench for a while without any data being permanently lost.

Element Selection and Stored Results

Each interaction in Afina can carry an extensive load of selector data. The data is exactly what scripts and automation jobs reach into during execution. Some examples are CSS selectors, XPath expressions, saved objects, click types, element indexes, and any other parameter that should look different from one interaction to the next.

The best part of this functionality is reusability. One selector can be used everywhere with consistent results. Each script plugs in its own match whenever the call reaches the interaction step. Instead of cloning the selector per script, a user simply prepares the variable correctly. Thus, automation becomes more flexible.

Furthermore, Afina offers two flavors of click logic: Single click and Double click. Single click triggers one tap on the element. Double click triggers a rapid two-tap sequence. Examples include opening a context menu, confirming a button action, expanding a list view, and any other scenario a user wants to drive through clicks.

Both kinds of clicks surface the same Wait for Element plus Wait time fields. The feature is impeccable for keeping a hundred scripts wired to the same selector in one shot. It is not limited here. Users can also pair the component with planned cleanup windows, or stash a snapshot before any major change is applied.