Automation of actions

Working with Action Components in Afina

The Action Automation components are the central hub of script logic inside Afina. They are the place where every screenshot, JavaScript run, network filter, and keyboard press finds a home. Users get a smooth experience to capture page state, inject custom code, block unwanted requests, and simulate keys whenever needed. Furthermore, the toolkit offers reliable management of timing windows, save targets, descriptions, code blocks, and the action data attached to each step.

Once action 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 step, locate any specific component in seconds with its title, and trigger actions across many scenarios in a single click.

Benefits of Action Components in Automation

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

Once an action 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 action to a pipeline, mark older steps for cleanup, link the right save target to a transition, and send the script into automation tasks. Thus, every newly-placed component becomes immediately operational.

Take Screenshot

A wide list of reasons exists to use the Take Screenshot component in Afina. To start with, it offers brilliant speed for visual capture. Then a user can shift focus to the reliability with already-prepared file paths. The component is totally effective for proving page state, deploying a large batch of audit captures at once, or restoring a known good visual reference after a workflow change.

Furthermore, the Saved object field at the top of the component panel provides uninterrupted access to per-element captures. A user picks the saved-object flavor and points at the matching variable. The platform takes care of the rest.

Moreover, the File name field supports a connected naming pattern. So, a user can pull a unique label straight from the script context whenever it is needed. After the capture wraps, the freshly-saved image settles into the file system and becomes immediately ready for launching, configuration, and use inside scripts.

Execute JavaScript

Different code-injection scenarios are available for various business needs. Users can drop a single statement at a time, or wipe a stack of redundant calls whenever the catalog changes. For routine cleanup, a user ticks the matching component and replaces the JavaScript field with a fresh block. The bulk option is located inside the script canvas at the top of the Action Automation group.

Before a script run clicks through, a user should check that the targeted code is no longer wired into an active loop, a side-effect chain, or a workflow that is currently running. The reason is simple: a JavaScript operation pulls related script references, tasks, page state, and work history along with the result. Thus, an unintended run may bring extra losses.

On the other hand, custom code is not always the right move. Many users prefer to keep an older snippet around, shift its save target, swap its wait window, or switch the description for clarity. The positive part is that the snippet simply sits on the bench for a while without any data being permanently lost.

Block Requests and Keys

Each script in Afina can carry an extensive load of action data. The data is exactly what scenarios and automation jobs reach into during execution. Some examples are blocked URLs, key codes, screenshot paths, JavaScript blocks, save targets, and any other parameter that should look different from one step to the next.

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

Furthermore, Afina offers two flavors of input control: Block Requests and Keys. The Block Requests action filters network traffic. The Keys action simulates key presses. Examples include Enter, Backspace, Tab, Space bar, Esc, Delete, Arrow Up, Arrow Down, and any other keystroke a user wants to send into the page.

Both kinds of action surface the same Wait from / Wait to and Description fields. The feature is impeccable for keeping a hundred scripts wrapped up cleanly in one shot. It is not limited here. Users can also pair the action component with planned cleanup windows, or stash a snapshot of script state before any major change is applied.