Sam asked whether the attorney hub data-gap tiles could be clickable and asked whether Injuries not listed and Pending Injuries List were redundant. The work focused on the New Cases data-gap section in the Payton and Nick attorney hubs.
Payton's dataGapFlags now include an href for every tile. Report-backed photo tiles open their source reports. Computed matter-data tiles open the Matter recent list as the entry point for data correction.
Payton's New Cases LWC now renders the data-gap tiles as anchor elements with hover and focus affordance. The controller test now asserts every flag exposes a drill link.
Nick's New Cases LWC now mirrors the clickable behavior. Its photo tiles point to Nick-specific reports, and the rest fall back to the Matter recent list. The visible label for injlist is now Treatment injuries missing, which separates it from the new-matter-only injury gap.
Injuries not listed is a new-matter intake gap: matters opened in the last 30 days with no related litify_pm__Injury__c record.
Pending Injuries List, now labeled Treatment injuries missing, is a Treatment-stage backlog gap: open Treatment matters for that attorney with no related litify_pm__Injury__c record.
They are not fully redundant. They measure the same underlying missing injury-record defect across different populations. A matter can overlap if it is new and already in Treatment, but the first tile catches intake/new-file misses while the second catches older Treatment backlog.
/Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/force-app/main/default/classes/AttorneyHubPaytonController.cls/Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/force-app/main/default/classes/AttorneyHubPaytonControllerTest.cls/Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/force-app/main/default/lwc/attorneyHubPaytonNewCases//Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/force-app/main/default/lwc/attorneyHubNickNewCases/Live Salesforce preflight confirmed LITIFY_ORG was connected and queryable. A Salesforce dry-run deploy succeeded with 4 of 4 components validated and 2 of 2 tests passing. Deploy ID: 0AfUV000001YxGP0A0.
Deploying a Nick Apex controller edit was not viable in the current local set because the selected Nick controller has no matching deployed test coverage. The workaround was to leave Nick's controller unchanged and make Nick's data-gap tiles clickable in the LWC layer.
The Payton LWC metadata was stale locally. Salesforce rejected a dry-run until the local js-meta.xml matched the live Small and Large supported form factors. The live metadata was retrieved, the local metadata was reconciled, and the final dry-run passed.