Every rule in OptimiDoc operates within a specific context that determines when it is evaluated and which conditions and actions are available. OptimiDoc provides exactly four contexts. This reference explains when each one fires and lists the exact conditions and actions you can use in each.
Overview of Contexts
|
Context |
Trigger Point |
Typical Use Cases |
|---|---|---|
|
Login |
A user logs in to a device |
Restrict device access, auto-print all held jobs, notify administrators |
|
Accept Job |
A job is received from a device |
Block jobs by queue or job title, redirect to another user, send notifications |
|
Before Print |
A job is about to be sent to the printer |
Force black & white or duplex, add a watermark, redirect to another device, save a preview |
|
Release Job |
A user releases a job for printing |
Validate page count or job type, reject jobs by consumption, run scripts |
Within a context, active rules are evaluated in priority order — the lower the number, the higher the priority. Evaluation is cumulative, not first-match: every rule whose conditions are satisfied applies its actions, and matching does not stop at the first rule that fires. Inactive rules are skipped, and a Reject Operation action flags the job for rejection without halting the remaining rules.
The conditions and actions offered on each context's tab are supplied by the server, so the rule editor only ever lets you build valid combinations. The tables below list what each context exposes.
Login
The Login context is evaluated when a user logs in to a multifunction device, before the device menu is displayed. Use it to control access to devices or to trigger automatic actions on authentication.
Available Conditions
|
Condition |
Description |
|---|---|
|
Login (Username) |
The user's login name |
|
User's Group |
The user's group membership |
|
User |
A specific user identity |
|
Department |
The user's department |
|
Device |
The device being accessed |
|
Device tags |
The tags carried by the device being accessed |
|
Current Consumption |
The user's accumulated usage for a chosen property (Total, Print, Copy or Scan) |
Available Actions
|
Action |
Description |
|---|---|
|
Reject Operation |
Deny access to the device |
|
Print All Jobs |
Automatically release and print all held jobs on login |
|
Send Email Notification |
E-mail the job owner |
|
Send Email To |
E-mail a specified address |
|
Run Script |
Execute a script or programme on the server |
Accept Job
The Accept Job context is evaluated the moment a job is received from a device, before it is stored in the job queue. This is the earliest point at which you can intercept and act on a job.
Available Conditions
|
Condition |
Description |
|---|---|
|
Login (Username) |
The login name of the user who submitted the job |
|
User's Group |
The group(s) the user belongs to |
|
User |
A specific user identity |
|
Department |
The user's department |
|
Job Title |
The document or job name |
|
Queue |
The print queue to which the job was submitted |
|
Date |
A calendar date; combine with Greater Than / Less Than to match before or after a given date |
Available Actions
|
Action |
Description |
|---|---|
|
Reject Operation |
Refuse the incoming job |
|
Redirect to User |
Reassign the job to a different user's queue |
|
Send Email Notification |
E-mail the job owner |
|
Send Email To |
E-mail a specified address |
|
Run Script |
Execute a script or programme on the server |
Before Print
The Before Print context is evaluated just before a job is dispatched to the physical printer. At this stage the job has already been accepted and is about to leave the OptimiDoc queue, making it the right place for last-minute modifications or redirections.
Available Conditions
|
Condition |
Description |
|---|---|
|
Login (Username) |
The login name of the user who owns the job |
|
User's Group |
The user's group membership |
|
User |
A specific user identity |
|
Department |
The user's department |
|
Device |
The target output device |
|
Device tags |
The tags carried by the target output device |
|
Job Title |
The document or job name |
|
Current Consumption |
The user's accumulated usage for a chosen property (Total, Print, Copy or Scan) |
|
Job Consumption Estimate |
The estimated cost of this job |
Available Actions
|
Action |
Description |
|---|---|
|
Force Black & White |
Convert the job to monochrome output |
|
Force Duplex |
Force double-sided (long-edge) printing |
|
Add Watermark |
Overlay watermark text on each page (PostScript jobs only) |
|
Reject Operation |
Cancel the job before it prints |
|
Redirect to Device |
Send the job to a different printer |
|
Save Job Preview |
Store a preview image of the job |
|
Send Email Notification |
E-mail the job owner |
|
Send Email To |
E-mail a specified address |
|
Run Script |
Execute a script or programme on the server |
Release Job
The Release Job context is evaluated when a user releases one or more held jobs at a device. It is typically used in pull-printing scenarios where jobs are held until the user authenticates at a device.
Available Conditions
|
Condition |
Description |
|---|---|
|
Login (Username) |
The login name of the user releasing the job |
|
User's Group |
The user's group membership |
|
User |
A specific user identity |
|
Department |
The user's department |
|
Device |
The device where the job is being released |
|
Device tags |
The tags carried by the device where the job is being released |
|
Number of Pages |
The page count of the released job (optionally filtered by paper format and colour mode) |
|
Job Type |
The type of operation — Copy, Print, or Scan |
|
Current Consumption |
The user's accumulated usage for a chosen property (Total, Print, Copy or Scan) |
Available Actions
|
Action |
Description |
|---|---|
|
Reject Operation |
Prevent the job from being released |
|
Send Email Notification |
E-mail the job owner |
|
Send Email To |
E-mail a specified address |
|
Run Script |
Execute a script or programme on the server |
Context Selection Guidelines
-
Use Login for access control, automatic print-all, and user notification at the device panel.
-
Use Accept Job when you need to act on jobs as early as possible — for example, blocking jobs by queue name or redirecting them to another user.
-
Use Before Print when you need to modify output just before it is sent — forcing black & white, adding watermarks, or redirecting to a different device.
-
Use Release Job for pull-printing scenarios where decisions depend on page count, job type, or the user's consumption at the moment of release.
Note on unavailable conditions. The rule editor exposes only the fields listed above. There is no standalone colour, paper-size, or duplex condition, and no time-of-day or day-of-week condition — use the Number of Pages sub-selectors for paper format and colour, and the Date field for calendar-based matching. The Device tags condition, shown above for the Login, Before Print and Release Job contexts, is available from the release following 26.07; in 26.07 and earlier the rule editor did not offer it.
Related articles