Skip to content

Core v1.1.6 · Modules v0.3.0

Released 2026-08-03. This is the baseline for the August 2026 stabilization freeze.

Core sharpens the tools BD uses to find and measure relationships — relationship-strength filtering in Client Locator and a materially more capable rollup engine. Modules 0.3.0 is the ERM review release: the relationship-review workflow that had been partly wired up is now a complete admin-and-reviewer experience.

Highlights

  • Filter Client Locator results by relationship strength, so "who do we know here?" can be narrowed to "who do we know well here?".
  • The rollup engine supports distinct counts and relationship-path traversal, removing two long-standing reasons to fall back to custom Apex.
  • 🧩 ERM review (Modules) is complete end to end — review queue, reviewer actions, auto-promotion, and subscription management.

New

  • Relationship Strength filter in Client Locator — a new Relationship_Strength__c field on Contact feeds a filter in the Client Locator UI, and the same filter is available when picking trip targets. (#195)
  • 🧩 ERM admin review queue — administrators get a dedicated queue for relationship records awaiting review, rather than chasing them through digests. (#287)
  • 🧩 ERM auto-promotion — relationships that meet the configured bar are promoted automatically on a batch schedule, with the review path reserved for genuine judgment calls. (#287)

Improvements

  • Rollup engine: COUNT_DISTINCT and relationship-path support — rollup definitions gain an Aggregation_Type__c and can now traverse a relationship path to their source records. Definitions are validated against the new capabilities before they run. (#236)
  • 🧩 Digest data tables — the data-table section renderer and its controller were reworked, improving how tabular content is built and displayed inside a digest. (#287)
  • 🧩 Dispatch scheduling — definition batching, selection, and schedule handling were tightened for more predictable run timing. (#287)

Changes

  • Contact data-quality banding migrated. The DQM picklist and its supporting fields (DQM_Band__c, DQMBands__c, Missing_Band__c, Missing_Count__c, Missing_Fields__c) were brought in line with the values used in the development org. Reports or list views that filter on the old band values need re-pointing at the new picklist entries. (#230)
  • 🧩 The Modules → Core dependency floor moved to Core 1.1.4-9. An org running Core older than 1.1.4 must upgrade Core before Modules 0.3.0 will install. (#287)

Admin & Configuration

  • Permission-set updates to CV_Data_Import_Full_Access, CV_Full_Access, and CV_Relationship_Data_Access accompany the new Contact fields — re-verify assignments after upgrading so relationship-strength data is visible to the people who need it.
  • The Opportunity_SCR_Create screen flow was updated alongside the contact-role work.

Under the hood

  • CI: QA workflows moved to Node 22, fixing a Salesforce CLI crash caused by a Node/undici version mismatch. (#227)
  • CI: the daily PR-stats job was moved off the top of the hour to avoid scheduler contention. (#228)

Known limitations

  • AI remains foundation only. Modules 0.3.0 ships CV_AI_Action_Template__mdt and the provider-adapter interfaces, but no AI object, UI, or permission set. The in-platform AI MCP Chat has been built and is in QA on develop; it is not in ClientVerse Modules@0.3.0-1 and cannot be enabled. It is expected in a later release.
  • The analytics module is not present.