3305 Main Street Ste 019 Vancouver, WA 98663

Integrator 2.82.0034

What's new in Integrator version 2.82.34

Posted 12/08/2010

We strongly recommend that you read this information prior to upgrading. New versions may include new features that can help you, resolutions to known problems, and changes to supported environments.


1 - Compatibility Updates

1.1 - Licensing - IMPORTANT

The licensing model has changed to allow individual interfaces (which exchange a particular type of data in a single direction) to be licensed individually.
Due to this change, you must update your license after installing this update in order to preserve your existing functionality. To update your license, you can
follow these steps.  This only needs to be performed on one workstation.

  1. Start Integrator
  2. When the Open Connection window appears, click Cancel
  3. Click the Help menu, then License, then Licensing. Your Company Name and License ID should already be displayed.
  4. Check the Select box in the grid and click Next.
  5. Leave Online selected and click Next. Note that if your firewall does not permit Integrator to access the Internet, you may use one of the other communication styles.
  6. After completing the licensing wizard, restart Integrator.

1.2 - Office Connector Compatibility

Integrator utilizes an Event 1 component (e1WhereBuilder.ocx) that is shared by Event 1 Office Connector. This version of Integrator distributes a newer version
of the component that is not compatible with versions of Office Connector 2.02.055 and prior. If your company has designer licenses of Office Connector, and Office
Connector is installed on the same computer(s) that run Integrator, it is important that you upgrade Office Connector. Version 2.02.56 of Office Connector should be
installed in conjunction with the installation of this version.

1.3 - Compatibility with Sage 300 Construction and Real Estate

This version supports Sage 300 Construction and Real Estate versions 9.0 through 9.7.

1.4 - Compatibility with Prolog Manager

This version supports Trimble Prolog Manager versions 6.5 through 2008 R2.

1.5 - Integrator Database Changes

Changes have been made to the Integrator database structure in order to accommodate new features. To upgrade your Integrator database, simply start the application and open one of your existing connections.

1.6 - Supported Environments

This version supports the following operating systems

  • Windows 2008 Server, 32-bit or 64-bit
  • Windows 7, 32-bit or 64-bit
  • Windows Vista, 32-bit or 64-bit
  • Windows 2003 Server, 32-bit or 64-bit
  • Windows XP
  • Windows 2000 with Service Pack

Note - Support for a specific operating system is also dependent on whether your version of Timberline and Prolog support the environment.

2 - Software Changes

2.1 - Database Connections

2.1.1 - Change Login Information

This version introduces a new feature under the File menu that allows you to change the login credentials associated with the databases Integrator connects to.
With an open connection click the File menu, then Logon, and then the desired database type to access this feature.

2.1.2 - Connection Method

In previous versions, Integrator automatically created and then used ODBC Data Sources (found in Windows Control Panel under Administrative Tools – Data Sources (ODBC)).
Beginning with this version, Integrator utilizes an approach for connecting to your databases that does not require an ODBC Data Source name. This change is intended to
alleviate connection problems experienced when properties of the ODBC Data Sources are modified (potentially by an upgrade of Sage 300 Construction and Real Estate for example).

2.1.3 - SDKUser Account Auto-Repair

The SDKUser account is a special account created on your SQL Server by Integrator for the purpose of interacting with the Trimble programming interfaces. This account
can become invalid if a Prolog database (and associated Integrator database) is relocated from one SQL Server to a new one. Beginning with this release, if Integrator
encounters a connection error that appears to be associated with this account, it will attempt to recreate or repair the account and then attempt to connect again.
This process will be silently performed during the connection process.

2.2 - Tool Bar

2.2.1 - Start Prolog Manager

A button depicting the Prolog Manager program icon appears on the Integrator toolbar. Clicking this button launches the Prolog Manager application. In previous
versions of Integrator, if Prolog Manager was not installed, Integrator would write an error to the error log each time the application started. This logging has been

2.3 - Timberline Macro Options

For tasks that utilize a Sage 300 Construction and Real Estate macro to carry out an import task, additional options have been added to Integrator that provide more control over how
macros are executed. This applies to the following tasks:

  • Budgets (going from Prolog to Timberline)
  • Contracts
  • Subcontract Cos

The new options can be accessed on the Import tab of the settings window for the above interfaces by clicking Options.

2.3.1 - Wait for macro to finish (check-box)

In previous versions, Integrator would launch the Timberline macro as an asynchronous process, meaning that Integrator would continue with processing while the macro
ran independently. Now, if this box is checked, Integrator will suspend execution and wait for the Timberline macro to finish before it proceeds.

2.3.2 - Maximum time to wait (seconds)

This setting only applies when the Wait for macro to finish box is checked. This setting allows for the maximum amount of time to be specified. The default
(recommended) amount of time is 600 seconds (10 minutes). If the macro does not finish in this amount of time, a warning message will be recorded on the recap report.

2.3.3 - Printouts

This setting allow you to specify a list of files associated with the execution of the macro. These would typically be the printouts associated with the tasks that
the macro executes. For example, this might include the print file name of the “Job Cost Import Commitments Journal”. By identifying these files, two things occur
when Integrator runs the macro:

  1. If the files identified here are found to already exist before the macro is run, the files are renamed to include the date and time as part of their file name. The files are then moved into a zip file having the same name. In this way, the history is not lost and the zip file contains an archive of the previous versions of the files.
  2. If the Wait for macro to finish box is checked, files listed here will be included as file attachments in the email that Integrator sends when running unattended. In addition to the files specified, Integrator will also include the macro log file as an attachment. The inclusion of these files is intended to increase awareness of the results of the import process.

2.4 - Budget Codes Interface

2.4.1 - Record Selection Criteria

In the Budget Code Settings window, a tab named “Criteria” has been added. On this tab, criteria can be defined that will determine which records Integrator
reads from the Timberline database when determining which Budget Codes (and associated Budget Group Lookup Items) to update or create in Prolog. This allows
for the filtering out of specific codes that are not intended to be integrated.

2.4.2 - Leading and Trailing Spaces

If your Prolog Budget Code Structure includes a space for the separator character on the last section shown in the code, this can result in a trailing space at
the end of the budget code. An issue was identified where sometimes the trailing space is not included in the setup of a new code. In previous versions of
Integrator, these codes were identified as not having been setup yet on subsequent runs. This has been corrected. Integrator will no longer include
trailing spaces in the code when determining if the code is already setup.

2.5 - Budgets Interface

2.5.1 - Record Selection Criteria

In the Budget Settings window, a tab named “Criteria” has been added. On this tab, criteria can be defined that determine which records Integrator reads
from the Timberline database when determining which Budget values to send to Prolog. This allows for the filtering out of specific values that are not intended
to be integrated.

2.5.2 - Query Transactions

This checkbox has been added in order to provide two options as the source for budget values being transferred from Timberline to Prolog. If unchecked, values
are read from the JC Master file totals. This is consistent with previous behavior. If checked, values are read and totaled from the JC Transaction files identified
on the Files tab. When utilizing the Criteria feature, this provides greater control of budget values being transferred on a transactional basis.

2.5.3 - Budget Hours

When transferring budget values from Prolog to Timberline, budget hours are now included.

2.6 - Contracts Interface

In previous versions, if a text value longer than 32,767 characters was placed in the Scope field of a contract, this would result in an Overflow Error 6
when Integrator processed the information. This has been corrected although the size limitation of the Scope field in Timberline remains at 380 characters.

2.7 - Subcontract CO Interface

Previous versions did not support the use of Sage 300 Construction and Real Estate Project Management (PJ) for management of Commimtent COs. If the "Use PJ for Change Management"
box of the PJ Job Setup window was checked, two problems would arise. First, Integrator would continually try to add any new Subcontract COs because it was looking for
them in the Job Cost database and not finding them. Second, Error 3265 would occur on subsequent runs after a Subcontract CO had been transferred from Prolog into
the Timberline Project Management database. This has been corrected so that Integrator will now acknowledge the "Use PJ for Change Management" checkbox and utilize either
the Job Cost database or the Project Management database accordingly when querying or updating Commitment COs.

2.8 - Cost Interface

2.8.1 - Non-Numeric Contract Invoice Numbers in Prolog

Integrator relies on the auto-numbering rules in Prolog and the Trimble AI-SDK component to automatically assign invoice numbers to Contract Invoices that
Integrator creates. It has been identified that if any non-numeric Contract Invoice numbers have been recorded for a contract (manually in Prolog), the auto-numbering
system of Prolog ceases to work. This would result in a Contract Invoice being created having no invoice number. The next time Integrator would need to create a
Contract Invoice for the same contract, the invoice would be rejected because the invoice number (a blank) would be duplicated. This would be reported on the Integrator
recap as “Error 0” with no description. This issue has been resolved by allowing Integrator to check for the existence of non-numeric Contract Invoice numbers. If found,
Integrator will apply its own auto-numbering logic to determine the next invoice number based on the largest numeric invoice number found for the contract

2.8.2 - Retainage on Contract Invoices

In previous versions, the retainage on the most recently added contract invoice would overwrite the total retainage value for the contract. This has been corrected so that
the newly added invoice will show its amount for the retainage and the total accumulated retainage for the contract will be correct.

2.9 - Substitution Tables

2.9.1 - Company ID Substitution Table

One of the existing options for company ID substitution tables allows you to have this table automatically populated by querying the companies in
Prolog Manager and using the value in the Short Name field as the Timberline Vendor ID. In previous versions if two or more Prolog companies used the
same Timberline Vendor ID, the company would not be added to the table. This would result in a rejection later when the Timberline Vendor ID was needed
in order to transfer a contract or cost. The rejection message however was very non-specific about why no Timberline Vendor ID was found in the table.
This has been improved so that a rejection message related to this scenario will provide a clearer description of the issue and will provide a list
of the Prolog companies that are sharing the same Timberline Vendor ID.

2.9.2 - Budget Code Substitution Tables

The user-interface for managing budget code substitution tables has been significantly improved. Now, when working with substitution tables, a list of
already-created tables is displayed. Each table is uniquely identified by the field it provides a replacement value for and the corresponding fields that
are used to derive each value. From the window showing the list of substitution tables, you can create a new table, edit an existing table, or delete a table.

2.9.3 - Contract ID Substitution Table - NEW

This is a new feature that permits the mapping of Timberline Commitment IDs to their respective Prolog Project Number and Contract Number combination.
This provides the ability to link contracts on jobs that are already in progress at the time Integrator is implemented.

Note – This feature is purchased and licensed separately.

2.10 - Unattended Operation

2.10.1 - Automation Wizard

In previous versions, when creating a desktop icon or batch file using the automation wizard, the wrong path to the IntegratorTasks.exe file was being used. This has been corrected.

2.10.2 - Memory Management

In previous versions, some memory was being allocated and not released when performing certain tasks. In some environments this may have lead to a Windows error upon termination of the program.

2.10.3 - More Detailed Diagnostics

To aid in providing support on unattended operation, more detailed information is now logged when tracing has been activated. This detailed information will aid the Event 1 support team in being able to more quickly resolve issues.

3 - Future Software Updates

Future software-updates will be brought to you by a significantly improved update notification program that includes the following features:

  • Optional update notifications are provided on a schedule of your choosing.
  • Updates can be downloaded automatically or on demand.
  • Updates are downloaded to a central location and are automatically available to other computers.
  • Installation is always performed on demand, and can be initiated directly from the update notification window.
  • Update behavior can be configured per workstation or globally from the server.
  • All of your installed Event 1 Software products are managed in a single window.