Skip to main content
Skip table of contents

Document Tracking

Contents

Tracked document flows are defined by assigning multiple workflow items and one workflow end at the corresponding component ports. All the documents that pass through the workflow items till the workflow end are logically grouped together as a single workflow and stored into the DB. Therefore each message send across a defined workflow is treated as a single workflow entry. A workflow entry can have multiple documents (one for each workflow item/end). The document contains the actual message that reaches the port (or a part of it, depending on the configuration).

The section below illustrates how to configure an external database for Document Tracking before starting to track.

Configuring Document Tracking

It is recommended using an external database for document tracking, which can be configured by providing the database configuration details in sbwdb.cfg file located in the Enterprise Server profile.

To configure document tracking, refer the Configuring SBW Database section.

Tracking in the Dashboard

To track data and manage the tracked data, log on to the Dashboard (Fiorano Web Console) and navigate to the Document Tracking tab on the left navigation panel.

For further information, please refer to the Document Tracking section in the Dashboard page.

Re-injecting a failed document

If a document fails in a workflow, it can be re-injected from the Document Tracking tab in the Dashboard.

Refer to the Re-injecting Failed Documents section which illustrates how to re-inject failed document(s).

Document Tracking in Event Processes

Document Tracking in Event Processes section explains how to assign document tracking to a workflow.

Deleting Document Tracking data 

To avoid issues such as Low Disk Space error, free some disk space by discarding old entries in the Document Tracking Database.

Refer the sections below:

In case of H2 database, SBW documents can be manually cleared by deleting the EnterpriseServers/{profile_name}/doctracking_db folder inside runtimedata directory. The server needs to be restarted after performing this action.

Please note that Fiorano recommends taking guidance from the Fiorano Technical Support Team before the manual intervention.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.