v1.7.10

Release date: July 9th, 2026

Jobs created in a Hover sub-org can now be shared to the parent org on creation, so the parent org's webhook subscription receives their completion and measurement events — fixing cases where sub-org jobs never completed or pulled measurements in Salesforce.
Controlled by the Enable Suborg Access on Job Create setting Hover_Config__c.Enable_Suborg_Access__c)
New field: Parent_Org_ID__c on the Hover Job record, stamped automatically at creation.

v1.7.9

Release date: June 26th, 2026

New hoverDeepLink LWC launches the Photo Capture flow from a record. Placeable on any object via App Builder using the configurable Job ID Field property (default HOVER_Job_ID__c, supports lookup paths like Hover_Job__r.HOVER_Job_ID__c).
Companion Hover_Deep_Link__c formula field gives the same link as clickable text. Mobile only.

Estimates are now created in Salesforce upon their creation in Salesforce. This functionality is gated behind the the Auto Create Estimate custom setting Hover_Config__c.Auto_Create_Estimate__c), off by default.
Upgrade note: grant the guest site user and the Hover permission set access to the new HoverSyncMaterialListOnCreate Apex class, or the flow fails silently.

Estimates split by trade/template via Split_Estimates_By_Trade__c Custom Setting. This is off by default.

Financing_Provider__c, Financing_Name__c, Financing_APR__c, Financing_Length__c, Financing_Down_Payment__c, Is_Financed__c.all added as new fields to the Hover Estimate object.
Adjustments: promotions now modeled as Adjustment_Value__c.
New measurement fields: Hips_Length__c and Ridges_Length__c

Release date: March 4th, 2026

Job Notes

Added Hover_Note__c and Hover_Note_ID__c fields to the Hover Job object to
support creating and updating notes directly from Salesforce.
Notes are automatically posted to Hover when a job is created with a note
pre-filled, and patched when the field is updated on an existing job.

Deliverable Change Request

Added support for the deliverable-change-request-state-changed webhook
event, enabling the integration to process upgrades from Capture Only jobs to
Roof Only or Complete.
On completion, the job's deliverable type is updated in Salesforce and
measurements are automatically retrieved.

Capture Only, Photos Only

Added support for Deliverable ID 7 (Capture Only, Photos Only) when creating
HOVER jobs from Salesforce.

Deliverable Sync on Job Completion
When a Hover job reaches the complete state, the Deliverable_ID__c field on
the Salesforce record is now automatically updated to reflect the deliverable
type in Hover (Roof Only or Complete).

Hover Estimate Line Items
Introduced a new Hover_Estimate_Line_Item__c custom object to store
individual line items from Hover estimates, with fields for name, product ID,
quantity, unit cost, total price, markup, tax rate, waste factor, trade type,
activity code, measurement unit, and variation.
Added full CRUD support (create, update, delete, upsert) for Estimate Line
Items, synced from the Hover Estimate API response.

Estimate Locking

Added a new estimate_is_locked__c field to the Hover Estimate custom object
to track lock status.
Implemented HoverLockEstimate and HoverQueueableLockEstimate Apex classes to
call the HOVER API and lock an estimate.
Added a new Lock Hover Estimate Flow to trigger the locking process from the
UI.
Updated the Update Hover Job Flow to incorporate the new estimate lock
process flow.

Release date: January 26, 2026

Estimation integration (Hover → Salesforce)
- Added a new custom object: Hover Estimates
- Supports a one-way sync of estimation data from Hover into Salesforce
- Users can initiate the Estimation workflow from Salesforce via an LWC on the Hover Job object
Inspection integration (Hover → Salesforce)
- Added a new custom object: Hover Inspections
- Supports a one-way sync of inspection data from Hover into Salesforce
Related lists
- Added dynamic related lists for Inspections and Estimates on the parent Hover Job object
Renaming
- Renamed Hover Material Lists to Hover Estimates
- No API name changes: underlying API names remain the same; only the user-visible labels have changed