2018.1

Workflow and all its services the same rights associated with the selected account (this is true
of all services with the exception of the PReS Workflow Messenger which always uses the
local system account). It is important to note that PReS Workflow and its services require
administrator rights to run on any given computer and that they must therefore be associated
with an account that has such rights.
When you are running the PReS Workflow Configuration program on a workstation, if it is
associated with an account that is different from your account, the following icon is displayed in
the lower right corner of the PReS Workflow Configuration program: . This is to draw your
attention to the fact that your PReS Workflow may have rights that differ from your rights, and
that this application and its services may therefore not be able to perform some of the actions
you can perform when you create or edit a given configuration.
The simplest thing to ensure that rights are the same across your whole network is to create an
administrator network account especially for PReS Workflow Tools. This will ensure that the
PReS Workflow and all its services have the same rights on all computers and that it is
therefore able to perform all the actions defined it needs to on every computer on your network.
A less permissive solution is to create an administrator local account for PReS Workflow and to
replicate it on each computer where PReS Workflow and its services are likely to perform
operations, such as get files, store files, or run applications and perform operations.
Local settings
Different users may create different printer queues. Let us say you have a big HP printer in your
office. User A creates a printer queue on his system called “Big HP” for that printer, and user B
creates one called “My printer” for the same printer. A configuration created on user A’s system
and then used on user B’s system would generate errors trying to print to the “Big HP” printer
queue.
Different users may also map network drives differently. Let us say this time that you have a
server in your office. User A maps that server’s main drive using drive letter “y:” while user B
maps it using drive letter “z:” A configuration created on one system and then used on the other
would both get and save the wrong files from the wrong drives. Note that such situations may
be avoided by using the Universal Naming Convention option.
User specificity
PReS Workflow configurations are not user specific as such. If you make sure that all the user
accounts have adequate network rights, that printer queues are defined the same way on all
systems, and that all network drives are mapped using the same drive letters (or that the UNC
Page 568