Overview

This feature allows managers to share their prints with their assistants without asking IT support. Users can decide with whom to share the print.

See Configuring and using Shared Queues for configuration and deployment information.
Delegation Print is based on Workgroup print sharing - Shared Queues and use that same techniques.
See Using Delegation Print - VIP shared queues for user workflow description.

VIPQueue - As a User I want to print my documents in the way so that colleagues I select can release them on the printers (using Print roaming story).

Administrator shall be able to define group of users that can share print jobs with another users.
User shall be able to decide prior print whether the print job will be designated to secured (Print roaming or shared queue).
User shall be able to select users (from the SafeQ Identity Database) and add them to private shared queue.

Print roaming with print queue management and re-print must be configured.
Both YSoft SafeQ Client and respective print driver have to be installed locally on any workstation required for print sharing.
Print drivers must send print data to SafeQ server via SafeQ Client [see Workstation Client].

Shared print jobs are not available on "print all" user action of print queue management, but only on specific selection.
Shared queues are defined in the "current availability" mode. That means that whoever is eligible to access the shared queue can see all available print jobs, regardless of when and for whom these have been intended.
Released print job changes owner to person who released it and thus is being accounted to this person, not the originating author!
Delegation Print is supported on ORS server. However, it is not possible for users to manage list of privileged persons through ORS, or even to create the queue. To do so, users must either manage the list during printing using SafeQ client connected to CML or through dedicated web application available on http(s)://<safequrl>/client.jsp, where <safequrl> is the address of CML server. This must be done at least once for each user, to create the queue.
Delegation print shared queues have reserved name in form "shared_<username>". Avoid creating non-VIP shared queue with such name. If non-VIP shared queue with such name already exists and user tries to create VIP shared queue, this VIP shared queue will replace the old non-VIP one.
Document is removed from the Shared queue after it has been released to the printer.
Marking shared job as favorite is not supported at the moment.
If printing via ORS, this configuration value has to be Disabled: localJobsFilteringEnabled