Sam asked whether the Important Details block could be moved into the RingCentral iframe block. The vendor RingCentral iframe is cross-origin, so Litify cannot safely inject Salesforce data into the iframe document itself. I moved the Salesforce-rendered Important Details field group into the RingCentral panel flow instead, directly above the RingCentral communications/actions area.
LitifyRingCentralContextController to return Party Important Details rows for Matter and Intake contexts.Security.stripInaccessible(AccessType.READABLE, ...) before rendering those Party fields.Account.Image__c Important Details rich-text note when populated.litifyRingCentralPanel HTML, CSS, and JS to render a compact Important Details field group in the RingCentral workspace.0AfUV000001WvH70AK, production 0AfUV000001WvIj0AK.Account.Image__c.0AfUV000001WvNZ0A0, LitifyRingCentralContextControllerTest 3/3 passed.0AfUV000001WvPB0A0, LitifyRingCentralContextControllerTest 3/3 passed.RC_IMPORTANT_DETAIL_COUNT=4 and RC_HAS_IMPORTANT_HTML=false, confirming the panel is now using real field rows./Users/samaguiar/Documents/Projects/admin/playwright-mcp-output/ringcentral-important-details-field-group-2026-05-17.png./Users/samaguiar/Documents/Projects/admin/_qa-queue/2026-05-17.md.Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/ringcentral-important-details-panel-2026-05-17/live-retrieve/.Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/ringcentral-important-details-panel-2026-05-17/apex-live-retrieve/.