The trigger is the first part of the rule that the administrator defines and it determines what may cause the rule to be executed. Each of the rule’s conditions, actions, notifications, or their combinations can require different triggers, enabling the creation of granular rules to meet your organization’s specific, complex needs. The YSoft SAFEQ Rule-Based Engine module helps administrators by guiding them through rule setup and disallowing unsupported combinations of parameters.
First, the administrator chooses the point in the print process that triggers the rule. The rule can be triggered when the YSoft SAFEQ server receives a print job from a user’s device, such as a workstation, or from a print server. The administrator then defines the way YSoft SAFEQ will process the job, for example, to redirect the job to a different queue, such as a direct queue on a different, more cost-efficient printer. The administrator can also specify that the rule causes notifications to be sent to the YSoft SAFEQ Client where a pop-up notification window appears on the user’s workstation about the action applied to their print job. A trigger can also cause a notification to be sent after a user logs out or when a job status changes.
Next, the administrator sets what will occur before the job is released to the printer. For example, the trigger can cause the job to be rejected or changes to be applied to the job, such as forcing it to be printed in B/W instead of color. The trigger can also, for example, cause users to be denied authentication at a printer.