TrebleHook Release Notes

• Added field Hide Populated Fields to the Treblehook Administration custom metadata type which when checked indicates to hide populated fields in the Update Stage user interface.
• Added field Enable Field Headings to the Treblehook Administration custom metadata type which when checked indicates to display the configured collapsible headers with the fields underneath in the Update Stage user interface.
• Added new object type Project Staging Group Header which is used to configure collapsible headers displayed in the Update Stage user interface.  Added field Display Order which is used to configure a specified display order for the headers.
• Added new field Project Staging Group Header to the Project Staging Configuration object type which is used to associate a header to a field configuration.
• Added new field Sort Order to the Project Staging Configuration object type which is used to configure the sort order of the fields.

• The fields are displayed in a 2 column layout.
• When configured, collapsible section headers are displayed with fields underneath each section—the sections default as open.
• Fields are displayed in the configured sort order
• When configured, populated fields are removed.
• Updated styling of the display.

Added automation, which will populate the Website field on the Account object type for records that don’t already have it populated by looking at the domain name of contacts that relate to the Account.  This can be configured on or off.

Added validation rule that will not allow users to remove the check from the new field Project Management System Early Setup Request on the Project object type.

Added Checkbox field Project Management System Early Setup Request to the Project object type, which indicates that a project is requested entry early into the project management system. This is typically used with the email notification service alerting a group of users that a project is ready for review.

I added a Checkbox field connected to the Project Management System to the Project object type, showing whether a project is integrated into a project management system.

Added Procore integration user interface, allowing Enterprise customers to create projects and related data in Procore from TrebleHook.

Added an email notification service that enables easy configuration to send email notifications to groups of users based on changes to a project records state.

Departments is a new object that can be used to identify different business units that may exist inside a company.  Employees can be linked to specific departments and projects can also be linked to specific departments for easier management.

Updated Administration App

• License Request Tab added
• Technical Support Tab added

Updated notification to identify what org the notification is coming from.

New fields added to Phases to be used with ERP integrations.

• Receivable Balance
• Receipts
• Billed Amount by Accounting Date

New Fields added

• Billed Amount for Accounting Date
• Receipts
• Receivable Balance
• Cost Burden Total

• Bid Type
• Project Region
• Project Owner Type
• Procore Stage

New Fields

• Bid Type
• Project Region
• Project Owner Type
• Industry
• Procore Stage
• Department Key

Other Enhancements

• Added scheduled apex jobs to clear out records in working projects nightly so that they do not take up storage space.

A new, streamlined project page has been created to make data easier to find. By organizing information into logical groupings (e.g., Contacts, Financials, Dates), users can quickly locate what they need.

The page begins with a project summary section that highlights the most frequently used data fields.

As you scroll down the page, you’ll see the logically grouped field data, as illustrated below. These groups and the fields within them are fully customizable to meet your organization’s specific needs.

Finally, we moved the related information to the right-hand side to better utilize screen space and enhance the readability of the project page.

The Project Life Cycle Project Stage Configuration & Record Management Solution serves two key purposes. First, it streamlines the process of setting required fields for each stage of the project lifecycle, ensuring a smoother implementation. Second, it enhances the user interface and customer experience by simplifying the movement of projects through different stages, all while ensuring that organizations collect the critical information needed at every step.

Configuration

Though typically managed by the TrebleHook implementation team, this enhancement directly benefits customers by accelerating the implementation process, allowing them to go live much faster.

Update Stage

Users will now have easy access to a button that guides them through updating a project’s stage, ensuring they enter all the critical information required.

Once the button is clicked, users will be prompted to select the next stage they want to move to.

Based on their selection, the required data fields will appear on the screen, displaying any existing data for updates or, if blank, allowing users to input the necessary information. Fields can be configured as required or optional, depending on the setup.

Departments is a new object that can be used to identify different business units that may exist inside a company. Employees can be linked to specific departments and projects can also be linked to specific departments for easier management.

New fields added to Phases to be used with ERP integrations:

• Receivable Balance
• Receipts
• Billed Amount by Accounting Date

The newly launched TrebleHook Administration Lightning Application streamlines administrative tasks by centralizing key features like User Management, License Allocation, and New User Requests. Previously buried under the ‘Set Up’ section, these functions are now more accessible, significantly reducing time and clicks for a more efficient management experience.

• User Management: Enables administrators to activate or deactivate users and reset passwords directly, bypassing the ‘Set Up’ area. This is the default view in the tabbed page layout.
• License Allocation: Allows administrators to create new user accounts and assign TrebleHook Licenses when available.
• User Request: Facilitates requesting new user accounts in scenarios where licenses are exhausted, prompting administrators to provision additional licenses and create the account on behalf of the customer.
• Exceptions and License Requests: Provides a platform for administrators to review automation and custom app logic errors (Exceptions) and access a list of license requests generated from the User Request feature.

A new field has been added to Projects to identify the data source if the record was created due to integration:

• Origination Source
• Project ID
• OpenAsset Project URL

TrebleHook now integrates seamlessly with OpenAsset. This new feature enables customers using both TrebleHook and OpenAsset to link the two systems for synchronized data sharing. Users can identify related projects in OpenAsset directly from TrebleHook and access the metadata of assets stored in OpenAsset.

Additionally, various data fields can be synchronized from TrebleHook to OpenAsset, eliminating the need for duplicate data entry. The integration also allows for the creation of new OpenAsset projects directly from within TrebleHook.

Various fields have been added to Phases to provide the ability to sync data from an ERP system such as Ajera:

• WIP Hours
• WIP
• Vendor Invoiced
• Total Contract Amount
• Spent
• Hours Worked
• ERP PhaseID
• Description
• Cost Labor
• Cost Burden
• Cost
• Billed

In addition, there are now two different record types for Phases to differentiate between something that is proposed and something that is now contracted. Each record type can have a different layout, showing only the relevant fields.

New permission sets have been introduced to align with upcoming Salesforce changes in Profiles/Permissions management. This transition from relying solely on profiles to using permission sets enhances our ability to customize user permissions with greater precision.

• TrebleHook Viewer – used to apply view only rights on TrebleHook objects
• TrebleHook Starter – used to apply access only to Projects and no other related object in TrebleHook
• TrebleHook API Integration User – used for the API license type for integrations
• TrebleHook Contracts
• TrebleHook Billing Rate Admin – used to give access for a customer to manage their billing rates

A new field has been added to Contacts to identify the data source if the record was created due to integration:

• Origination Source

The Exceptions Log component displays a concise list of error entries, captured through error handling mechanisms set up by administrators and developers in their automation processes and within the specific customer org. By default, this list is organized and displayed with records sorted by each entry.

TrebleHook now offers integration with Ajera, enabling seamless synchronization of data from Ajera to TrebleHook. This integration allows TrebleHook users to access Ajera data, create reports and dashboards, and merge select information from both systems in a unified view. Initially, the integration supports syncing of Accounts, Contacts, Projects, and Phases to TrebleHook.

Two new record types were introduced to Proposals to differentiate between proposed pricing and contracted/actual pricing that may be coming in from an ERP integration.

A new field has been added to Accounts to identify the data source if the record was created due to integration:

• Origination Source