Operation Definitions and Instances
Operation definitions identify business workflows in the terminal event stream. Create one from Operation Definitions, selected Runtime events, Session Viewer start/end markers, or from a suggested operation definition surfaced by session scans.
Set name, type, workspace, and start/end/reset triggers. Triggers can match screen name, action, and field conditions using AND logic. Define inputs and linked entities, then activate the definition.
TermIQ periodically scans recorded sessions and shows suggestions on the Operation Definitions page with a proposed name, start → end screen pair, and confidence. Create a definition from a suggestion in one click or dismiss suggestions you do not need.
When events match an active definition, TermIQ creates database-backed instances that progress from start to in-progress to completed, reset, or failed. Review them in Runtime → Operations. Use Retroactive Analysis to preview historical matches and save selected results without replaying host traffic.
Define business-operation triggers and collect or backfill matching instances.