Ensure Batches are Committed on a Regular Basis - XML Tag Import Processor - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

XML Tag Import Processor

XML Tag Import Processor
Foundation 23.1

While documents are in the Awaiting Commit queue, they only exist in the first mass storage copy of the disk group. Consequently, if the mass storage copy has a drive failure and a backup is not available, the data is lost. Additionally, every system has a limit to the number of batches that can exist in the Awaiting Commit queue. Once this limit is met, no new processing is allowed. This limit is set during installation.

When documents are committed, data is copied to any secondary mass storage and removable copies assigned to the disk group. Each document is also updated in the database to modify its status as committed. Because of this, it is usually a good idea to commit during non-peak hours.

After a batch has been committed, it appears in the Committed queue. This queue maintains all of the TIP batches in OnBase. This queue will never “fill up”; it simply displays the status of the batches.

Once the batch has been committed, the batch cannot be purged. In order to delete the documents in the batch:

  1. Double-click on the batch to open it.
  2. Select the desired documents.
  3. Right-click and choose the Delete Selected option.

When viewing a batch in the Committed queue, there are several options that may be useful.