Summary

Sam asked to fix the RingSense formatter Staff row and continue independently. The Flow now passes a clean staff name into the already-live RingSenseNoteFormatterAction.

Work completed

• Confirmed the prior active Flow version was 51 and that the Flow was back at the Salesforce 50-version cap.
• Saved evidence for obsolete version 2 before deletion at Litify_AI_Integration_Project/salesforce-metadata/tmp/rc-flow-staff-version-cleanup-2026-05-13/flow-version-2-before-delete.json.
• Deleted only obsolete inactive Flow version 2, id 301UV00000hFSXvYAO, to clear the version cap.
• Patched force-app/main/default/flows/RingCentral_Process_RingSense_Calls.flow-meta.xml to add calcStaffName, using $Record.Owner:User.FirstName + " " + $Record.Owner:User.LastName.
• Passed calcStaffName into the formatter action as the staffName input.
• Validated XML with xmllint.
• Check-only Flow deploy passed: 0AfUV000001WdFN0A0, formatter tests 3 of 3 passed.
• Live Flow deploy passed: 0AfUV000001WdGz0AK, formatter tests 3 of 3 passed.
• Activated Flow version 52 through FlowDefinition. Check-only activation passed: 0AfUV000001WdIb0AK. Live activation passed: 0AfUV000001WdKD0A0.

Live state

• Active Flow is RingCentral_Process_RingSense_Calls version 52, id 301UV00000m3OdHYAU.
• Version 51 is obsolete.
• Version count is 50.
• Retrieved active metadata confirms activeVersionNumber is 52, Flow status is Active, staffName is passed to calcStaffName, and Format_RingSense_Note_HTML remains in the scheduled path.

QA status

• Metadata and deploy QA are complete.
• Rendered-output QA is pending because there were no RingSense Tasks or Litify Notes created after the staff-row activation timestamp 2026-05-13T16:09:47Z at the time of checking.