Configure Visibility reporting - Brainware for Transcripts - 24.1 - 24.1 - Ready - Brainware - external - Brainware/Brainware-for-Transcripts/24.1/Brainware-for-Transcripts-User-Guide/Configure-Brainware-for-Transcripts/Configure-Visibility/Configure-Visibility-reporting - 2024-10-28

Brainware for Transcripts User Guide

Platform
Brainware
Product
Brainware for Transcripts
Release
24.1
License

To configure Visibility reporting, complete the following steps.

  1. Open the <project>.ini file.
  2. Set the ConnectToReportingDB parameter to Yes.
  3. Set the SQLConnectionGroup parameter to the following.
    REP_OP_ConnectToReportingDB=Yes
    REP_VL_SQLConnectionGroup=01
    
  4. Intelligent Capture begins the reporting trail for each document upon the initial import of the document into the system, but if you want reporting to start sooner, such as at scan time, then set the REP_OP_StartNewRecordForImportedDocument parameter to No.
  5. Set the ConnectionString parameter to the following for each string connection, SQL_VL_01_ConnectionString, SQL_VL_02_ConnectionString, and so on.
    SQL_VL_01_ConnectionString=Provider=SQLOLEDB.1;Password=test;Persist Security Info=True;User ID=test;.initial Catalog=BFT;Data Source=W08-SERVER\SQLEXPRESS,1254
    If no SQL connection group is specified, the system always defaults to group 01. This applies to all SQL connection groups within the system.
  6. Set the IMP_VL_URN parameter to COMPONENT2.
  7. Set the REP_VL_ReportingKey parameter to URN.
  8. (Optional) If you want to use a specific naming convention for any Visibility reporting tables created in the databases, set the names of the tables using the following parameters.
    REP_VL_ReportingDBDocumentTable=BRWdocument
    REP_VL_ReportingDBFieldTable=BRWdistillerfields
    REP_VL_ReportingDBLineItemsTable=BRWdistillerLineItems
    REP_VL_ReportingDBLineItemsTable2=BRWdistillerLineItems2
    REP_VL_ReportingDBHistoryTable=BRWdocstatus
    REP_VL_ReportingDBImageTable=BRWDOCIMAGE
    
  9. (Optional) Information is not written to a database from any documents processed in the Designer module. However, you can have information written to a database from any document processed in the designer for testing and debugging purposes by setting the REP_OP_ReportingInDesigner parameter to Yes.
    In a production environment, this should always be set to No.
  10. (Optional) If you want to use the Visibility Reporting database to house an image of the document, set the REP_OP_StoreImageInReportingTables parameter to Yes. Only configure this parameter if you are using Brainware Visibility reporting for late archiving. In all other cases, to display the document image using Visibility, set the REP_VL_StorageDirectory parameter to the following.
    REP_VL_StorageDirectory=\\My Computer\Brainware Projects\Export
  11. (Optional) To retrieve a document stored within the Brainware Visibility tables using a URL, which is both stored against the record in the reporting database and is also available for export to a downstream system, set the REP_VL_ArchiveURL parameter to the following.
    REP_VL_ArchiveURL=http://archivesystem.brainware.com/Page.aspx?URN=XXXXX

    Where XXXXX is the point in the URL where the unique document identifier is inserted by the system to retrieve the image.