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.