RPM Copy to Queue Action

What it does

Copies the print job to another queue.


The copy to queue action was introduced in in RPM 5.0 to better develop the workflow capabilities. The paradigm we developed with transforms and actions worked for many situations, including broadcast printing, email and archive, and others.

We added this action with two processing scenarios in mind:

  1. Staged processing, where you would make some changes to the data, run some actions that use that format, then copy to another queue where you run more transforms. An example of this would be:
  2. Grouping like processing, where for instance you are sending print jobs to the same list of recipients. Why not just copy to a queue that does that? Then if the list ... or, when the list changes, you only have to change one action. That's a very simplistic example, of course.
  3. Dynamic job routing: you can now direct print jobs to queues using job data in RPM Elite.

You can find more examples of using the copy to queue action in the Actions Portal.

Copy queue action


  • Specific Queue: Use this setting to choose a queue from the list, rather than create one using current job data
    • Destination Select the queue where the print job should be copied. Every currently defined queue except the current queue will be added to the droplist.
    • Add Queue This lets you enter a queue name adhoc so you can copy to a queue you had not already created. This button will also provide you with the option to open a configuration window for the new queue right away.
  • Dynamic Queue: Use this setting to construct a queue name from data in the current print job
    • Variables: Select a job attribute to use in the template
    • Insert: Click this button to insert the current job attribute in the template mask, at the cursor position in the template mask
    • Template: Contains plain text you enter plus a string to specify a specific job attribute
    • Create queues that do not exist: Select this setting for RPM to create new queues; otherwise the job will error since the queue does not exist. 

The Dynamic Queue setting is the essence of dynamic job routing.

We recommend keeping the 'Create queues that do not exist' setting on so that you don't lose print jobs. You can drag the job into another queue more easily than recreating it at the origin.


Let's say you have two users who send print jobs to this queue. Let's call them Fred and Sally. Fred and Sally each have their own printer.

This is one way to approach this problem.

  1. Let's imagine you have queues defined in RPM named "print-fred" and "print-sally" which are each configured to print to the correct network printer.
  2. Select "Dynamic Queue"
  3. In the Template enter this text: print-
  4. In the Variables list, select "User"
  5. Click the Insert button

Now you can have Fred and Sally (and anyone else) send print jobs to this queue, where we find the Copy Queue action. Any job originating from the user "fred" will go to "print-fred", and the same with "sally".

For more information: