Automate the creation of projects, subcontractors, and contacts in TrustLayer and provide real-time compliance visibility in Viewpoint Vista.
What is Viewpoint Vista?
Viewpoint Vista is an integrated, comprehensive suite of software solutions that helps contractors manage all areas of operations. It’s designed to streamline complex project management, improve control over project financials, and enhance field-to-office team collaboration. With Viewpoint Vista, contractors can expect improved efficiency and reporting across their projects.
Integrate TrustLayer with Viewpoint Vista
With TrustLayer's Viewpoint Vista (Hosted) integration, the creation of projects, subcontractors, and contact in TrustLayer can be initiated directly from Viewpoint Vista, streamlining compliance and risk management. This integration ensures that TrustLayer compliance data is accurately mirrored in Viewpoint Vista compliance codes.
Quick Setup
Configure authentication with Viewpoint Customer Support and create SQL user.
Communicate TrustLayer Requirements <> Vista Compliance Code mapping with the TrustLayer team
Configure the ViewPoint Vista integration within your TrustLayer account.
Viewpoint Vista <> TrustLayer Data Mapping
To ensure a smooth integration process, it’s essential to understand how data flows between Viewpoint Vista and TrustLayer. Below you'll find a guide depicting how project details, company profiles, user associations, and compliance data are mapped to keep both systems aligned and up-to-date.
Data Considerations
JC Jobs: By default sub-jobs are not considered and only open jobs will be synced to TrustLayer.
AP Vendors: By default only active vendors are synced to TrustLayer.
PM Firm Contacts: Firms should be initialized via AP Vendors so that the firm number is identical to the vendor number. If these numbers are not identical TrustLayer will not be able to import contacts.
Additionally TrustLayer is able to filter synced contacts by title.
Compliance Codes: TrustLayer is able to map compliance codes to three different levels of TrustLayer compliance, all of which can be configured as a date* or flag code in Viewpoint Vista:
Profile level status - Is vendor compliant? Yes/No
Subject level status - Is vendor compliant with Commercial General Liability? Yes/No
Requirement level status - Is vendor compliant with Commercial General Liability - Each Occurrence must be greater or equal to $1,000,000? Yes/No
*Expiration dates can be sent to Vista when a date compliance code is used.
Configuration Options
Option | Description | Choices |
Default Party Type | Standard classification for new parties. | Custom to Workspace |
Compliance Format | Determines the compliance data detail level. |
|
Compliance Sync Level | Controls the granularity of compliance data sync between Vista and TrustLayer. |
|
Compliance Sync Mode | Specifies direction and method of compliance data sync. |
|
Project Description Sync Mode | Determines how project descriptions are synced. |
|
Default Compliance Profile | Predefined compliance requirements for new projects or parties. | Custom to Workspace |
Compliance Synchronization | Enables or disables overall compliance sync. |
|
Filter Contacts by Title | Restricts contact sync based on job titles. | Custom to Workspace |
Contacts Synchronization Mode | Determines how contacts sync between Vista and TrustLayer. |
|
Common Errors
Common Errors
Compliance code group description error
If you're integrating with Agave and encounter an error similar to the one below, it typically indicates a missing description in the Compliance Code Group:
Error
json
CopyEdit
424 POST https://api.agaveapi.com/subcontracts/2e8b327b-2a88-5c84-801b-63c299d711f0/compliances/
{
"message": "Compliance Code Group OCCIP Tier is missing a description."
}
Explanation
Agave relies on the "description" field in the Compliance Code Group table to assign types of compliance. If this field is blank or missing, the system cannot access the compliance type via its identifier, resulting in the error.
Action required
Please have your client update their instance to ensure all Compliance Code Groups include a description. This is mandatory for the integration to function correctly. Agave can remove the requirement in specific cases, but that would bypass intended validation logic and is not recommended.