General Requirements

Assemblage is generally installed to a network folder on your file server (nothing is actually "installed" to the server, though).

The server should have enough free disk space to contain several copies of all of the content used in assemblies.

Workstations then launch Assemblage using a shortcut.

The workstations running Assemblage have the following requirements:

• Windows 8 or higher (32 and 64 bit versions of Windows 7 and Server 2003 or 2008 are also supported)
• At least 2GB of RAM

Assemblage is in use in a number of terminal server based sites (including as a published app).

Requirements for Printing Support

Adobe Reader or Adobe Acrobat version 6 or above.

Printer capable of desired printing tasks (e.g. double sided, paper tray pulls, stapling - if those are important to you).

Requirements for Axys Interaction

In order to utilize the Scripter Tool, Axys must be accessible via a mapped network drive on the workstation running the Scripter tool. 

Axys requires that Adobe Acrobat (full) be installed to support generation of PDF files.  Please check with Advent for version requirements matching your version of Axys.

Axys also has interesting requirements about supported versions of MS Office - please refer to their technical support.

If you can run a report in Axys, then use the File > Save As, then choose the PDF format and actually get a PDF file, then that workstation is fine.  Note that this procedure uses the *internal* PDF Save As operation in Axys - printing directly to the Acrobat print driver is NOT a sufficient test.

Requirements for Email Delivery

Email is sent via standard SMTP connection - you will need to know your SMTP server name and any credentials required to send emails.

Requirements for Bulk Conversion of Excel or PowerPoint

One of the following PDF print drivers must be installed to the workstation doing the conversion:

• Attach Plus (www.attachplus.com)
• Adobe Acrobat 6 or above

Requirements for Portfolio Center Integration

No special requirements, as long as the user has access to the Portfolio Center SQL database.

Requirements for Bulk Upload to Web Portals

As long as the web portal supports bulk upload (uploading of multiple documents for multiple clients), Assemblage should be able to integrate with it.

Assemblage Consultant Requirements

The Assemblage Consultant will require:

• Full access to the network drive to which Assemblage is installed during the time in which they will be configuring the software
• The workstation and Windows user must have access to SQL databases we will need for your particular configuration (e.g. Junxure, Portfolio Center, Advent Axys, etc.)
• If you are using Advent Axys, the workstation *must* have Adobe Acrobat installed.  This is a requirement of Advent Axys, not Assemblage (Note: Adobe Reader is not sufficient, Adobe Acrobat is required)
• Trumpet utilizes ScreenConnect for our remote connection to the workstation.  Please ensure that your firewalls are set up to allow us to access the workstations necessary for our configuration and training. 

Assemblage itself runs only on user desktops (or as a simple published app) - there are no services installed or changes made to the file server except for the creation of a shared network folder.

During installation, the Assemblage executable and configuration files are installed to a network drive.

Assemblage should be installed to a network drive accessible by those in the firm who will need to use the software (e.g. X:\Assemblage).  This does not need a dedicated network drive, and can be installed to an existing location. This network drive should have enough disk capacity to hold all the content that will be included in your report packages.

1)    Download and save the Assemblage Installer file provided to you via email
2)    Double click on the installer executable to run the Installation Wizard
3)    Click "Next" at the Welcome window
4)    Read the Software License Agreement and select "I Agree"
5)    Select "Browse" and locate the network location (drive letter) to which you wish to install Assemblage
6)    Select "Install"
7)    Navigate to X:\Assemblage (where "X" is the network drive to which Assemblage is installed) and double click on the Assemblage executable file (assemblage.exe) to launch
8)    If Assemblage prompts you to install a Java runtime, follow the prompts (this is a one time installation that will be done on each workstation as the user launches for the first time)
8)    When prompted, copy and paste the license number provided to you via email
9)    Click "OK"

Assemblage should now be installed on your network.

The Assemblage Scripter Tool uses globally defined Axys settings when generating Advent Axys Reports.

This configuration is available from the main Assemblage application, Tools->Preferences, Axys:

Fill in the network path to Advent Axys in the "Axys Path" field.

If the firmwide.inf file is located in a directory *other* than the directory identified in the Axys Path field, you should specify the firmwide.inf path in this field.

What is Advanced Printer Configuration?

Advanced Printer Configurations allow you to print your assemblies with different rules for each section.

In other words, you may wish to print certain sections of your Assemblies double-sided or staple a portion of your Assemblies together.

How to Configure Printer Presets

The first step in applying Advanced Printer Configuration is to configure Presets for your printers. Here's how to set that up:

• From the main Assemblage screen, go to Tools -> Preferences
• Select "Printers" from the Navigation panel on the left.
• Highlight the printer you wish to use from the list of available printers.
• Select "Add"
  
  

This will open the add preset dialog.

• Give the preset a Preset name (e.g. Doublesided, or Doublesided and stapled).
• Click the "Configure" button.
• This will open your printer preferences dialog where you can define the way you want your printer to be configured for this preset.
• Add the settings you want and click "OK".

You can add as many presets as you need, including printing from different trays for letterhead paper, doublesided, etc. Whatever your settings your printer will allow you can add a preset.

Next, you can click the "Test" button to test that you have the printer configured in the way you wish it to be set up.

Use your Printer Presets

From the main Assemblage application, load the configuration you wish to use to Print.

Highlight the Assemblies you wish to print, right click and choose Send to -> Printer.

Select the appropriate printer from the drop down menu for printers:

In the "Use Preset" column, select the drop down menu and choose the preset you wish to apply to that section of the Assembly:

Here, we're printing the Cover Letter DoubleSided.

If you wish to apply the preset to all the sections included in a branch, you may do so. For example, if you wanted to staple all the reports together for a particular account, you might opt to staple at the Reports Assembly level:

Once you have your presets defined, simply select the "Start Printing" button.

Background

The Assemblage Emailer Tool can either use a globally defined mail server configuration settings when sending emails, or can use your instance of Outlook.  These instructions apply to those firms who wish to use a globally defined mail server.  This is useful if your firm doesn't use Outlook as your email handler or uses the 64-bit version of Outlook.

Note:  Because Assemblage is a 32-bit application, it does not integrate with the 64-bit version of Outlook.

Configuring the Globally defined configuration settings:

This configuration is available from the main Assemblage application, Tools->Preferences, Email, or in the Emailer tool directly.  You can access a shortcut to the emailer tool under "Tools -> Preferences" in the Emailer tool directly.  To access the Emailer tool directly, navigate to X:\Assemblage\Tools (where X: is the network drive where Assemblage is installed)

Please work with your system administrator to get the SMTP Server properties configured for your specific mail server.

The From address will be the address the test email will be sent from.  The To address will be the address the test email will be sent to.

Testing

It is very important to click the Send Test Email button and confirm that you get a green checkmark.  You should also confirm that the recipient (To address) receives the test email.

Having trouble?  Here's a link to: Troubleshooting Tips

Note for Office365 Users

See below for the SMTP Server settings if you use Office365.

Assemblage often utilizes a firm's existing SQL Databases to collate various pieces of content.  Trumpet establishes those connections via Windows authenticated connections. 

This configuration is available from the main Assemblage application, Tools->Preferences, Database connections:

You can have multiple Database connections

To add a database connection, select "Add"

When the "Add..." window opens, provide a Connection name (typically the name of the software):

The Connection URL field should be completed as follows:

jdbc:jtds:sqlserver://<servername>/<databasename>;instance=<instancename>

Where you replace the "<servername>" with the actual server name, <databasename> with the actual database name and <instancename> with the actual instance name

Encryption

If your SQL server requires SSL encryption, you will need to add ssl=required to the end of your Connection URL. 

e.g. jdbc:jtds:sqlserver://SRV2014/JUNXURE;instance=JUNXURE;ssl=required

e.g. jdbc:jtds:sqlserver://SRV2014/PC;instance=PORTFOLIOCENTER;ssl=required

If you have a set user that you would like to set for accessing the Database you can add the following to the string:

";user=<username>;password=<password>"

e.g. jdbc:jtds:sqlserver://<servername>/<databasename>;instance=<instancename>;user=<username>;password=<password>

Testing

To ensure that you have access to the appropriate database, select "Test Connection"

If your connection is set properly, you will see the a green check, along with the dialog that says "Successful connection made!"

Assemblage may utilize a firm's existing SOQL (Salesforce) Database to collate various pieces of content. This requires Assemblage to log into the Salesforce API.  When you log into Salesforce from an outside application (Assemblage) using the Salesforce API, you must to add a security token to the end of the user's password.

Prior to setting up your Salesforce Connection in Assemblage, you must obtain this security token.

Obtain a security token from Salesforce

From Salesforce:  Navigate to Settings > My Personal Information > Reset My Security Token.  This will send a token to the user.

Once you have the security token, you are ready to configure the connection for Assemblage.

Configure Assemblage to connect to Salesforce

This configuration is available from the main Assemblage application under Tools > Preferences > Salesforce connections:

Enter the Salesforce username in the Salesforce user field

Enter the password and security token in the Password field (enter your password first immediately followed by the security token, without any spaces or characters in between)

Select "OK"

Assemblage enables your firm to automatically and electronically collate, assemble, file and deliver PDF documents to clients and other recipients.  In order to accomplish all of this, there are many tools available for use within the Assemblage software.  You may use some or all of these tools in your particular configuration.  This document covers all of the tools.

There are 4 main activities that you will perform with Assemblage

1. Create Content: create the individual pieces of content that will be assembled (e.g. Cover Letter, Reports, Market Commentary

2. Assemble:  pull or collate like content together by recipient

3. Deliver: print, upload to a web portal, or encrypt for e-mail delivery

4. Archive: file the assembled content to your network directory structure, CRM or DMS

Assemblage should be installed to a network drive accessible by those in the firm who will need to use the software (e.g. X:\Assemblage)

Within the Assemblage folder, you will have a structure that looks similar to this:

The important aspects of this folder are as follows:

1)  Assemblage.exe - This is the actual Assemblage application.  You can open the application by double clicking on this executable.

2)  Workspace Folder - This folder contains subfolders for each of the various "Projects" you have for Assemblage.  In this example, there are two projects, one for Quarterly Reports, and a second for Tax Reports.

Within the Workspace Folder, you will have several sub-folders:

Assembler In -  This folder contains additional folders for each "Section" of the Assembly (e.g. Performance Report, Market Commentary, etc).  The contents of these folders should be PDF files

Config - This folder contains the configuration files or instructions for the various tools you will use to generate, assemble, deliver and archive.

Splitter In - This folder contains additional folders for each "Section" of the Assembly that requires splitting.  These are typically mail merge documents (e.g. Cover Letter from your CRM).

Upload - This folder contains the contents for uploading to your portal.

Working - This folder contains Assemblage's working files.  You will not need to access this file.

 

To open Assemblage, simply double click on the Assemblage.exe file in your directory structure.

You may wish to add a shortcut to Assemblage or an Assemblage Tool on your desktop for faster access. 

To do so:

For Assemblage:

Right click on the Assemblage.exe file in your Assemblage directory and select "Copy"

Right click on your desktop and choose "Paste Shortcut"

For Assemblage Tools, such as Autofiler or Publisher for ShareFile,

From your Assemblage Directory select the Tools Folder

Select the Tool you want to add the shortcut for, right click and "Copy" as with Assemblage

Next, Right click on your desktop and choose "Paste Shortcut"

You will need to clear the content of your assemblies prior to generating the content for your next reporting cycle.  There are a couple of methods for doing this:

1. Navigate to the Assembler In directory and delete the contents via the network directory structure.  You will want to ensure that you do not delete the folder directly beneath the Assembler In folder but merely delete the content itself.
2. Use Assemblage's Delete Files option.
   
   • In the "Sections" area of Assemblage, select the section in which you wish to delete the contents (reports)
   • Right click and select "Delete Files"
     
     
   • Select "Yes" to delete the files:
     
     
   • Repeat for each section in which you want to delete the content
     Note:  You will only want use this method for deleting *all* the content for a given section.  If you wish to delete a single file or only a few files, you can do so in the Details Pane.  See more information on this by referencing the following link:  Details Pane
     
     
     

Assemblage will *only* assemble PDF files.  Therefore, the content to be assembled must be in PDF format.

Assemblage utilizes several tools to create content.  The tools that you will utilize will depend largely on the source used to generate the content and how that source generates the content, and some of the content will not require an Assemblage tool at all to generate.

The Tools and their usage are as follows:

PDF Splitter - This tool is used to split PDFs that contain content for multiple recipients, clients, or portfolios.  This is typically used to split mail merged documents into one pdf per recipient.  An example of this may be an Address Sheet or Cover Letter.

Scripter -

Axys Runner - The Axys Runner (within the Scripter tool) is used to generate PDF Content from Axys. 

PPT2PDF Converter - The PPT2PDF Converter is designed to take existing Powerpoint documents from a directory structure and convert them to PDF.  You will only utilize this tool if your firm has the need to convert Powerpoint files for multiple clients, recipients, or portfolios on a large scale.   An example of this might be a powerpoint presentation that is customized per client.  You would not use this tool for converting a piece of static content that all clients will receive.

XLS2PDF Converter - The XLS2PDF Converter is designed to take existing Excel documents from a directory structure and convert them to PDF.  You will only utilize this tool if your firm has the need to convert Excel files for multiple clients, recipients, or portfolios on a large scale.   An example of this might be an Invoice or Statement that is customized per client.  You would not use this tool for converting a piece of static content that all clients will receive.

Unzipper - This tool is used for special zip files.  The purpose of this tool is to unzip the contents of a .zip file into a directory structure with a naming convention which will be used for Assembling.

1. From the Assemblage Tools folder located at X:\Assemblage\Tools (where "X" is the network drive in which Assemblage is located), double click on the Axys Scripter tool
2. If you use the full version of Assemblage, you can launch the tool by opening Assemblage, and selecting "Tools -> Scripter"

Select your Configuration 

Tip:  You can use "Recent Configurations" to load the configurations you've recently used.

Adding the Items to Process

Assembling is really pulling together or collating like content together by recipient.  Assemblage uses multiple methods for mapping content together so that you can view, deliver, and archive the content.

Background & Purpose

The purpose of the Assemblage tool is to Assemble generated content into a single PDF file per recipient.

Launch the Tool

Open Assemblage by double-clicking on the Assemblage.exe file in your Assemblage directory.

Select your Configuration

Select "Configuration > Open".

Understanding the Assemblage Dialog — Sections Panel

The Sections panel of the Assemblage tool is your window into what you're viewing in the Assemblies panel.

How to view sections:

When you load an Assemblage configuration, by default you will be displaying the Assemblies in that configuration at the sections "highest" level.  In the following illustration, this is the Final Assembly.

The Assembly that is showing has (showing assemblies) next to it and is in bold font.

If you wish to view the Assemblies or content of another Section, you can simply double click on that section, or if you prefer, select the section, right click and chose "Show Assemblies"

In the illustration below, I have selected the Reports Assembly, and this is only viewing those assemblies in the Assemblies pane.

Finally, if you select an item that is not an assembly, but rather a section within that assembly, you will see that content.

This is useful when troubleshooting why a piece of content might not be matching up to its' parent assembly.

Disable Content –

You may have a need to disable a piece of content for a certain reporting period.  While you can certainly choose not to generate the given report, you will still be presented with Issues that might make your Quality Assurance process difficult.  Therefore, you can opt to disable the section.

To do so, simply highlight the section you wish to disable (this can be an Assembly or a piece of content within the Assembly),  and select "Toggle enabled"

 This will disable the content.

Disabled content will be displayed with a greyed-out icon.

This can also be useful in situations where you want to review certain pieces of content, like the reports, but not others (like the Cover Letter), or where you don't yet have the content but want to begin your review process without seeing Issues in the Issues lists.

Another situation where this might be useful is if your reporting sets automatically generate Year to Date and Quarterly Reports.  In the first quarter, of course, the Year to Date values are the same as the Quarterly, so most advisers only send out one.  Therefore, you could disable the content of the Year to Date report.

Understanding the Assemblage Dialog — Assemblies Panel

The Assemblies Pane is a list of all of the Assemblies in Assemblage.  Here are some tools and techniques for making you even more efficient in using the Assemblies Pane.

Sorting

You can sort on any of the columns within the Assemblies pane.  Just click on the section and it will sort.   While the fields in the pane vary based on your particular needs (you may have a Delivery column, or several columns for the various delivery types).  If you'd like to see all of one particular type of Delivery Method, simply click on the Column Header.  

The triangle next to the field represents the fact that you are sorting on that column and whether or not you are sorting in an ascending or descending fashion.  To change the sort, just click on the field again. 

You can also sort on multiple columns.  For example, you might wish to sort by Delivery Method and Advisor because a particular advisor has reviewed their reports and you're ready to deliver only those.

In the example above, the Advisor with the initials MD has told the Assemblage operator (that's you) that their Assemblies are ready to go.  So, you sort by Advisor / descending because MD falls alphabetically towards the end of the list.   Next, you sort by Delivery Method so that you can email, Print, and then upload her respective reports.

Select Multiple Assemblies

The Assemblies pane allows you to select some or all reports in a lot of different ways.  You can use "Shift + Clicking" and "Ctrl + Clicking" as you would in the Windows Explorer.

Using the example above, if the Assemblage Operator (that's you again!) wanted to send the emails for MD, you would highlight the BLAKEBI1 Assembly by selecting it with a mouse click, then hold down your shift key and highlight MOONLI1.  This will highlight all of those Assemblies which you can then choose to email.

Alternatively, if you haven't sorted, or wish to be more selective, you can use "Ctrl + Clicking".  To do this, simply select the first assembly, select the CTRL key on your keyboard, and then use your mouse to click the other entries. 

Finally, if you want to select all the Assemblies (maybe you want to print them all for review), selecting Ctrl+A on your keyboard will highlight all the Assemblies.

Preview Multiple Assemblies as one Document

Now that you understand how to select multiple Assemblies, I want to share a cool tool with you which is how to view multiple assemblies as one PDF document. 

Perhaps you have an advisor who wants you to provide them with one PDF with all their clients Assemblies in it so they can view them electronically and not have to open / close multiple PDF files.

This is really easy to do.  Simply select that advisor's assemblies using the methods above, right click on one of them, and choose "Preview".  This will open one large PDF with all of the Assemblies in them.

Here's an example of a large PDF with Multiple client's reports included:

There's no magic going on here now, this PDF is a document that you can file elsewhere on your network, or if you prefer, you can teach this technique to the Advisors as well as you can run Assemblage from any number of workstations!

ID Filter

People often ignore this really powerful field, but it's incredibly useful.  For example, if you want to find the Assembly for Sarah Wasatch, you can simply start typing her Assembly ID into the ID Filter field.  Assemblage will filter the list based on the characters that you have typed in:

If you want to see Assemblies that have the letter "C" in them, just put a "C" in the ID Filter field:

Understanding the Assemblage Dialog — Details Panel

When you highlight an Assembly in the Assemblage application, the Details area shows you what's going to be included in that Assembly.  Reviewing this can be instrumental in determining what (if any) issues an Assembly might contain, and the order in which the content will appear in the final assembly.  Viewing this is similar to viewing a Table of Contents of what is included in the Assembly. 

But that's only the beginning of what the Details pane can be used for – this email covers the really neat tools that the Details view gives you.  Master these, and you'll be well on your way to being an Assemblage power user.

Preview a single piece of content

You can double click on that file and Assemblage will launch the PDF of just that piece of content.

If you right click on a piece of content, you can do the following:

Preview

Preview the content.  This is a preview of what the document will look like when assembled.

Tip: If you select multiple pieces of content, then Preview, you will get a PDF with just that content included.  This is very handy for shooting someone a question about a couple of reports in an assembly.

Delete file from disk

Delete the file.  This works well, for example, if you have run a report for a client who should not receive it.  You can simply right-click and delete the file from disk (you should also remove that file from the group or set so you needn't have to delete it each quarter).  This also works well when reviewing the ##MISSING## Assembly, if you have files that appear there that shouldn't be (for example, your Cover Letter merge includes a new client that shouldn't get a Quarterly Report yet).

Edit file on Disk

Need to add a special note to a cover letter for a particular client?  Selecting Edit file on Disk opens the PDF in the network directory structure and will allow you to annotate the PDF (assuming you have a PDF Editor on your workstation).

Understanding the Assemblage Dialog — Issues Panel

Want to check to see which assemblies might be missing content without printing them all out first?  Want to see how many of your assemblies might have issues without scrolling through the Assemblies list?  Aren't sure why there is an issue with an Assembly?  Here are some tools to help you:

View All issues

If you want to see what issues you might have in all your assemblies, simply run your Assemblage Configuration without clicking on any assembly in the Assembly list.

You can see a list of all the issues in the Issues section in the bottom panel of Assemblage.

This panel provides you with a description of the issue (on the left) and the Path to which Assembly is having the issue (on the right).  Here we can see that 3 Assemblies have issues. 

So, you can see in the illustration above that EVERBO01 should be getting an invoice, but there is no Invoice that matches the Assembly ID.  This is a list of all of the issues for the set of Assemblies you have run.

If you'd like a list of all assemblies that are missing a particular piece of content, you can sort the Description list.  For example, you might want to sort this list so that all the Assemblies that don't have an Invoice are together so you can set up my Portfolio Management Software to include those clients in your batch print jobs.

Sort Assemblies by the Issues Column

You can also sort by the Path if you want to order the Issues by Assembly ID.  Simply click on the Column to sort it.  When you're reviewing the Assemblies with issues, you may want to Sort the Assemblies by those that have issues so that you can go through them one at a time.

To sort the Assemblies, click on the Issues Column:

The Assemblies with the most issues will float to the top of the list.

View the Issues for one particular Assembly

You may wish to only view the issues for one particular assembly at a time.

To do this, simply select the Assembly in the Assemblies list and view the Issues information at the bottom of the screen:

In the above illustration, this Assembly is missing an Invoice.

Finally, it's really important to understand that Assemblage does not prevent you from Delivering Assemblies with Issues.  For example, you might have a situation where a new client doesn't have enough history with your firm to produce a Year-to-Date Report, so one was INTENTIONALLY not run for that client.  You can still assemble the rest of the reports for the Assembly and deliver the available content.

 

• Missing Identifiers in your various databases

• Identifiers entered incorrectly in your various databases (e.g. typo)

Note:  See your Assemblage Configuration Summary Sheet for information on how content is mapped to assemblies.

Purpose

Some firms have workflow needs that require tracking within Assemblage.  This can be achieved in Assemblage by utilizing Custom Tags.  Your Assemblage Advisor can assist you in setting up the columns.

How to Use

Custom tags can be anything you'd like to assign to a particular assembly.  In our example, we'll be using the date a particular assembly was printed.

Add Custom Tags:

Highlight the Assembly(ies) you wish to tag, right-click and choose "Custom Tags" (select from the available custom tags):

In the Modify Tag window, confirm the number of Assemblies you wish to tag, and choose the "Set Tag(s) to:" radio button:

Type any value you'd like into the window below:

Select "OK" to add the tag:

Clear Custom Tags:

Upon completion of your reporting process, you may wish to clear the custom tags.  To do so:

Highlight the Assembly(ies) in which you wish to clear the tag, right-click and choose "Custom Tags" (select from the available custom tags):

In the Modify Tag window, confirm the number of Assemblies in which you wish to clear the tag, and choose the "Clear Tag(s)" radio button:

Select "OK" to clear the tag:

Introduction to Delivering Assemblies

Note: For all delivery options, you can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Print your Assemblies

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Advanced Printing

Advanced Printing features are available if your printing process requires stapling, and/or different tray pulls

You will send the assemblies to the Print Job Manager the same way that you would if you did not require Advanced Printing, however, when the Print Manager opens, you will have some additional steps:

For each section that you wish to use one of your configured printer settings, you will add that configuration to the Printer Setting column.  Click in the box and choose the configuration from the drop down menu.

 

Background:

We have added options to print with Adobe or another PDF rendering program to Assemblage.

Process:

In Assemblage select Tools> Preferences 

That opens Preferences window. In that window select the Printers option in the left hand panel.

Here you can set the Printing Strategy. The choices are Use Internal PDF Renderer or Use Adobe Renderer. If you have specific Adobe print settings for your reports you can set the Strategy to Adobe Renderer.

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Zipping your Assemblies

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

 

Removing Specific Files From ClientView

Background & Purpose

The ShareFile folders option allows you to send files to the ShareFile portal where your recipients can log into the portal to receive the Assemblies.  You must have a ShareFile account to utilize this method of delivery.

Upload files to ShareFile

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Right click and choose "Send to -> ShareFile folders"

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Archiving is essentially filing your assemblies to their final destination for compliance purposes, or for future reference.

There are several tools for archiving:

Bulk PDF File - Although not used often you might want to archive your Assemblies as one single PDF document containing all your assemblies.

Send-to Folders - This method for archiving simply sends the selected assemblies to a folder on your network naming them with the Assembly ID.  While it is a method for archiving files, this is typically done during the review process.

File System Auto Filer - This tool archives files to a folder structure on your network, where the files can be named and stored in a particular folder structure using database look ups.

Encryptor - This tool for archiving files to a folder structure on your network and is similar to the File System Auto Filer.  It applies encryption and password protection to the filed documents.  While this is not a common method for archiving, if your firm requires this level of encryption, it is possible to apply.

Worldox Auto Filer - This tool for archiving files to the Worldox Document Repository

Net Documents Auto Filer- This tool is for archiving files to the NetDocuments repository

Background & Purpose

This method for archiving is very basic and simple.  It will generate one PDF file which contains the Assemblies that you have selected.  You may wish to utilize this for Advisor Review for example, to provide the advisor with a single PDF file with all their client's assemblies in it.

Using the Bulk PDF File Method

Select the Assemblies you wish to include in your PDF File.

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Right-click and choose Preview

This will open a single PDF file with all the Assemblies you selected included

You can then save this PDF file to any location on your network using any naming convention you please.

Background & Purpose

This Feature simply sends the selected assemblies to a folder on your network and names the PDF file with the Assembly ID.

Using the Folder method

Select the Assemblies you wish to archive.

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Right Click and choose Send To > Folder

The Choose Destination Folder window will open:

Select the appropriate folder, (or you can create a new one).

and Select OK

You will receive a prompt that the files have been filed

To view them simply select "Yes" and the Folder will open

Background & Purpose

This tool archives your assemblies to a folder structure on your network, and allows for files to be named and stored in a particular folder structure.

Use the File System Autofiler

Select the Assemblies you wish you file.

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

 

Background & Purpose

The Encryptor Tool is used for archiving files to a folder structure on your network and is similar to the File System Auto Filer.  It applies encryption and password protection to the filed documents.

Using the Encryptor Tool

Select the files you wish to file and encrypt.

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Background & Purpose

The Worldox Autofiler tool is used for archiving files to the Worldox Document Repository.  This can only be used by firms that use the Worldox Document Management System.  Worldox must be running on your workstation in order to use this tool.

Using the Worldox Autofiler

Select the assemblies you wish to file to Worldox

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Double click the appropriate configuration (instructions) or select "Choose Another" and select the file from the appropriate Workspace\Project\Config folder.

 

If you have a YYYYQQ in any of the fields, change that to have the appropriate year/quarter information.

 

Sort the list of items to be filed by selecting the "Problems" column.

 

 

Resolve any issues that you may have and select "Configuration > Reload"

 

 

If you wish to save all the files in the list to Worldox, select "Save All Files", if you wish to save only the highlighted files, select "Save Selected Files"

If you wish to cancel the file saves at any point in time, select "Cancel" (any files that have a green check in the Save Result column will have been saved, and you will need to delete them directly from Worldox)

Select the Assemblies you wish to file to NetDocuments

Note:  You can select all or a portion of the assemblies using the common Windows keyboard commands (Ctrl+A will select all the assemblies on the list.  Shift+click and Ctrl+click work in this pane as well).

Right-click and choose Send To > NetDocs Autofiler

Double click the appropriate configuration (instructions) or select "Choose Another" and select the appropriate Workspace\Project\Config\ folder.

On Version 2.3.83 The Publisher Tool interface will Show a button, "Connect to NetDocuments"

Clicking on the Button will open a Browser window to the NetDocuments Sign in screen. After Pressing Login the Browser Screen will update to show "Connected to NetDocuments - please go back to Assemblage/NetDocs Autofiler to continue"

From there the Autofiler will connect and be ready for you to upload files.

Note:  NetDocuments requires that users log on and approve access by a given application.  This means you will need to authenticate to NetDocuments when you launch the tool.  If possible, the NetDocs Autofiler will re-use recent credentials, but NetDocuments times sessions out after about an hour, after which you will need to authenticate again.

Opening your Assemblage configurations on a new computer for the first time is a pretty simple Process. This guide will walk you through that process. This process works the same for the main Assemblage Configurations as well as the other Assemblage tools.

1.Open Assemblage and in the upper left corner Click on "Configuration" then "Open"

You will get a window that looks like this.

4.Now you'll see all the internal folders of the project. The one that you want to open is the "Config" folder.

5.Now you should see the familiar names of your configuration files. You can now select the one that you want to open.

After you load the first configuration Assemblage will remember that config folder that you last loaded from. If you want to load a config from another workspace you simply need to push the "up a folder" icon twice to get back to your Workspace folder.

Repeat steps 3 to 5 for the next configurations that you want to load.

Once the configuration has been loaded it will be remembered in the "Recent" list for future use.

General Requirements

Assemblage is generally installed to a network folder on your file server (nothing is actually "installed" to the server, though).

The server should have enough free disk space to contain several copies of all of the content used in assemblies.

Workstations then launch Assemblage using a shortcut.

The workstations running Assemblage have the following requirements:

• Windows 8 or higher (32 and 64 bit versions of Windows 7 and Server 2003 or 2008 are also supported)
• At least 2GB of RAM

Assemblage is in use in a number of terminal server based sites (including as a published app).

Requirements for Printing Support

Adobe Reader or Adobe Acrobat version 6 or above.

Printer capable of desired printing tasks (e.g. double sided, paper tray pulls, stapling - if those are important to you).

Requirements for Axys Interaction

In order to utilize the Scripter Tool, Axys must be accessible via a mapped network drive on the workstation running the Scripter tool. 

Axys requires that Adobe Acrobat (full) be installed to support generation of PDF files.  Please check with Advent for version requirements matching your version of Axys.

Axys also has interesting requirements about supported versions of MS Office - please refer to their technical support.

If you can run a report in Axys, then use the File > Save As, then choose the PDF format and actually get a PDF file, then that workstation is fine.  Note that this procedure uses the *internal* PDF Save As operation in Axys - printing directly to the Acrobat print driver is NOT a sufficient test.

Requirements for Email Delivery

Email is sent via standard SMTP connection - you will need to know your SMTP server name and any credentials required to send emails.

Requirements for Bulk Conversion of Excel or PowerPoint

One of the following PDF print drivers must be installed to the workstation doing the conversion:

• Attach Plus (www.attachplus.com)
• Adobe Acrobat 6 or above

Requirements for Portfolio Center Integration

No special requirements, as long as the user has access to the Portfolio Center SQL database.

Requirements for Bulk Upload to Web Portals

As long as the web portal supports bulk upload (uploading of multiple documents for multiple clients), Assemblage should be able to integrate with it.

Assemblage makes it easy to copy the tables within the main Assemblage application or the other tools.

In version 2.2 and higher, You can now right click and choose "Copy Selected" which will copy the tables to your clipboard, where you can paste to an excel spreadsheet or text file.

The following is a list of software that we have integrated with.  It is not exhaustive, so if your software isn't listed, chances are still very good that we can integrate with it.

Contact Management Software

Assemblage will integrate with most Contact Management Software.  Here are a few examples:

• Junxure
• Junxure Cloud
  
• ProTracker (Access and SQL Versions)
• Maximizer
• Access
• Microsoft CRM
• Sales Logix
• Salesforce
• Tamarac's Advisor CRM
• GoldMine
• ACT

Note:  If your CRM is cloud-based, we may require an export from that CRM to integrate as we cannot read databases that are not stored on your system.  This is an easy step.

Portfolio Management Software

Assemblage will integrate with most Portfolio Management Software.  Here are a few examples:

• Portfolio Center
• Advent Axys
• dbCams
• Morningstar Office
• Black Diamond
• Orion
• Tamarac
• Advyzon
  

 Note:  If your Portfolio Managment software is is cloud-based, we may require an export from that CRM to integrate as we cannot read databases that are not stored on your system.  This is an easy step.

Web Portals

Assemblage integrates with any portal that allows for bulk upload.  Here are a few portals that we have integrated with:

• ShareFile
• Wealth Access
• Box.net (in conjunction with Box.net synch functionality)
• Junxure's ClientView — On Premise
  
• ModestSpark
• AdvisorVault (including AdvisorVault's Desktop Connector)
• ElevateCDS (Formerly FamilyOfficeNetwork)
• InvestCloud (Formerly Light[PORT])
• IAS (Interactive Advisory Software)
• Tamarac's AdvisorView Portal
  

 Document Management Systems

• Worldox
• Share Point
• NetDocuments
• "Light" DMS systems part of popular CRMs
• Windows folder tree

When your Assemblage license has expired, the steps to update it are easy:

Note: If you do not have the new license or would like to renew your license, please open a support ticket at http://support.trumpetinc.com/

1. Launch Assemblage
2. Select "Tools"
   
3. Click on "Preferences"
   
4. In the "Preferences" window, select "License"
5. Enter the new license into textbox and click "Add License"
   
   Note: If you would like to delete the old license, select it and hit the "Remove" button.

This page is designed to discuss known file naming conventions for Worldox Autofiler purposes:

 Portfolio Center Reports

Black Diamond Reports

Schwab 1099s

Fidelity Statements

 Morningstar Office Reports

Tamarac (AdvisorVault) Reports

If the item you wish to auto-file is not listed, please contact a Trumpet Support representative to request further information.

Assemblage only creates Assemblies if there is content for a given recipient.  If there is no content, it will not generate the assembly for you to deliver or archive.

Therefore, to prevent having an Assembly for a former client you should not create content for them.  Here's a sampling of how you can prevent generating the content:

Contact Management Software - Remove the client from the "Rule" that you are using to generate your address sheets and / or cover letters.

Portfolio Management Software -

1. Portfolio Center - Remove the group or accounts from the sets that you utilize to run your batch jobs
2. Advent Axys- Remove the group or accounts from the master group or other source that you use to generate your reports

Note:  The list above isn't meant to be exhaustive but to provide you with some suggestions for how to prevent the generation of content.

If you do generate content for a former client and do not wish to deliver or archive this content, you can delete it by accessing it via the Details Pane in Assemblage.  It is recommended that you remove the Client from the source at the time that you do this so you aren't continually having to delete it.

Trumpet doesn't not recommend a specific vendor for purchasing window envelopes.  You may opt to go with purchasing them from your printer company or your office supply store.  If those aren't options for you, here are some websites we've found that will print logos and / or return addresses if you'd like:

Envelopesuperstore.com
ActionEnvelope.com
Printusa.com

Background

Assemblage is designed to be installed to a Windows network folder.  This folder typically holds both the application executable binaries as well as the shared content that is used by all users.

SharePoint is not a true Windows file server, so the effective install location of Assemblage is different for each user (SharePoint places the folders in the user's Windows profile).  As a further complication, attempting to stream the Assemblage application files (instead of having them available on a local disk or low latency network share) does not work very well.

The following procedure addresses these issues and allows Assemblage to work when installed to a SharePoint (or other file syncing based service like ShareFile, Google Drive, or Egnyte).

Installation Procedure

1. Create a folder in SharePoint that will be used to store the Assemblage application. 

1.a. If you are migrating from an existing system, copy the existing Assemblage folder over (CRITICAL: Be sure to show hidden files - you MUST copy the existing .globalconfig folder from the existing Assemblage folder)

or

1.b. if you are installing new, install from the installer that Trumpet will provide and set the install path to the SharePoint folder

2.  Move the Assemblage\Workspace folder to a SharePoint folder that is OUTSIDE of the Assemblage folder

For each user who will use Assemblage:

1.  Set the Assemblage folder to "Always keep on this device"  (this is critical - it will not be possible to run the Assemblage application properly)

2.  Set the Workspace folder to sync or "Always keep on this device" (depends on your preference - it will be faster if you Always Keep on this device.  But Assemblage's working files will consume more local disk space)

3.  Add a desktop shortcut pointing at the Assemblage.exe file in the SharePoint repository

Testing the Installation

Double click the Assemblage shortcut on the user's desktop and confirm that it launches without error messages (if this is a new install, you will be prompted to enter your license number.  If this is an existing install and you are prompted to enter a license number, you probably didn't copy the .globalsettings folder back in step 1a.)

Configuration Changes

Any existing tool configuration will need to be adjusted to account for the new workspace folder location.  Note that because SharePoint syncs to the user's profile, each user effectively has a different path for the workspace folder.  Any absolute paths in any of the Assemblage tool configuration files will need to be adjusted to use relative paths, or use the {env.USERPROFILE} variable.

Generally speaking, paths in Assemblage are relative to the Assemblage executable folder.  The exception are paths for content (PDFs for assembling, stamp PDFs, or blank page insertion PDFs) that are defined in a WDA file - these are relative to the baseInputPath defined at the top of the WDA.  The baseInputPath itself is defined relative to the Assemblage executable folder.

Trumpet is happy to help with these configuration changes - please send an email request to support@trumpetinc.com to put in a request.

Background

Most clients will have installed Assemblage to a network location, and then a shortcut to the executable will be saved on some user workstations. This article is for if you have cancelled your Assemblage subscription and would like to "clean up" by removing the traces of the software.

How to Remove Assemblage

• For individual users simply delete the Assemblage shortcut from their desktop. 
• To remove the Assemblage application and all settings and configurations then locate and delete the Assemblage folder from your network location (usually it is nested under a folder called "Trumpet).
  • There is no "uninstallation" package. Deleting the folder is all that is needed. 

CAUTION: 

If you delete your Assemblage network folder you WILL LOSE your custom configuration files that Trumpet built for your specific use. If you need to reinstate your Assemblage subscription then fees would be associated with recreating lost/removed configuration files. 

Background

When uploading documents via the NDImport tool, you receive the following error:

 

Resolution:

There was an updated version of the importer tool that you will need to download.  For instructions and the link for the update, please visit:

NetDocuments Import Utility

 

 

Note: these instructions were provided by Advent, and are not supported in any way by Trumpet

 

Excel macros do not record many of the changes to chart appearance that were possible in Excel 2003.  However, you can use a chart template in Excel 2007 to make the same changes, and reference the template in your Excel macro. 

A chart template in Excel is a spreadsheet file containing common data and formatting options that is used as a model for other spreadsheets. Excel does not provide a comprehensive list of changes you can make using a chart template. Formatting can include the following:

• Font styles and size.
• Chart type changes.
• Chart layout changes.
• Color changes - changing the fill colors of your chart.
• Moving/Deleting/Resizing the chart legend.

The steps below detail how to create a chart template in Excel for your APX and Axys reports and then how to apply the saved chart template to an Excel macro and then how to reference the Excel macro in an Axys or APX report.

A. Create an Excel Chart from a Report

1. Run a report for which you can create a chart.
2. In the report dialog box, select the Graph check box.
3. Define the chart you want to create, and click OK.
4. Click OK. The report runs.
5. If the chart does not appear on screen, click the "Reports and Charts View" icon to display the chart view.
6. Single-click the chart to display the chart frame (do not double-click).
7. Choose File > Save As.
8. In the "File name" field, enter a name for the chart, 8 characters or less (Example: Graph).
9. In the "Save as type" field, choose "Excel Chart (*.xls)."
10. Click Save to save the report as an Excel chart.
11. Close the report window.

B. Create a Chart Template in Excel

1. In the Windows menu, choose Programs > Microsoft Excel.
2. In Excel, from the Office Button choose open.
3. Open the chart (*.xls) that you saved created from the report in Axys or APX (Step 10).
4. Select the chart area (clicking once on the chart area), this will activate the Chart Tools menu.
5. Make the necessary changes you want to make to the chart appearance. 

• You can change the colors of the series (if using Microsoft Office Ultimate 2007 you can apply a Color Scheme to change all the colors of your graph).
• Move and resize the legend.
• Change the font style and size of the report title.
• Change the chart layout of the report.

1. When changes are completed, click on Chart Tools >Design Menu > select the "Save as Template" button.
2. Save your chart template to the default location (we will discuss how to move the template to shared location so that it can be used by the whole office later in this document.) 
3. You may want to test the template at this point to make sure that your changes apply (you can only do this if you save the template to the default location). 
   1. To do this close the open Axys or APX chart without saving and re-open it. 
   2. Select the chart, click on Charts Tool > Design > select "Change Chart Type."
   3. Select "Templates" from the left side of the screen, and in the My Templates section on the right select the template you just created and click OK. 
   4. You should see all the changes applied to the chart that you had made before.
   5. When you have completed the review of the chart, close the chart file without saving and re-open it.

C. Create a Macro in Excel to Reference your Chart Template

1. With the chart open in Excel make sure that the chart is selected (you can tell because the Chart Tools menu will be activated).
2. Click on the View menu, then Macros > Record Macros.
3. Give the macro a name (i.e. Graph.). You will need to reference this name from when running your report.
4. In the "Store macro in" field, choose New Workbook, and click OK.
5. Click on the Chart Tools > Design > Change Chart Type.
6. Select the templates folder from the left side of the screen, then choose the template you just created (Step B7) from the right side of the screen and click OK.
7. Click on the View Menu > Macros > Stop Recording.
8. From the View Menu choose Switch Windows and select the workbook created by the macro (it will be called Book2).
9. Click on the Office Button > Save As.
10. Make sure you select the type Excel Macro Enabled Workbook (.xlsm) and give it a name and save the file.

D. Using Your Excel Macro in Reports

1. Run your report. 
2. In the report dialog box, select the Graph check box.
3. Click Browse.
4. Choose the name of the Excel Macro-Enabled Workbook (.xlsm) file you created (Step C9) and click OK. The file name appears in the "Excel Macro File" field.
5. In the "Excel Macro Name" field, enter the name of the Excel macro that you created (Step C3).
6. Click OK.
7. Click OK again. The report runs and displays chart with the changes recorded in the Excel macro.

To store the Chart Template in a shared location on a server so that it can be used by the whole office:

1. Follow the steps above.
2. Copy the template you created in part B to the server.  For example, you might create a directory off the APX or Axys share for templates and copy the templates to \\server\apx$\templates or \\advent\axys\exceluse.  Chart templates have the extension CRTX and you commonly find them in your user directory on the machine where you create the chart template.  

• In Microsoft Windows Vista: "Roamings\<USERNAME>\AppData\Romaing\Microsoft\Templates\Charts" where USERNAME is the name of the user who created the template.
• In Microsoft Windows XP:  "c:\documents and settings\<USERNAME>\Application Data\Microsoft\Templates\Charts" where USERNAME is the name of the user who created the template.

1. Open the Excel workbook you saved in Step C10. 

• If you have not enabled all macros in Excel Trust Center then when you open the document you may need to enable macros. To enable all macros all the time go to the Office Button > Excel Options > Trust Center > Trust Center Settings. Then from the left screen choose Macro Settings and Enable all macros. 

1. Go to View > Macros > View Macros.
2. Select your macro and click Edit.
3. You should see a path reference to Roamings\advent\AppData\Romaing\Microsoft\Templates\Charts\template1.crtx.
4. Change it to the new location \\server\apx$\templates\template1.crtx / \\advent\axys\exceluse\template1.crtx and save.
5. Close the macro and test it.

Description

When running reports that contain graphs, the report run hangs with a dialog displayed that says "Server Busy".  When the user clicks to clear the dialog, the report run process continues as it normally would.

Discussion

This issue is caused by Axys not properly setting a timeout delay parameter when they tell Excel to generate the graph.  If you are running the scripter on a slower computer, this will be an issue.

Resolution

Unfortunately, because this behavior is caused by a problem in Axys, there is nothing that Assemblage can do about it (we ask Axys to run the report - once we make that request, we have no control over the process).  We have known about this issue for quite some time (at least 5 years).  We have even provided Advent with the system calls they need to make to adjust the behavior, but the issue has not, as near as we can tell, been fixed.

The only fix that we can suggest at this time is to run the reports on a faster workstation, or call Advent and complain loudly.

For reference (just in case someone from Advent development ever sees this), here is a Microsoft article describing the Windows API calls that Axys should be using: 

http://support.microsoft.com/kb/248019

Background

Advent Axys requires the full version of Adobe and the Scripter utilizes this application for generating the reports.  You may receive the following message when generating the reports:

Resolution

1. Navigate to your list of printers, right click on the Adobe PDF Printer and select "Printing Preferences"
2. Select the Adobe PDF Settings tab, and uncheck the "Rely on System fonts only; do not use document fonts" check box
   
3. Select "OK"

If your printer driver has been updated, or you are printing from a different computer than the presets were originally created for, you may need to re-configure the presets.

To adjust the presets:

1. Tools->Preferences
2. Choose the Printers option
3. Select the printer
4. Select the preset that you want to edit/check  (or create a new preset if you still need the old one - i.e. if you are going to be printing from different computers that require different presets)
5. Click Edit
6. Click Configure next to the Use printing preferences setting
7. Make your changes
8. Click OK in the printer settings dialog
9. Click OK to close the Edit preset... dialog
10. Click OK to close the Preferences dialog

Note:  there have been reported issues of problems with printer presets not working specifically with Konica Minolta printers utilizing the PCL Print drivers.  Updating to the PostScript print drivers resolves these issues.

Background

User receives the following error:

Unexpected error during processing - [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied

Discussion

This error means one of several things:

1. You have changed your SQL server, but Trumpet has not yet updated your configuration to use the new server name (if this is the case, please request a configuration change via email to support@trumpetinc.com)
2. The Windows user you are logged in as does not have permission to access the SQL Server - have your system administrator check your SQL Server settings
3. The SQL Server is shut down or inaccessible from your workstation - have your system administrator check your network

 

Background

Assemblage uses Java, which must be installed on the workstation in order for Assemblage to launch.

Newer versions of Assemblage will point your browser to the Java download screen if Java is not detected on the workstation, otherwise use the steps in below to manually install Java

Resolution

1. Go to www.java.com
2. Click Free Java Download
3. Install Java, then launch Assemblage again

Symptoms

When launching Assemblage, the user receives an error stating "There is a problem with the 32 bit Java installation on this computer"

In later versions of Assemblage, an error code will be displayed in parenthesis.

Background

This issue can indicate several different types of problems:

• Java installation on the workstation is corrupted
• Workstation has insufficient memory to launch Assemblage

Resolution

1. First, ensure that you are running Assemblage 1.1.61 or higher - there were fixes added to 1.1.61 for some common causes of this error, and we also added an error code in parenthesis that will help to diagnose the issue.
2. Next, ensure that you have the latest Java runtime installed - go to www.java.com and install the latest version
3. Finally, if you still receiving this error message, please open a support ticket by emailing a screen shot of the error message to support@trumpetinc.com

 

 

Symptoms

After upgrading Junxure, attempts to load Assemblage configurations result in the following error message:

Error message - Unable to refresh cache Unable to interact with database [Microsoft][ODBC SQL Server Driver][SQL Server] The SELECT permission was denied on the object tblClientsUnfiltered, database Junxure, schema dbo

Background

In a recent upgrade, Junxure changed permissions on certain tables in their database.  We have added special handling to the Assemblage database handler to detect this situation and automatically work around it.

Procedure

Upgrade Assemblage to version 1.0.352 or higher.  Please see Update Instructions for details on how to do this.  If you need a download link, please send a request to support@trumpetinc.com and include "Need Assemblage upgrade to fix Junxure issue" in the subject line.

Symptoms

Users with Salesforce integration may see the error below when running configuration files in the various Assemblage tools:

Background

Assemblage utilizes a Salesforce username, password & security token to read the Salesforce database from someone in your firm.  If that user obtains a new security token, leaves your firm, or changes their password in Salesforce, you will see the error message above. 

Procedure

You can follow these instructions:  Salesforce Connection Set Up to reset any of the values above.

Background

While assembling your reports you receive this error message:

Unable to refresh cache - Salesforce exception: The users password has expired, you must call SetPassword before attempting any other API operations

Resolution

Your Salesforce password has more than likely expired.  Even though you are logged into Salesforce, if you were to log out, you would probably be prompted to change your password.

Go ahead and log out of Salesforce, then follow these steps to update Assemblage to reference the new password for Salesforce:

Assemblage may utilize a firm's existing SOQL (Salesforce) Database to collate various pieces of content. This requires Assemblage to log into the Salesforce API.  When you log into Salesforce from an outside application (Assemblage) using the Salesforce API, you must to add a security token to the end of the user's password.

Prior to setting up your Salesforce Connection in Assemblage, you must obtain this security token.

Obtain a security token from Salesforce

From Salesforce:  Navigate to Settings > My Personal Information > Reset My Security Token.  This will send a token to the user.

Once you have the security token, you are ready to configure the connection for Assemblage.

Configure Assemblage to connect to Salesforce

This configuration is available from the main Assemblage application under Tools > Preferences > Salesforce connections:

Enter the Salesforce username in the Salesforce user field

Enter the password and security token in the Password field (enter your password first immediately followed by the security token, without any spaces or characters in between)

Select "OK"

Description

When a client receives a copy of their Assemblage report and opens it up in Preview on a Mac with OS X, they are not able to use the bookmarks in the left side of Preview.

Background

While the option of bookmarks can be selected:

Preview does not have the functionality to use bookmarks in PDFs.

Note: The user has selected Portfolio Holdings and it still is showing the cover sheet.

Resolution

It is recommended that a Mac OS X user should download a free copy of Adobe Reader at Get Adobe Reader as it is capable of using bookmarks in PDFs on OS X

Background

Assemblage stores its Global Settings in .globalsettings folder of the Assemblage directory.  Upon launching, Assemblage looks up the location of the .globalsettings folder based on the "Start In" folder of the shortcut used to launch Assemblage.

If you migration the Assemblage application to a different drive letter, and change "Target Path" only in your shortcut, as seen in the illustration above, you would still be referencing an old location of Assemblage.

Solution

1)  Delete the shortcut formerly used, and create a new shortcut to the Assemblage.exe file at the new server location.

2)  Change the "Start In" path of the Assemblage shortcut to reflect the new location.

Background

'Heap" is the memory of the computer that is available for an application to use.  Applications create objects which they place into the heap.  When the application is finished with the objects, they remove those objects from the heap.  If you are receiving messages that reference Java Heap Space, your Assemblage configuration may require more memory than Assemblage uses by default - or your computer doesn't have enough memory for Assemblage to run at it's default heap size.  The default heap size that Assemblage requests is 768 MB.  If your computer can only provide Assemblage with 500 MB when it launches, then Assemblage will reduce it's heap usage to 500 MB.  Note that it is quite possible for a PC with 2 GB of memory to not be able to provide Assemblage with the full 768 MB RAM due to memory segmentation.

Before you read further: Sometimes this problem is not caused by memory. Open up the Excel file used to map your assemblies and make sure there are not a lot of extra empty lines at the bottom of your data. If you find that you do, then delete the extra lines, re save the excel and try again.

If your Assemblage configuration has a moderate number of assemblies (100-300), then heap space errors are probably caused by a lack of memory on your PC.  We recommend a minimum of 4GB of RAM.  And more if your operating system supports it.

If your Assemblage configuration results in a very large number of assemblies, you may need to increase the amount of heap space that Assemblage will use.  In order for this to work, your PC must have a large amount of available RAM, and be running Assemblage version 1.1.62 or higher.

Solution

To adjust the Assemblage heap size, you will need to be on Assemblage 1.1.62 or higher, and adjust the shortcut you use to launch Assemblage to control the size of the heap that will be requested.

Right click on your shortcut, and choose Properties.

Update the Target field to include

 /maxheap=### (where ### is the size of the desired heap in MB). 

In the illustration above, the heap size that Assemblage will request is 1.5 GB or 1500 MB.

Note:  This will only work if the workstation has a lot of memory (RAM)

Note:  If your PC does not have enough continuous RAM to allow the heap size you specify, Assemblage will automatically reduce the RAM it uses (even if that is less than you requested in the /maxheap setting).

Background

This problem ('Driver does not support this function') almost always means that a database driver is missing from your workstation.  Assemblage uses ODBC technology to connect to your databases - if the appropriate ODBC driver is not installed, Assemblage cannot query data.

Resolution

Microsoft Visual FoxPro ODBC Driver

Microsoft has stopped shipping FoxPro ODBC drivers in Windows 7.  If one of your data sources uses FoxPro (e.g. dbCams), you must manually install the FoxPro ODBC driver.  Microsoft does not make this easy.

After much diffing, we have found a download link that still works (we also have a copy of this installer that we have copied in case this link breaks at some point in the future):

http://download.microsoft.com/download/vfoxodbcdriver/Install/6.1/W9XNT4/EN-US/VFPODBC.msi

Condition: When sending an email with the Email with Regular Attachment tool the tool will indicate that the email sent. Shortly there after an email notification is received that says:

"This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524]."

Solution: In the Emailer tool empty the "From Address" field and try again.

Exchange Servers

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 PCs that the Assemblage Emailer tool will run from.

Important Note: Trumpet does not provide support for how to configure or manage Exchange servers - the information below is provided as an aid to you, but you should use it at your own risk.  If you are not a certified Exchange administrator, we encourage you to contract with someone who is.  Trumpet will be unable to answer technical questions about these procedures.

 

550 5.7.1 Unable to relay

This is an error reply from your SMTP mail server indicating that your mail server is not configured to allow you to send emails through it.  Typically, mail servers for an organization will be configured to allow mail from within the organization to be sent to other addresses within the organization, or to addresses external to the organization. It will also typically allow mail coming from an address external to an organization to be sent to addresses within the organization. What it will typically not allow is mail coming from an address external to the organization to be sent (relayed) to another address also external to the organization. The configuration of the mail server determines whether such relaying is allowed, and which addresses are considered internal vs. external. Often mail servers will require you to authenticate before they will relay messages. 

For Assemblage's emailer tool to work properly, your SMTP server must allow for mail to be sent from within the organization to be sent to other addresses external to the organization.  Your system administrator will be able to assist you in the configuration of your mail server to allow for appropriate relays.

 

Error sending text email - can't send command to SMTP host sun.security.validator.ValidatorException:  PKIX path building failed:  sun.security.provider.certpath.SunCertPathBuilderException:  unable to find valid certification path to requested target

If you are using a self-signed certificate for your Exchange server, you have two options:

Tell Assemblage to not check the certificate

1. Go to Assemblage, Tools->Options, Email
2. Change the Authentication Type to be 'SSL w/ Self Signed Cert'

Register your self signed certificate with the Java runtime on the workstations that run Assemblage

1. Export your Exchange certificate in .p12(.pfx) using the Export-ExchangeCertificate command in the shell. You can get a list of certificates using Get-ExchangeCertificate.
2. Use the following Java command to import the certificate:
       keytool -import -alias imap-server -file <path to exported certificate>
3. It seems depending on the security set in Java, you may also need to add the issuer of the Exchange certificate as a trusted authority

Remember that Assemblage will use the latest 32 bit Java runtime installed on the workstation, so make sure you run keytool from the correct directory!

Symptoms

Scripter configurations that use the AxysRunner to run Axys reports fail. 

Error message says '"Files not Processed" "1 Files were not processed. See the logs for error information.'

The Logs tab shows the following detailed error message:

Caused by: java.io.IOException: Cannot run program "?:\Advent\Axys\rep32.exe" (in directory "some directory\AppData\Local\Temp\assemblage\axysRunner"): CreateProcess error=740, The requested operation requires elevation.

This elevation requirement is being done in the executable manifest of the rep32.exe executable, and can only be fixed by the Axys developers.

Background

Advent Axys changed the Axys application to require that it be run elevated (why they did this is beyond us - it makes absolutely no sense).  This means that the process that launches Axys (i.e. Assemblage) must also be run elevated, or you must disable UAC on the workstation that will be running Axys.

Workaround

Either of the following workarounds will work:

1. Run Assemblage with UAC elevation (right click, Run as Administrator)
   Note: if you run Assemblage with UAC elevation, it will be unable to integrate with other applications that you have running.  For the purposes of running Axys reports, this is probably not an issue.
2. Disable UAC on the workstation that will be running Axys
   Tip: Here is information about how to properly disable UAC: http://www.howtogeek.com/howto/windows-vista/disable-user-account-control-uac-the-easy-way-on-windows-vista/

Resolution

Contact Advent support and request that they fix Axys so it does not force users to run elevated.  Note that so far, none of our users have had any luck with this - but if you are able to get them to fix this, please do let us know.

 

Symptoms

When publishing files to ShareFile, you may see the message "validate folder '\<FOLDER>' does not exist, but you can actually "see" that the folder exists, and that there are no issues, typos, etc.  for that folder:

Background

This may be due to the fact that the Shared Folder was created under "My Files & Folders" and then shared to a different user.  For example, Andrea logs into ShareFile as herself, and creates the folder "Clients" under the "My Files & Folders" area of ShareFile.  Andrea then shares the folder "Clients" with Ryan.

If you're logged into ShareFile as Ryan, you simply see the Clients folder under the "Shared Folders" area:

However, if actually double click to open the "Clients" folder, you will see Andrea's email address referenced.

In Trumpet Publisher, if you choose to publish the files anyway, it will rename the original Clients folder showed to /andrea@trumpetinc.com/Clients and create a new "Clients" folder.

Resolution

Trumpet recommends that you create your folder structure within the Shared Folders area to prevent issues like this one.

 

 

 

 

Background

When using Trumpet Publisher for ShareFile in a remotely hosted environment, the Publisher tool may open to a blank screen.  In some hosted environments this is caused by security constraints on the hosted environment.  Never fear, you can still use Assemblage (Trumpet Publisher for ShareFile) in a remotely hosted environment, but there are special security considerations.

When you launch Trumpet Publisher for ShareFile, Assemblage launches a Java Applet pointed at the ShareFile login.  Some hosted environments block the Java Applet from loading from their group shares and cannot adjust the security settings on these group shares globally. 

Resolution

Assemblage (or the Trumpet Publisher for ShareFile tool) should be installed to a custom share (or regular share mapped to a network drive) that allows more customization of the security settings so that Assemblage can properly launch the Java Applet.

Background

User is attempting to auto-file documents from a network UNC path (a path that starts \\SERVERNAME\LOCATION) instead of a mapped network drive letter.  That UNC path isn't known to Worldox (see below for an explanation of what "Known to Worldox" means).

Under these conditions, Worldox refuses the request to file the document, and Worldox Auto-Filer enters a retry loop.

UNC Paths Known to Worldox

Worldox will consider a UNC path as safe to file to under the following conditions:

1. The UNC path is part of a Worldox cabinet definition
2. The UNC path is mapped to a network drive letter on the user's workstation
3. The UNC path is configured as an allowed folder in Worldox group security (see Resolution below for steps to do this)

Resolution

The fix is to add the UNC path to Worldox's group security using the following procedure:

• Launch WDAdmin
• Security > Groups
• Choose the Paths\Folders radio button
• Click "Add"
• Enter the UNC share name (e.g. \\MyServer\SomeShareName), then click "Add"
• In the second column, make sure the (Everyone) group has a green "+" next to it (this is the default behavior, so it should be fine as-is)
• Click "Save Security"
• Relaunch Worldox so the workstation receives the updated security configuration
• Run the WD Auto-Filer again, and it should work properly

Symptoms

Launching Assemblage displays the following error:

Background

This happens when Java Access Bridge is enabled on the machine where Assemblage is installed.

Solution

Disable Java Access Bridge â€” Run the following command at a command prompt:   "C:\Program Files (x86)\Trumpet\Java\jdk-11.0.3\bin\jabswitch.exe" /disable

Warning:  This may interfere with other applications that required Java Access Bridge.

Symptoms:

After running your Scripter configuration you receive a Files Not Processed box letting you know that "X files were not processed. See the logs for error information"

When you check the logs you see the following error:

Output PDF file C:\Users\USERNAME\AppData\Local\Temp\assemblage\axysRunner\MACRONAME.pdf not found after running script. This may be because Axys didn't run the report properly, or Axys may have the $pathpdf variable set. If $pathpdf is set, clear it, then try again

Background:

The Scripter runs an Axys Command line to run the macro and print out the report. When the error above it hit it is because part of the creation/output process did not function as the command line tried to run.

Troubleshooting:

1.  In Axys Network settings make sure that there is not a variable for $pathpdf
2. Test running the Macro in Axys
3. Test the Adobe PDF print driver by printing to a pdf from a program like Word
4. Verify the Adobe Trust settings per Adobes guide: https://helpx.adobe.com/acrobat/kb/security-warning-postscript-pdf.html
5. Turn Off Adobe preview after printing setting
6. Run the Elevated Scripter
7. Copy the Command line from the Scripter Log and run it in a Windows Command prompt
8. Remove the "-u" from the Axys command line i.e. X:\axys3\rep32.exe -macro -vf -pw-123 

Symptoms: 

When Printing files using Assemblage you receive the following error: DMLERR_NO_CONV_ESTABLISHED

Background:

If the user sees DMLERR_NO_CONV_ESTABLISHED in the print manager, there is a possibility that the version of Acrobat is newer than Assemblage has been configured to integrate with.  In version 2.3.76 of Assemblage we added registration entries for Acrobat through the year 2030.  If the user hits this error they should update to Assemblage version 2.3.76 or above. 

If they continue to get this error and it is before 2030, then the error is something else (maybe related to Acrobat security or possibly the Acrobat installation being corrupted).

This error can happen if you are setting a retention period longer than the maximum configured for your ShareFile account.  The default is 180 days, so any retention period longer than 6 months can cause this problem.

To adjust this 180 day limit in ShareFile, go to:

Settings (gear icon on the left)->File Settings.  Then adjust the "Maximum access expiration period"

It is relatively simple to replace an existing stamp with a new one.  For example, if your firm changes its logo or decides they'd like to have their page numbers in a different location on their reports.

The Stamps that Assemblage uses are located in the Configs\Stamps folder in your Assemblage Workspace.

To update your stamp, you can simply create a PDF of the stamp as you wish it to appear (if this is a letterhead stamp, you may wish to obtain one from your graphic designer or printer), and replace the appropriate file in your Configs\Stamp folder.

 

To "Hide" the Assemblage merge fields do the following:

- Open your merge form template (yours might look something like this)

 

- Select the Assemblage merge fields (including the ## signs)

- Right click, and change the font to White:

 

- Save your template

 

Assemblage 2.1.16 and higher allows you to format the body of your emails using a rich text editor.   Here are some of the options you have for formatting:

Formats:

Font Family:

Font Sizes:

Text Color:

Background Color:

Alignment:

Left, center or right alignment of text

Text Formatting:

Bold, italics, underlining, strikethrough and clear formatting

Embed Images:

Embed your logo or other images:

Bullet Points, Numbering and Indentions

Superscript and Subscript

Add superscript and subscripts for footnotes and documenting

 

 

Encryption is critically important to any sort of security because a file that only has a password on it and is not encrypted can be opened and read by anyone with the right skills. That is worse than no security at all, because it gives a false impression of security.  When you apply a password to an attachment in the Assemblage Emailer tool, the contents of the file are actually encrypted.  Without the password, the decryption keys are not known, so the content cannot be recovered by an attacker.

The size of the encryption key is usually measured in 'bits'.  Most encrypted traffic that goes over the Internet uses 128-bit encryption.  Generally speaking, the larger the key, the stronger the encryption - but you have to be a bit careful with this.  A modern computer would require many, many thousands of years to try every combination of a 128-bit encryption key (this is called a 'brute force' attack).  By going to 256-bit encryption, you can change that to millions and millions of years.  But the *effective* security is the same.  128-bit key lengths have been found by the security community to provide a nice balance of encryption that would take a really, really long time to crack with brute force techniques, without the key becoming ridiculously long.

When you password protect email attachments in the Assemblage Emailer Tool, the software takes the password and turns it into a 128 (or 256) bit key using an algorithm called a one-way hashing algorithm.  If you input the same password, you get the same 128 or 256-bits of effectively random data.  But it is not possible to start with the 128-bits of data and obtain the password.
 
The files generated by Assemblage are actually not password protected.  In fact, the password isn't part of the file at all.  Instead, the contents are encrypted using a symmetric algorithm.  The key for the symmetric algorithm is obtained by taking the password and processing it with a one-way hashing algorithm.
 
When a user opens the attachment, they are prompted for a password.  The password is not compared against any value in the attachment.  The password is used to mathematically obtain the decryption key.

Assemblage offers 4 different levels of Encryption.  See PDF Compatibility Levels for more information on the level of encryption for each version of Adobe.

The higher the level of encryption you use, the more secure the attachments will be from attackers.  That being said, certain versions of Adobe are required to decrypt the attachments as well.

In Assemblage versions 2.02 and higher the default setting is to apply AES 128 bit encryption, if you wish to use a different level of encryption, please notify your Trumpet Consultant.

Let's start with examples of bad passwords:
 
1.    Regular English words (i.e. not including numbers, symbols, combination of upper and lower case)
2.    A client's social security number, a portion of the client's social security number, or any other piece of information that might be guessable
3.    Any password that you e-mail to the recipient (if an attacker has access to one email, they probably have access to all of them!)
4.    Anything that is short (shorter than 8 characters is generally considered to be bad)
 
My recommendation is to let the recipient decide the password.  That puts the onus on them to choose something that is secure.

The strongest safe in the world does no good if the combination is written on the door.

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

Updating your Assemblage Software

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

1. Ensure that no one else in your firm has Assemblage open.  Then, launch it on your workstation.
2. Download the new Assemblage installer, by going to "Help -> Check for Updates" in Assemblage
3. Double click the Assemblage installer for the Production Version
   
4. Choose the *network* folder where Assemblage is installed
5. If prompted for your client code, type in the client code provided in the update notification email
6. Accept all other defaults
   Tip: If you receive an error message about not being able to overwrite assemblage.exe, it means that another user is running Assemblage. Please have them close it, then try again.
7. Launch Assemblage by double clicking on the Assemblage.exe application
8. If prompted for your license number, copy and paste it from the update notification email

That's all there is to it!

Updating your Assemblage License

Starting with version 2.2.93, Assemblage will have an 'Automatic License Update' feature.  After you've paid your yearly invoice with Trumpet, a new license is automatically generated.  Therefore, if your installation has access to the Trumpet servers, Assemblage will see this new license, download and update the license number automatically.

Note:  Assemblage will check for a new license when it is launched.  If the license has expired or will expire in the next 30 days, Assemblage will automatically update it.

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 follow these instructions to input your license manually:

• Open Assemblage (or any of the Assemblage tools)
• Select "Tools-> Preferences"
• Select "License" in the navigation panel on the left hand side of the screen
• Paste your license number in to the License Number: field, and then select "Add License"
• Select "OK"

As mentioned, all of this assumes your installation has access to Trumpet's servers.  If a connection cannot be established, you simply follow the instructions listed above.

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 Assemblage installation.  Depending on the update notification, that email may contain your client code and/or license number.

1. Ensure that no one else in your firm has Assemblage open.  Then, launch it on your workstation.
2. Download the new Assemblage installer, by going to "Help -> Check for Updates" in Assemblage
3. Double click the Assemblage installer for the Production Version
   
4. Choose the *network* folder where Assemblage is installed
5. If prompted for your client code, type in the client code provided in the update notification email
6. Accept all other defaults
   Tip: If you receive an error message about not being able to overwrite assemblage.exe, it means that another user is running Assemblage. Please have them close it, then try again.
7. Launch Assemblage by double clicking on the Assemblage.exe application
8. If prompted for your license number, copy and paste it from the update notification email

That's all there is to it!

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

Updating your Trumpet Publisher/Emailer Software

These steps assume that you have received an email instructing you to update your Trumpet Publisher installation.

1. Ensure that no one else in your firm has Trumpet Publisher open.  Then, launch it on your workstation (this will be the Trumpet Publisher or Trumpet Emailer shortcut).
2. Download the new Trumpet Publisher installer, by going to "Help -> Check for Updates"
3. Double click the installer
4. Choose the *network* folder where Trumpet Publisher/Emailer is installed
5. Accept all other defaults
   Tip: If you receive an error message about not being able to overwrite assemblage.exe, it means that another user is running Trumpet Publisher. Please have them close it, then try again.
6. Launch Trumpet Publisher/Emailer by double clicking the appropriate shortcut in the main installation directory
7. If prompted for your license number, copy and paste it from the update notification email

That's all there is to it!

Updating your License

Starting with version 2.2.93, Trumpet Publisher/Emailer will have an 'Automatic License Update' feature.  After you've paid your yearly invoice with Trumpet, a new license is automatically generated.  Therefore, if your installation has access to the Trumpet servers, Assemblage will see this new license, download and update the license number automatically.

Note:  Trumpet Publisher will check for a new license when it is launched.  If the license has expired or will expire in the next 30 days, Trumpet Publisher will automatically update it.

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 follow these instructions to input your license manually:

• Open Trumpet Publisher
• Select "Tools-> Preferences"
• Select "License" in the navigation panel on the left hand side of the screen
• Paste your license number in to the License Number: field, and then select "Add License"
• Select "OK"

As mentioned, all of this assumes your installation has access to Trumpet's servers.  If a connection cannot be established, you simply follow the instructions listed above.

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 Trumpet Publisher installation.

1. Ensure that no one else in your firm has Trumpet Publisher open.  Then, launch it on your workstation (this will be the Trumpet Publisher or Trumpet Emailer shortcut).
2. Download the new Trumpet Publisher installer, by going to "Help -> Check for Updates"
3. Double click the installer
4. Choose the *network* folder where Trumpet Publisher/Emailer is installed
5. Accept all other defaults
   Tip: If you receive an error message about not being able to overwrite assemblage.exe, it means that another user is running Trumpet Publisher. Please have them close it, then try again.
6. Launch Trumpet Publisher/Emailer by double clicking the appropriate shortcut in the main installation directory
7. If prompted for your license number, copy and paste it from the update notification email

That's all there is to it!

This article contains details of every change made to Assemblage.  There are also Version Summaries available with highlights of each major release.

2.4.11 - 

- Added support for automatically handling Fidelity zip files in Assembler in folders via fidelityZipContentSource sub-element for contentSources

- Assemblage will now use the Windows SSL trust store instead of requiring private certificate registration

- Layout bug fix - NetDocuments Autofiler mis-displayed the warnings screen if "Folder" checkbox was unchecked

2.4.8 - dev release

- Bug fix "No ContentProvider available" default text in emailer and sharefile emailer
- Bug fix - HTML email editor blank in some situations

2.4.4 -

- Added urlpath() function to line value expressions (CSV, Excel, etc... translator expressions)

2.4.1 -

- Add support for sending emails using 64 bit Outlook (previously, only 32 bit Outlook was supported)

2.3.105 -

- If a user is not licensed for full Assemblage, and they run Assemblage.exe without command switch specfying a tool, they will be prompted for the tool they wish to launch (this effectively replaces the 'tools' subfolder shortcuts)

2.3.104 -

- Added ability for translator URLs to use extractor syntax for common extractors
- Added env.USERPROFILE, env.APPDATA, env.LOCALAPPDATA as common extractors

2.3.103 -

- Functional change to ShareFile integration - login now happens in the user's web browser instead of in an embedded browser view inside Assemblage

2.3.102 -

- Bug fix - Worldox connection not initializing in some cases

2.3.100-

- Limit the length of the example string when complaining about <<YYYY>> needing to be replaced - this prevents huge multi-line strings (like HTML body content) from consuming the entire error box.

2.3.98-

- Added replaceregex() function to line value expressions (CSV, Excel, etc... translator expressions)

2.3.97-

- Copy/paste extractors now supports more than one extractor

2.3.96-

- Enhancement - it is now possible to copy/paste Extractors between extractor lists in the various tools

2.3.94-

- Added support for using nd.user.* extractors in advanced extractors in NetDocs Autofiler configurations.  See Assemblage Documentation for example of how to use this to populate an Author field that is based on the current ND user.

2.3.93 -

- Added xlat:ndattributes translator for creating maps based on NetDocuments attribute lists

2.3.92 -

- Added 3 special extractors to NetDocs Autofiler:  nd.user.id  nd.user.email and nd.user.displayname

2.3.87 -

- Enhancement to NetDocuments AutoFiler - now supports saving to workspace folders in addition to cabinet folders

2.3.85 -

- Bug fix - ShareFile Folders tool produced warning about root folder not existing when the folder actually did exist, if any of the extractors used in the Folder setting returned values that contained slashes (e.g. the 'client folder' extractor returned a folder *and* a subfolder.  So instead of returning 'Jones, Bob', it returned 'Jones, Bob/documents')

2.3.83 -

- ND Autofiler - The NetDocuments authentication login now occurs in the user's browser instead of in a window inside Assembalge/Autofiler.
   - When the user launches the NetDocs Autofiler tool, they will see a "Connect to NetDocuments" button.  When the user clicks this button, their standard web browser will open and allow them to log into NetDocs.  Once they log in, they will be returned to the NetDocs Autofiler tool. 
   - A bonus of this change is that any authentication the user has made in their browser will happen automatically and the user can use browser based password manager integration

- WD Auto Filer - if parent field is not specified, and child field has multiple parent values, and the parent is required, the error message now states that there are two parents (instead of leaving the parent blank and the error saying that the parent isn't specified) 

2.3.81 -

- Bug fix - The Worldox API fails if m/d/yyyy strings are longer than 8 characters.  This can result in documents having empty (or junk) date cabinet field values after auto-filing. Worldox Auto-Filer now checks for cabinet field strings that look like (m/d/yyyy) dates and converts them into YYYYMMDD format before sending them to Worldox.  

2.3.80 -

- Splitter now preserves the modified date (the output file will have the modified date of the source file) 

2.3.78 -

- workaround for Worldox API bug when auto-filing documents from UNC paths that also contain long file names - we now use native file copy operations instead of Worldox API operations for UNC paths

2.3.77 -

- Move to log4j-2

2.3.74 -

- Disabled TLS v1 and v1.1 for email sending 

2.3.76 -

- Add PrintHandler support for Acrobat and Reader versions 21 through 30

2.3.75 -

- Added Print Strategy setting to Printers Preferences.  Options are "Built In" and "Acrobat".  The internal PDF renderer uses our internal PDF renderer which will be faster and does not require Acrobat to be installed.

2.3.71 -

- Bug fix - printing some malformed PDF files (with huge tiling images) resulted in out of memory exceptions 

2.3.67 -

- Added translation to use Windows GillSansMT for GillSans fonts during printing if GillSans isn't embedded (tpt97108)

2.3.66 -

- Bug fix - database connections were not saving
- Added support for MySQL/MariaDB databases

2.3.64 -

- Add support for custom SSL trust store (<network home>\cacerts.private)
- Printing Assemblies to paper no longer depends on Adobe Acrobat (note: Acrobat is still required for running Axys reports to PDF)

2.3.60 -

- Added support for /autorunwithclose and /autorun switches with the following tools: autofiler, ndpublisher, wdautofiler, emailer, sharefileemailer, wealthaccesser. These switches already worked for ShareFile Publisher.

2.3.59 -

- Added support for XLSX and XLSM files as translator sources. This is part of the existing xlat:xls translator, so no adjustments needed other than pointing the translator at the xlsx file

2.3.58 -

- Regression bug fix introduced in 2.3.52- expiration dates weren't being submitted to ShareFile with file uploads

2.3.56 -

- Salesforce integration - Added ability to set alternate authentication and service endpoints in Salesforce preferences screen

2.3.54 -

- Added retry loop (3 times, 1 second delay between) to ShareFiler uploads that fail with an IOException

2.3.53 — 

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

2.3.52 -

- Bug fix - FINRA enabled ShareFile accounts refused ShareFile upload attempts in the ShareFiler and ShareFileEmailer tools

2.3.51

- Workaround for ShareFile breaking their API on 2/25/2020 (shift from token to code OAuth request types)

2.3.49 - 

- Move to ShareFileAPI-2.0.5 (change JSON date format in ShareFile API requests)
- Make HTML based login screens load faster

2.3.48 - dev release - 

- Fix issue (introduced by change at ShareFile) where document expiration dates were defaulting to 30 days even when 'Never Expires' was selected - we now hard code an expiration date way in the future.

2.3.47 -

- Remove 'Hide Adobe Button' and force setting to false for all existing configurations

2.3.46 -

- Bug fix - ShareFile Publisher was setting the wrong time zone when setting document expiration dates (resulted in documents expiring several hours before they should have)

2.3.45 -

- In Worldox tools, change references to 'profile group' to 'cabinet'

2.3.44 -

- Added logging output when Send To jobs complete in any of the tools

2.3.34 - dev release

- Bug fix - DataBind exception when launching Assemblage with expired license (Java 11 compatibility issue)

2.3.33 - dev release

- Moved to JRE 11 (and Trumpet private Java runtime)
- Updated InstallJava to download from Trumpet's site and to check for version 11 or higher
- Updated the launcher to check Java version against Trumpet's private java runtime

2.3.31 -

- Possible Bug fix - ShareFile users using 'Log in with my company credentials' were seeing "Our site does not support Internet Explorer..." error message

2.3.30 -

- Added aggregateextractor with MAX and MIN types (returns the max or min item returned by the linked extractor)

2.3.27 -

- Added skip(#) to CSV and XLS tranlator query spec. Adding ;skip(3) to the 4th part of the XLS query string, or the 3rd part of the CSV query string, will cause 3 rows to be skipped. Any integer may be specified. If skip(#) is not specified, the default is 0 (i.e. skip no rows)

2.3.24 -

- Bug fix - Java bug (in Java 1.8u161 and 1.8u171 - https://bugs.openjdk.java.net/browse/JDK-8196011) causes application crash when logging into NetDocuments or ShareFile - fix is to force insatlling 1.8u172 or higher
- When Assemblage launches, if it detects that the installed JRE is version 1.8.0_161 or 1.8.0_171, it will launch the Java installer which will download and install 1.8.0_172

2.3.20 -

- ShareFile Emailer now adds mail headers to support SMARSH integration

2.3.19 -

- Bug fix - one site was experiencing out of memory errors during assembling (caused by memory management of stamps)

2.3.18 -

- Updated the version check url to be https to work with the new version update https redirection

2.3.16 -

- Made From email address in the Emailer tool optional. MAPI doesn't require it (though SMTP does), and sometimes explicitly setting it causes MAPI emails to be rejected by the server

2.3.15 -

* The new "From" fields in Sharefile Emailer are not available for MAPI emailing as well
- tpt75829 Fixed bug that indicated a missing From address when MAPI emailing is configured
- Made the Sharefile Emailer "From" fields available for MAPI emailing
- The new "From" field, if enabled (not using the default) is a required field
- If MAPI is configured, the Sharefile Emailer won't show the configured email address in the UI
- Modified SendStrategy to have two new methods, for determining if a custom default from address is supported,
and to retrieve the default from address
- Refactored the "From" field support to remove logic from the SFEmailConfig object, and instead place it
into the presentation model and send entry updater/processor

2.3.14 -

- Modified SFEmailerConfig to store a From address value and a default From address. The default From is reloaded from the stored
preferences each time the config is loaded. (tpt75493)
- Modified the SFEmailerSendEntry object to hold the request From address (default or configured).
- Modified the SFEmailerSendEntryUpdater and ProcessorFactory to use the From address to configure the email sender, if it's not MAPI, with the from address
- Added JCheckBox support to ComponentFactory
- Added bindComponentDisabled() to PresentationModelViewBindingBuilder to allow for components to be disabled from bound properties
- Ensured PDFPrintHandler.exe was packaged with the installer (tpt75829)

2.3.13 -

- Minor code refactoring to Custom Tag editor

2.3.12 -

- Minor changes to refresh error handling to ensure we aren't swallowing errors
- Minor code changes per code review: Tag dialog view layout and string injection, instance type check, etc.

2.3.11 -

- Refactored SourcePath to FolderContentProvider and made it implement ContentProvider
- Created TranslatorContentProvider to provide required files to be translated from a file
- Modified MatchJobPersistentContentHelper to add support for new ContentProviders section, including
support for the new TranslatorContentProvider source
- SourcePath section in WDA is now legacy, and shouldn't be used moving forward. Use ContentProviders instead
- Modified PdfFileContent to have a tag error if the file doesn't exist
- Modified FolderBasedSection to work with ContentProviders rather than SourcePath objects (to support multiple provider types)

2.3.10 - dev release

- Added support for making logical page numbering used in TOC display be equal to the physical page numbering of the resulting PDF (use <toc resetLogicalPageNumberingAfter="y" ...> when defining the TOC)

2.3.9 -

- Modified Custom Tag editor to have same button look-and-feel as other dialogs in Assemblage
- Created ContentProvider interface for common content methods - extracted common methods from SourcePath
- Added JRadioButton support to the PresentationModelViewBindingBuilder

2.3.8 - dev release

- Refactored the Custom Tag dialog into its own class, CustomTagEditor, and made it use the MVC architecture
- Added the ability to tag or clear a tag for multiple assemblies at one time
- Created a DynamicMenuItem for use by the MenuBuilder class, to give better support for dynamic menus and their features
- Centered Custom Tag dialog over the parent frame

2.3.7 - dev release

- Added CustomTag and CustomTags to support the new custom tagging feature
- Modified MatchJobPersistentConfigHelper to load custom tags for an assembly when the config is loaded
- Created a LockingStorage class that will read and write a file, but ensure an exclusive lock first
- Added a LockingKVFileStore class for reading and writing to kv (key/value)(currently csv) files
- Added a LockingKVFileTranslator class for reading a kv file for use by extractors
- Added "kv" as a new translator provider type
- Added getCustomTags() to Section
- Updated AbstractSection to be able to add and get custom tags
- Added a CustomTagAwareSection interface for use by the sections
- Made the AbstractSection store custom tags. Added a method to refresh the metadata for a section programmatically
- Modified MigrationHelper to set custom tags in the assembly sections upon creation
- Modified CompositePresentationModel to set the custom tags into the AssemblyListPresentationModel and update them with changes upon refresh
- Modified the AssemblyListPresentationModel to track custom tags, create actions for them, and display the Custom Tag dialog for a tag and
selected assemblies when an action is triggered
- Modified AssemblyListView to provide a pull right Custom Tags menu on the assembly popup menu

2.3.6

- Bug fix - Some MAPI systems were hanging when ShareFile Emailer attempted to set an explicit From email address

2.3.4

- Fixed status text in email testing that erroneously said test was being done via SMTP server when MAPI was actually being used (this was just a minor UI issue)
s

2.3.3 -

- Added support for patterns in stampPath and rotatedStampPath - the pattern is evaluated against the section ID where the stamp is defined

2.2.161 -

- Ensured the Configuration Chooser dialog closes after the user selects a file from the file chooser dialog
- Set a default minimum size for the Configuration Chooser to prevent previous stored sizes from making the buttons unreadable
- Added the log viewer and log location menu items to Assemblage application and the Scripter tool
- Added Preference dialog support to the Scripter tool
- Resolved several missing menu item text strings in Assemblage
- Modified GUIFramework::PersistentConfigActionProvider to track whether the file chooser was canceled or not

2.2.160 -

- Bug fix - SQL Server connections fail under Java 8 when ssl=required is added to connection string

2.2.158, 2.2.159

—Adjust cache time out for map translators

2.2.157 -

- Bug fix - stamp suppression didn't work on pages inserted using forceLastPageEven or forceFirstPageOdd (the stamps are applied to those blank pages)

2.2.156 -

- Added compatibility with Adobe Reader DC 2017.XXXXX

2.2.155 -

- Bug fix - row2 syntax added in 2.2.154 was sometimes returning an extra .0 (acting as if it were a 'row' function instead of 'row2')

2.2.154 -

- added support for 'row2' syntax in extractor expression language


2.2.153 -

- Bug fix - Table of Content content not being included for TOC entries defined in sub-WDA files
- Bug fix - Table of Content section empty if TOC was included in a sub-WDA file
-Fixed bug in the Splitter that caused a NullPointerException when the Remove Spaces checkbox is enabled.
- Added ability to switch between secure.sharefile.com and secure.securevdr.com servers for ShareFile authentication (use Preferences->ShareFile to switch between them)


2.2.149 -

- Bug fix - when configuring printer settings, the settings weren't sticking


2.2.148 -

- Bug fix - java.lang.StackOverflowError when using AxysItemVariableLookupExtractor on an Axys group that contains itself

2.2.147 -

- Fixing up some old unit tests that weren't behaving
- Modified the PatternProcessor to look for <<text>> in the provided text, and throw an error if found


2.2.146 -

- Bug fix - Java runtime 8u102 and above resulted in HTML editors (in the Emailer and ShareFile Emailer tools) to not function properly
- If Assemblage is being run against Java 8u102 or later, it will have to be upgraded to version 2.2.146 or newer to run either emailer.

2/17/2017

2.2.145 -

- Regression Bug fix - changes in 2.2.143 could result in TOC content not appearing in assemblies where the toccontrol came before the TOC section in the assembly

2.2.143 -

- Bug fix - TOC label issues were being reported even if TOC section wasn't present in assembly

2.2.142 -

- Added support for TLS1.1 and TLS1.2 SSL transport for web services interaction

2.2.141 -

- Updated ShareFileAPI.jar to v0.0.18


2.2.138 -

- Added tool tip text to the "Export without Clear" checkbox in PDF Splitter, to help the user understand the meaning
- Modified the Send "all" button in the various tools to be "Send All [item]", in order to help make the functionality clear
- Added a "Copy to clipboard" menu item to the Print Jobs table in the Print Job Manager
- Added a "Copy to clipboard" menu item to the Issues table in Assemblage
- Added the Assemblage icon to the Unzipper frame
 
2.2.137 -

- Added the ability to test a database connection in the Preferences dialog
- Added the ability to test a Salesforce connection in the Preferences dialog


2.2.134 -

- Issues are no longer generated if a section is conditionally suppressed (if either enabledForAssemblyIdPattern or includedForAssemblyIdPattern returns 'N')


2.2.133

- Added XLSX output mode to APXRunner (latest version of APX generates XLSX files, so configurations need to use XLSX instead of XLS for output mode)

2.2.132

- Installer now prevents installation to special system folders (Program Files, Windows, System32, Desktop)
- Removed the uninstaller - uninstallation should be done by manually deleting the application folder

2.2.131

- Added unit testing for AssemblageTempFolderManager

2.2.130


- Added drag and drop support for extracting zip files into the tools
 
2.2.129

- Added keyup change listening to the email body of the Emailer and Sharefile Emailer tools, to ensure that changes are
    stored to the config immediately.
   
2.2.128

- Modified the width of the email service config port text field, so it shows all digits completely
- Upgraded the file drag and drop for tools, to track the number of failed file adds, and also still add files that
    are valid (which wasn't happening previously.) If any files fail, an message is displayed indicating how many.
- Moved the extractor refresh routine to occur on a cancellable background thread, thus dramatically speeding up
    extraction configuration.
   
2.2.127

- Changed text for the table copy to clipboard menu item to read "Copy to clipboard" for all tables/tree tables
- Modified the error message when email is not configured to actually point the user to the configuration screen.
- Fixed some border appearance issues with the "Publish to" field as a result of the overlay fix
- In Assemblage, fixed issues with improperly configured bookmarks and TOC settings. If values are missing, a
    human readable error message is displayed if the assemblage is prepared.
- Added additional validation to TOC and bookmark configurations in assemblages. Errors are now displayed as
    issues, so they can be properly addressed if desired.
- Added a static extractor called "sharefile.attachments" to Sharefile Emailer, which allows for placing the
    attachment block anywhere within the body of the email.
- Modified Sharefile Emailer to allow attachment block to be placed anywhere in the body of the email text

2.2.126

- Fixed text overlay issue in Sharefile Publisher "Publish to" text field caused by new L&F by modifying the new border
    given to the text component
     
2.2.125

- Added the ability to turn off the expiration date for Sharefile Emailer, as not all users have permissions to set the date

2.2.124

- Fixed bug in Emailer, where special characters were being replaced with "?" in the received email.
- Updated TrumpetEmailSender to v1.0.23

2.2.123

- Fixed issue with Printers card in Preferences, where the table wasn't stretching when the split pane was expanded
- Added an "Export without clear" checkbox to the PDF Splitter. The setting is saved with the config. If checked, Send
    will Export without clear, so the user doesn't need to remember to use that menu item.
- Fixed some layout sizing issues with the results panel of the PDF Splitter
- Added Copy selected rows support to most of the table/trees in Assemblage and the tools
- Made the copied text from the tables/trees match the text visible in them


2.2.122

- Modified the @path command line argument to extract file contents of a folder and subfolders
- Added two new command line arguments, that allow tools to attempt to autorun. In other words, to auto-send
    files configured on the command line. Using /autorun will show the gui still, and /autorunandclose will
    run without a gui and will close the app upon success (and show on failure.) Requires that a
    config file and one or more valid files have been designated on the command line, and that the tool
    has a persisted login authorization. Any error will result in the tool being displayed. No errors results
    in the file(s) being sent to the associated service.
- Configured Sharefiler Publisher to use the new autorun capabilities   
- Added /help or -help as a standalone command line argument, which will print the valid command line argument
    instructions to the console.
- Increased the default height of the Printers table in the Printer configuration within Preferences.
- Modified the Look-and-Feel for the app, adding the Trumpet colors, and giving a more modern look to the app and tools.
- Added Calibri and Segoe UI as available fonts to the emailer interface.
- Enabled the View in Explorer and Preview context menu items in the tools only when a single row is selected.
- Added a 'selected items' count label above the table, which shows the number of items selected in the table
- Added a "Send Selected Files" button to the left of the "Send Files" button in ShareFile Publisher, which sends only the selected files to the service.
    The "Send Files" button now sends ALL files, even if some are selected.
- Added 'Selected Assemblies' count label above the Assemblies table, which shows the number of item selected in the table.
- Added 'Selected Jobs' and 'Jobs' count labels above the Print Jobs table in the Print Job Manager.
- Added a right-click Remove Selected Jobs popup menu to Print Job Manager, to remove selected print jobs from the table.
- Disabled the Start Printing button when no jobs exist in the print jobs table in Print Job Manager.

2.2.121

- Modified WealthAccesser to persist credentials, so login isn't necessary when valid credentials exist
- Disabled the 'Remove item(s)' right-click menu item in Tool tables when no rows are selected
- Added 'Copy selected item(s)' right-click menu item to Tool tables, enabled when rows are selected
 
2.2.120

- Improved Emailer error message displayed when no emailer service is configured and user attempts to send emails.
- Improved Sharefile Publisher send error messages to state if a send fail is due to an upload failure or expiration date update failure.
- Added the ability to delete multiple extractors at once.
- Added the ability to drag and drop a folder onto Publisher (and any other tools with base file functionality), and have
    all child files of the folder added to the list of files to process.
- Added Explore Database to the Tools/Development Tools menu in the tool apps
- Modified the Database Explorer window to show any configured connections, as well as recent URLs
- Made the buttons on the Preferences/Database connections window selection sensitive, and made the Remove button work with all selected rows.
- Added a Remove button to the Licenses window in the Preferences dialog
 
2.2.119

- Improved error message from config queries to be human readable and give good pointers to problem source


2.2.118 -

- Added forceLastPageEven to <section> or <subassembly> elements

2.2.117 -

- Added interleaveBlankPages setting to <section> element of WDA files - if "y", a blank page is inserted after every page in the underlying content (if the source PDF is 3 pages, this will cause 6 pages to be added P1, Blank, P2, Blank, P3, Blank).  Useful if the PDF must be sent elsewhere for printing and we need to ensure that some content doesn't get printed double sided.


2.2.115 -

- Bug fix - Share File publisher tool Publish To path wasn't updating when changes were made to the "Warn if folder does not exist" Folder value

2.2.114 -


- Added support for fontColor in style element, and color in the separator element.  Colors are specified in #rrggbb notation (e.g. #aabbcc)

2.2.113 -

- Bug fix - For sites using SalesForce integration, dragging files to Publisher results in no action when SalesForce credentials are incorrect.

2.2.112 -

- Bug fix - NetDocuments AutoFiler - date fields were not being set properly (undocumented NetDocs API change) - dates should be specified in m/d/yyyy format
- NetDocs Autofiler now validates required fields



2.2.110 -

- Improved error handling in WealthAccess Publisher when logon is no longer valid (error message mistakenly reference ShareFile)


2.2.109 -

- Bug fix - PDFSplitter - Some PDFs resulted in 'Could not find image data or EI' error message


2.2.107 -

- Added concatenateextractor (takes multiple items returned by a linked extractor and concatenates them together, along with a configurable separator) into a single string
- Bug fix - Spitter extractor dialog fails

7/21/16

1/20/16

2.2.74 -

- Added initial branding for Trumpet Publisher for Wealth Access and Trumpet Publisher for ShareFile distributions
- We now create separate installers for TrumpetPublisher4SFSetup and TrumpetPublisher4WASetup
- Added ability to link to separate help pages for each tool (still need to get help pages created and update links references)

12/30/15

2.2.71 -

Bug fix - /close command line argument leaves an assemblage.exe process behind (this prevents the Assemblage installer from finishing running). This was introduced in 2.2.50 (when we added the splash screen).

2.2.70 -

Bug fix - the change in 2.2.66 resulted in HTML body not loading for firms with slow network connections (i.e. config gets loaded before HTML editor renders)

2.2.68 -

- Issue fix - ShareFile Publisher and Emailer tools display white screen instead of login dialog

2.2.67 -

- Bug fix - When sending emails using SMTP (in Emailer or SF Emailer tools), the To and Bcc addresses were being put on the Cc line

2.2.66 -

- Fix - Emailer and ShareFile Emailer tools not properly displaying the HTML editor on machines running Java 1.8.0_60 (Java bug: https://bugs.openjdk.java.net/browse/JDK-8134922 )2.2.65 - 

- Adjusted launcher error message if Java isn't detected to explicitly refer to "32 bit" versions of Java
- Bug fixes for jdbc translator not working properly after 2.2.64 changes

2.2.63 -

- Refactored XLSTranslator, CSVTranslator and SalesForceTranslator so they properly handle query strings that have semicolons inside string literals (previous, the following XLS query would have messed up: Sheet1;split(1,';');1 )
- Added ability to specify column expression strings to SQL translators (xlat:db) - you can now specify the full column expressions (like you do with Excel and SalesForce) to specify the from and to column. Column names OR numbers (1, 2, 3) can be used. e.g. 1;2;SELECT Col1, Col2 FROM TABLE or Col1;Col2;SELECT Col1, Col2 FROM TABLE

2.2.60 -

- Adjust ordinalextractor so it places the ordinal at the beginning of the result instead of the end - so the ordinal (0, 1, 2) will be pre-pended to the results of the associated extractorLink. Document 81000 has been updated with this change.

2.2.59 -

- Added Tools->Preferences to Zipper and ClientView Publisher tools
- Added Help->Check for Updates to Zipper and ClientView Publisher tools

2.2.58 -

- Added ordinalextractor - this will append the ordinal value (0, 1, 2) of the results of the associated extractorLink. See documentation for ordinalextractor in 81000 for details.

2.2.57 -

- ClientView Publisher now auto-fixes Junxure database URL connections to use jtds driver (this was the root cause of the issue we fixed in 2.2.56)

2.2.55 -

- Added preliminary support for installing WealthAccess Publisher to Mac OS X
- Added deployment option for Mac installations ([PreRelease-]MacAssemblage-x.y.z.app.zip gets pushed to getresource)
- Added checks for Windows specific libaries/features (database drivers, WDAPI, MAPI) and don't attempt to load them unless we are Windows

2.2.54 -

- ClientView Publisher bug fix - security changes in Junxure database schema caused publishing to fail with 'permission denied' errors

8/26/15

2.2.53 -

- ND Auto Filer - bug fix - Changing configurations didn't change the attribute patterns if the new configuration pointed at the same cabinet as the old configuration
- ND auto filer - ND logon screen now takes the full size of the auto-filer dialog while the user is logging in
- ND Auto filer - bug fix - the 'Folder' value was being populated even if the 'Save to Folder' checkbox was unchecked

2.2.52 -

- Bug fix - email sender would show Java error from SMTP sender if Mail Username wasn't initialized

2.2.51 -

- Added where empty() syntax to line processor (CSV, XLS, SalesForce query string syntax)
- Bug fix - null pointer exception when handling null column values

2.2.50 -

- Added a splash screen to Assemblage (and other tool) launches

8/21/15

2.2.49 -

- Added Wealth Access Publisher Project default configuration to the workspace folder in the installer

2.2.48 -

- ShareFile Publisher - Adjusted UI related to folder validation (added checkbox to enable validation, rearranged fields)

2.2.47 -

- Added support for ASSYONLY license types - this allows launching of the main Assemblage application, but none of the Publisher or AutoFiler tools are enabled

2.2.46 -

- Regression bug - introduced in 2.2.7 when we moved to MIME uploads - Uploading files from disk that happen to have the same filename as previously uploaded files result in the original file receiving a new version, even though the SF filename was different (sorry this is so confusing - it's a super weird and difficult to explain bug on the SF side)

2.2.45 -

- Bug fix - regression - 2.2.44 resulted in errors if CC or BCC fields were empty

2.2.44 -

- Bug fix - SFEmailer and Emailer tool - added support for sending to multiple recipients (comma separated list into the To, CC or BCC fields)

2.2.43 -

- Bug fix - certain email address formats (i.e. Some Name <email@address.com> ) were failing to send

2.2.42 -

- SF Publisher - folder validation logic not working for sub-folders - i.e. \{portal folder}\subfolder

2.2.41 -

- SF Publisher - Add validation logic to prevent publishing folders that end with period

2.2.40 -

- SF Publisher - adjust labels to read 'Validate folder' and 'Publish to'
- SF Publisher - Bug fix - validated folder was failing validation if it was set to /{someextractor} (hard coded folders worked properly)
- SF Publisher - Display the full Publish To path in the grid
- SF Publisher - If pattern for Validate folder or Publish to fails, insert < MISSING > in to the target path column in the grid

2.2.39 -

- Bug fix - the regresssion from 2.2.37 change - if the SF variable contained underscores, the translator failed with error "Unexpected value _"

2.2.38 -

- Adjusting ShareFile Publisher 'portal folder' UI with Dan's idea of displaying the portal folder as an uneditable portion of the target path

2.2.37 -

- SalesForce translators (xlat:sf) now support expression language on the from and to portion of the query string (i.e. same expressions that are already available in XLS and CSV translators)

2.2.36 -

- Emailer tool and SFEmailer tool now shows warnings if To, CC, BCC email addresses have a space at the end of them

2.2.35 -

- Wealth Access Publisher now allows sub-sub folders by using backslashes in sub-folder names
- Wealth Access Publisher now clears the password when user clicks Logout

2.2.34 -

- Wealth Access Publisher now integrates with the production WA system instead of the development system

2.2.33 -

- Added email address validation (look for @ in email address) to SF Emailer tool and Emailer tool (emailer tool now validates bcc and cc as well as from and to)
- Bug fix - ND Auto Filer save to Folder wasn't resolving extractors ({Client} left in the field value)
- Bug fix - ShareFile Publisher throws null pointer exception when partial extractor is provided in Portal Folder field
- Fixed type-o in 'Publisher to' label (s/b Publish to)

2.2.32 -

- Bug fix - if user clicked 'Test' in Printer preferences in the 'Add Preset' dialog without first configuring the preset, a null pointer exception was thrown. In this circumstance, we now just print to the printer without attempting to load any preset.

2.2.31 - 

- Added Unzipper tool to the tools subfolder

2.2.30 - 

- Bug fix - Emailer tool wasn't validating CC and BCC fields
- Fixed up licensing in Wealth Access tool and SF Emailer tool

2.2.29 - 

- Unzipper tool now supports PUBLISHER, AUTOFILEFOLD, AUTOFILENETDOCS, AUTOFILEWDOX license types
- Added /unzipper command line argument for launching Unzipper tool

2.2.28 -

- Bug fix - the sub-tool configuration and Send buttons weren't getting grayed out while a send was active
- Enhancement - If the user isn't logged into SF in their web browser, navigating to a ShareFile folder from Assemblage will now display a login screen that will take the user to the correct folder after they log in (in the past, if they weren't logged in already, they were not taken to the folder after logging in)

2.2.27 -

- Changed title bar of Emailer and Publisher tools to be "Emailer for XXXX" and "Publisher for XXXX" (instead of "Assemblage XXXX Publisher", etc...)
- Removed hyphen from "E-mailer" window caption
- Overhaul of refresh logic on all tools - refreshes should be considerably more responsive now
- Added features to Publisher for ShareFile so users can better manage when portal folders don't already exist
- Publisher for ShareFile now has a 'Portal Folder' and a 'Sub-folder & filename' field. Together, these define the target path. The Portal Folder will be validated to make sure it exists already and the user will see warnings if the portal folder doesn't exist
- Added right click menu to create the portal folder and take the user to it (so they can provision it)
- Added 'Drop Files Here' label in file drop zone
- Added tools shortcuts for launching Wealth Access Publisher and SF Emailer 

2.2.25 -

- Allow sending via Outlook even if the Windows default mail client isn't set to Outlook

2.2.24 -

- Added validation message if email attachment doesn't have a file extension (in regular Emailer tool and ShareFile emailer tool)

2.2.21

- Bug fix - scripter could cause problems if backslashes were in manually entered items

2.2.17 -

- Bug fix - Java 1.8.0_45 would crash SF Publisher and SF Emailer after the initial login

2.2.16 -

- Adjusted desktop shortcut creation in ShareFile Sales Team installer (fixed up names, added shortcut for Emailer tool)
- Build script now automatically pushes Trumpet Publisher for ShareFile Sales Team installer to getresource and install.jsp

2.2.15 -

- Bug fix - problems with investor extractor resulted in modal error dialogs

2.2.14 -

- Initial working release of WealthAccess Publisher (Send To menu, or launch via /wealthaccesser command line switch)
- Adjusted ShareFile Publisher and ShareFile Emailer so logon screen is displayed full screen instead of inside the Configuration panel

2.2.12 - 

- Fixed case in which emails sent via Outlook (MAPI) can remain unsent within the Outlook outbox on some platforms or some versions of Outlook when Outlook isn't running at the time the user performs the send.

2.2.11 -

- Bug fix - worldox.lfn extractor was resulting in descriptions prefixed with a superscript 2 in some cases

6/4/15

2.2.10 -

- Added preliminary support for Acrobat DC and Adobe Reader DC (Acrobat/Reader 15)

2.2.9 -

- Initial release with ability to send emails using Outlook (as an optional alternate to using an SMTP mail server)

2.2.8 -

- Updated to leverage new Trumpet email component.
- Replaces prior SMTP code with reliance on the new email API.
- Added support for additional email protocol - MAPI.
- Updated email configuration UI to allow user selection of SMTP or MAPI
- Updated email configuration UI to allow test email to be sent via MAPI
- Added logic for detecting availability of MAPI and restricting configuration options accordingly.

2.2.7 -

- Workaround for ShareFile publishing failing at sites with older versions (2.x) of ShareFile local storage center

2.2.6 -

- Bug fix - tab characters in PDF content caused splitter to fail (issue with Adobe PDF print driver at one site)

2.2.5 -

- ShareFile Emailer tool didn't allow sending to multiple recipients (you can now specify multiple addresses in the To field separated by commas, and it will deliver properly)
- Adjusted the column displays to list the filename and the attachment name - and not display CC and BCC (which aren't currently supported anyway)

2.2.4 -

- Bug fix - ShareFile Emailer tool displayed error about From address, even though there is no place to configure a From address

2.2.3 -

- Bug fix - Expiration date in ShareFile Publisher wasn't sticking
- First iteration of ShareFile Emailer tool is functional

2.2.2 - 

- TOCControl can now allow for mutliple lines in a single TOC entry (use \n to insert newline in the text pattern)

2.2.1 -

- Bug fix - Emailer wasn't able to send through Office 365 SMTP server

3/18/15

2.1.30 -

- Bug fix Publisher was failing to set expiration date if the uploaded filename was different from the filename on disk

2.1.29 -

- Publisher for ShareFile enhancement - added ability to set an expiration duration for published files

2.1.28 -

- Bug fix - Advanced Configuration in the Add Items panel of the Scripter tool fails under Java 8 with error 'ReferenceError: "importPackage" is not defined in <eval> ast line number 1'

2.1.26 -

- Increasing communication timeout with ShareFile (trying to resolve 'Connection timed out' errors)

2.1.24 -

- Default height of SF logon screen for new users is now set so the Login button is visible

2.1.23 -

- Bug fix - 'Not connected to ShareFile' warnings appeared after clicking Logout button

2.1.22 -

- Added 'Remove item(s)' context menu to all tools using the new UI

2.1.21 - 

- ShareFile Publisher now presents users with the ShareFile login screen. During login, users who have accounts with multiple repositories can choose the repository they want to work with.
- ShareFile Publisher added right-click > View in ShareFile menu

2.1.20 -

- Better handling when corrupted configuration files cause unexpected errors - prior behavior was to make a backup of the config file then kill it. This is the same behavior, but we've extended the number of error conditions under which this will happen instead of displaying an error to the user and failing the Assemblage launch)

2.1.19 -

- Improve error logging when sending fails in any of the new tools (now include the ID of what we were sending when the send failed)

Summary 2.1

• The Emailer Module now has a rich text editor, giving you better control over the look and feel of the emails you send from Assemblage. Customize the formats, font and images in your email.
• The Scripter tool now allows you to generate Excel files rather than PDF files.  This is a great way to deliver reports to CPAs who wish to upload those files to their tax software.
• Trumpet Publisher's integration with NetDocuments now allows for one-click filing.
• Deeper integration points with Java version 8

2/20/15

2.1.18 -

- If there are translator configuration errors, throw exception instead of silently pretending there wasn't a translator2.1.16 - dev release

2.1.13 -

- Added Insert Image button to Emailer tool

2.1.12 -

- Bug fix - Scripter wasn't working under Java 8. We now have a compatibility shim that we automatically insert on Java 8 machines

2.1.11 -

- Added Hyperlink button

2.1.10 -

- Emailer tool enhancement - Emailer now supports rich text (HTML) editing, image insertion

2.1.9 -

- Bug fix - regression in auto-translation of ODBC connection URLs for some translatorUrl values

2.1.8 -

- Bug fix - auto-translation of ODBC connection URLs wasn't working for named database connections

2.1.6 -

- Junxure SQL connection string wasn't auto-converting to jtds URLs when the string started jdbc:odbc

2.1.5 -

- Move to different database drivers (we have tried to make this self-upgrading, but reconfiguration of some database connections may be necessary)
- Bug fix - Worldox field extractors were causing Assemblage to crash

2.1.4 -

- NetDocs Auto Filer will now preserve the file's modification date during filing

2.1.3 -

- Added setOutputMode() to APXRunner in Scripter. Valid values are as follows:
- setOutputMode(APXRunner.OutputMode.PDF);
- setOutputMode(APXRunner.OutputMode.PDF_ACROBAT);
- setOutputMode(APXRunner.OutputMode.XLS);
If you use XLS, be sure the output file field in the Scripter has the correct XLS file extension!

2.1.2 -

- Bug fix - AUTOFILENETDOCS licenses weren't working (showed as INVALID) - inconsistent definition between application and LMS coding

2.0.33 -

- ND Auto Filer will now also accept AUTOFILENETDOCS license types (in addition to ASSEMBLAGE, ASSEMBLAGEB, NDPUBLISHER and DOCBRIDGE)

2.0.32 -

- Installer now writes Trumpet-UpdateHistory.txt in the application home folder to track update history
- First release with new Net Documents Auto Filer tool)

2.0.31 -

- Bug fix - Emailer shows 'Can't have more steps than the total' error after sending one email

2.0.30 -

- Bug fix - null pointer exception when opening print manager if no default printer is available

2.0.29 -

- Installer wasn't always defaulting to the previous install path. We now write and read the install location to HKCU "SOFTWARE\Trumpet\Assemblage\InstallPath"

2.0.28 -

- If CSV file is passed in using @ parameter, ignore rows that start with a semicolon (comment lines)

Summary 2.0.27

Worldox Auto-Filer Enhancements:

• Added "Create Relationship" checkbox.  When this checkbox is selected, the newly filed documents will be set up as children of the specified path identified in the field,
• When the "Delete Original After it's been Filed" checkbox is selected, the Worldox Auto-Filer will delete the files from the input folder after they've been successfully filed.  Now, you don't have to delete the files as a separate operation.

Worldox Auto-Filer, File System Auto-Filer and Trumpet Publisher Enhancements:

• View in Explorer - You can now right-click on a document in the document list and chose "View in Explorer".  This will open up Windows Explorer, highlighted on the document you've selected.
• Preview - You can now right-click on a document in the document list and chose "Preview". This will open a copy of the document.  This can be handy if the filename doesn't include useful information you need to identify for mapping purposes.
• Docs / Minute Readout - This display provides you with an estimated time required to file or publish documents.  It can be found at the bottom of the window once you've opted to split / publish / file the documents.
• Cancel - You will now see a "Cancel" button.  This allows you to stop the tool from splitting, publishing, filing - whatever tool you're working in - in case you need to make changes.

2.0.27

- Publishing to ShareFile failed with a NullPointerException
- Better error message if servername isn't valid

2.0.26 -

- Tools now have a expand/collapse button on the divider bar between the configuration and the entry list (allows viewing the list in full view)
- WDAutoFiler now shrinks the configuration view of the fields aren't part of the selected profile group (previously, the fields were hidden, but they still took up space)
- The 'Delete the original after is has been filed' checkbox is now visible when not in edit mode, but it is only enabled (i.e. user can only change the setting) if in edit mode (old behavior was to not show the setting at all - this could cause user to not understand the behavior of the configuration)

2.0.25 -

- When WDAutoFiler fails on a document, it now waits 3 seconds between retries, and will retry up to 10 times

2.0.24 -

- Fix potential problem with 2.0.23 change when all list items are being processed and user adjusts sort order

2.0.23 -

- UI improvement - all tools - users can now interact with the entry list at the bottom of the tool display while the processing is underway.
- Added 'Cancel' button to the tools (b/c we no longer have a modal progress dialog with a cancel button)

2.0.22 -

- WDAutoFiler feature enhancement: 'Delete original after it has been filed' checkbox. When active, files are removed from their original location after being filed to Worldox. This setting will only display when in Edit mode.

2.0.21 -

- WDAutoFiler when run from the command line was not auto-loading the configuration provided after /wdautofiler

2.0.20 -

- If WDAutoFiler enters a retry loop, the status of the retry attempts is now displayed in the progress bar text

2.0.19 -

- Performance fix - dragging a large number of files to WD Auto Filer resulted in significant UI hang (the refresh was happening on the GUI thread instead of a background worker thread)
- Added retry loop to WDAutoFiler - if the auto-file fails, we will try again up to 20 times, waiting 250 milliseconds between each attempt
- Added Docs/Minute read-out when auto-filing
- WDAutoFiler wasn't always disabling the Save Files button during refresh

2.0.17 -

- Pattern inspector now gives explicit info about whether the results were empty strings, or empty result
- Pattern inspector no longer supports inline regex in pattern expressions

2.0.16 -

- Bug fix - Database explorer would fail with arrayindexoutofbounds when displaying byte arrays that weren't 16 bytes or longer
- Database explorer will now silently translate &lt; &gt; and &amp; so users don't have to edit that when they copy and paste from the WDA file

2.0.15 -

- TOC generation - added special extractors that can be used in toccontrol: {toc.chapter} and {toc.localchapter} - see doc 81000 for details
- TOC generation - new TOC style setting: horizontalAlignment (LEFT, CENTER, RIGHT) - default is LEFT. Note: this only takes effect if includeNumber is N

2.0.14 -

- APX Runner - if no user is specified, the current user will be used

2.0.13 -

- WD Auto Filer bug fix - if extractor in comments resulted in No Value (instead of empty string), no Problems were displayed, and the auto file failed with a null pointer exception
- WD Auto Filer validation enhancement - if an extractor for a field results in No Value (instead of empty string), a Problem is now displayed. Users can check the 'Use empty string when exctractor fails' checkbox if they want the value to be empty when extraction fails

2.0.12 -

- Added setMaxMillisToWaitForPdf to ApxRunner:
- Determines how long Scripter will wait (in milliseconds) to detect the result of the PDF generation. After the call to RepRun returns, we poll ever 250ms up to this timeout. Default is 1250ms.

2.0.11 -

- Bug fix - launching WDAutoFiler without Worldox running resulted in strange error message. We now present a configuration validation error.
- Bug fix - really old WDA files that had the deleteUsedFiles attribute set on sections caused an exception when loading in modern Assemblage

2.0.10 -

- Bug fix - The change in 2.0.8 caused SAXParseException exceptions while loading WDA files that used CSV and XLS translators

2.0.9 -

- Bug fix - WDAutoFiler - non-required, table validated fields were throwing errors if value was empty

2.0.8 -

- Bug fix - if CSV translator URL was empty, the translator failed instead of assuming 1;2
- Bug fix - if XLS translator URL was empty, the translator failed instead of assuming 0;1;2

2.0.7 -

- Bug fix - WDAutoFiler - if parent field was not table verified, validation of values in child field failed

2.0.6 -

- Bug fix - Emailer tool - CC and BCC were not resolving patterns to values

2.0.5 -

- Move to Java 7 runtime for Assemblage
- Assemblage.exe launcher will now check to ensure that the workstations has Java 7 or higher installed
- Assemblage directory now contains an InstallJava.exe applet - when launched, this will check if Java 7 or higher is installed. If not, it will download Java 7 and install it. This is safer than using the java.com installer b/c we can turn off the Ask toolbar garbage and prevent the Java browser plugin from being installed.
- Bug fix - created date on assembled PDF files wasn't being updated to the date the assembly happened, if the file already existed in the working folder

2.0.4 -

- Attemped Bug fix - created date on assembled PDF files wasn't being updated to the date the assembly happened, if the file already existed in the working folder

2.0.3 -

- Bug fix - WD Auto Filer fails with 'From File is invalid(18)' error when autofiling files with very long paths. This fix requires that 8.3 filenames are enabled on the *source* file system as well as the target file system (if those are different file systems).

2.0.2 -

- Added encryption strength setting to Emailer tool - available values are as follows (along with which versions of Acrobat are capable of decrypting PDFs generated with this encryption level):
Acrobat 3.0 and later (RC4 40)
Acrobat 5.0 and later (RC4 128)
Acrobat 7.0 and later (AES 128)
Acrobat 9.0 and later (AES 256)
- Changed default encryption strength to AES-128 (Compatible with Adobe 7 and higher) (used to be RC4 128)

2.0.1 -

- Added Tools->Development Tools menu to all sub-tools
- Added internal log viewer to Development Tools in all sub-tools

Summary 2.0

• Added support for printing to Acrobat XI
• Improved performance for "Send to > Printer" operations
• PDF splitter is now 25% faster when reading large PDF files
• When you hover over an item in the display lists of the Emailer, Publisher, or AutoFiler tool, you will see the full text
• You can now copy and paste the status grid from the Emailer Tool for compliance purposes. This includes the document identifier and the date sent
• Added option "SSL w/Self Signed Cert" to the Emailer Tool's preferences as an authentication method for users with Self Signed Certificates

1.1.134 -

- Added Help menu to sub-tools (New UI based tools only)
- New feature: Added CC and BCC addresses to emailer configuration

1.1.133 -

- Bug fix - if translator returned no value, the regex result was being passed through as if the translator hadn't been specified. Bug introduced in version 1.1.113

1.1.132 -

- Bug fix - Sites on 1.1.91 through 1.1.111 that use the Tools shortcuts lost their settings after updating to 1.1.112 or above.

1.1.131 -

- Added PUBLISHER to allowed license type for the ND Publisher Tool

1.1.130 -

- Added ZIPPER to allowed license type for the PDF Splitter tool

1.1.129 -

- Added PUBLISHER to allowed license type for the PDF Splitter tool

1.1.128 -

- Significant performance enhancement for axysparentlookupextractor (esp. for large data sets)
- axysparentlookupextractor will automatically remove the + aggregate marker from the front of any input text
- axysparentlookupextractor will remove spaces before or after the input text before looking up the parent group(s)

1.1.127 -

- Bug fix - window icon for Pattern Inspector came up as a cofee cup instead of the Assemblage icon
- Added 'Configuration->Edit configuration file' menu
- Pattern Inspector overhaul
  - you can now specify the WDA path explicitly.  This will load and process the extractors in the WDA without having to actually load the assemblies (should make design iterations much faster)
  - the default WDA path is pulled from the current loaded WDA (if there is one)
  - there is a drop down MRU for the WDA Path field, so you can quickly flip between them during pattern development
  - if the modified date of the WDA changes, the file is automatically reloaded when you click the Refresh button
  - Improved the window layout of pattern inspector (it resizes a lot nicer now)

1.1.126 -

- Bug fix - PDFs that used fonts with space character width set to 0 wound up with extra spaces in their text extraction during splitting. If the space width is 0, we now use the default glyph width as the space width.
  - new itextpdf-5.4.5-20140116.jar

1.1.125 -

- Bug fix - entities aren't always grouping together if there is case difference between the sortby values. This also fixes an issue with duplicate entries appearing in the Details pane during refreshes.

1.1.124 -

- Added expandAggregates setting to axysparentlookupextractor. The default is true (+@groups below the parent are expanded to get their children).  If set to false, aggregate groups become children.

1.1.123 -

- Splitter now accepts AutoFilerFolder licenses

1.1.122 -

- Bug fix - if Scripter was unable to clear output folders, it silently failed.  We now display a modal error dialog.  This can happen if the output folder contains a sub-folder.

1.1.121 -

- Bug fix - suppressstamp instructions that happened before stamps were inserted didn't impact that stamps.  For example- in the following, the suppressstamp wasn't actually suppressing the stamp:
    <assembly>
      <suppressstamp>
      <section>
        <stamp>
  The reason this bug existed was that suppressstamp was originally implemented to suppress stamps like page numbers from certain sub-sections.  It now works *both* ways.
 

1.1.120 -

- Add status of stamp (Suspended or Active) to TagView display
- Add tags assigned to stamps in TagView display

1.1.119 -

- Send heartbeat when a license is removed from LicMgr (it used to only send when a license was added)

1.1.118 -

- Errors during reading of XLS files now display the name of the file

1.1.117 -

- Assemblage now writes it's path to HKEY_CURRENT_USER\Software\Trumpet\Assemblage\InstallPath whenever it launches
- The installer now uses the path at HKEY_CURRENT_USER\Software\Trumpet\Assemblage\InstallPath.  If that path is missing, it then uses the old behavior - HKEY_LOCAL_MACHINE\SOFTWARE\Trumpet\PDFSplitterAndAssembler\InstallPath - and if that's missing, it sets the value to "<network path>\Assemblage"

1.1.116 -

- Installer will now close running instances of Assemblage, if it can (obviously, we can't close older instances b/c that code wasn't part of the application back then)

1.1.115 -

- Installer now defaults to <network location>\Assemblage
- Bug fix - multi-extractors in wda files could cause big ugly errors if the translator returned multi-values (issue introduced in 1.1.113)
- Patterns now support -> notation to create chains:  {{ex1}->{ex2}->{ex3}}
- Added new translator:  worldox.lookup - the value passed in is used as a doc ID search against Worldox and the path of the found document is returned.  This can be used in conjunction with the other worldox.* extractors to do some pretty cool stuff.

1.1.114 -

- Assemblage now sends a heartbeat whenever it launches and when a license gets added through the UI
- Installer no longer sends heartbeats
- Installer now shows a big message for brand new installs (trying to discourage users from installing into an incorrect folder)
- WDAutoFiler now has a Create Relationship checkbox and field.  When checked, the newly filed documents will be set up as children of the specified path

1.1.113-

- Change extractors used in tools so if the underlying translator returns multiple values, it will throw an error instead of just picking one of the values at random

1.1.112 -

- Added Tools->Development Tools->Show logs folder to main Assemblage and Tools->Show logs folder to all 'new UI' tools

1.1.111 -

- WDAutoFiler now specifies the profile group number the same as WDAdmin's ID (it used to be one more than what appeared in WDAdmin).  Old WDF configuration files are automatically adjusted to account for the difference in behavior.
- Bug fix - shortcuts in the Tools folder had incorrect 'Run In' path set (they would prompt for license number when used)
- Bug fix - shortcuts in the Tools folder had incorrect icons

1.1.110 -

- Bug fix - Send To->WD Auto Filer wasn't bringing up new tool

1.1.109 -

- New UI tools now display number of rows in a label
- DB Explorer displays number of rows in the field explorer (the dialog that comes up after clicking Inspect Selected)
- Make Extractor list have an extra column that displays the current extracted value of the selected row in the tool
- Added View In Explorer and Preview context menus to WD Auto Filer, File System Auto Filer and ShareFile Publisher
- WDAutoFiler now works with Worldox Cloud and Enterprise

1.1.108 -

- Bug fix - NullPointerException in FolderSearchItemSource if the URL in the shortcut file is invalid
- Clicking the X in the configuration chooser now closes the tool (for users to get to the tool in it's default state, they have to click the New button in the configuration chooser)
- In any tool, the prompt to save changes to a config now only displays if the tool is in Edit mode (avoid problems with users accidentally overwriting configuration)
- Initial work on WD Auto Filer user interface overhaul

1.1.107 -

- Bug fix - null pointer exception in bytesToHexReverse in some corner cases when displaying fields of type sql_variant

1.1.106 -

- Added 'SSL w/ Self Signed Cert' option in email configuration - should help SSL situation where the certificate is self signed, and the user doesn't want to register the certificate with the JVM

1.1.105 -

- PDFPrintHandler - added debug lines (tracking down a crashing issue)
- Added Trumpet Publisher Project sample project to installer
- Updated to jWDAPI 20130508 - adding ability to detect when WDAPI doesn't load (vs has errors)

1.1.104 -

- New license types AUTOFILEFOLD (identical to FOLDERAUTOFILE), AUTOFILEWDOX (identical to WDAUTOFILE), PUBLISHER (identical to WEBUPLOAD)
- Make Assemblage installer run with regular User priveleges (trying to avoid UAC elevation prompt)

1.1.103 -

- Added Schema and data type columns to dbExplorer
- Properly display UUID type fields (SQL data type uniqueidentifier)

1.1.102 -

- Added FormType extractor to Fidelity Unzipper tool - Fidelty unzipper extractors are now: "AccountNumber", "ClientID", "FileName", "FormType"

1.1.101 -

- Bug fix introduced in 1.1.100 - an old itext jar file was part of the distribution - definitely no good - treat version 1.1.100 as completely broken

1.1.100 -

- Bug fix - some PDFs (annotations added in conjunction with digital signature) caused Heap Space errors

1.1.99 -

- Made APXRunner only include the -N (run as user) option if the ScriptRunnerCommand is "REPRUN" (this option isn't supported under other run types like SSRSRUN)

1.1.98 -

- Added setScriptRunnerCommand(String) command to APXRunner.  Valid values are "REPRUN" (the default) and "SSRSRUN".  This will allow users to run using the old and new style reporting engine

1.1.97 -

- Better error message if sub-extractor specified in GroupingExtractor doesn't exist

1.1.96 -

- Bug fix - if WDAutoFiler was launched, then at some point later, Tools->Preferences was opened, the preferences were reset to their default values.  If the OK button was clicked, the preferences in the .globalsettings folder were lost.

1.1.95 -

- Default splitter configuration will now have pattern set to {id} and a default extractor named id with regex set to ##(.*)##

1.1.94 -

- Bug fix - PDFSplitter wasn't properly parsing text from some PDF files that contained unusual character encoding strategies

1.1.93 -

- If Assemblage is not able to access the .globalsettings folders, it will now fail to launch instead of launching with default values

1.1.92 -

- Emailer - copy and paste of Emailer status grid will now include the document ID and the date sent as a human readable string

1.1.91 -

- Bug fix - Print To would crash in some cases
- Print To operations are now faster (better optimized checking for whether Acrobat is running before we send a print job)
- Installer now creates a sub-folder called Tools with links to each of the sub-tools

1.1.90 -

- Bug fix - Acrobat XI support (added in 1.1.87) was not working

1.1.89 -

Bug fix - If Storage Path in ClientView Publisher results in a null value for any document, processing halts completely at that document with error message 'Unable to complete submission'

1.1.88 -

- Bug fix - in some extremely rare circumstances, corruption in a config file (used for storing the window size and position) could cause a NoSuchElementException error

1.1.87 -

- Added support for bulk printing to Acrobat XI (also pre-emptively added support for Acrobat XII when it comes out)
- New verison of PDFPrintHandler.exe - 1.0.0.30

1.1.86 -

- Bug fix - SalesForce integration was only returning first 2000 rows of queries
- Installer now gives Retry option if it is unable to replace or remove existing files

1.1.85 -

- Bug fix - worldox.* extractors weren't available in Emailer and Sharefiler tools
- Added logging if license is invalid or is about to expire
- If global settings can't be loaded, we rename the problem config file to a backup name (config file name + date stamp) - hopefully this will help us with tracking down issues related to global settings resets

1.1.84 -

- Bug fix - Send To->ShareFile didn't do anything
- Hovering over list items in any of the 'new' style tools displays tool tip with the full text
- Adjust labels in ShareFile preferences screen to be more obvious of expected value for 'host'
- Simplified configuration of ShareFile settings - now we only ask for the target path, instead of a separate basepath and subpath

1.1.83 -

- Bug fix - Splitter - editing extractor pattern with an invalid pattern resulted in a modal error dialog instead of in-line error message
- Significant performance enhancements when reading large PDF files - splitter is now 25% faster

1.1.82 -

- Added /sharefiler command line switch
- Ability to specify a file list without a configuration file on the command line (i.e. /emailer @%@) without getting an error message
- PDF Splitter now displays performance metrics during analyzing (pages/sec) and splitting (exports/sec)

1.1.80-

- Allow PDFSplitter to handle much bigger files

1.1.79 -

- Make CSV translator query strings support the complex syntax that XLS translators have

1.1.78-

- Added Copy button in extractor lists throughout Assemblage where new tool UI has been implemented (Splitter, autofiler, emailer, etc...)

1.1.77-

- Splitter - Inline regular expressions are no longer allowed in the Subsection ID pattern field
- Splitter - when loading legacy configurations, all extractors are converted to named extractors (regardless of whether a region was specified on the ID field or not)

1.1.76-

- Ability to clear all files for selected section(s) (right-click on section(s), Delete files)

1.1.75-

- Bug fix - corrupted MRU configuration file resulted in Assemblage not launching.  Assemblage will now launch properly.
- Splitter is now 20% faster
- Splitter now supports multiple text extraction zones via the user of independently configured extractors
- Splitter now displays the text on a given page during configuration of each extractor

1.1.74 -

- ClientView Publisher now populates filesize and Publish Date fields in ClientView

1.1.73 -

Resolved an issue with querying Junxure's tblclientsunfiltered table
Auto Filer will now warn if there is not a file extension in an output path.

1.1.72 -

Added /emailer command line switch for launching Emailer tool stand-alone
Added ability to drag files onto Emailer tool

1.1.70 -

Allow assembling PDFs that are partially secured (i.e. restricted)

1.1.68 -

'Hide Acrobat during printing' is now unchecked by default - this feature was causing too many problems

1.1.67 -

Added Salesforce support (Additional Salesforce configuration in preferences, plus new xlat:sf translator type - the url is only xlat:sf (nothing after it) - the query is of the form <from spec>;<to spec>;<SF query> - for example: "Name;Contacts.records.FirstName;SELECT Account.Name, (SELECT Contact.FirstName, Contact.LastName FROM Account.Contacts) FROM Account"

1.1.65 -

Bug fix: NullPointerException when a file that is part of an assembly is renamed without performing a refresh - error message now describes the issue and resolution (Tools->Refresh)

1.1.64 -

Bug fix: Unparseable date: "" errors when using CV Publisher without Expiration Date filled in
Bug fix:  [Microsoft][ODBC SQL Server Driver]Optional feature not implemented error when using CV Publisher with Expiration Date filled in

1.1.63 -

Made Emailer Configuration Chooser and File System Auto Filer Configuration Chooser have a window title

1.1.62 -

Added new command line option to Assemblage.exe to control the size of the heap that will be requested
  -    /maxheap=### (where ### is the size of the desired heap in MB).  The default is 768MB.  If you want to allocated 2GB of heap (2GB = 2000 MB), you would use: assemblage.exe /maxheap=2000
  -  Note that the adaptive heap algorithm may decide to actually set the value to lower than you request - the actual value used is in the -Xmx value visible using /launcher_verbose
There is also another command line argument that may be of use - this has been in the launcher for awhile, but not documented:
   -  /launcher_verbose   - this will display a summary of all of the options that are being used when setting up the java virtual machine (this also writes a text file with the same information to a file called launcher.txt in the current working directory (normally, this is the network Assembalge folder)

1.1.61 -

Fix for "There is a problem with the 32 bit Java installation on this computer" error on computers with small amounts of RAM (i.e. 2GB or less)
    - New launcher that dynamically determines the maximum heap (memory) size that will be available to Assemblage
    - We try for 1 GB of heap space - if we don't get it, we then reduce the heap until we are successful
    - Note that it is possible for this error to occur for other reasons - in the new code, the error message has been adjusted to also display an error code - the (-4) error code indicates a memory related issue.  Other error codes could be caused by other problems, including corrupted Java installations.

1.1.60 -

Added support for Expiration Date to ClientView Publisher (published documents can now be set to expire on a certain date)

1.1.59 -

Bug fix: AutoFiler would show "Warning - File already exists" immediately after auto-filing each PDF.

1.1.58 -

In Edit Extractor dialog, if extractor returns no result, the result now displays as "## No Extractor Result ##" instead of just a blank

1.1.57 -

Bug fix - introduced in 1.1.49 - NPE in CVPublisher if database preferences didn't contain the database named in the CVPublisher configuration
 
1.1.54 -

Emailer and AutoFiler - If a send entry has validation Problems, and the user clicks Send anyway, we now error saying "See Problems" instead of allowing the underlying error (which is usually an NPE) to surface
If there are multiple problems/warnings for a Send entry, we now add (hover for details) to the end so the user knows they can hover to get the details of the problems/warnings

1.1.53 -

Extractor list now fills available vertical space in emailer and file system auto filer tools
Bug fix - changes to extractor list weren't taking effect in emailer tool
Bug fix - emailer tool was saving new configurations with afl file extension instead of .emailer

1.1.52 -

Bug fix - NetDocs Publisher wasn't generating meta.csv file contents
Added progress bar to NetDocs Publisher
Bug fix - NetDocs Publisher wasn't displaying all column data immediately after loading a configuration

1.1.51 -

Made default interface type be DEFAULT (this is the same as V2 for the time being - but it allows overriding with the /3 command line switch).  There should be no impact on our deployment process from this change - you should continue setting the V3 interface in the preferences after installing the first time.
Fixed bug - "Problem Last component must be non-null" error when launching Assemblage with V2 interface on workstaiton with Java 7 installed
Better error message if translatorFromExtractor refers to an invalid extractor

1.1.50 -

Add APX preferences screen for centralized APX configuration
Adjusted APXRunner to use preferences instead of settings being hard coded

1.1.49 -

Initial implementation of APXRunner for scripter to use
Better error messages in Scripter output log
Made CV Publisher so it will look up the Junxure URL value in the Database manager first.  If that doesn't exist, it will evaluate the URL as a jdbc url

1.1.48 -

Bug fix:  Verbose output in scripter wasn't showing all debug messages

1.1.47 - dev only

Adjusted NetDocs Publisher tool so it works with files instead of Assemblies
  - this adjustment has a breaking change that WILL break existing NetDocs Publisher configurations.  We are changing the definition of the ID column to be the full path of the file instead of the assembly ID.  Please coordinate updates with any sites that currently have the NetDocs publisher
Added /ndpublisher command line argument to launch the ND Publisher

1.1.46 - dev only

Tools->File System Auto Filer now opens the new auto-filer interface
Dragging files from the file system to the new auto-filer list will add the files to the list for processing

1.1.45 - dev only

Added 'Show Assemblies' right click menu to section list

1.1.44 - dev only

Allow toggle enabled to work on multiple sections at a time
 
1.1.43 - dev only

Single clicking on Sections no longer changes the main Assemblies list to focus on that section.  You must now double click on a section to shift focus to it.  I'm calling this the 'focused section'
Focused section displays in bold and has "(showing assemblies)" after the section name - let me know if this should be changed
Added Toggle Enabled right click menu to Section hierarchy view
Section icon now grays out when the section is disabled via the Toggle operation
Validation rules specific to a section are now removed when the section is disabled via the Toggle operation
 
1.1.42 -

Added Firmwide.inf path to Axys settings.  If specified, AxysRunner will use this as the firmwide.inf file instead of the one in the Axys root directory

1.1.40 -

Adjusted sort behavior of tool entry list so errors sort above warnings (then we sort by the number of issues, which is what we did before), then we sort by the text of the issues
Made list validation message list number of errors and warnings if there are both

1.1.39 -

Bug fix:  Print Manager displayed MISSING printers (resulting in Null printer exception if the user attempts to print to it)
Bug fix:  Capturing Printer Defaults Failed - SUCCESS_CloseAcro(0x83)
Bug fix:  Sorting columns in tool entry list causes NullPointerException

1.1.37 -

New license manager behavior:
 - once the user puts in a new license for a given type (i.e. ASSEMBLAGEB), any old licenses for that license type will be removed from the license manager user interface automatically (prior to this, users had to type the Delete key to remove an old license).
 - expired licenses will be automatically removed from the user interface after they are 90 days past their expiration date
 - The user will now see a dialog warning that their license will expire in XX days

1.1.36 -

Changes to the standard tool behavior:
 - Added edit mode toggling (for now, this just shows/hides the extractor list)
 - Added graphical progress bar
 - Added list validation message (gives a quick summary of the total # of errors or warnings in the list - displayed right above the Send button)
 - Added Refresh menu
Auto filer:  Added check if target file exists for each list entry (marks entry with a warning if it does)

1.1.35 -

Added better error trapping to extractor editing dialog (should fix validation display issues seen during testing)
Better error checking if config file specified on command line does not exist

1.1.34 -

Bug fix: Right click/filter on section list when no section is selected shows NullPointerException error
Updated default Workspace - added a blank metadata section to assemblies
Changed Emailer to use new standard tool interface
Changed File System Auto Filer to use new standard tool interface

1.1.33 -

In main Assembler, Send To operations will apply to ALL assemblies if no assemblies are selected when the Send To command is invoked
During install, we now log the version of installer to Trumpet-UpdateHistory.txt

1.1.32 -

Fixed nullpointerexception in splitter when loading configurations that didn't have rectangle filters defined
Improved Help->Check for Updates so it now lists production release and pre-release downloads (if appropriate)

1.1.31 -

Changed wording in assemblage.exe error message that displays when the JVM couldn't be loaded to indicate that it should be 32 bit Java
Bug fix - fix problem with "Colorspace not supported" and "Color depth not supported" warnings during splitting some PDF files

1.1.29 -

Fixed problem with auto-filer copying huge files

1.1.28 -

Better error messages if preview assemblying fails
Better error message if an input PDF is corrupted

1.1.27 -

Overhaul of Email configuration dialog, added support for TLS and SSL authentication types

1.1.26 -

Added 'Hide Acrobat during printing' checkbox to Print tool - this means that we can truly do background printing and let the user continue working.  This is enabled by default (printing will be done 'silently' by default), but you can change it back to the old behavior if needed for troubleshooting
Acrobat will now be closed before and after running of print jobs

1.1.25 -

Added Help->Check for updates menu - this will check for the latest production and prerelease versions and allow the user to download the latest one

1.1.24 -

Bug fix: ERR_NOSUCHFILE when trying to print assemblies that contain double spaces in the name

1.1.23 -

Bug fix - driver class in connection info wound up null in some scenarios

1.1.22 -

Added replace(<col spec>, <findtext>, <replacewith>) to column specification language

1.1.21 -

Bug fix - null pointer exception in splitter (Embedded image with no resource dictionary defined)
   
1.1.20 -
    
Bug fix - classcastexception when loading WDA files in V2 interface

1.1.19 -

Changed field label in SQL add items wizard from 'URL' to 'DB Connection Name'
Optimized handling of big PDF files (should be much faster now)

1.1.18 -

Bug fix - errors resulting from XLS cells containing formulas caused xlat:xls translators to fail
XLS Reader will no longer return "Error :xx" if an Excel cell has an error - it will just return blank

1.1.17 -

Make SQL item source (in scripter) so it can work with database connections configured in preferences.  For backwards compatibility if you specify a full SQL URL (jdbc:odbc:......) in the database connection field of the SQL Add Items dialog, it will still work, but certainly the preferred method moving forward is to use a named database connection.

1.1.15 -

Bug fix - printer list showed multiple instances of the same printer with different case if the printer as mapped has different casing than it did when the printer configuration was originally set up.  Printer lookup by name is now case insensitive.

1.1.14 -

if translatorQuery isn't specified, it will be assumed to be ""
Filenotfound error when saving settings will now contain the full path of the file (instead of the relative path)

1.1.13 -

New assemblage.exe launcher with improved error messages if Java isn't installed on the workstation
Bug fix - unable to load preferences (like DB connections) after update to Java virtual machine where the vendor name switched from Sun to Oracle

1.1.11 -

Adding support for Acrobat PDF print driver in PPT and XLS -> PDF conversion.  Use runner.setPdfPrinterService("Acrobat"); in the script

1.1.7 -

Added Send Test Email to email configuration dialog

1.1.6 -

Added searchParents setting to axysitemvariablelookupextractor (setting this to N will make the variable lookup happen in the item only, instead of also searching parents for that variable value)

1.1.2 -

Bug fix:  subassembly elements with sections sub-element (instead of wdaPath) wound up getting double TOC, bookmark and stamp tags

1.1.0 -

Added ability to place <sections> sub-element inside <subassembly> elements

1.0.372 -

Fixed bug that caused XLS item sources in scripter to skip over the first row of data

1.0.369 -

Made directToAcroMode work for 64 bit operating systems

1.0.367 -

Added axysordinallookupextractor

1.0.366 -

Added SMTP Port number to email configuration
Blank SMTP usernames will now be sent as null instead of a blank string (needed for some smtp servers)

1.0.362 -

Attempted to fix all places where the default selected folder was going to My Documents instead of the network folder for Assemblage
Changed strategy for determining the Assemblage network folder to use application.home system property (which gets set by our launcher)

1.0.361 -

adjusted launcher so it fixes DLL load path problem - msvcrt71.dll not found
Changed heap space to be 768 MB instead of 512 MB (address issue with huge assemblies)

1.0.360 -

Added .setRunGroupsConsolidated(true/false) to AxysRunner - if true, any @ group passed in will be prefixed with a + before processing

1.0.357 -

Added Edit file on disk menu option to build plan tree view (opens the source file directly where it can be edited)

1.0.356 -

AxysManager now reads netwide.inf to determine cli and grp folder locations (if netwide.inf exists) instead of just assuming the folders are under the axys home directory

1.0.355 -

Added Tools->Preferences to Emailer and Splitter tools

1.0.354 -

Improvements to Emailer:
1. allow creation of emails without attachments
2. encryption is optional
3. columns are sortable
4. better error messages if something goes wrong during send

1.0.353 -

Added DB Explore button to database connections preferences dialog (allows quick testing of URL)

1.0.352 -

Work around for compatability problem with upcoming Junxure release (may/june) that contains a significant security overhaul.  Magic transforming of 'tblclientsunfiltered' to 'tblclients' in any query with a URL that includes the text 'junxure'
 
1.0.351 -

Added first draft of Emailer module

1.0.349 -

Added includedForAssemblyIdPattern (this supplements the enabledForAssemblyIdPattern) - see the documentation for details
Made wda files so we validate the attribute names (if we mis-type an attribute, it will now give an error message)
Error messages when loading multi-level assemblies are now much friendlier

1.0.348 -

WDAutoFile can now file to Inactive codes (fix for SR 90124)

1.0.347 -

Added worldox.user.code, worldox.user.initials and worldox.user.name extractors (mostly useful in the WD Auto-filer for populating the Filed By field)

1.0.346 -

NetDoc Publisher - double clicking Column Def and Extractor Def tables opens the entry in edit mode

1.0.338 -

Minor UI tweaks in NetDocs Publisher module

1.0.337 -

Fixed:  Reload command isn't available after saving a new file in splitter
First iteration with NetDocs Publisher module added

1.0.334 -

Added splitregex(in, regexToSplitOn) command to Excel column specification language

1.0.333 -

Lot's of little UI fixes:
 - fixed labels that were missing text
 - Removed scroll bar behavior from right pane of preferences dialog (eliminate issue with the panel resizing oddly)
 - Fixed dialog icons so they should NOT show the Java coffee cup (if anyone still sees a Java coffee cup icon anywhere in the app, be sure to tell me)
 - Adjusted default width of the Connections Add dialog so it's not so small
 - Fixed layout behavior of translator query field in Extractor definition pane

1.0.331 -

AxysRunner scripter will now fix the output path by converting illegal characters to -

1.0.328 -

New icons

1.0.327 -

Added .safe entries for all of the worldox.field# and field#desc extractors

1.0.326 -

Improved error messages when PDF file reading fails during Send To operations (error should now have the path of the file that caused the problem)
Added the following extractors (these are available pretty much everywhere in the system):
    worldox.field1
    worldox.field1desc
    worldox.field2
    worldox.field2desc
    worldox.field3
    worldox.field3desc
    worldox.field4
    worldox.field4desc
    worldox.field5
    worldox.field5desc
    worldox.field6
    worldox.field6desc
    worldox.field7
    worldox.field7desc
    worldox.date.created
    worldox.date.created.safe - same as date.created, but replaces / and : with -
    worldox.date.updated
    worldox.date.updated.safe - same as date.updated, but replaces / and : with -

1.0.325 -

Overhaul of extractor definition pane in Auto Filer, WD Auto Filer, Encryptor, Scripter and CV Publisher
Extractor definition pane option 'Use empty string when extractor fails' - this will cause the extractor to return an empty string instead of null if the extractor fails (useful in cases where it might be ok for an extractor to fail)
Selecting items in the Items To Process list now updates the Sample String in the extractor definition pane
 

1.0.321 -

Added 'Print Sub-jobs' setting to printer configuration (turned on by default).  When set, each sub-PDF is printed to the printer as a separate print job.

1.0.320 -

Added direct to Adobe mode to AxysRunner (via setDirectToAcroMode(true); ) - this is still very, very rough - the user has to set Adobe PDF as the default printer

1.0.311 -

Deleted PdfDocumentWriter (was used by splitter before 1.0.310, but no longer needed)
Adjusted PDFPrintHandler so it doesn't use security descriptor when opening printer - this allows us to use the print handler for normal users - a very big deal

1.0.310 -

Bug fix:  Splitter didn't properly handle input files that were flipped upside down

1.0.309 -

Bug Fix:  Some XLS files would fail with a NegativeArrayIndex exception

1.0.308 -

Proper handling for print jobs run through Acrobat 10 (I've tested on reader, should work for full)
We now leave Acrobat open between print jobs (performance enhancement) - we close it every 50 operations just for good measure (keep the temp folder flushed out)

1.0.0.305 -

Printer preferences are now specified and edited directly inside Assemblage (you no longer set the defaults then capture them).  This should be much easier to manage.

1.0.0.302 -

Added worldox.* extractors to Scripter

1.0.0.301 -

AxysRunner will now properly handle macros that are specified with full paths

1.0.0.299 -

Updated default Workspace so wda files use relative paths for basepath and output directory

1.0.0.298 -

When clicking New in Splitter configuration chooser, edit mode is now automatically turned on by default

1.0.0.297 -

Added worldox.lfn.safe, worldox.xname.safe and worldox.lfnunder.safe named extractors - these replace characters that aren't allowed in filenames with dashes (/\:*?\"<>|)

1.0.0.295 -

Added worldox extractors to auto-filer

1.0.0.292 -

Added name of PDF file to error messages when the PDF couldn't be read
baseInputPath and outputDirectory values in WDA files can now be specified using relative paths.  Paths will be relative to the folder containing the wda file (e.g. baseInputPath="..\Assembler In\")

1.0.0.290 -

Added DB Connection configuration to preferences.  Once configured, a named database connection can be used in any translator using xlat:db:<name> (e.g. xlat:db:portfoliocenter )

Summary

• Added support for emailing using 64 bit Outlook (in addition to 32 bit Outlook)
• Login to ShareFile now happens in the user's browser (when launching the ShareFile tools, user clicks a Connect to ShareFile button, which will take them to their browser).  This allows the user to use their password manager, and addresses issues with compatibility of the embedded web browser that was used previously.
• New translators for working with NetDocuments code tables, obtaining current user, etc
• Enhancements to facilitate deploying Assemblage in a SharePoint (or similar file sharing) environment instead of installing to each user's workstation [contact Trumpet support for more information]
• PDFs are printed using an embedded PDF rendered instead of relying on Acrobat

To see the complete list of changes see:  Change log

Summary

• Added the ability to allow users to apply Custom Tags to individual Assemblies.  See:  Custom Tags for how this is used.  If you would like to utilize Custom tags, email support@trumpetinc.com and an Assemblage support technician will be happy to set this up for you.
• Added the ability to have the Table Of Contents page numbers be equal to the physical page of the PDF file
  
• Added the ability to verify that required content is included in the Assembly
• Updated to private Java Runtime based on the open source Liberica JDK
• Updated Assemblage to work with ShareFile authentication protocols
• Assemblage now works with .xlsx and .xlsm mapping files

To see the complete list of changes see:  Change log

Summary 2.2

• Added ShareFile Emailer tool functionality
• Added the ability to send emails using Outlook (as an alternative to SMTP mail servers).  This ensures that items will be placed in your "Sent" folders in Outlook (only works with 32-bit versions of Outlook)
  
• Added Support for Acrobat DC and Adobe Reader DC
• Overhauled refresh logic to make the "refresh" capabilities much faster and more responsive.
• Added features to Trumpet Publisher for ShareFile so that users are better able to manage portal folders that don't already exist.  You can now validate the existence of a portal folder.
• Added integration with Wealth Access portal
• Added a splash screen when launching Assemblage and it's other tools
• Resolved issues for FINRA clients receiving 403 errors when sending from ShareFile Emailer tool.  Users can now specify "Always" for the attachments to publish properly.
• Added TLS + SSL authentication type for Emailer tools SMTP connections
• Added a new shortcut in the "Tools" folder to run Axys Scripter elevated for those firms that require Axys to run elevated.
• Adjusted the look and feel for the entire application and tools to have a new updated interface.
• Resolved issue with special characters being replaced by question marks in the Emailer and ShareFile Emailer tool.

Summary 2.1

• Added the ability to run reports from APX via the Scripter tool
• NetDocuments Auto Filer preserves the file's modification date during filing
• Emailer tool supports rich text (HTML) email messages and awesome email editing tools.  More information regarding these tools can be found here:  Email Formatting
• Trumpet Publisher for ShareFile now presents the users with a login screen.
• Each tool has an "Add / Remove Items" selection which is shown by right clicking on item(s) in the list.  If you drag and drop items to the tools that shouldn't be there, you can easily remove them.
  
• Trumpet Publisher for ShareFile now allows you to set an expiration date for published files.

• Added support for printing to Acrobat XI
• Improved performance for "Send to > Printer" operations
• PDF splitter is now 25% faster when reading large PDF files
• When you hover over an item in the display lists of the Emailer, Publisher, or AutoFiler tool, you will see the full text
• You can now copy and paste the status grid from the Emailer Tool for compliance purposes. This includes the document identifier and the date sent
• Added option "SSL w/Self Signed Cert" to the Emailer Tool's preferences as an authentication method for users with Self Signed Certificates

• Added "Create Relationship" checkbox.  When this checkbox is selected, the newly filed documents will be set up as children of the specified path identified in the field,
• When the "Delete Original After it's been Filed" checkbox is selected, the Worldox Auto-Filer will delete the files from the input folder after they've been successfully filed.  Now, you don't have to delete the files as a separate operation.

Worldox Auto-Filer, File System Auto-Filer and Trumpet Publisher Enhancements:

• View in Explorer - You can now right-click on a document in the document list and chose "View in Explorer".  This will open up Windows Explorer, highlighted on the document you've selected.
• Preview - You can now right-click on a document in the document list and chose "Preview". This will open a copy of the document.  This can be handy if the filename doesn't include useful information you need to identify for mapping purposes.
• Docs / Minute Readout - This display provides you with an estimated time required to file or publish documents.  It can be found at the bottom of the window once you've opted to split / publish / file the documents.
• Cancel - You will now see a "Cancel" button.  This allows you to stop the tool from splitting, publishing, filing - whatever tool you're working in - in case you need to make changes.