Define and identify application states using visual elements
A State represents a distinct screen, dialog, or condition in your application. In model-based automation, states form the nodes of a state machine graph that defines your automation workflow.
Unlike traditional automation that relies on hardcoded positions or element IDs, Qontinui identifies states visually by looking for identifying images on screen. This makes automation resilient to UI changes and resolution differences.
Click the 'Add State' button in the state diagram panel
Give it a descriptive name like 'Login Screen' or 'Dashboard'. The name should clearly indicate what this state represents.
Write a detailed description of when this state is active and what it represents in your application.
Add screenshots of unique UI elements that identify this state. See the Identifying Images section below for details.
Identifying images are visual elements that Qontinui uses to recognize when a state is active. When automation runs, Qontinui checks if all required identifying images are visible on screen to determine the current state.
Select UI elements that only appear in this state (e.g., specific titles, icons, or buttons)
2-3 identifying images per state increases reliability and reduces false matches
Avoid blurry or low-contrast images. Higher quality = better recognition
Crop to just the identifying element (e.g., a button, not the entire screen)
Controls how closely the screen image must match your uploaded image (0.7-0.95 typical). Lower = more fuzzy matching, higher = exact matching required.
Default: 0.85
If checked, this image MUST be visible for the state to be considered active. Uncheck for optional images that only appear sometimes.
Default: Checked
Check this if the image appears in multiple states (e.g., a common toolbar). Shared images alone don't uniquely identify a state.
Default: Unchecked
Mark one or more states as initial where automation begins. Multiple initial states are allowed for parallel starting conditions.
Type: Boolean (checkbox)
Mark states where automation should stop. Multiple final states are allowed for different end conditions.
Type: Boolean (checkbox)
Beyond identifying images, states can contain additional elements for more complex automation:
Define rectangular areas within the state for searching or interaction
Examples:
Define specific point coordinates for precise clicking or positioning
Examples:
Define text values for identification, input, or verification
Examples:
Note: Most automations only need identifying images. State regions, locations, and strings are advanced features for complex scenarios.
Multiple states can be active simultaneously. This is useful for:
Qontinui verifies states by template matching: it searches the screen for your identifying images and checks if all required images are found. This happens automatically before executing actions and during state transitions.
