What is Symphony Profiler?

The Symphony Profiler add-on for Worldox® is part of Symphony Suite, The Complete Imaging Solution.  Symphony Profiler enables the user to quickly profile a stack of paper documents from their desktop using Symphony Profiler's pop-up "reservation" form.

Then that batch of documents can be handed to a clerical worker or intern to scan. The clerical worker does not need to know anything about Worldox or how the firm files its documents. In fact, once the filing reservations are made, the scanning and filing of documents is literally reduced to the push of one button.

This greatly reduces the time to get paper documents filed into Worldox while almost eliminating filing errors.

...

Symphony Profiler Architecture

• Symphony Profiler Workstation - Allows users to make file reservations.  Reservations are stored in the Worldox document repository
• Scans Folder - Documents scanned from any device and/or workstation are placed in one or more monitored scans folders
• Symphony Profiler Processor - Monitors scans folders for newly scanned files, fulfills reservations and saves the results back to the Worldox document repository

Where Does Symphony Profiler Get Installed?

Network Symphony Installation is the main installation for Symphony Profiler.  This is known as the *network* installation) gets installed onto a shared drive on your file server. The network Symphony installation consists of:

• Centralized configuration files
• Symphony Profiler Processor (the Symphony back-end processor) is installed to the local disk of a back-end workstation (typically the Worldox Indexer PC)
• Symphony Profiler Workstation (the Symphony end-user component) may be installed to the local disk of each workstation that will be making reservations, however it is accessible directly from the Worldox user interface.  Our recommended strategy is to utilize the embedded instance of Symphony Profiler from within Worldox.
  

 

...

Here are things to consider as you plan a Symphony Profiler deployment:

1. Which computer will run the Symphony Profiler Processor?  We recommend using the Indexer PC
2. Which Worldox user code should the Symphony Profiler Processor use?  Worldox security will be enforced, so choose a user code that has full access to all areas of the document repository (we usually recommend using the 00000 user code, but check to ensure that there are no security configurations blocking that user code)
3. We recommend that you configure the scanner(s) to place scanned documents into a dedicated Input Folder on the network.  For example, if your scanner supports creation of different scan profiles, create a scan profile on the scanner named 'Symphony' and have documents scanned with that profile get placed into a dedicated Symphony input folder.  You can use multiple folders if preferred
4. Does the scanner(s) automatically detect and remove blank pages when users scan mixed duplex and single-sided pages?  If not, Symphony Profiler can perform blank page removal
5. If you would like to utilize the firm's own SMTP Servers for the purpose of configuring the daily status notification e-mails, what is the SMTP (mail) server name and, if it requires authentication, the login name and password?  Alternatively, you may opt to use Symphony's email server (See Email Configuration for more information)
6. Which users should receive notification of issues with regards to reservations, and what are their e-mail addresses?
7. Have you configured the scanner to scan with a minimum of 300dpi?  Symphony Profiler can encounter problems reading the barcode of documents scanned with 200dpi or lower.
8. If you have a "Hole removal" feature, we recommend disabling that  as it can remove a portion of the barcode on the cover sheets.
   

...

The installation of Symphony Profiler consists of:

• Installing the main application package to a network drive
• Installing the Processor component to a back-end workstation or server (the Indexer PC works fine for this)
• (Optional) Installing the Workstation component to all workstations
• Performing a test scan

The procedure is straightforward and should take less than 15 minutes to complete.

Preparation

1. Ensure the computer to which you are installing Symphony Profiler meets the minimum system requirements
2. On the workstation to which you will be installing Symphony, launch Worldox as the user you intend to have Symphony Profiler run as (e.g., 000000) to ensure that Worldox has fully initialized that user code on this workstation (Note: Worldox does not need to remain running for Symphony Profiler to run - it simply needs to be launched once)
3. Ensure that a modern web browser and Adobe Reader (or Acrobat) are installed on the indexer PC (this is not strictly necessary, but it makes troubleshooting easier)
4. Complete the Symphony Profiler Site Survey with the client:  Symphony Profiler Site Survey

Install Symphony Profiler on the Network

1. Download and save the Symphony Profiler Setup file
2. Double click on the installer executable to run the Installation Wizard
3. Select "Next" on the first screen
4. Select the destination folder by clicking "Browse" - Important: this should be a location on a network drive - do NOT select a folder on the C: drive of the Indexer PC for the Network installation! 
5. Once the destination network folder is selected, click "Next"
6. If this is a brand new installation, you will be prompted that Symphony Profiler has not already been installed to this location.  Select "Yes" to continue with the installation.
7. Click "Install"
8. Upon completion of the installation, you will be prompted to Install the Symphony Profiler Processor.  Leave this option selected, and click "Finish" to begin installation of the back-end processor
9. Adjust security on the network SymphonyProfiler\Workstation\Shared folder so all users have full control permissions to that folders contents
10. Ensure that opportunistic locking and SMB2 have been disabled on your file server (reference our Disabling Opportunistic Locking and SMB2 article for details if you haven't already done this)

Note:  Installers can be downloaded from the Channel Partner Resource Center - Implementation Resources page

Install Symphony Profiler Processor

You will be prompted to run the Symphony Profiler Processor installation immediately upon completion of installing Symphony Profiler. This installs the Processor to the local disk of the computer.

1. From the "Symphony Profiler Processor Setup" window, select "Next"
2. Leave the default destination folder as is, and select "Next". Note: This installation will be on the local disk of the computer.
3. Determine if you'd like to run Symphony Profiler Processor as a Service or as a Logged in user and select the appropriate radio button.
   
   1. If you choose to run Symphony Profiler Processor as a Service, you will be prompted to add a Password, please do so, and select "Next"
   2. If you choose to run Symphony Profiler Processor as a Logged in use, select "Next"
      
4. Leave the "Start Symphony Profiler Processor" check box checked, and select "Finish"
5. When the Symphony Profiler Processor application launches, you will be prompted to input the license number. Enter the value provided by Trumpet
6. Check any software Firewall on the Processor workstation and confirm that it is allowing Symphony Profiler Processor to listen to inbound connections
   (see: Disable the Firewall on the Indexer PC for details on configuring Windows Firewall, and the problems that can occur if the firewall is not configured properly).
7. Click "OK"

 The Symphony Profiler Processor should now be running, and is ready to be configured.

Configure Symphony Profiler Processor

Now that the Processor has been installed on the indexer workstation, it can be configured for your specific environment. 

Configuration is performed in the Edit > Preferences dialog of the Symphony Profiler Processor. Here are the minimum settings you should review during your installation:

1. E-mail — this allows the Symphony Profiler Processor to send notification and status e-mails
1. Enter e-mail configuration information
2. Use the "Send Test Message" button to ensure that you receive the test e-mail
   Tip: For more information, visit E-Mail Configuration
2. Worldox — 
   1. Provide the Worldox user code that Symphony Profiler Processor should run as. This user must have full access to the areas of the repository that you wish to make reservations in. Click the "Refresh" button and confirm that you see the profile groups you want to have monitored
   2. Enter the path for the Worldox application in the Worldox Network Folder. 
      NOTE:  If you are running Symphony Profiler Processor as a Service, then you must enter the UNC path of the Worldox installation in the field
      
   3. Determine if you would like to add the Symphony menu and buttons to Worldox.  If so, check the check box (highly recommended), the alternative is to install a local workstation component for each user.  For more information on the Symphony Menu versus workstation component visit  Symphony Profiler Workstation Installation Instructions
3. Monitored folders — Add each of the folders you wish the Symphony Profiler Processor to monitor - leave the other settings for each folder as their defaults
4. Image Processing — If the scanner(s) does not automatically perform blank page removal when scanning mixed duplex/simplex documents, set the drop down to 'Remove all blank pages.' Leave the other settings at their default values

Testing your Installation

Perform the following steps to test your installation of Symphony Profiler:

1. Create 2 cover sheets. Follow the "Creating Cover Sheets" instructions in the Symphony Profiler User and Administration Guide (found in the Achieving Implementation Success guide)
2. Create 2 reservations. Follow the "Creating Reservations" instructions in the Symphony Profiler User and Administration Guide
3. Perform a single scan operation to fulfill the 2 reservations.  Follow the "Fulfilling Reservations" instructions in the Symphony Profiler User and Administration Guide
4. Monitor the Symphony Profiler Processor to confirm that the reservations are fulfilled. Follow the "Symphony Profiler Processor User Interface" instructions in the Symphony Profiler User and Administration Guide.  Or, show the history of the reservations in the Symphony Profiler Workstation application following the "Operator's Historical Information" instructions in the Symphony Profiler User and Administration Guide

Tip: If you do not have a scanner available, there is a sample scanned document at Server\SampleCoversAndDocuments.pdf – you can make reservations for the following reservation IDs (HNWR7 AEHF7 KK4C4 CC3NX), then drop this test file into the Server\Input folder.

...

These instructions provide a more detailed look at the Symphony Profiler e-mail configuration settings, which are available by navigating to Edit > Preferences > Email in the Symphony Profiler Processor.  You can opt to either use Symphony's servers for sending email notifications, or you can opt to use the client's SMTP servers.

Option 1: Configuring Symphony Profiler to send Daily Status Notifications using Symphony's Servers

By default when you install Symphony Profiler Processor, it will be configured to use Trumpet's Email servers

If you wish to use this method:

1. Complete the "Send Notifications to" field with the email address of the person(s) you would like to receive Symphony Profiler status and error e-mails (to specify multiple e-mail addresses, separate each address with a comma)
   Tip: This e-mail is sent daily, and should be delivered to a user who will actually review it.
2. Ensure that the "Deliver notifications via" field's drop down is set to "Symphony's servers"
3. Select  the "Send Test E-mail"
4. Confirm that the test was sent and that the user(s) received the test e-mail

Note:  Emails will come from donotreply@symphonysuite.com so you'll want to ensure that you add that email address to your spam filter's whitelist.

 

Option 2: Configuring Symphony Profiler to send Daily Status Notifications using your SMTP Server

If you wish to use this method:

1. Complete the "Send Notifications to" field with the email address of the person(s) you would like to receive Symphony Profiler status and error e-mails (to specify multiple e-mail addresses, separate each address with a comma) 
   Tip: This e-mail is sent daily, and should be delivered to a user who will actually review it.
2. Ensure that the "Deliver notifications via" field's drop down is set to "Your mail server"
3. In the "From Address" field, complete the e-mail address information for the e-mail address you would like to have the Symphony Profiler e-mails come "from" (we typically recommend symphony@yourfirm.com, where "your firm" represents the domain name for your firm
4. In the SMTP server name field, specify the name of the SMTP server
5. If the server requires SMTP authentication, click the checkbox, select the appropriate authentication type from the drop down arrow and complete the login name and password
6. Select  the "Send Test E-mail"
7. Confirm that the test was sent and that the user(s) received the test e-mail

Troubleshooting Tips: You may need to configure your Exchange server to support SMTP.  In some cases, Exchange will configure itself to be very restrictive with which IP addresses it will allow incoming SMTP connections to come from, and you will need to adjust that list to include the IP address of the PC that the Symphony Profiler Processor will run from.

...

This tab is pretty self-explanatory - Upon installation, enter your Symphony Profiler License in the space provided and click 'OK'.

Starting with version 1.7.28, Symphony Profiler will have an 'Automatic License Update' feature.  Basically, after you've paid your yearly invoice with Trumpet, a new license is automatically generated.  So if your installation has access to the Trumpet servers, Symphony Profiler will see this new license, download and install.

Note:  Symphony will check for a new license once every 3 days under normal circumstances, and once per day when your license is within 30 days of expiring.

If you've paid your invoice (and received notification of a new license) and don't want to wait for the automatic update to kick in, you can click the 'Check for Latest License' button on this page.  This will manually trigger Symphony Profiler to retrieve the updated license from Trumpet's servers.  As mentioned, all of this assumes your installation has access to Trumpet's servers.  If a connection cannot be established, you can always copy/paste your new license into this screen.

When you receive notification from Trumpet that your new license is generated, it is still highly recommended that you A) update your installation to the latest version of the software, and B) verify your license has been updated.

 

...

These instructions provide a more detailed look at the Symphony Profiler Worldox configuration settings, which are available by navigating to Edit > Preferences in the Symphony Profiler Processor.

1.  Confirm that the Worldox User Code listed in the User ID section is the one you would like the Symphony Profiler Processor to use

Tip: Symphony Profiler will only process areas of Worldox that it has read/write access to.  For this reason, we recommend (but do not require) that you configure this user as a 'Manager' user in Worldox.  If you use ethical walls, be sure that the user you select has access to all areas of your document repository

2.  Enter the path for the Worldox application in the Worldox Network Folder.  NOTE:  If you are running Symphony Profiler Processor as a Service, then you must enter the UNC path of the Worldox installation in the field

3.  Select "Refresh List" (this will tell you which Profile Groups that user has access to)

4.  Determine if you would like to add the Symphony menu and buttons to Worldox (recommended).  If so, check the check box.  For more information on the Symphony Menu, visit  Symphony Profiler Workstation Installation Instructions

 

...

The Monitored Folder(s) is the folder(s) that the Symphony Profiler Processor monitors for scanned documents that should be matched up to a Symphony reservation.

Note: We recommend that you configure the scanner(s) to place scanned documents into a dedicated Symphony input Folder on the network.  For example, if your scanner supports creation of different scan profiles, create a scan profile on the scanner named 'Symphony' and have documents scanned with that profile placed into a dedicated Symphony input folder.  You can use multiple folders if preferred.  Visit the FAQs section for instructions on configuring dedicated scan paths for certain scanners.

When running Symphony as a service make sure to use the UNC path.

These instructions provide a more detailed look at the Symphony Profiler Monitored Folder configuration settings, which are available by navigating to Edit > Preferences in the Symphony Profiler Processor.

1. By default, the Symphony Profiler Processor configures a single Input folder in its network installation location.  If additional folders need to be added, select "Add"
2. In the "Folder" field, select the ellipses (...) button and browse to the folder on your network that Symphony Profiler should monitor
3. Leave the "Reservation ID regular expression" field as is
   Tip: This is an advanced configuration option that can be used to process the input filenames in certain ways.  It is unlikely that you will need to change this, especially if you are using Symphony Profiler cover sheets.
4. Click "OK"
5. Repeat for any additional folders that need to be added
6. Remove any folders that should not be monitored by selecting them and clicking "Remove"

...

These instructions provide a more detailed look at the Symphony Profiler Image Processing configuration settings, all of which are available by navigating to Edit > Preferences in the Symphony Profiler Processor.

The Symphony Profiler Processor can identify and remove blank pages from your scanned documents.  Many scanners already have this capability, in which case we recommend that you let the scanner do the work of removing blank pages.  If you have a scanner that does not do this, and you are going to be scanning double sided, here is how to configure the Processor to remove pages:

• Leave "Threshold" at the default

Tip: This threshold defines how sensitive the blank page detection algorithm is.  The higher the number, the less sensitive it is.  The default value should be fine for most cases, but if the scanner is dirty, or you are seeing some 'bleed through' of content from the front side, you may need to increase this number.  At this point, we recommend you provide Trumpet with a document containing any blank pages that were not correctly identified, and we will analyze it and provide a recommended threshold level.

• Leave Required block count set at the default

Tip: The block count also defines how sensitive the blank page detection algorithm is.  The lower the block count, the more sensitive the processor will be to remove blank pages.  For example, if the Required Block Count is set to 1 Symphony Profiler is more likely to treat a page as non-blank than if the Required Block Count is set to 8.   At this point, we recommend you provide Trumpet with a document containing any blank pages that were not correctly identified, and we will analyze it and provide a recommended Block Count.

• Determine what Symphony Profiler should do with blank pages

• Leave blank pages alone:  If a file contains blank pages (e.g. when scanning duplex), all blank pages in the document will remain.  This is the default setting, and is recommended unless the scanner does not provide blank page removal
• Remove blank page following cover:  Symphony Profiler will remove blank pages only following the cover page when scanning duplex
• Remove all blank pages:  This will remove all blank pages including the one immediately after the cover and any others that are blank

...

By default, Symphony Profiler will install the workstation component to the Worldox menu and button bar of all users.  Using the Symphony Imaging menu in the Worldox interface allows users to do most things directly from Worldox.

Note:  If you would rather revert to the 'legacy' method of installing the workstation component to each machine individually, the steps are listed below.  And if you would like to move away from the 'legacy' method and use the new Worldox integrated method, you can un-install the Symphony Profiler workstation component from each machine and begin using the integrated menu/button.  One big advantage of using the new method is that nothing has to be touched on the workstation when installing a Symphony Profiler update. 

Note:  If you don't see the Symphony menu/button automatically when the feature is enabled (the default setting), the resolution takes about 5 seconds, and only needs to be done once on the workstation - How to Add the 'Create Reservations' button to Worldox.

The Symphony Imaging menu provides users with most of the functionality as you would have if you installed the Symphony Profiler Workstation.  The major differences: 

1. If the user requires Background File Transfer, they must choose to "Start Scans Transfer"
2. Users are unable to view Processor Status from the Symphony Imaging window.
3. As mentioned above, when utilizing the Symphony Imaging menu, users will not be prompted to install / update to latest code which can be great for folks with locked down systems.

You can certainly opt to have most users take advantage of the Symphony Imaging menu and have select folks utilize the full Workstation installation.

Symphony Imaging Menu Installation

In the Symphony Profiler Processor, navigate to Edit -> Preferences -> Worldox, and check the 'Add Symphony menu and button to Worldox'

Symphony Workstation Installation

These instructions apply to both regular Workstation and Terminal Server installations:

1. Navigate to X:\SymphonyProfiler\Workstation\Mirror\ (Where "X" is the network location to which Symphony is installed)
   Note: for some firms, the folder location may be X:\Trumpet\ExpressProfile\Workstation\Mirror
2. Double click on the Workstation Setup executable in that folder
3. From the "Symphony Profiler Workstation Setup" window, select "Next"
4. Leave the default destination folder as is, and click "Install"
5. Leave the "Start Symphony Profiler Workstation" check box checked, and select "Finish"
6. The Symphony Profiler icon should now be in the system tray

These instructions should be followed on all workstations that will use Symphony Profiler.

IMPORTANT! Ensure that all scanners in the firm are configured to scan at a minimum of 300dpi.  Documents scanned with 200dpi or lower do not produce a clear enough barcode for Symphony Profiler to read.

Silent Mode Installations

If you wish to deploy Symphony Profiler Workstation using a batch deployment system, the Workstation installer can be run in silent mode - please refer to the Installing Symphony Profiler Workstation in Silent Mode article for details.

...

Note: If you are migrating to new hardware see Moving Symphony Profiler Processor to New Hardware for instructions.

 

To uninstall Symphony Profiler Processor (in the event you are moving to a new indexer pc, etc)

Use

1. Control Panel, Programs and Features
2. Select Symphony Profiler Processor
3. Click Uninstall

or

1. Navigate to C:\Program Files\Trumpet\SymphonyProfilerProcessor
2. Select "Uninstall.exe"
3. When the Uninstall wizard opens, select "Uninstall"

 

...

The following resources will also be of use for getting up to speed quickly:

• Symphony Profiler Quick Start Sheet
  
• Symphony Profiler Quick Start Video

...

Before you can begin making reservations, you'll need to create some cover sheets.

Cover sheets are used to associate your document with a completed Worldox index card.

Here's how:

• Right-click on the Symphony Profiler Workstation icon in the system tray and choose "Create Covers"
  
     

Tip:  IF you have Symphony Profiler Workstation installed, you can also right-click on the Symphony icon in the system tray by your close and choose "Create Cover Sheets"

• Enter the number of cover sheets you'd like to create (cover sheets can be reused)
  

• Click "OK"

• A PDF file containing the cover sheets will display in your web browser
  
• Print this PDF

NOTE: We encourage you to print the cover sheets on pastel yellow paper so that it's easy to reuse them (do not print them on dark shades of paper). These cover sheets are not user-specific, so any other user in the firm can also make reservations with these cover sheets.

TIP: For regular use, print enough for the user to use between scanning sessions. It's also really simple for the user to create new covers when they need them, but that may involve a walk to the printer, so it's best to do it in batches.

...

Before you can begin making reservations, you'll need to create some cover sheets.

Cover sheets are used to associate your document with a completed Worldox index card.

Here's how:

• Select the Symphony Imaging menu in Worldox and choose "Create Covers"
  
• In the Cover Sheet request window you will be presented with two options: 
  1) to be emailed a link for generating cover sheets
  2) copy and paste the URL for generating cover sheets to your clipboard.

Option 1 - Email

1. If you would like to be emailed, select "Email instructions for generating cover sheets to:" and enter your email address in the corresponding field
   
2. You will receive an email that looks like this:
   
   
   Select the "Click to Generate Cover Sheets" link
3. Input the number of cover sheets you wish to create and select "Create Cover Sheets"
   
   
4. A PDF file containing the cover sheets will open
5. Print the PDF

NOTE:  You may also wish to bookmark this page for future use to skip the email step.

Option 2 - Web Browser Directly

1. If you would like to copy and past the URL directly into your web browser, select the "Copy the cover sheet creation address to the clipboard so I can paste it into my web browser" radio button
   
2. In your web browser's address window, select Ctrl+V to paste the creation address
3. Input the number of cover sheets you wish to create and select "Create Cover Sheets"
4. A PDF file containing the cover sheets will open
5. Print the PDF

NOTE:  You may also wish to bookmark this page for future use to skip Copy and Paste step.

NOTE: We encourage you to print the cover sheets on pastel yellow paper so that it's easy to reuse them (do not print them on dark shades of paper). These cover sheets are not user-specific, so any other user in the firm can also make reservations with these cover sheets.

TIP: For regular use, print enough for the user to use between scanning sessions. It's also really simple for the user to create new covers when they need them, but that may involve a walk to the printer, so it's best to do it in batches.

 

 

...

IMPORTANT: The exact detail of this process is actually important to avoid problems caused by users scanning a cover sheet without ever having filled in an index card. Please emphasize to the user that they should NOT pick up the cover sheet until after they type the reservation ID into the Reservation ID dialog.

Create Reservations by Typing Reservation ID (most common)

Now that you have cover sheets available to you, it's time to create a reservation:

• Ensure that Worldox is running
• Ensure that you have a stack of cover sheets available. Place them on one side of your keyboard
• Place the stack of documents for which you wish to create reservations on the other side of the keyboard
• Double click on the Symphony Profiler Icon in Worldox (or double click on the Symphony Profiler icon in your system tray)
• The Worldox – Create Reservation window will open
•  Complete the Worldox profile for the first document and click "OK"
• The Symphony Profiler Reservation ID window will open
• Type in the Reservation ID from the first sheet in your stack of cover sheets

NOTE: If you type in an invalid reservation ID, Symphony Profiler will prompt you that the ID is not valid.

 

• Place the cover sheet on top of the document immediately and set the package to the side

• Once you have entered the Reservation you will be given three options:

• Another Similar (Alt+S) – This option will open the Worldox – Create Reservation window with the information from your last save pre-filled. You can change any information necessary and select "OK"
• Another (Alt+A) – This option will open the Worldox – Create Reservation window which you can then fill in
• OK (Alt+O) – Select this option if you are finished creating reservations

You have now successfully created a Worldox filing reservation!

Create Reservations with Handheld Barcode Scanner

If you are doing a lot of back scanning you can optional use a handheld barcode scanner (like this one:  Barcode Scanner) to input the Reservation IDs. 

Here are the steps you'll follow:

• Ensure that Worldox is running
• Ensure that you have a stack of cover sheets available. Place them on one side of your keyboard
• Place the stack of documents for which you wish to create reservations on the other side of the keyboard
• Double click on the Symphony Profiler Icon in Worldox (or double click on the Symphony Profiler icon in your system tray)
• The Worldox – Create Reservation window will open
•  Complete the Worldox profile for the first document and click "OK"
• The Symphony Profiler Reservation ID window will open
• Scan the barcode on the cover sheet with the handheld barcode scanner
• Place the cover sheet on top of the document immediately and set the package to the side
• Lather, rinse, repeat until you're finished with your stack of documents.

Note: this works great when your scanning mass quantities of documents.  If you're only creating a few reservations at a time, it may be more efficient for you to type in the Reservation IDs.

...

IMPORTANT:  We strongly recommend that you purchase a scanner that detects misfeeds rather than specifying the page count.  If you as a user miscount the pages, but the scanner does not misfeed, your Administrator will receive an Urgent Notification Email.

If you wish to ensure that the page counts of the scanned document match the physical page count, when creating your reservation,

• Select the Advanced bar
  
• Select the "Check Page Count" check box
  
• Count the pages (not including the cover sheet) and enter that number in the field provided. If you are scanning double sided, enter the total number of sheets you expect to have in the final document. This ensures that there are no issues with scanner mis-feeds, etc. If the page count is not identical, the Symphony Profiler Administrator will receive a notification email.

...

If you wish to notify a particular individual that a document reservation has been fulfilled, you can send them an email notification.

• Select the Advanced bar in the Symphony Profiler Reservation window
  
• Select the "Send Email To" check box:
  
• Enter the email address of the person you wish to receive notification when the reservation has been fulfilled
• Enter the Subject line for the email.
• Select one of the options "Another Similar", "Another" or "OK" to complete your reservation.
  Note:  You will not be allowed to complete the reservation unless both the email address and subject line have been completed.

Upon fulfillment of the reservation, the user you indicated should receive notification that the reservation has been fulfilled will receive an email that includes a link to open the document, and the full path to the document in the Worldox Document Repository.

 

...

To fulfill your reservations, simply scan all of the documents (including the cover sheets) as one bulk scan operation. Save to one of the Symphony Profiler monitored folders. This can be done in a single scan operation, and there is no need to name the file in any particular manner.

Note:   If you re-scan a document within one hour of its original scan, and an additional reservation has not been made for that Reservation ID in that time, Symphony Profiler Processor will create a new version of the original document and re-fulfill the reservation.  This allows you an hour to re-scan a document if the scanner misfeeds, etc.

...

You can check the status of any reservations that *you* have made using the "Favorite Files" button in Worldox. Use the "Just These" button next to the Symphony Profiler filter option, and it will show you both unfulfilled and recently fulfilled reservations. It follows the same rules as the other Worldox favorite matters, which means you should see about 30 days worth of history.

Note: This is workstation-specific, so it will only show reservations for that user.

To check on a reservation made by a different user, you'll need to refer to the Symphony Profiler Processor.  See Checking on Reservation Fulfillment for more details.

Another way of checking is to use the Show History menu from the Symphony Profiler icon in your system tray. Note that this method is an older feature that is no longer supported by our development team.

•  From Worldox, select "Symphony Imaging -> Show History"
  
• This will launch the recent history of the workstation
  
  

Tip:  If you have Symphony Profiler Workstation installed, you can also right click on the Symphony Icon in the system tray by your clock and choose "Show History"

Note: Both of those methods are workstation-specific, so it will only show reservations for that user

To check on a reservation made by a different user, you'll need to refer to the Symphony Profiler Processor.  See Checking on Reservation Fulfillment for more details.

...

You can find a reservation in Worldox in a number of ways. 

To Find Reservations that you have created:

• Use your Worldox Favorites > SymphonyProfiler favorites list to retrieve recent reservations you have made
  
  

To Find reservations that anyone may have created:

• Search Worldox for all reservations by typing the following into the location bar: *.xpf
• From the Symphony Profiler Processor interface, double click on an entry in the Unfulfilled Reservations list.  This will open Worldox with the reservation selected

...

Editing the Worldox Profile Information

If you need to edit the index card associated with the reservation (e.g., change its doctype or description), locate the reservation in Worldox (see Finding a Reservation) and perform an Edit > Profile operation, just like you would any other document.

Editing the Reservation Page Count

If you have provided a page count with the reservation and need to edit it, locate the reservation in Worldox (see Finding a Reservation) and double click on it. This will open the reservation and allow you to edit it.

...

If you need to delete a reservation, locate the reservation in Worldox (see Finding a Reservation) and delete it, just like you would any other document.

...

Each night, Symphony Profiler Processor will send your Symphony Administrator a Daily Status email.  If you are not the Symphony Administrator for your firm, but still wish to check the status of the processor, you can do so you will need to have Symphony Profiler Workstation installed.   Here's how to check on the reservations:

• Right click on the Symphony Profiler icon in the system tray by your clock.
• Select "Show Processor Status"
  

This will open a web browser window that contains the Profiler System / Reservation Status.

Note:  This functionality is not available when running Symphony Profiler embedded from within Worldox.

...

Background

Worldox Cloud users have the challenge of scanning to a location on their local network, and getting the files into the Worldox Cloud. Symphony Profiler provides an excellent solution for this scenario, combining the power of pre-profiling with a powerful background file transfer feature.

How It Works

The background transfer is quite intelligent. Features include:

• Delayed transfer will let the file age 30 seconds prior to moving it to ensure the file is fully created before obtaining an exclusive lock on the file and then beginning the transfer.
  
• Bandwidth throttling (though in practice we don't find this is necessary in most cases). You can watch the file transfer progress in the BFT window.
  
• Automatic restart (if the user terminates their remote desktop connection half way through a transfer, it will pick up again as soon as the user re-connects)
• File transfer happens inside the secure channel of the remote desktop session itself, so there is very little special configuration required (the user does have to enabled sharing of their local disks in the remote desktop session)
• No software installation required on the remote PC (other than whatever scanning software the user wishes to use)

Here's a typical use-case:

1. User Verifies the background file transfer is running: Enable the background file transfer by selecting "Symphony Imaging > Enable Background Transfer"
   
2. User makes reservation in Worldox Cloud
3. User places the cover sheet on the physical paper
4. User repeats the process, accumulating a to-be-scanned stack
5. User scans the stack on their local scanner and saves the results to a standard location on their local C drive and / or can also scan to a network drive on their local servers
6. The Symphony Profiler background file transfer mechanism reaches through the Worldox Cloud, and pulls the file from the local scans folder or the network drive.  The file is then placed in one of the Symphony Profiler monitored folders on the Worldox Cloud

Configuration

Configuration is made in the settings of the user's Symphony Profiler Workstation instance running inside the remote desktop session.

• Select Symphony Imaging > Open\Start Scans Transfer from the Worldox menu (or right-click on your Symphony Profiler system tray icon and select Background Transfer).  This starts the scans transfer.
• Select Symphony Imaging > Open\Start Scans Transfer from the Worldox menu again in order to view / configure the locations
• Check the 'Enable...' checkbox
• In the From field, specify the source folder (this will be a TSCLIENT\ based path) on the hard drive of the user's remote PC      
  • It will be formatted like this: \\tsclient\C\users\yourname\Documents\SymphonyScans
    
  • If this is not being used in a Cloud installation then a direct path name is used (ie: C:\users\yourname\....)
  • Note: This field does not support UNC paths
    
• The To field will already contain the Symphony Profiler Processor's monitored Folder, so no need to change that
  

Below is an example of what it should look like. In short: if you're a Cloud user who needs to configure this, copy the path of your folder location and insert \\tsclient\ before the drive letter, then remove the colon ":" from after your drive letter. You should be set! You'll notice that the "Resume" button will be enabled once you've identified a valid path.

Use

1. Scan your documents into the folder designated in your "From" field
   Note: ANY document put into that folder will be moved into the Cloud
2. Enable the background file transfer by selecting "Symphony Imaging > Enable Background Transfer"
3. Once you select that option from the Worldox menu, the software will automatically begin the background transfer of files, if you'd like to see progress of the transfer, you can select "Symphony Imaging-> Open\Start Scans Transfer" to see the progress
   
4. If you happen to be looking at your source folder then you will see your files disappear as they are transferred to the Cloud
   

Note: If there is an issue connecting to the Cloud, background file transfer problems are reported via system tray notification (a pop up).

If the From or To folder for background file transfer are not available, the Symphony Profiler Workstation will retry up to 30 seconds before showing a warning.  After the warning is shown, it will wait for the polling delay (60 seconds by default), then try again repeatedly.

Important Safety Tip

Symphony's background transfer process is essentially piggy-backing on the WDSaaS connection.  Which means that if you close or restart Worldox Cloud, it's severing the connection to the server.  So any time you restart Worldox, you'll need to restart the background file transfer as well. 

...

The Symphony Profiler Processor contains four quadrants:

• The upper left quadrant shows which reservations have not yet been fulfilled
• The upper right quadrant shows which files have been saved to the monitored folder(s) but do not match to a reservation ID
• The lower left quadrant shows the recently fulfilled reservations that Symphony Profiler has processed
• The lower right quadrant shows a log of activity the Processor has performed recently

Tip: Double clicking on entries in any of the lists will display the reservation and/or file.

...

The following is a representation of the steps that the Symphony Profiler Processor uses to fulfill reservations.

...

Monday through Friday, the person(s) identified in the Symphony Profiler Processor Email Settings should receive an email with a status of all pending reservations, unprocessed files, or other alerts.

IMPORTANT: If you do not receive the daily email, check the Symphony Profiler Processor immediately.

Here's what the email will look like:

In this example, there were two files scanned that didn't have reservations (the Unprocessed Input Files) and a number of reservations that haven't yet been fulfilled. As reservations get older, they will switch from green to yellow to red.

Note: Unprocessed Input Files less than five days old will have a green status, less than ten days (but older than five) will be yellow and anything ten days or older will have a red status.

Tip: See Daily Status Email Troubleshooting Process to determine how to resolve these issues.

...

If the "Check page count" option was selected when creating a reservation and your page counts do not match, the person(s) receiving the daily status emails will immediately receive an email indicating that there was a problem.

...

To ensure that the Symphony Reservation Status emails are meaningful, it is important that you have a dedicated path for documents that should be saved through Symphony to Worldox. 

Symphony considers an unprocessed input file as an error, and will send alert emails to the firm's Symphony administrator.  If the firm saves non-Symphony documents to the folders that Symphony monitors, it becomes very difficult for the user to determine when there actually is an error condition.

Therefore, we strongly recommend that you configure all network scanners so users scan Symphony related documents to a dedicated scan path.  This path should be accessible by the workstation that is running the Symphony Profiler Processor. 

In addition, you will configure all network scanners so users scan non-Symphony related documents to another target.  This path does not need to be accessible by the workstation that is running the Symphony Profiler Processor.

 

IMPORTANT! Ensure that all scanners in the firm are configured to scan at a minimum of 300dpi.  Documents scanned with 200dpi or lower do not produce a clear enough barcode for Symphony Profiler to read.

...

There are two methods for an administrator to check reservation fulfillment in Symphony Profiler.

Method #1: Consult the Symphony Profiler Processor

1. Open the Symphony Profiler Processor (this is typically installed on the Indexer PC)

2. Consult the upper-left quadrant of the interface

This will show all of the unfulfilled reservations for the firm.

Method #2: Search Worldox for .xpf Files

1. In Worldox, locate the "location bar"

2. To for just a specific file format use * and the format type (xpf)

3. From the results, find the reservation that contains the description matching what you entered.

 

...

If configured properly, you should be receiving Daily Status e-mails from Symphony Profiler.  However, if you would like to check on the status more immediately, and without logging into the indexer PC, you can obtain a Symphony Profiler status update at any time by doing the following:

• Right-click on the Symphony Profiler icon in the System Tray
• Select "Show Processor Status"
  

If the Symphony Profiler Processor isn't running, you will see an error message as follows:

This is a great indication that the workstation running the Symphony Profiler Processor (typically the Indexer workstation) has been logged off, or that the Symphony Profiler Processor software has been shut down.

If the Processor is running, a browser window will open giving you the status of the Processor:

Any unfullfilled reservations, etc., will show in this window just as you would see them in your Daily Status e-mail.

...

Background

If users wish to create reservations for scanned documents that should be restricted from other users, they can take advantage of Worldox's security features to do so - both Ethical Walls and file level security classifications are supported.  When the reservation is fulfilled, the security of the scanned document will be the same as that originally assigned to the reservation.

The only caveat is that you must configure the security so Symphony Profiler can modify the document.  Recall that Symphony interacts with Worldox as a regular Worldox user (normally 000000, but this can be configured in preferences).  This article describes how to configure Worldox security to ensure that the Symphony user will be able to actually fulfill reservations.

If you do not do this configuration, the reservation will not be fulfilled, and you will see the following errors in the logs (Document for reservation xxxxx can not be written to):

Configuration for Ethical Walls

In the ethical wall configuration, be sure that you have added the Symphony Worldox user (usually 000000) to the users list for the ethical wall, and that you have configured that user to have full access to documents covered by the ethical wall.

Configuration for Security Classifications

When users classify individual documents, they need to make sure that they include the Symphony Worldox user (usually 000000) in the classification and give full access to that user.  To make this easier, we suggest creating the following two security classifications (this is done from WDAdmin, Security->Classifications):

• <Private - for Symphony documents>
• <Read Only - for Symphony documents>

First, create the <Private - Symphony documents> classification:

1. WDAdmin, Security->Classifications
2. Click New
3. Ensure that the <Everyone Else> group has NO rights assigned  (this is the default)
4. Click Add User
5. Choose the Symphony Worldox user (usually 000000)
6. Ensure that the Symphony Worldox user has full rights
7. Click OK
8. You will be prompted for a classification name and Who Sees It
9. Set the name to:  <Private - Symphony documents>
10. Set the Who sees it to: Everyone
11. Click OK

Now create the <Read Only - Symphony documents> classification:

1. WDAdmin, Security->Classifications
2. Click New
3. Configure the <Everyone Else> group so it has Find and Read rights assigned
4. Click Add User
5. Choose the Symphony Worldox user (usually 000000)
6. Ensure that the Symphony Worldox user has full rights
7. Click OK
8. You will be prompted for a classification name and Who Sees It
9. Set the name to:  <Read Only - Symphony documents>
10. Set the Who sees it to: Everyone
11. Click OK

 

When the user is creating a reservation, they can now choose one of those classifications to ensure that the reservation will be secured AND that Symphony Profiler will be able to fulfill it.

...

In the event you should need to remove the Symphony Profiler Processor, the steps to do so are below. Note— if you're looking to migrate Symphony Profiler to another workstation, the instructions to do so can be found here: Moving Symphony Profiler Processor to New Hardware

Navigate to the installation folder.  You can find this easily by right-clicking the Symphony Profiler Processor shortcut found on the desktop of the Indexer PC and selecting 'Open file location':

From within the installation folder, run the Uninstall.exe application.

When the uninstaller launches, simply click 'Uninstall', wait for it to complete and then hit 'Finish'.

  

Symphony Profiler Processor will then be uninstalled.

...

Background

As you may already know, Symphony Profiler uses the unique Reservation ID from your scanned cover sheet to identify which reservation your scan belongs to. In order to do this, Symphony must be able to "read" the text on the cover sheet. Scanners can be pretty helpful when it comes to 'cleaning' up a scan, but sometimes those efforts result in hidden layers of data that can blind Symphony. If your scanner is doing something to the image that causes it to be unreadable by Symphony then this tool will allow us to quickly see that.

This tool is specifically designed to aid in troubleshooting, especially by our Support team. So, if you are having issues, remember to reach out for help!

How to Use

In the "Scanned Files from Monitored Folders" quadrant in the Symphony Profiler Processor interface left-click to highlight a file, then right-click and select "View Image..."

If the resultant image is very different from the scanned PDF (as viewed in Acrobat or Reader) then it's best to let Trumpet know so our development can investigate the processor algorithms and enhance them to work with the image.

...

This section deals primarily with Terminal Server implementations - if you have other uses for it, please let us know!

Background

Remote users of Terminal Server installations often have a challenge scanning from a local scanner, and getting the files into the remote session. This is especially true of ad-hoc remote sessions (like a single user working from home on the weekend).

Symphony Profiler provides an excellent solution for this scenario, combining the power of pre-profiling with a powerful background file transfer feature.

How It Works

The background transfer is quite intelligent. Features include:

• bandwidth throttling (though in practice we don't find this is necessary in most cases)
• automatic restart (if the user terminates their remote desktop connection half way through a transfer, it will pick up again as soon as the user re-connects)
• file transfer happens inside the secure channel of the remote desktop session itself, so there is very little special configuration required (the user does have to enabled sharing of their local disks in the remote desktop session)
• no software installation required on the remote PC (other than whatever scanning software the user wishes to use)

Here's a typical use-case:

1. User makes reservation in remote desktop session
2. User places the cover sheet on the physical paper
3. User repeats the process, accumulating a to-be-scanned stack
4. User scans the stack on their local scanner and saves the results to a standard location on their local C drive
5. The Symphony Profiler background file transfer mechanism reaches through the remote desktop session, and pulls the file from the local C drive.  The file is then placed in one of the Symphony Profiler monitored folders on the server

Configuration

Configuration is made in the settings of the user's Symphony Profiler Workstation instance running inside the remote desktop session.

• Right-click on the Symphony Profiler system tray icon (again, this is inside the remote desktop session of the user)
• Choose Background Transfer
• Check the 'Enable' check box
• In the From field, specify the source folder (this will be a TSCLIENT\ based path) on the hard drive of the user's remote PC.  We generally recommend creating a Scans folder in My Documents
• In the To field, specify one of the Symphony Profiler Processor monitored folders (this will be on your file server)

Now that you have it set up, you can monitor progress in the Background Transfer dialog, or close the dialog (click the X) to let it run in the background.

Note: To transfer files from a location on your network, that location must be accessible via a mapped network drive letter instead of a UNC path.

Test

Now, create a reservation just like you normally would. When you scan the file, save it to the My Documents\Scans folder and you can see how it transfers to the network monitored folder for fulfillment.

Note: there are other use-cases for remote scanning, including having a network scanner push the scanned document over a WAN connection to the monitored folder in the home office. If you have a full blown WAN connection, that may be easier to configure and administer than using the background file transfer feature.

...

The Symphony Profiler Workstation installer can be executed with a /S (that's a capital "S" - case is important).  This will cause the install to happen in silent mode (so that user intervention isn't required).

It is imperative that the command be launched from the network home location for Symphony, so you should not place a copy of the installer elsewhere on the network.)

In addition, the installer does require elevation, so if you are running the installer in silent mode, you will need to do that from an elevated process.

...

You may wish to change the look and feel of the Cover Sheets your firm uses.  For example, you may want to include more specific instructions regarding how to save the cover sheet to the Symphony Profiler Monitored Folder, or you may simply want to jazz them up by adding your own logos, etc.

Here are the instructions for customizing your Cover Sheets:

1. Create a new subfolder in the SymphonyProfiler\Server folder called Templates
2. Create a PDF document containing the Customized Cover Sheet information you wish to use.
3. Save the PDF document to the SymphonyProfiler\Server\Templates folder naming it cover_template.pdf
4. Close Symphony Profiler Processor, Close Symphony Profiler Workstation
5. Relaunch Symphony Profiler Processor and Symphony Profiler Workstation

The next time you Create Cover Sheets you will see the "Customized" Cover Sheet

...

There may be occasional circumstances where you are OK with having the scanned file be older than the reservation date.  This is particularly useful in demonstration scenarios where you may need to scan some documents prior to demoing the software as there may not be a scanner easily accessible at a site, etc.

Disabling Scan Is Older than Reservation Error Checking for Individual Reservation IDs

To configure for this exception:

• Navigate to the Network SymphonyProfiler\Server folder.
• Open the config.xml file using Notepad.
• Locate <demoModeConfig sampleReservationIds=""/>
• Specify the sampleReservationIds you wish to allow to be older than the reservation date

Your config.xml file will look something like this:

Disabling Scan Is Older than Reservation Error Checking for All Reservation IDs

Another workflow may be as follows:  Attorney is at a client site somehow, without Worldox available to them.  There is a bunch of paper that they are gathering, so they take a stack of cover sheets with them, and interleave those into the paper, then scan the whole batch and return the stack to the client.  Then they transfer the scan to the site, and the user then profiles the documents from the Input folder?  i.e. go through the electronic version and create profiles for each.

Important: We do not recommend this workflow, but in such cases, you can change the configuration to allow for this.

To configure for this exception:

• Navigate to the Network SymphonyProfiler folder.
• Open the config.xml file using Notepad.
• Locate <demoModeConfig sampleReservationIds=""/>
• Specify an asterisk for the sampleReservationIds

Your config.xml file will look something like this:

...

Background

By default, Symphony Profiler will send a status email notification at 10PM each night.  This procedure tells you how to adjust that time.

Process

1. Update Symphony Profiler to version 1.0.5.19 using Help->About
2. After the update is installed and Processor is running again, go to Edit->Preferences, then click OK  (this forces the configuration file to be rewritten)
3. Close S-Pro Processor
4. Locate the Network\SymphonyProfiler\Server\config.xml file and open it for editing in notepad
5. Locate the entry that says "sendEmailTime", and change it to the time you wish (this is a 24 hour clock, and the format is important hh:mm:ss)
6. Save and close config.xml
7. Launch S-Pro Processor

...

Symphony Profiler Requires:

Windows XP or higher (including server operating systems)
750 MHz or faster processor
512 MB RAM
1 Gb available disk space
100 Mbps or better network connection to your file server

 Typically, Symphony Profiler Processor is installed to the PC that also runs the Worldox indexer, but this is not required.

Scanners

Any scanner or scanning software that is capable of generating PDF files will work with Symphony.  For details, refer to our Testing Your Scanner article.

Does Symphony Profiler Run on a Mac OS?

No, Symphony Profiler is only compatible with the Windows operating system.

...

Known Good Scanners and Software

The following scanners and scanning applications have been tested for compatibility with Symphony Profiler:

Desktop Scanning Software

Note: For desktop scanning, the scanner model itself does not matter - just the scanning software.

• Adobe Acrobat 5 through 11
• Fujitsu ScanSnap software (see Configuring "Scan to Symphony" for the Fujitsu ScanSnap )
• ScanToPDF
• eCopy Desktop
• many others...

Multi-Function Devices

Any scanner that generates PDF files should work with Symphony.  The following is a list of the scanners that we've explicitly tested, but we have many, many users using many, many different types of scanners.

• Xerox WorkCentre MFD
• HP Laserjet M3035 MFP
• Ricoh Aficio MPC6501 SP
• Konica Minolta bizhub C300
• many others...

Device Not Listed?

If you'd like to check your scanner's compatibility ahead of time, print the attached sample cover sheet, then scan and email it to support@trumpetinc.com.  Trumpet will do a quick analysis to make sure there are no issues.  Be sure to tell use the full model of your scanner!

...

To configure the Fujitsu ScanSnap to automatically scan directly to the Symphony Profiler input folder, Trumpet recommends setting up a "Scan to Symphony" profile in the ScanSnap Manager.  Here's how:

1. Right-click on the ScanSnap Manager icon in the system tray and select "Scan button settings"
   
2. Switch to the Application tab 
   Tip: The "Use Quick Menu" checkbox must be unchecked to access the Application tab.
3. Select the "Scan to File" application
4. Switch to the Save tab
5. Set the "Image saving folder" to your desired Symphony Profiler input folder
6. Ensure all other options on the Scanning, File Option and Paper tabs are configured as desired
   Tip: Use the Duplex Scan option under the Scanning tab, and Symphony Profiler will automatically remove blank pages for any single-sided scans.
7. Select Profile > Add Profile
8. Name the Profile "Scan to Symphony"
   
9. Click OK
10. Left-click on the ScanSnap Manager icon in the system tray, and ensure the "Scan to Symphony" profile is set as the default scanning profile
    

...

Trumpet recommends that you uninstall the Symphony Profiler Workstation from your client's sites, and utilize the Symphony Menus in the Worldox client.  Why?  This prevents users from having to update the Symphony Profiler Workstation when you apply updates.  We've found many instances of firms where the users don't have UAC Control properly set, or where the users are prevented from elevating because they don't have the administrator password to allow them to do so.  This means that an administrator has to walk around to each workstation and install before the users can actually make their reservations!

In all modern versions of Symphony Profiler, you have the ability to ditch the old-school workstation install. 

By selecting the "Add Symphony menu and button to Worldox" checkbox in the Symphony Profiler Processor:

the firm will have the "Create Reservation" button in the Worldox interface:

and the full "Symphony Menu" as well:

 

 

 

...

If you'd like to add the Create Reservations Button to Worldox and it's not already present, you may need to enable the feature in Symphony Profiler. 

Adding Symphony Profiler to the Worldox Menu and Default Button Bar

To enable the feature from the workstation running Symphony Profiler Processor (this is typically your Indexer workstation):

• Ensure you're running the latest version of Symphony Profiler.  For instructions on updating, see:  Update Symphony Profiler
• In Symphony Profiler Processor, navigate to Edit > Preferences
  
• Select Worldox from the navigation panel on the left
• Check the "Add Symphony menu and button to Worldox" check box
  

The next time your users launch Worldox, they will see the new Symphony menu, and they should see the Create Reservation button if they are using the default Worldox button bar.

Adding Symphony to Customized Button Bars

You may still have folks who do not see the Create Reservation button in Worldox.  This is typically due to the fact that they have customized their button area.  If a user has customized the button area and would like to add the Create Reservation button, they can do so by performing the following steps:

• Right-click on the button area of Worldox and choose "Append Button"
  
• Select File > Send To > Create Reservation
  
• This will add the "Create Reservation" button to Worldox

 

 

...

Background:

Generally, we don't have an exception list because in our experience, the only anti-virus software that causes Symphony problems are poorly written apps.  However, if you suspect your anti-virus software is causing issues with Symphony, or if you wish to increase efficiency, it couldn't hurt to add the following to your exclusion list.

Solutions:

We recommend adding the following to your anti-virus exclusion list:

X:\Trumpet\SymphonyProfiler\Workstation\Shared\UsedRes.dat

(Note, the "X:\Trumpet\SymphonyProfiler" represents the installation location.  Since installation locations are configurable by the installer, this location may be different at your site.)

...

Background

Because Worldox now runs as a service, Trumpet has received many requests to have Symphony Profiler also run as a service.  This is possible using version 2.0.0 and higher of Symphony Profiler.

Resolution

If you are performing this update in concert with updating Worldox to run as a service, after the Worldox update you'll want to ensure that you've launched the Worldox client in mirrored mode on the machine running the Symphony Profiler service (typically the Indexer) as the Symphony Profiler user.  You can determine the user by selecting Edit > Preferences... > Worldox.  It's typically 000000, but yours may be different.  

To run Symphony Profiler as a service: 

• Select Help > Check for updates... on the Symphony Profiler interface
• Select the pre-release version to download the installer 
  
• Run the installer — accept the defaults until you come to the "How would you like to run Symphony Profiler?" step
• On this window, select "Run as a Windows Service" — Enter the Domain\User and Password.  Click 'Next'

NOTE:  Worldox must be configured to run using full UNC paths (no mapped drives), and this includes the Audit Trail configuration.

...

While Symphony Profiler provides you with Daily Status Notifications, you may also want to do real time monitoring of the Symphony Profiler Processor.  You can monitor the software on the workstation that's running it and the process as well, but perhaps you don't have permissions to view that workstation. 

You can run Symphony Profiler Processor's interface by installing it on a separate workstation, but not running the service.  Here's how:

• On the monitoring workstation, run the processor installer by navigating to the network location of the installer
  e.g. \\server1\share\Trumpet\SymphonyProfiler\Server\Updates\SymphonyProfilerProcessorSetup-X-X-XX.exe
• When prompted to run as a logged in user or a service, opt to run as a logged in user
• Uncheck the check box indicating "Start Symphony Profile Processor" in the final window of the installer wizard
• Update the Symphony Profiler Processor desktop icon to add the following switch: /noserver  to the end of the target line.
• Update the Symphony Profiler Processor icon in the start menu to add the following switch:  /noserver to the end of the target line
  

NOTE:  Failure to update these switches can cause undesired results so you really want to make sure you do that!!!

• The user then can launch from that desktop or start menu shortcut and see the Symphony Profiler Processor interface
  

...

Automation capabilities were added to Symphony Profiler Workstation in version 1.0.4.31

Right now, automation allows a caller to display the Symphony Create Reservation dialog, providing default values for the various aspects of the Worldox index card dialog.

Automation is exposed via standard Windows COM capabilities.  The type library for accessing the automation is titled 'Symphony Profiler Workstation Type Library' (if you wish to use early binding), or via CreateObject calls against the SymphonyProfiler4WD namespace.

This functionality is still fairly new, and we are very open to extending it and our documentation - if you are a developer and would like more information, please open a support ticket by emailing support@trumpetinc.com

Here is example code that demonstrates how to invoke the automation:

' This example uses late binding.  You can also use early binding by including
' a reference to "Symphony Profiler Workstation Type Library" in your project
Public Sub exerciseShowReservationDialog()
    ' first, set up a WDReservationInfo object with the default values you want the Save As dialog to display
    ' if you want to use the user's defaults, just create the info object and don't populate it

    Dim info As Object
    Set info = CreateObject("SymphonyProfiler4WD.WDReservationInfo")
    ' Due to the vagaries of the Worldox API, the PG # you need to specify here is one more than
    ' the number that appears in wdadmin - so the following entry refers to PG 20 as displayed in wdadmin
    info.pgid = 21
    info.Description = "test desc"
    info.field1 = "code1"
    info.field2 = "code2"
    info.field3 = "code3"
    info.field4 = "code4"
    info.field5 = "code5"
    info.field6 = "code6"
    info.field7 = "*WDUSER"

    ' Next, connect to the Symphony Profiler 4 WD application
    Dim app As Object
    Set app = CreateObject("SymphonyProfiler4WD.Application")

    ' Then request that it show the reservation dialog, with the default save as dialog values specified
    ' Info - specifies the values that the Worldox profile should be pre-populated with
    ' Flags - optional parameter - 0 by default
    ' 0 - Another and Another Similar buttons will operate as normal
    ' 1 - Suppress Another Buttons - the Another and Another Similar buttons will be suppressed
    Dim rslt As Long
    rslt = app.ShowReservationDialog(info, 1)

    ' Handle the return code
    ' 1 = OK pressed
    ' 2 = Cancel pressed
    If (rslt <> 2) Then
        Debug.Print "PG = " & info.pgid
        Debug.Print "Path = " & info.Path ' path is Read Only, set to the path of the XPF file after the reservation is created
        Debug.Print "Field1 = " & info.field1
        Debug.Print "Field2 = " & info.field2
        Debug.Print "Field3 = " & info.field3
        Debug.Print "Field4 = " & info.field4
        Debug.Print "Field5 = " & info.field5
        Debug.Print "Field6 = " & info.field6
        Debug.Print "Field7 = " & info.field7
        Debug.Print "Description = " & info.Description
    Else
        Debug.Print "Canceled"
    End If

End Sub

...

Here are some things to check if you have files in your input folders that do not have a matching reservation:

1. Check the Status message in Symphony Profiler Processor for that document
• If 'Problem - Scan older than reservation', this means that the document was scanned before the reservation was created.  See Scan Older Than Reservation error article for the cause and resolution for this issue.
• If 'In use by another application', this means that the scanned document is open somewhere else on your network.  The must likely culprit is the scanning software itself (if you are using a desktop scanner).  Check to ensure that the file isn't left open in your scanning software.  If not, ask your IT administrator to check your server's 'open files' list for the problem document, and see which user has it open.
2. Check to ensure the document was scanned with the corresponding cover sheet
   
   • If the document is missing a cover sheet, Symphony Profiler will not know how to file the document, so it will leave it in the input folder.  To resolve this issue, see the Scanned a document without it's cover article.
3. Check to ensure that a reservation was actually created for the document
   
   • The No Reservation message on scanned document article covers this in detail
4. Check to ensure the document wasn't accidentally filed twice
   • In the Symphony Profiler Processor application that runs on your Indexer workstation, check to see if the 'Recently fulfilled list' already contains a reservation for the file in question (also, an exhaustive list of all reservations ever fulfilled can be found in the Server\logs sub-folder of your network Symphony Profiler directory)
   • If it does, the document may have been scanned twice - check to make sure the file is correctly filed in Worldox, then delete the duplicate file from the Input folder
5. Check to ensure the Symphony Profiler Processor is monitoring all Worldox profile groups
   • In the Symphony Profiler Processor application that runs on your Indexer workstation, select Properties > Edit > Preferences > Worldox
   • Select "Refresh" from the middle of the screen
   • If the profile group isn't listed, adjust Worldox security so the Worldox user listed in the preferences dialog has appropriate access
6. Check to ensure the document was meant to be filed to Worldox in the first place
• Sometimes, users may scan non-Symphony files into the input folder by mistake. If the documents are meant to be filed outside of Worldox, re-file them accordingly
• If you have a network scanner, consider creating multiple scan targets - one for Symphony related documents, and another for non-Symphony related documents

To understand the workflow process for Symphony Profiler, see:  Symphony Profiler Workflow

For Symphony Profiler "Basic" Users

...

From time to time, you may wish to do further research on a particular reservation ID to determine how it has been used and fulfilled through Symphony Profiler.

You can research a particular reservation ID via the Symphony Profiler Processor.

• Go to Help > Research
  
• When the Input windows opens, simply enter the reservation ID you wish to research
  
• Select OK
• Symphony Profiler will search through the various logs to provide you with a summary of the log entries for that particular reservation ID

Here's an example:

Here is some helpful information for understanding the information presented to you in this file:

The first portion of the entry is the date and time of the event:

Note: Time is viewed in military time formatting

The next portion of the entry is the log from which the entry is found:

For example, the first line entry on 3/30/12@10:26:01 is from the Split.log file and the second entry is from the fulfilledreservations.log file

Finally, the last portion of the entry includes the information found at that date and time in that particular log file that matches that reservation ID:

...

If the machine that S-Pro Processor is currently running on needs to be replaced, follow these steps to set Processor up on a different PC or VM:

Preparation

• On the new workstation, launch Worldox in mirrored mode as the user you intend to have Symphony Profiler Processor run as (e.g., 000000) to ensure that Worldox has fully initialized that user code on this workstation (Note: Worldox does not need to remain open for Symphony Profiler Processor to run - it simply needs to be launched once)

Migration Procedure

1. From the new workstation, navigate to the network Symphony Profiler folder
2. Navigate to the Server\Updates sub-folder
3. Run the SymphonyProfilerProcessorSetup installer
4. From the "Symphony Profiler Processor Setup" window, select "Next"
5. Leave the default destination folder as is, and select "Next". Note: This installation will be on the local disk of the computer.
6. Leave the "Start Symphony Profiler Processor" check box checked, and select "Finish"
7. Click "OK"
   

Processor will launch with all settings preserved.

IMPORTANT:

Finally, uninstall Processor from the old hardware using Control Panel (see these Uninstallation Instructions for details)

...

By default, Symphony Profiler expects Worldox to run with standard mirroring — Even on Terminal Server sites.  However, if you are unable to use the standard mirroring install for the Worldox workstation and have chosen Worldox's "Plan B" method, there are some necessary steps to properly install Symphony Profiler:

• Copy WDREGKEYS.INI from the network into each of the TS private installations (e.g. \\servername\share\Worldox\' to C:\Worldox of each TS.)
• Copy the 'Worldox\Icons\3rdParty' folder from the network install to each of the TS private installations.
• Copy WDMSMAIN.INI from the network installation to the TS Private installations. This is what makes the Symphony Profiler icon available in the button bar.
• Make sure that the [Btns] section of WORLDOX.INI is the same throughout each installation (we add an '13006' entry to the Worldox Main value)
• Make sure that WDSTUSER.INI is consistent across all installations (the 'Program' links are properly pointing to the network installation)
  

...

Background

User has a file named Sample.pdf and transfers the file using Background File Transfer via Symphony Profiler.  Prior to the reservation having been fulfilled, user saves another file to the scans folder called Sample.pdf.  That second file is not transferred to the input folder.

Resolution

That file cannot be transferred to the input folder because a file of that name already exists.  This only happens if the original document reservation has not been fulfilled.  There are several options for you in this scenario:

• Rename the file in the Scans folder location
• Use a naming convention on the scanner that includes a unique filename (some scanners allow an automatic filename with the date and time stamp to ensure things are not duplicated)

...

Background

You have Background File transferred configured / set up on your office workstation but you are working remotely today from home.  You have Worldox installed and try running the background file transfer, but it is not successful.  This is because the Background File Transfer is not specific to the instance of Worldox that you're running but rather a one-time set up.

Resolution

Reconfigure the Background File Transfer on your home computer following the steps found in this article:  https://support.trumpetinc.com/index.php?pg=kb.page&id=1282

When you're back in the office, you'll need to follow those steps again.

...

...

Version Numbers

Trumpet products are versioned with a 3 digit number (e.g. 2.7.3, 2.18.4).  All versions of the product are released serially (i.e. version 2.7.3 contains all of the changes from 2.7.2, 2.7.1, 2.6.18, 2.6.17, etc…).  New versions are created frequently (often once or twice per week), and each version change consists of a very small amount of changed or additional functionality (i.e. one bug fix or one new feature).

It is not at all unusual for Trumpet to produce 2 or 3 versions of a given product in a single week.

Trumpet also has reporting on which customers have which versions – and whether those installations are in an OK, WARN, or ERROR status level.  We also track support requests (issues) by which version of the software was installed at the time of the request.  This allows us to make quantitative assessment of the risk of a given version of each product.  If a given version is in use at many sites, all of which are OK, and there have been no reported issues for that version, then we can say with confidence that the build is stable and safe to deploy broadly.

Because each version bump incorporates a very small number of changes, it is very, very easy to identify any regression issues that arise.

Release Management

Trumpet has 3 phases that a given software version might go through:

DevRelease	Software is highly unstable.  No testing has been performed.  May contain known and unknown huge glaring bugs and problems. This is not available to download through your software, and should not (and could not) be deployed to any system unless Development is involved
PreRelease	The software is considered stable, and has passed internal QA, but we don’t have exhaustive experience at tons of sites – it may still contain unknown bugs, but regressions are highly unlikely
Production Release	Software has been proven to be robust at a large number of sites – any bugs remaining are small.

 

This means that the latest Production release will always be at the same or less version as the latest PreRelease.  For example, 2.3.7 might be the latest Production release, and 2.3.23 might be the latest PreRelease.  The PreRelease would contain 16 small changes since the Production release was made.

Periodically (usually around every 3 months), a review determines the latest PreRelease that is considered to be ready for Production.  This review consists of looking at how many sites are running the PreRelease, whether there have been any support requests made for versions between the current Production release and the PreRelease that may indicate an issue with the underlying code, and whether sites currently using the PreRelease are in a warning or error state. 

Installers for DevRelease are named ‘DevRelease-ProductName-x.y.z.exe’.  Installers for PreRelease are named ‘PreRelease-ProductName-x.y.z.exe’.  Installers for Production are named without a prefix (‘ProductName-x.y.z.exe’).

Once a PreRelease version has been declared ready for production, a Production release is created with the same version number as the PreRelease (this is the exact same installer – we literally just rename the installer exe).

Once a Production version is identified, we generally bump the second number of the version for the next PreRelease we create.  For example, if a 2.3.16 PreRelease is marked as a Production release, the Production release will be 2.3.16, and the next change we make to the product will be under version 2.4.1.

Risk Management

The reason we have these phases is to minimize the risk of exposing a given problem to a large number of users.  PreReleases tend to roll out gradually to a small handful of sites as we work with firms who actually need functionality, or to those sites who choose to install it pro-actively.  PreRelease and Production releases could be installed by anyone at any time by doing a Help->Check for Updates (or we may send a blast email announcing a new version’s availability).

This approach results in customers being able to install the latest ‘Known Good’ version on a regular basis (3 or 4 times per year), while still enabling customers who need changes or fixes to get rapid updates at extremely low risk.

How risky are PreReleases?

Pre-Release versions are very stable.  If we are fixing a bug or adding new functionality, it is extremely rare that work could cause problems for the useful functionality of earlier versions (we refer to this sort of issue as a ’regression’, and our release management cycle is designed to prevent this sort of issue).  So there is a small chance that a given PreRelease might not completely fix the bug it was intended to fix – or there may be a subtle issue with new functionality that was added - but it is very rare that a given PreRelease would actually break the application in a meaningful way.

If you have an issue or need that the latest PreRelease fixes, it is generally a good idea to update, unless the issue is truly not important to your organization.

PreReleases (if available) can be obtained using the Check for Updates functionality available in all of Trumpet’s applications.

How risky are Production releases?

Production versions are not only very stable, but have had a good number of sites using the version without issue.

We recommend that you install all Production updates as they become available (though it’s perfectly fine to schedule this into your regular maintenance schedule).

...

Updating your Symphony Profiler license / software is a two step process, the first, is to update your Symphony Profiler software, and the second is to update your Symphony Profiler license.  The following are instructions for doing each of these operations:

Update Symphony Profiler Software

These steps assume that you have received an email instructing you to update your Symphony installation.  Depending on the update notification, that email may contain your client code and/or license number.

1. Connect to the workstation that Symphony Profiler Processor is running on (this is usually the indexer PC)
2. In the Symphony Profiler Processor application, click Help > Check for Updates.  Save to your desktop
3. Double-click the Symphony Profiler installer
4. Click "Next", then "I Agree"
5. Leave the installation folder as the root of the *network* folder that contains your Symphony Profiler installation (if you are updating, this should be pre-filled), then click "Next"
6. After the installation completes, leave the "Install Symphony Profiler Processor" checkbox checked, then click "Finish"
7. The Symphony Profiler Processor installer will now launch
8. Click "Next"
9. Leave the installation folder as the default (this will be installing to the local C drive of the workstation), click "Next"
10. After the installation finishes, leave the "Start Symphony Profiler Processor" checkbox checked, then click "Finish"
11. The new version of Symphony Profiler Processor will launch

That's all there is to it!

Note for if users have the local workstation component installed on their computers (the component is not technically required, but many still have it and prefer it): Once the back-end is updated, the workstations will receive an update notification the next time Symphony Profiler Workstation is launched (normally when users log in) - to get the Workstation update sooner, you can close Symphony Profiler Workstation and re-launch it, then follow the update prompts.

Update Symphony Profiler License

Starting with version 1.7.28, Symphony Profiler will have an 'Automatic License Update' feature.  Basically, after you've paid your yearly invoice with Trumpet, a new license is automatically generated.  So if your installation has access to the Trumpet servers, Symphony Profiler will see this new license, download and install.

Note:  Symphony will check for a new license once every 3 days under normal circumstances, and once per day when your license is within 30 days of expiring.

If you've paid your invoice (and received notification of a new license) and don't want to wait for the automatic update to kick in, you can perform the following steps:

• Open the Symphony Profiler Processor (from the Indexer workstation)
• Navigate to Edit -> Preferences
• Select "Licensing" in the left hand navigation panel
• Select 'Check for Latest License' button on this page. 

This will manually trigger Symphony Profiler to retrieve the updated license from Trumpet's servers.  As mentioned, all of this assumes your installation has access to Trumpet's servers.  If a connection cannot be established, you can always copy/paste your new license into this screen.

When you receive notification from Trumpet that your new license is generated, it is still highly recommended that you A) update your installation to the latest version of the software, and B) verify your license has been updated.

...

These steps assume that you have received an email instructing you to update your Symphony installation.  Depending on the update notification, that email may contain your client code and/or license number.

1. Connect to the workstation that Symphony Profiler Processor is running on (this is usually the indexer PC)
2. In the Symphony Profiler Processor application, click Help > Check for Updates.  Save to your desktop
3. Double-click the Symphony Profiler installer
4. Click "Next", then "I Agree"
5. Leave the installation folder as the root of the *network* folder that contains your Symphony Profiler installation (if you are updating, this should be pre-filled), then click "Next"
6. After the installation completes, leave the "Install Symphony Profiler Processor" checkbox checked, then click "Finish"
7. The Symphony Profiler Processor installer will now launch
8. Click "Next"
9. Leave the installation folder as the default (this will be installing to the local C drive of the workstation), click "Next"
10. After the installation finishes, leave the "Start Symphony Profiler Processor" checkbox checked, then click "Finish"
11. The new version of Symphony Profiler Processor will launch

That's all there is to it!

Note for if users have the local workstation component installed on their computers (the component is not technically required, but many still have it and prefer it): Once the back-end is updated, the workstations will receive an update notification the next time Symphony Profiler Workstation is launched (normally when users log in) - to get the Workstation update sooner, you can close Symphony Profiler Workstation and re-launch it, then follow the update prompts.

...

Updating your Symphony Suite license / software is a four step process:

1. Update your Symphony Profiler Software
2. Update your Symphony Profiler License
3. Update your Symphony OCR Software
4. Update your Symphony OCR License

The following are instructions for doing each of these operations:

Updating your Symphony Profiler license / software is a two step process, the first, is to update your Symphony Profiler software, and the second is to update your Symphony Profiler license.  The following are instructions for doing each of these operations:

Update Symphony Profiler Software

These steps assume that you have received an email instructing you to update your Symphony installation.  Depending on the update notification, that email may contain your client code and/or license number.

1. Connect to the workstation that Symphony Profiler Processor is running on (this is usually the indexer PC)
2. In the Symphony Profiler Processor application, click Help > Check for Updates.  Save to your desktop
3. Double-click the Symphony Profiler installer
4. Click "Next", then "I Agree"
5. Leave the installation folder as the root of the *network* folder that contains your Symphony Profiler installation (if you are updating, this should be pre-filled), then click "Next"
6. After the installation completes, leave the "Install Symphony Profiler Processor" checkbox checked, then click "Finish"
7. The Symphony Profiler Processor installer will now launch
8. Click "Next"
9. Leave the installation folder as the default (this will be installing to the local C drive of the workstation), click "Next"
10. After the installation finishes, leave the "Start Symphony Profiler Processor" checkbox checked, then click "Finish"
11. The new version of Symphony Profiler Processor will launch

That's all there is to it!

Note for if users have the local workstation component installed on their computers (the component is not technically required, but many still have it and prefer it): Once the back-end is updated, the workstations will receive an update notification the next time Symphony Profiler Workstation is launched (normally when users log in) - to get the Workstation update sooner, you can close Symphony Profiler Workstation and re-launch it, then follow the update prompts.

Update Symphony Profiler License

Starting with version 1.7.28, Symphony Profiler will have an 'Automatic License Update' feature.  Basically, after you've paid your yearly invoice with Trumpet, a new license is automatically generated.  So if your installation has access to the Trumpet servers, Symphony Profiler will see this new license, download and install.

Note:  Symphony will check for a new license once every 3 days under normal circumstances, and once per day when your license is within 30 days of expiring.

If you've paid your invoice (and received notification of a new license) and don't want to wait for the automatic update to kick in, you can perform the following steps:

• Open the Symphony Profiler Processor (from the Indexer workstation)
• Navigate to Edit -> Preferences
• Select "Licensing" in the left hand navigation panel
• Select 'Check for Latest License' button on this page. 

This will manually trigger Symphony Profiler to retrieve the updated license from Trumpet's servers.  As mentioned, all of this assumes your installation has access to Trumpet's servers.  If a connection cannot be established, you can always copy/paste your new license into this screen.

When you receive notification from Trumpet that your new license is generated, it is still highly recommended that you A) update your installation to the latest version of the software, and B) verify your license has been updated.

Updating your Symphony OCR license / software is a two step process, the first, is to update your Symphony OCR software, and the second is to update your Symphony OCR license.  The following are instructions for doing each of these operations:

Update Symphony OCR Software

These steps assume that you have received an email instructing you to update your Symphony installation.  Depending on the update notification, that email may contain your client code and/or license number.

1. Connect to the workstation that Symphony OCR is running on
2. From the upper right-hand corner of the Symphony OCR main page, click the 'Check for Updates' link
   
   
   
   
3. Save the Symphony OCR installer to your desktop or browser
4. Once the installer has finished downloading, double-click to launch the install
5. Click "Next", then "I Agree"
6. Leave the installation folder as the default, then click "Next"
7. Leave the selected radio button under "How would you like to run Symphony OCR", and click "Next". Alternatively, if you'd like to adjust this then do so now to change the way it runs (Service vs logged in user)
   
8. After the installation completes, leave the "Start Symphony OCR" checkbox checked, then click "Finish"
9. Symphony OCR will launch

That's all there is to it!

Update Symphony OCR License

Starting with version 6.4.96, Symphony OCR will have an 'Automatic License Update' feature.  Basically, after you've paid your yearly invoice with Trumpet, a new license is automatically generated.  So if your installation has access to the Trumpet servers, Symphony OCR will see this new license, download and install.

Note:  Symphony will check for a new license once every 3 days under normal circumstances, and once per day when your license is within 30 days of expiring.

If you've paid your invoice (and received notification of a new license) and don't want to wait for the automatic update to kick in, you can perform the following steps:

• Navigate to the Licensing Page by selecting the Licensing link in the left hand navigation panel of Symphony OCR.
• Select the "Check for Updated License" link on this page. 
• This will manually trigger Symphony OCR to retrieve the updated license from Trumpet's servers. 

As mentioned, all of this assumes your installation has access to Trumpet's servers.  If a connection cannot be established, you can always copy/paste your new license into this screen.

When you receive notification from Trumpet that your new license is generated, it is still highly recommended that you A) update your installation to the latest version of the software, and B) verify your license has been updated.

...

Symphony Suite consists of two software components that need to be updated individually.  Here are instructions for each:

Symphony OCR Update Instructions

Symphony Profiler Update Instructions

...

Summary 2.0

• Improved the processing of color and gray scale images that had light content
• Resolved issues to insure that when you install updates to the Processor, it is completely shut down.
• If either the "From" or "To" locations are unavailable for the Background File Transfer process, Symphony Profiler will retry accessing these locations for 30 seconds, and then issue a warning.  After that warning is shown, it will retry repeatedly every 60 seconds.
• Upon installation the network path for the Symphony Profiler Processor will be converted to a UNC path (if required) to allow the Symphony Profiler Processor service to access the network installation directory.
• If the network connection to Worldox fails, the Symphony Profiler Processor will show an error dialog
• Improved the blank page detection for color scans that have light marks on them (e.g. staple holes showing on blank pages)
• Adjusted the window behavior of the Background File Transfer process.  In versions 2.0.39 and higher, when you select "Symphony Imaging -> Start/Open Scans Transfer",  the background file transfer will silently run.  Selecting the menu item a second time will display the dialog.
• Resolved issues with Symphony Profiler As a Service crashing occasionally
• Updated to private Java Runtime based on the open source Liberica JDK
• Added Worldox Connection Reset every 60 minutes (1 hour) to resolve issues with connecting to the Worldox API

To see a full list of changes, visit:  Change Log

...

Changes

20210212

2.0.62 -

- Adjusted message box titles throughout so it is clear that the dialog belongs to Symphony Profiler (there were some error dialogs during launch where it was not clear which application was displaying the message)

20200814

2.0.61 -

- Updated license agreement to refer to Trumpet, LLC instead of Trumpet, Inc.

20200313

2.0.59

- Re-enable Worldox connection reset (every 60 minutes) - workaround for WDAPI failure issue introduced in WD build 131021.1515

20200117

2.0.56 - 

- Bug fix — resolve issues with documents taking a long time to "Split"

2.0.53 - dev release

- Bug fix - email notifications resulted in error 'java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter'

20190923 

2.0.53 -

- Bug fix - email notificaitons resulted in error 'java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter'

2.0.51 -

- Moved to JRE 11 (and Trumpet private Java runtime, non-oracle)

20190403

2.0.49 -

- Bug fix - license update requests could hang and prevent SPro from launching if license server communication stalled

20180831

2.0.43 -

- Bug fix - Worldox integration fails at sites that had UNC paths containing spaces and wdcommon\wdmirror.ini files referencing drive letter based CPs

20180713

2.0.42 -

- Fix - Processor installer was defaulting to blank installation path for WD Cloud installs

2.0.41 -

- Bug fix (caused by WDAPI mishandling of TCPIP connections) - SPro crashes occassionaly when running as a Windows Service

2.0.40 -

- Changed Symphony Imaging>Start Scans Transfer menu text to be 'Start/Open Scans Transfer'

2.0.39 -

- Improvement in response to issue: In WD Cloud envrionments starting in May 2018, the S-Pro system tray icon is not showing when launched from the Worldox Symphony Imaging->Start Scans Transfer menu, so users were unable to access the background scans transfer dialog after it was running. Selecting the 'Start Scans Transfer' menu again resulted in 'Symphony Profiler is already running' message.
- If the background transfer is already running and the user clicks 'Start Scans Transfer', the running S-Pro instance now displays it's background transfer dialog

2.0.33 -

- Regression fix - dark background cover pages weren't getting barcodes detected properly (introduced 2.0.31)

2.0.31 -

- Improved blank page detection in color scans that had light marks on blank pages

2.0.29 - Dev Release

- Made the client set the Worldox network folder if the service fails to initialize it

2.0.28 - Dev Release

- Added a Worldox Network Folder field to the Worldox config panel in the Properties dialog
- Added support for local Worldox mirroring
- Made the client show an error dialog when the Worldox connection fails

2.0.42 -

- Fix - Processor installer was defaulting to blank installation path for WD Cloud installs

2.0.41 -

- Bug fix (caused by WDAPI mishandling of TCPIP connections) - SPro crashes occassionaly when running as a Windows Service
* we now force WDAPI to use Windows Messages by appending .sm to end of session ID

 

2.0.18 -

- Modified the additional Symphony Profiler Processor client warning message to be more user friendly
- The split file backup logic was changed from copying the file stream to the new source to using the Files.copy() method
- Changed the server status check from every 5 minutes to every minute for faster updates

2.0.17 -

- Fixed a potential exception in the reservation finder, when XPF the list retrieval from Worldox fails
 
2.0.16 -

- Added some belts and suspenders to the service startup, to help ensure it fully fails when a major error occurs
- Removed stray error dialogs in the service
- Added additional trace logging to help with debugging


2.0.14 -

- Background file transfer problems are now reported via system tray notification
- If the From or To folder for background file transfer are not available, SPro Workstation will retry up to 30 seconds before showing a warning.  After the warning is shown, it will wait for the polling delay (60 seconds by default), then try again repeatedly.



2.0.10 -

- Bug fix - installer was not always successful in closing running instance of SProProcessor down


2.0.6 -

- Bug fix {tpt75015} Added error checking around the Check for updates dialog setup to prevent a potential
    issue caused by a Java bug in jre1.8.0_73
          

2.0.3 -

- Improved processing of color and grayscale images that had light content


2.0.2 -

- Ensured logs folder was created in the temp directory

2.0.1 -

- Fixed bug in PdfImageFileImpl that prevented an encrypted file from being deleted after a failed open attempt

2.0.0 -

- Different app modes will create different log file names, based on client only, service only, or both
- Modified the WDExpressProfile - ProcessorSetup.nsi to create the logs directory and ensure permissions allow writing


1.9.8 -

- Reworked the network list creation logic to select a random port as a starting point for port connection, then iterate through all ports to find one open
- Stored the service hostname in the config if it changes from that already persisted
- Modified ExProListAppender (for hooking into the logging) to select its own port, rather than be passed one
- Created NetworkListUtils to handle creation of ListPeers for NetworkLists


1.9.5 -
- Made the log viewer autoscroll to the bottom when a new log entry is added
- Modified the service status object to also report if barcode handling is licensed
- Repaired many edge cases in startup/shutdown to help ensure the client always connects to the service,
    and that all processes are completely stopped upon shutdown of the client or service
- If running as a standalone application, closing the client now also stops the service
- Removed /nethome settings from the service mode installer
- Modified localHome to use application.home setting
- Log list in client now autoscrolls to the bottom when a new log item is added

1.9.4 -

- Reworked service issues code to provide better functionality
- Fixed many startup issues that appeared during testing
- Added launcher_service command line argument support to StartupOptions, so we can know when the app is running as a Windows service
- Prevented network list shutdown when the service reinitializes
- Added /nethome settings to the service mode installer shortcuts ** These will have to be changed later


1.9.2 -

— Initial creation of SPRO as a service
— SPRO can now run as a Windows service, if desired. The client can be run as a separate application that communicates with the service.
- Separated the client and service startup and management code out of the application class, and into client and service classes
- Made the client more of a thin client, that makes requests of the service, rather than doing processing itself
- Modified the service to hold all the processing data and log data in lists, and serve the lists to the client through NetworkLists
- Modified the processor messages, displayed above the lists on the client, to be received via a NetworkList from the service
- Changed the log display to be a list, and limited to 2000 items
- On startup, the client reads the service host name and attempts to connect. It then waits for the service to initialize before proceeding
- Modified existing client menu item actions to make server requests for the activities.
- Created service handlers for the client menu item requests, to perform the actual tasks
- Made several domain objects serializable, so they could be streamed by the NetworkLists
- Created LogItemListPane, to display the log items in the client as a list

20171214

2.0.18 -

- Modified the additional client warning message to be more user friendly
- The split file backup logic was changed from copying the file stream to the new source to using the Files.copy() method
- Changed the server status check from every 5 minutes to every minute for faster updates

2.0.17 -

- Fixed a potential exception in the reservation finder, when XPF the list retrieval from Worldox fails
 
2.0.16 -

- Added some belts and suspenders to the service startup, to help ensure it fully fails when a major error occurs
- Removed stray error dialogs in the service
- Added additional trace logging to help with debugging

2.0.14 -

- Background file transfer problems are now reported via system tray notification
- If the From or To folder for background file transfer are not available, SPro Workstation will retry up to 30 seconds before showing a warning.  After the warning is shown, it will wait for the polling delay (60 seconds by default), then try again repeatedly.
* Move to SymphonyProfiler4WD.EXE version 1.8.17


2.0.10 -

- Bug fix - installer was not always successful in closing running instance of SProProcessor down


2.0.6 -

- Bug fix {tpt75015} Added error checking around the Check for updates dialog setup to prevent a potential
    issue caused by a Java bug in jre1.8.0_73
          


2.0.3 -

- Improved processing of color and grayscale images that had light content


2.0.2 -

- Ensured logs folder was created in the temp directory

2.0.1 - dev release

- Fixed bug in PdfImageFileImpl that prevented an encrypted file from being deleted after a failed open attempt

2.0.0 - dev release


- Different app modes will create different log file names, based on client only, service only, or both
- Modified the WDExpressProfile - ProcessorSetup.nsi to create the logs directory and ensure permissions allow writing


1.9.9 - dev release


1.9.8 - dev release

- Reworked the network list creation logic to select a random port as a starting point for port connection, then iterate through all ports to find one open
* Added a user friendly service error message when service lists fail to initialize
- Stored the service hostname in the config if it changes from that already persisted
- Modified ExProListAppender (for hooking into the logging) to select its own port, rather than be passed one
- Created NetworkListUtils to handle creation of ListPeers for NetworkLists


1.9.5 -

- Made the log viewer autoscroll to the bottom when a new log entry is added
- Modified the service status object to also report if barcode handling is licensed
- Repaired many edge cases in startup/shutdown to help ensure the client always connects to the service,
    and that all processes are completely stopped upon shutdown of the client or service
- If running as a standalone application, closing the client now also stops the service
- Removed /nethome settings from the service mode installer
- Modified localHome to use application.home setting
- Log list in client now autoscrolls to the bottom when a new log item is added

1.9.4 -

- Reworked service issues code to provide better functionality
- Fixed many startup issues that appeared during testing
- Added launcher_service command line argument support to StartupOptions, so we can know when the app is running as a Windows service
- Prevented network list shutdown when the service reinitializes
- Added /nethome settings to the service mode installer shortcuts ** These will have to be changed later


1.9.2 -

- Separated the client and service startup and management code out of the application class, and into client and service classes
- Made the client more of a thin client, that makes requests of the service, rather than doing processing itself
- Modified the service to hold all the processing data and log data in lists, and serve the lists to the client through NetworkLists
- Modified the processor messages, displayed above the lists on the client, to be received via a NetworkList from the service
- Changed the log display to be a list, and limited to 2000 items
- On startup, the client reads the service host name and attempts to connect. It then waits for the service to initialize before proceeding
- Modified existing client menu item actions to make server requests for the activities.
- Created service handlers for the client menu item requests, to perform the actual tasks
- Made several domain objects serializable, so they could be streamed by the NetworkLists
- Created LogItemListPane, to display the log items in the client as a list

20170804

1.8.19 -

- Bug fix - crash when creating reservations if the "recently used list" for Email Subject or Email Address was longer than ~20 items


1.8.16 - 1.8.17

— No changes

20170428

1.8.15 -

— No Changes
     
1.8.14 -

- Bug fix - if a reservation was not writable when S-Pro first found the XPF file, the file would be marked as unwritable from that point forward (or until the XPF file was modified in some way).  We now check the writable state each time the document is found, instead of only the first time.

20170310

1.8.13

- Bug fix - non-barcode enabled sites could have duplicate reservation IDs
- Enhancement - improve randomness of reservation IDs generted for non-barcode enabled sites
- Update to SymphonyProfiler4WD.exe version 1.8.13.1

1.8.12

- Bug fix - input file was left locked if it failed to read due to unknown encryption algorithm

20161209

1.8.11

- Bug fix - "Unable to connect to Worldox - Worldox must be launched before making reservations" errors in some very rare cases

1.8.10

- Grayscale image processing enhancement - pages with light gray are enhanced during black and white conversion process to maintain contrast of barcodes

20161021

1.8.8 -

- Bug fix - Processor was finding input files that had .$$$ file extensions (Worldox uses this extension on files it is actively moving - Symphony Profiler will now ignore those files)

1.8.7 -

- Bug fix - reservations with PENDING reservation code were being added to the used reservations manager.  Symphony Profiler no longer 'finds' the reservation if the code is 'PENDING'

1.8.6 -

- Added additional logging to Workstation
- Workstation now flushes changes to used reservation file (trying to keep disk caching from causing lost writes)

1.8.5 -

No Changes

1.8.4 -

- Bug fix - null pointer exception when extracting images from certain quasi-malformed PDFs (rg operator never called)

1.8.3 -

- Bug fix - registration of XPF open handler wasn't working properly in Worldox Cloud sites

1.8.2 -

- Moved to SymphonyProfiler4WD.exe version 1.7.16 (internal changes to support rework of used reservation tracking algorithm)
- Major overhaul of used reservation tracking algorithm
- Symphony Profiler now tracks the unfulfilled reservations in persistent storage (when SPro launches, the list of outstanding reservations will be populated right away)
- The used reservation tracking system will now self-heal if the underlying file loses records due to disk failure or file tampering

1.8.1 -

- Bug fix - some light grayscale scans weren't being detected as having content (binarizer optimization)

20160712

1.7.21 -

- Bug fix - if license becomes invalid, the reservation matching process is stopped - that's OK. But if the license becomes valid again after that, the matching process wasn't getting restarted.

1.7.19 -

- Bug fix - barcode processing wasn't being activated even though it was enabled by the license

1.7.18 -

- Added license Grace Period if user count goes above license
- Better error message if we can't connect to WDAPI

1.7.17 -

- Changes to Create Reservation dialog as follows:
- Fixed tab ordering on create reservation dialog
- Corrected bug with chevron appearance on the advanced button in create reservation dialog
- Fixed a problem with loading WDAPI32.DLL on system which do not have their PATH env variable correctly set with the path to the Worldox root folder.
- Created client component with version number 1.7.12

1.7.14 -

- Fixed bug 'Enter Reservation ID' label sometimes suppressed.
- Fixed bug 'Email Subject' label text sometimes appearing when Advanced was collapsed.
- Changed - client version changed to 1.7.10

1.7.13 -

- Bug fix - change in 1.7.11 wasn't working for the case where the input file is not in the splits folder (Was still showing 'pending match' instead of 'No reservation found in file'

1.7.12 -

- Bug fix - unable to detect barcodes on colored sheets generated by some scanners (image mask w/ explicit color issue)

1.7.11 -

- Special handling for NullPointerException from javax.swing.plaf.basic.BasicScrollBarUI.layoutVScrollbar()

1.7.10 -

- Differentiate between No Match b/c barcode wasn't found and No Match b/c there isn't a pending reservation ID
- new messages are
- If the input file is in the splits folder (i.e. it came from a barcode scan): 'No matching reservation found'
- If the input file is not in the splits folder (i.e. it doesn't contain a barcode): 'No reservation found in file'

1.7.7

- Client: Replaced the 3rd party expand/collapse group box with a simpler home-grown 'GroupButton.
- Client: Save/restore the expanded/collapsed state of the group button.
- Client: Ensure that we expand the advanced group button if any contained checkbox is checked, even if the config indicates that advanced was collapsed.

1.7.5 -

- Bug fix - S-Pro could cause some scanners (Lexmark x646dte) to fail scanning when scanning large numbers of pages

1.7.3 -

- Bug fix - If network drops unexpectedly, Used Reservation tracking system can get stuck in a loop showing error 'Unknown error - Already opened'

1.7.2 -

- Bug fix - If scan had incorrect page count, then user adjusted reservation to match the physical page count, SPro would generate 'Header signature not found' errors and would not fulfill the reservation (Regression introduced in 1.0.5.94)
- Bug fix - If user created reservation and scanned it, then deleted the resultant file from Worldox, then scanned using the same reservation ID within 10 minutes, SPro would display 'Reservation file unwritable' on the file and would not fulfill the reservation

1.7.1 -

- Bug fix - email notifications would occasionally result in "Communication error - Read timed out" error

1.0.6.1 -

- Bug fix - when attempting to open really big files, if there wasn't sufficient RAM to map the file into memory, processing would fail. We now drop back to a slower method of reading the file if this memory issue happens.

Summary 1.0.6

Here is an overview of the major changes in 1.0.6:

• Symphony Profiler now works with handheld barcode scanners to make the profiling process even faster. Instead of hand-keying the reservation ID from the Symphony Profiler cover sheet, you can use any handheld scanner to scan the barcode at the top of the cover sheet. A great tool when profiling many documents at once. Learn more here: Handheld Barcode Scanners
• You can now create custom cover sheets! Spice up the Symphony Profiler cover sheets by adding your own fun messages, your company logo, filing instructions specific to your firm - anything you like! Here's how: Create Custom Cover Sheets
• Create Symphony Profiler reservations directly from Worldox. We've added a "Create Reservation" button to the Worldox icon bar, making it even faster to initiate a Symphony Profiler reservation. Further details can be found here: Make Reservations from Worldox

1.0.5.108 -

- Bug fix - on some workstations, the Create Reservation dialog would drop behind the main Worldox window when initiating the reservation from the Create Reservation button or menu in Worldox (user clicks Create Reservation, profile dialog appears, user fills it in and clicks OK, Create Reservation dialog appears but is beneath the main Worldox window )

1.0.5.107 -

- Bug fix - If users saved the same input file into the Input folder multiple times, it would result in error messages about being unable to overwrite files in the Splits directory (this problem was introduced in version 1.0.5.94)

1.0.5.106 -

- Bug fix - unexpected errors during scheduled task processing left the scheduler non-functional (e.g. if the network was unavailable during reservation searching, it could result in a later reservation/split result not being matched even though a match was clearly visible on screen)

1.0.5.105 -

- Bug fix - workstation would crash if user initiated a second reservation without completing the first. The application no longer allows this
- Workstation updated to 1.0.5.105

1.0.5.104 -

- Adjusted installer so it automatically detects Worldox Cloud environment and adjusts installation to be safe for deploying to the cloud servers

1.0.5.103 -

- Bug fix - Processor was checking for file locks on input files every time it looked for matches, even if there wasn't a match - this could result in interaction problems with non-Symphony scanned document (we saw an issue where eCopy was leaving 0 sized PDF files in the input folder)

1.0.5.102 -

- Bug fix - Create Reservation button in Worldox toolbar was labeled "06 Send To" on some workstations

1.0.5.101 -

- Bug fix - SPro wasn't removing sections from WDSTUSER.INI when embedded integration was enabled then disabled
- Bug fix - default background file transfer monitored folder was \tsclient\c\ instead of \\tsclient\c\ (single backslash at the front instead of double backlash)

1.0.5.100 -

- Bug fix - UnsupportedOperationException error message when refreshing Worldox cabinet list

1.0.5.98 -

- Bug fix - SSCLOUD and SPROFILERCLOUD licenses weren't working

1.0.5.97 -

- Bug fix - 0 sized PDF files in the input folder would get locked and never released - the underlying bug that resulted in the locked file has been resolved
- 0 sized files in the input folder are now completely ignored (this is a meta fix to the 0 size bug fix in this release)

1.0.5.96 -

- WDSaaS based installs now store user settings in a folder on the network (Workstation\Settings\<username>\) (this behavior is controlled by the saasModeEnabled setting in settings.xml)

1.0.5.95 -

- Regression bug fix - the 1.0.5.94 change would cause repeated email notifications to be sent if page count validation failed
- On launch, S-Pro Processor will now kill orphaned instances of WDAPI (address issue where failures in WDAPI leave WBAPI.EXE running)

1.0.5.94 -

- SPro will now change the name of the input file in the splits folder by adding the analysis status. This is only for files that have been split, so regular input files will not be renamed.

1.0.5.92 -

- Bug fix - after the fix for 1.0.5.91, the same error situation results in notificaton emails being sent over and over again
- Bug fix - the error condition described in 1.0.5.91 results in an incorrect info line being added to the log pane saying that the reservation will be fulfilled again as a new version, even though that shouldn't (and doesn't) happen. We now only display that message if we are actually going to create the new version

1.0.5.91 -

- Bug fix - if page count check box was selected, and first scan had invalid page count, then scanning a second scan with valid page count resulted in the 'good' scan being version 1 and the 'bad' scan being version 2

1.0.5.90 -

- UI Bug fix - the email test dialog displayed the SMTP server name in the progress message when 'Symphony's Servers' was selected

1.0.5.87 -

- Workstation now supports data entry using a handheld barcode scanner to scan ID from cover sheet

1.0.5.86 -

- If background file transfer is enabled when S-Pro Workstation launches, a 'Background file transfer started' baloon tip will appear near the system tray

1.0.5.85 -

- If background transfer is unable to connect to From or To path, it will retry for up to 5 seconds before failing
- workstation version 1.0.5.85

1.0.5.84 -

- Workstation bug fix - in some rare circumstances, Symphony Profiler crashes after the double click when creating a new reservation
- Workstation version 1.0.5.84

1.0.5.83 -

- Workstation Bug fix - Show History dialog - double clicking on history entry didn't search for the correct document if the same reservation ID was in the history list multiple times
- Workstation - Show History list now contains a column for doc ID
- Workstation version 1.0.5.83

1.0.5.82 -

- Workstation 1.0.5.82 - adding debug message box displaying setDefaultFromFolder value...
- and just undid the message box from 1.0.5.82
- Bug fix - WD Enterprise wasn't displaying Symphony icon on Create Reservation button
- Processor now registers Symphony162432.ico into the Worldox\Icons\3rdParty folder
- This fix also requires that the C:\Worldox\RDA\WDxxMAIN_INI file be the latest from Worldox (must have [Icons] 13006 value)

1.0.5.81 -

- Bug fix - the fix in 1.0.5.80 didn't fix everything - now it's working
- Workstation 1.0.5.81

1.0.5.80 -

- Bug fix - workstation Create Covers dialog was not validating properly (validation logic for radio buttons was reversed)
- Workstation 1.0.5.80

1.0.5.79 - No changes

1.0.5.78 - 

- Bug fix - workstation would crash when using Another or Another Similar on some workstations. We now don't unload WDAPI if the user clicks Another or Another Similar. We do still unload it if they click OK or Cancel.
- Workstation 1.0.5.79

1.0.5.77 -

- Workstation will no longer attempt to open and edit files that don't have .xpf file extension

1.0.5.76 -

- Server now pushes Symphony Imaging>Edit Reservation command into Worldox menus

1.0.5.75 -

- Server now pushes settings into WDREGKEYS.INI so WD will register XPF file extension and open handler
- The special TEST123 reservation ID is not allowed anymore (b/c of the length check added in 1.0.5.73). The test code has been changed to QQQQQ
- Workstation 1.0.5.75

1.0.5.73 -

- Bug fix - workstation allowed entry of codes longer than 5 characters (if the checksum happened to be correct)
- Workstation now reads [CodeDisplay] MaxCodeLength and MinCodeLength values from the settings ini file and validates using those instead of hard coded values
- New Workstation 1.0.5.73
- Server now pushes [CodeDisplay] MaxCodeLength=5 and MinCodeLength=5 to the global settings ini file

1.0.5.72 

- Added /startBackgroundTransfer switch to workstation (displays the Background Transfer dialog if the background transfer can't autostart)
- New workstation 1.0.5.72

1.0.5.71 -

- No changes

1.0.5.70 -

- Bug fix (NullPointerException while writing to the very end of ini files)
- Bug fix - ini files were getting duplicate sections added to them
- jwinini-1.0.2.jar

1.0.5.69 -

- Add 'Start Scan Transfer' menu to Worldox
- New workstation version 1.0.5.70
- Added /setDefaultFromFolder command line switch to workstation. When used, this sets the default From Folder for background file transfer (i.e. what will appear if nothing is configured already) to the passed in value
- Default To folder in background file transfer module will now point at the Symphony\Server\Input folder by default
- Defult From folder in background file transfer module will now point to My Documents\SymphonyScans
- In Enterprise deployments, the 'Start Scan Transfer' menu will initialize S-Pro with the user's \\TSCLIENT based My Documents\SymphonyScans folder as the default From folder

1.0.5.68 -

- Added a /mirror command line switch to Workstation - when used, copies itself to %localappdata%\SymphonyProfiler\Mirror then launches from there
- New Workstation version - 1.0.5.69
- S-Pro menu and button in Worldox interface now use /mirror switch

1.0.5.67 -

- changed help URL in Create Covers email template to be http://support.trumpetinc.com/index.php?pg=kb.page&id=1212

1.0.5.66 -

- Bug fix - if network dropped out while writing to FlatFileUsedReservationManager, the file was left open and couldn't be written to again

1.0.5.65 -

- Bug fix - analysis of some PDF files could fail with 'Map Failed' error message
- move to itext-5.4.5-20131118b.jar (fix potential native memory leak when deflating zip streams)
- Tweak to table elements in create covers email content

1.0.5.64 -

- Bug fix - sites that had UNC mapped profile groups where the UNC share was no longer valid would wind up with no PGs being found at all
- update jWDAPI.jar to 20131218
- Workstaton now gets the message it displays after a succesful sending of a cover sheet email from the server
- New workstation - 1.0.5.64
- Improved wording for dialog after sending cover sheet email
- Fix email help hyperlink

1.0.5.63 -

- New SaaS mode cover generation dialog - radio button for sending email or just putting the URL onto the clipboard
- Workstation ver 1.0.5.63

1.0.5.61 -

- New option in Worldox config screen to allow pushing S-Pro commands into the Worldox menus and button bars
- New cover page email template
- We are now using the live cover generation web page

1.0.5.60 -

- Initial support for pushing S-Pro commands into Worldox menus

1.0.5.59 -

- Added support for creating cover sheets in SaaS installations.

1.0.5.58 -

- 'null' exceptions where appearing in log quadrant when 1.0.5.49 issue happened. These will now be logged at DEBUG level so won't appear in the quadrant or clobber the log files
- Bug fix - BASEPATH_AT_A_TIME was behaving like ONE_AT_A_TIME
- Disable imaging configuration field values (can't be edited in the GUI any more)

1.0.5.57 -

- Added resetFrequencySeconds to WDConnection configuration in settings.xml (not exposed in UI). This determines how frequently the Worldox session will be reset - prior to this, it was the same as the search frequency (once per minute). Default is 60 minutes.
- When searching for XPF files, if we are unable to find any base path of any PG, we attempt to reconnect network drives
- SPro now has a configurable strategy for searching for XPF files. This is configured in the WorldoxConnection settings in settings.xml - allowed values are (default value for now is 'FAST', which is the same behavior that we have always had):
- FAST - searches all avialable PGs for *.XPF (b/c of a bug in WD, may fail if indexes for some PGs aren't available)
- ONE_AT_A_TIME - searches each PG at a time - this is the most robust option, but will be considerably slower
- BASEPATH_AT_A_TIME - searches all PGs belonging to the same basepath. If the firm has a single basepath, this is the same as FAST. If multiple basepaths are in-use, will be slower than FAST

1.0.5.56 -

- SPro will not attempt to reconnect any disconnected network drives (for profile groups the registered WD user has access to)

1.0.5.55 - 

- If you put a log4j.properties file in the root SymphonyProfilerProcessor directory, you can adjust logging levels for that one install

1.0.5.52 -

- Fix potential race condition when resettings Worldox session

1.0.5.51 -

- Bug fix - special handling added in 1.0.5.49 wasn't implemented properly - caused all errors to be silently absorbed

1.0.5.50 -

- Bug fix - if there was a problem opening the FlatFileUsedReservatioManager, it could leave the lock on that file open until S-Pro is shut down.

1.0.5.47 -

- Added ability to send notificaitons using Trumpet's mail servers.  Default is to use Trumpet's servers.  Existing sites will use the existing configuration.

1.0.5.46 -

- Installer now checks for setup.ini [TrumpetConfig] WarnAboutWorkstationAdmin=Y  - if set to 'Y', a big warning is shown warning that you need to involve the sys admins before applying updates b/c sys admins may be needed to update workstations

1.0.5.45 -

- change installer - the Java bundle id download link is now BundleId=81819 (Java 7_u45)
- change installer - the Java installation now completely runs in silent mode - the user doesn't have to click through Java installation screens, and they aren't taken to a web site to test the Java install after it completes
- change installer - the Java installation is configured to NOT integrate with the web browser on the machine

1.0.5.44 -

- Added logging to web interface triggered shutdowns.
- Change email schedule so it sends 10pm Sun through Thursday (used to be Mon thru Fri)

1.0.5.43 -

- Don't include read only PGs in XPF searching (try to minimize bad profile groups that could cause XPF searching to not return all files)

1.0.5.42 -

- Workstation installer now points to new video URL (http://bit.ly/1fAqzVJ)

1.0.5.41 -

- Better error handling if user puts non-image PDF into input folder

1.0.5.40 -

- API change: Added flag to ShowReservationDialog() to allow suppression of Another buttons
- API change: *WDUSER passed to Field1, Field2, etc... is now resolved to the current Worldox user
  - Move to Workstation 10.0.5.39

1.0.5.39 -

- Removed Client ID and Partner ID prompts from licensing.  Heartbeats will now rely on license # to look that info up.

1.0.5.38 -

- Added WDReservationInfo.Path variable to API
- Move to Workstation 1.0.5.38

1.0.5.37 -

- Improvement to barcode scanner to handle hairlines in scan results

1.0.5.36 -

- Prevent S-Pro from starving other processes when it is processing large scans. S-Pro will now throttle it's usage if another process needs the CPU

1.0.5.35 -

- Bug fix - handle PDF files that use indexed color mapping (Fujitsu ix500 ScanSnap on Mac was doing this)

1.0.5.34 -

- Bug fix - very large pages scanned at high resolution (like 11x17@600dpi) caused OutOfMemoryExceptions - we now tile the rendering operations for large pages to keep memory consumption down

1.0.5.33 -

- Bug fix - in non-barcode mode, if workstation failed to obtain next reservation ID, a dialog was left on screen with no way for the user to kill it.  This would leave a reservation with ID PENDING in Worldox
- New version of Workstation - 1.0.4.44

1.0.5.32 -

- If SPro finds an XPF file that is actually a PDF file, it will fix the extension
- If SPro finds a corrupted XPF file, it displays 'CORRUPTED' in the Type column

1.0.5.31 -

- In some rare circumstances, usedres.dat was left locked by a OverlappingFileLockException

1.0.5.30 -

- Made Check For Updates and About menus work, even if something goes wrong with launch

1.0.5.29 -

- Added support for new license style (e.g. AW10P-M-xxxxxxx)

1.0.5.28 -

- Bug fix - encrypted files in the input folder caused S-Pro to hold locks on the file permanently

1.0.5.27 -

- Files in the working\splits folder will no longer be analyzed for barcodes when S-Pro launches

1.0.5.26 -

- Installer change:  We no longer display errors if firewall changes couldn't be made (this may cause things to fail down the road, but we are seeing a lot of cases where the firewall push is failing for no good reason)

1.0.5.24 -

- Bug fix - analysis of huge PDF files resulted in 'map failed' error message

1.0.5.23 -

- We now exclude file named XNAMEDAT.CRS from input folder (this is a new data file type that Worldox just added)
- We now exclude hidden files from input folder

1.0.5.19 -

- Added internal setting to configuration file (sendEmailTime) to control what time of day email notifications get sent out (not exposed in the user interface)

1.0.5.18 -

- Bug fix - if reservation was checked out, checking XPF back in was not resulting in it being available for fulfillment

1.0.5.17 -

- Added Help->Show Logs menu
- Added check to see if files are checked out before processing them

1.0.5.16 -

- Bug fix - if a PDF failed to open, it could be left in a permanently locked state (this would result in the file attempted to being reprocessed over and over again, without success)

1.0.5.15 -

- Bug fix - file locking on PDF in input folder resulted in "0 is zero or negative" error message instead of "file is in use"
- Bug fix - analysis of zero sized files could result in those files remaining locked until S-Pro is closed

1.0.5.14 -

Add retry loop to the check that makes sure that the network input folders are writable (some sites may have A/V or backup systems that grab short term locks on those directories and prevent us from checking them properly if we try too quickly)

1.0.5.12 -

- Status column for scans list will now display "Pending analysis" before we analyze/split and "Pending match" while waiting for matching to happen.  The status will only become "No Match" if matching was attempted and failed.

1.0.5.11 -

- Fixes to prevent scanners from manipulating input files once Symphony starts working on them - Symphony will now exclusively lock input files while it is processing them

1.0.5.10 -

Bug fix - Cannon scanners were creating temporary files named ~~something.tmp.pdf in the output folder - we now ignore files that start with ~

1.0.5.8 -

New setting in SymphonyProfilerWorkstation\local_settings.ini - [StartupSettings] NetworkRetries=5 - specifies the number of times workstation will try to connect to the server (during launch) before giving up and showing the user an error.  Retries are 1 second long.

1.0.5.6 -

In non-barcode mode, reservation dialog had 'X' to cancel button.  When users pressed this to close the dialog, it acts as a 'cancel' and deletes the reservation.  There is no need for cancelling the reservation at this point, so we now disable the X

1.0.5.5 -

Allow firms to disable 'Scan is older than reservation' error checking.  This is done by specifying <demoModeConfig sampleReservationIds="*"/> in config.xml

1.0.5.4 -

Users can now override template used in cover sheet generation by creating a SymphonyProfiler\Server\Templates\cover_template.pdf file
Added Help->Research feature - users can type in a reservation ID and a summary of all activity from all log files will be presented in choronological order
Processor now writes to split log using 24 hour time and MM/dd/yyyy@HH:mm:ss format
Processor now writes to fulfilled log using 24 hour time and MM/dd/yyyy@HH:mm:ss format
Split backup files are now named using 24 hour time format (yyyyMMdd@HH-mm-ss)
Split log now includes the modified date of the file that was split (second to last column, after the reservation IDs)
Split log now includes the split backup file path (last column, aftter the file modified date column)
Workstation - space characters are now filtered from the reservation ID dialog (both typed and pasted)
Workstation now writes to log files using 24 hour time format (to indicate the difference, separator between date and time is now @ instead of blank space) - MM/dd/yyyy@HH:mm:ss format
Bug fix - when making Worldox setting changes in preferences dialog, an instance of the WD API executable was left running
Bug fix - Workstation - When Reservation ID dialog is shown, it will have the focus (allowing users to type immediately instead of clicking on the dialog first)

1.0.5.1 -

Better error handling if reservation ID is missing from XPF file (in a rare scenario, a user created an XPF file and manually saved into Worldox).

Summary 1.0.4

Symphony 1.0.4 brings a major change to the workstation user interface - an overview of the changes is described in the following articles on the Symphony Suite Blog:

• New design for Symphony Profiler Reservation Dialog
• Another Similar Button Coming to Symphony Profiler
• Workstation now has an API

Changes

1.0.4.42 -

Bug fix - in some rare scenarios (server disconnect), it was possible for a reservation to be removed from the "In Use" list, even though the reservation hadn't actually been fulfilled or deleted
    S-Pro will no longer mark reservations as deleted unless the XPF file is gone, and at least one of the parent folders of the XPFFile is still present
    S-Pro will not add used reservation markers for any XPF file it finds in Worldox that isn't already marked as being in-use

1.0.4.41 -

Bug fix - some PDFs caused "Problem: Java heap space" errors during splitting
    
1.0.4.40 -

Email notification referred to WDL attachment, but we are no longer attaching a WDL - changed text to instruct user to click hyperlinks instead
Workstation 1.0.4.40 - changes to support interaction with WDSaaS (S-Pro running direct on remote workstation) - the "Enter ID" dialog now contains the filename of the XPF file (this was needed to trigger automated checkin of new files)
    
1.0.4.39 -

Bug fix - Processor wasn't looking in new Updates folder for updates
Bug fix - old Server\Mirror folder is now removed during install
Bug fix - Server\Updates folder now gets purged prior to install

1.0.4.38 -

The location of the Processor setup.exe has been moved from Server\Mirror to Server\Updates - this is to try to keep users from accidentally installing Server when they are doing workstation installs.

1.0.4.37 -

Processor 'Launch failed' dialog now includes information about the computer that is already running Symphony Profiler Processor

1.0.4.36 -

Workstation 1.0.4.36 now has an additional context menu: Check Processor Status - this opens a browser with a view of the current Processor status

1.0.4.35 -

Workstation will now download and display the cover page PDF without using the web browser (it opens directly in the PDF viewer for the workstation).  This is controlled by the BrowserForCovers setting in expressprofile.ini
Workstation\Shared\expressprofile.ini now has some additional values in it - here is a list of all current values:
                [URLs]
                createcovers=<url pattern to use to get PDF with cover pages in it>
                ping=<url to a simple ping request to check is Processor is running>
                status=<url to display Processor status information>
                [Features]
                Barcode=<1 if barcode is allowed, 0 if not>
                BrowserForCovers=0  <tells workstation to use acrobat for displaying cover sheets, instead of in the web browser - this will eventually be removed once we are sure that viewing covers in acrobat has no problems
                [ProcessorInfo]
                Version=Version of Processor
                Host=<name of the workstation running Processor>
                RunAs=<windows user that is running Processor>
Workstation has two new command line arguments: /createcovers and /showhistory

1.0.4.34 -

Workstation Bug fix - launching SymphonyProfile4WD with /makeres caused application crash
 - workstation updated to 1.0.4.34

1.0.4.33 -

Exposed additional tuning parameter (Required Block Count) in Image Processing configuration
Changed the default Required Block Count from 10 to 9 (with it set to 10, a page with the single word TEST on it gets flagged as a blank page.  With it set to 9, it identifies this as content)

1.0.4.32 -

Workstation (1.0.4.32) - Bug fix - double clicking Symphony icon brought up initial Worldox Save As dialog in a way that ignored the user's favorites quick profile settings (in most cases, the wrong profile group was displayed)

1.0.4.31 -

Workstation (1.0.4.13) - Added COM automation interface for Symphony Profiler Workstation
  - Added SymphonyProfiler4WD.Application as primary automation integration point
  - Added object SymphonyProfiler4WD.WDReservationInfo to capture reservation information
  - Application.ShowReservationDialog(WDReservationInfo) method allows triggering of reservation dialog from other programs

See example code

1.0.4.30 -

UI tweaks
    - Add/edit monitored folder dialog used to show "Edit monitored folder" in title, even when adding new monitored folders
    - Add/edit monitored folder dialog is now about 50% wider than it was (hopefully to show more of the path)

1.0.4.29 -

Workstation (1.0.4.12) - Before saving changes to XPF, check to make sure the XPF is actually present - if not, don't save the changes.  This should prevent the user from accidentally re-creating the reservation if it gets fulfilled while they have the reservation open for editing
Help links in email notifications now point to appropriate help spot pages

1.0.4.28 -

Fix NPE on launch of Processor if network folder doesn't contain a Mirror folder - problem will now be logged and bypassed
Improve barcode recognition accuracy on lower DPI scans (e.g. 200dpi)
     - Barcode is now a little wider and a little taller
     - Old cover pages are still supported

1.0.4.27 -

Added Info logging when a reservation ID is removed from the used reservation manager because the XPF has dissapeard
Bug fix - If computer clocks weren't synced up, and scans were done very quickly after making the reservation, it was possible for reservations to be created with a date slightly later than the scan - which would then get flagged as a problem.  To fix this, we now allow a 5 minute lookback period - if the scan is 5 minutes older than the reservation, we flag it as an error - otherwise, we let it fulfill

1.0.4.26 -

Bug fix:  If XPF was modified after creation (i.e. page count adjusted), the scan would be flagged as being older than the reservation

1.0.4.25 -

Handle NPE if input file doesn't exist
Better logging if input file isn't handled (we now include the path of the input file)
If there are multiple pending reservations with the same ID, we won't fulfill reservations for that ID

1.0.4.24 -

If we split a large document (>5 reservations in the input file), we now release processing so matching can occur immediately.  This is a hack way of allowing the splitting to run in parallel with the matching.

1.0.4.23 -

Workstation - Bug fix - When double clicking on a reservation, page count was coming up with an odd large number even if page count wasn't initially specified

1.0.4.22 -

Fix "Unexpected error reading barcodes - bitIndex < 0" error when reading some PDF files

1.0.4.21 -

Workstation updated to 1.0.4.9
  - Bug fix: If Worldox API had not been registered yet, creating reservation crashes Symphony Profiler Workstation
  - Reservations now have a Date= value that tell when the reservation was created (this is captured as the # of seconds since 1/1/1970)
Fix corner case where user could scan, then create a reservation (the most common scenario of this is when the user creates reservation, scans and fulfills, then copies the scan back into the input folder.  Then at some later point (after ignoring error messages from the processor), they re-use the cover sheet and create a new reservation.  Prior to this build, the old scan would fulfill the new reservation.  Now, the scan will get flagged with error 'Problem - scan older than reservation'

1.0.4.20 -

Installer change: Changed the folder selection page so it is very explicit about requiring a NETWORK folder

1.0.4.19 -

Bug fix:  Worldox connection reset wasn't working properly - we now reset the worldox connection every 8 minutes (should fix problem with being able to search against profiles after they have temporarily gone off line)
We now check for expired licenses during running and shut processing down
Email notification now includes info about licenses that will expire in the next 30 days

1.0.4.18 -

Improvement to despeckling algorithm (better handling for small black dots in a white field)

1.0.4.17 -

Admin guide link now goes to knowledge book instead of PDF
Workstation updated to 1.0.4.7
  - Right Click -> User Guide now goes to knowledge book
Workstation updated to 1.0.4.8
  - Workstation now logs all reservations created by each user to the network Workstation\logs folder
Processor now logs purges of the usedres.dat file

1.0.4.16 -

Make sample image have modified date of 'today'
During install, we now log the version of installer to Trumpet-UpdateHistory.txt
New version of workstation - 1.0.4.6
- Bug fix - workstation crashed if UsedRes.dat file wasn't writable by the user - we now provide a meaningful error message

1.0.4.15 -

Bug fix: Not recognizing barcodes in some PDFs (MediaBox offset issue)
Overhaul of check for updates dialog - added Pre-release and Production release as separate download links, plus clickable update instructions and release notes

1.0.4.14 -

Added httpServerConfig section to config.xml - this has a useIpAddress setting that can be used to control whether S-Profiler will use IP address or host name in the URLs it provides to the workstation component

1.0.4.13 -

Fixed 'Unexpected error.... Width (-xxxxx)' error in some PDF files

1.0.4.12

Fixed problem with WDL links in email notifications not working properly in some browsers

1.0.4.9

Added support for TLS and SSL authentication in email configuration
Added daily heartbeat functionality
Workstation change:  Coversheet menu will now be hidden instead of grayed out for users not licensed for barcode handling

1.0.4.7

Improved error handling if Worldox license itself is invalid
Workstation - Added new Symphony Banner user interface to all dialogs
Workstation - overhaul of how we interact with the Worldox API - eliminate crashing issue on slow workstations

1.0.4.6 -

Bug fix - If reservations are fulfilled at exactly the same time that the reservation list was being refreshed (or if the WD indexer is shut down), and the reservation number was used in the last 60 minutes, a new version of the original fulfilled document is created instead of the new file being created

1.0.4.4 -

Workstation will now retry connection to home server up to 5 seconds before it errors out
Added watermark banner to Get Reservation ID dialog
Better handling of scans that have lots of white dots in the black bars (New image despeckling algorithm)

1.0.4.1 -

** moving to a new minor build number to reflect significant UI changes
High performance support for huge >~2GB files
New Workstation applet:
 - If back-end server is down when creating cover pages, the user gets a meaningful error message instead of a "Page could not be found" browser page
 - separate dialogs for old behavior (manual keyed reservation) vs new (barcode cover sheets)
   ** Note - it is no longer possible for the user to switch between barcode and manual key entry operation modes
 - Complete overhaul of the ID from Cover Page dialog
   a) validation messages are displayed next to the field they apply to
   b) Advanced options are grouped together (right now, there is only one advanced option, but I expect this to grow)
   c) Print Covers is now a less obtrusive hyperlink (instead of a button)
   d)  Data entry prompts appear next to each field (in addition to validation)
 - Complete overhaul of the "manual keyed reservation ID" dialog
   a) Everything that could be removed has been
   b) It is no longer possible to specify a page count from this dialog
 - Addition of Another Similar button - this brings up the exact same profile as the previously saved reservation (including document description)
 - Short cut keys= Alt+S = Another Similar.  Alt+A = Another.  Alt+O = OK

...