BlueRithm + Procore Integration

Overview 

The Bluerithm integration with Procore was created to automate common overlapping workflows and activities between the platforms.

Procore is a construction management platform. Observations are assigned in Procore to project team members and are used similarly as Issues in BlueRithm. 
The integration syncs BlueRithm Issues to Procore Observations. Changes to BlueRithm Issues can be pushed, pulled or two-way-synced with Observations (see more about this below). 

Observation and Issue Priorities

Procore only accepts specific Priorities. BlueRithm Projects that use custom Priorities will be restricted to the Procore specific Priorities when connected to a Procore project. 
IMPORTANT: Any existing Issues that use custom Priorities in a BlueRithm project will not be synced with Procore until they are updated to match a corresponding priority in Procore. The available priorities in Procore are limited to: 

Low  Medium  High  Urgent  

A configuration form in BlueRithm can be used to update all existing issue priorities in a single operation, if desired. 

Observation Title and Issue Identifier

If the integration settings are set to either Pull or Two-Way Sync, the Procore Observation Title will be changed to a BlueRithm Identifier when it's replica is created in BlueRithm. If continuous sync is enabled, from that point on any changes made to the Observation Title or Issue Identifier will be saved and reflected on the Observation and Issue. 

Deleting Issues

When a user deletes a BlueRithm Issue, there's an option to place the corresponding Procore Observation into the Procore Recycle Bin.

Connect to a Procore Project

To enable the Procore integration, users will have to go to the Settings tab of a Project page and login to Procore. Once logged in, you will be redirected to a page where you can select the Procore Project you would like the BlueRithm Project to be assigned to. 
Observation Types that are available to the selected Procore Project are available to select as the default Observation Type. This is needed for Push functionality to push all previously existed BlueRithm Issues.

Current Features

Synchronize Procore Observations and BlueRithm Issues

Configuration options:

Push: When push is enabled any Issues created or updated will create/update the corresponding Procore Observation. Any Issues that previously existed before the Procore Project connection will be pushed via the Function App that runs every three minutes. Any issues that use custom Priorities will not be synced until the Issue is updated with the allowed Priorities.

Pull: When pull is enabled any Procore Observations created or updated will create/update the corresponding Issue. Any Observations that previously existed before the Procore Project connection will be pulled via the Function App that runs every three minutes.

Two-Way: Two-Way Sync implements both Push and Pull.

Continuous Sync: When the Continuous Sync option is selected in the Project Settings all changes are continuously synchronized between linked issues in BlueRithm and Procore regardless of the Sync Type (Push, Pull, Two-Way). The sync checks for the most recent update between the Issue (Entered Date, Last Owner Edit, Last Respondent Edit fields) and the Observation (Updated At field) and updates the latest changes.

NOTE: The profile that Procore Observations show for Created By, edits, etc. will be the Procore profile that was used to connect to the Procore project. It may be advisable to create a Procore profile specifically for BlueRithm to authenticate with so that Observations created and edited in BlueRithm are clearly shown as such in Procore. This Procore profile must have sufficient write privileges to create Observations. 

Similarly, the profile that BlueRithm Issues will show Entered By, edits, etc. for will be the BlueRithm profile that was used to connect to the Procore project. It may be advisable to create a BlueRithm profile specifically to authenticate with Procore so that Issues created and edited in Procore are clearly shown as such in BlueRithm. This profile can be a guest profile so it won't count against your seat limit, but it must be set to an Account Admin role at least for the it's used to authenticate to the Procore project. 

Limitations

Files will not be synchronized between the platforms. 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us