A-61635 December 2010
G-3
5. The update service will lock the setup which prevents other workstations
from modifying it while the upload is in progress. If the update service
cannot obtain a lock (another user is in the process of updating the setup)
a Data Conflict error will result. Remedies for this are the same as
described in Step 2.
6. If no data conflicts occur, the setup will be uploaded to the server which will
then increment the version for the specific setup files.
7. Other workstations will detect the more recent version(s) on the server and
download it.
Although changes are submitted from a client to the server when they are
made, downloading new setups from the server to the client occurs
periodically and is not event-driven. Therefore, a small delay will occur
between the time a new setup is created and the time it is replicated and
becomes visible on other workstations. It is recommended that at least 2
minutes be allowed for this process to occur. During this time, data conflicts
may persist but simply waiting for the update cycle to occur should bring things
back into synch and allow update operations to proceed. Following a data
conflict, it is recommended that users close out any setup windows and reopen
the setup after waiting to allow data refresh to occur.
Deleting and renaming
setups
Currently, setups cannot be deleted or renamed because it is impossible to
detect if other workstations in the NE workgroup have the setup in use. This
may be re-enabled in a future release of Capture Pro Software.
Centralized Batch
counters
The Remote Administration server supports a central batch counting facility,
both at a system level and job level.
These counters are shared throughout the NE workgroup. When a batch is
created, if a batch counter is included in the batch name formula, the NE client
will request the next counter from the RA server and it will be automatically
incremented.
Some changes have been made to the NE client to accommodate this. Since
the counter is global, users can no longer change batch counters when they
create a new batch. The batch name window will be “grayed out”. This implies
that jobs which include batch counters in batch name formulas cannot be used
in off line mode.
In Network Edition, no one can change the system-level batch counters. Job-
level batch counters can still be reset through the job setup; however use
caution when doing this to avoid batch name conflicts.
