Overview

This article describes differences between shared queues and Delegation Print (aka VIP shared queues).

Accounting differences

There are no accounting differences between terminal types. Shared job is always accounted to user, who released the job. No matter if shared queue is VIP or not.

Displaying on terminal differences

This behavior is controlled by printSharedJobs SafeQ property which is disabled by default.

a) printSharedJobs=Disabled

If job owner sign in, everything is normal.

If some another member of shared queue (no matter if VIP or not) sign in, behavior depends on terminal:

• Terminal professional and SRET: Shared job is not visible in main menu. Job is shown only in waiting jobs list.

• Terminal embedded: Shared job is shown in main menu (for example Print(1)) but it is not possible to print it from main menu. This job can be released only from waiting jobs tab.

b) PrintSharedJobs=Enabled

If some another member of shared queue (no matter if VIP or not) sign in:

• Terminal professional and SRET: Shared job is visible in main menu.

• Terminal embedded: Shared job is shown in main menu (for example Print(1)) and it is possible to print it. Even KM Print all will print both private and shared jobs.
  

Using of billing codes

SafeQ client allows user to select billing code for print job. Job is accounted to this selected BC (BC of user, who sent job).

In case, that job is accounted to user, who released the job, BC of user who sent the job is used.