LEARN BY BUILDING

Workflow examples

Follow observation, decision, action and verification in practical desktop and game workflow designs.

01 · Launch and type

Program → launch the real local .exe. Window → wait until it exists, then Activate. Focus the text field and send sample text with Keyboard. Verify the visible result. Use readiness checks rather than an unnecessarily long fixed delay.

02 · Continue when an image appears

Find image → Fixed image → select region → Wait until visible → Continue. Check the found result and perform the appropriate Mouse/Keyboard action. Test that a similar image is not selected accidentally.

03 · Compare an OCR value

Read text → Price_Text. Convert with NUMBER(TRIM(Price_Text)) into Price. Condition: Price > 100. Call the appropriate helper in the true branch. Handle conversion errors separately; do not trigger an irreversible action from unverified OCR.

04 · Repeat three times

Variable Counter = 0. Loop: Counter < 3, maximum 3. Inside the block: Keyboard, Wait and Counter = Counter + 1. Verify that these actions are really children of the loop.

05 · Recover with a supervisor

Make a supported window/image check a supervisor, select Recovery and set an appropriate interval/confirmation count. Recheck the condition inside Recovery, prepare the application if needed and choose an explicit continuation path.

06 · A short coordinate route

Window target → local coordinate OCR → axis test → movement method → nearby destination → tolerance → test. Learn a local arrow reference if used. Watch progress in the log and divide distant targets into waypoints when appropriate.

Design principle

Observe, decide, act and verify. Sending a click does not mean the task is complete. Share common work with Call group rather than copying it.

07 · Follow an object and act conditionally

  1. Start from the user’s actual open scene; relaunching is not always necessary.
  2. Create a clearly named object-library resource.
  3. Capture an example and tightly annotate the target.
  4. If background interferes, use GrabCut and inspect the Alpha mask for missing object details.
  5. Observe with the instant tracker first; test motion and disappearance.
  6. Select this resource in Find image → Trained object.
  7. Continue when found; stop or enter Recovery when absent.
  8. Act only when Target_Found is true. Never reuse a stale location.
  9. Verify the post-action state with another image/OCR observation.
  10. Test similar objects, occlusion and scale changes.

08 · Coordinates, heading and arrival action

  1. Select the window target.
  2. Preview the local coordinate reading; separate X/Y if necessary.
  3. Establish axis signs with short north/east movements.
  4. Set real forward/turning keys and distinguish turning from strafing.
  5. Teach the map arrow; revisit the reference if the map rotates.
  6. Try a nearby target, for example 820,875 from 815,869. These are illustrative values.
  7. Configure a pre-movement key only when needed and allow its action to settle.
  8. Set practical tolerance, movement and time limits.
  9. Inspect position, heading error and reading age in the log.
  10. Apply the arrival key only after verified arrival. Use waypoints around obstacles.

09 · Replay with checkpoints

  1. Prepare the starting scene and window.
  2. Choose recording, countdown and mouse sampling interval.
  3. Record a short route and finish with the recording-stop key.
  4. Inspect the event list for unwanted input and long waits.
  5. Add checkpoints where needed and validate the route.
  6. Test a small part at normal speed first.
  7. Configure local OCR for start verification or coordinate checkpoint synchronization.
  8. If focus is lost, restore the state rather than assuming the route can safely continue.

10 · Desktop data transfer

  1. Prepare the source label or table.
  2. Read a tight OCR region into a clear prefix such as Npc_Text.
  3. Clean whitespace with TRIM; convert numeric content with NUMBER and handle errors.
  4. Validate the accepted range or format before sending.
  5. Activate the destination window and input field.
  6. Queue variable text, Tab and any required Enter action.
  7. Read or inspect the destination to verify transfer.
  8. Retest a single sample whenever the source layout changes.

Actual interface images

Original demo scene + actual Find visual panel · illustrative composition · original demo / illustrative composition
Original demo scene + actual Navigate panel · illustrative composition · original demo / illustrative composition
Next stepBuild a workflow with these modules ↗Resolve a problem ↗