PSIcapture Documentation: Shared Batch Update versus Local Batch Update process.


We have noticed that when you go to update a shared batch and instead of clicking the Begin Update Button you click Cancel (see screenshot), PSIcapture will loop through the list of batches and load and compress each one then close the update batch module.

When you do the same thing with local batches it will just close.

Is this correct behavior? When you have a lot of batches that were brought in to be updated and you cancel it loops through them all before closing.


This behavior is intended for the following reason: When they Select Batches to update, we check out Shared Batches so no one else can open them during the update process.  When they press Cancel, it runs thru the normal Check In process for each of the selected Batches (which includes the compress db process).

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.