# Features Update — Salesforce Composite Envelope Builder **Date:** February 25, 2026 **Prepared by:** Cleo (OpenClaw agent) --- ## Overview This document summarizes all recent enhancements and refactors to the Salesforce Composite Envelope Builder project. It is intended for internal tracking and as a reference for future development and rollout. --- ## Major Updates (2026-02-25) ### 1. Salesforce Flow V3 Composite Envelope Send - Enabled sending a single envelope containing multiple Docusign templates directly from Salesforce Flow. - Replaced individual envelope sends (one per template) with a composite call using custom Apex logic. - Templates looped in Screen Flow, short names concatenated for document label, better visibility for recipients. ### 2. Email Subject & Body Improvements - Envelope email subject now dynamically uses the combined document names (Short_Name__c, comma-separated). - Envelope email body concatenates all template email messages (`dfsle_EmailMessage__c`), visually separated by `---` lines for clarity. - No longer uses template-level subject for the envelope; keeps subject concise and relevant. ### 3. Authentication Refactor - Removed custom Apex authentication (DocusignAPIService/DocusignCredentials). - All composite envelope sends now use dfsle managed package authentication, with no reliance on custom credentials or Named Credentials. - Simplified error handling and removed obsolete credential loading logic. ### 4. Codebase Cleanup - Deleted legacy classes and tests (`DocusignAPIService`, `DocusignCredentials`, and related tests) from both Salesforce instance and Git repository. - All business logic now consolidated in `DocusignCompositeEnvelopeBuilder`, `DocusignEnvelopeRequest`, `DocusignEnvelopeRequestHandler`, and `DocusignEnvelopeResult`. ### 5. Flow XML & Deployment Workflow - Updated Flow XML (`Docusign_Envelope_Templates_V3.flow-meta.xml`) for new composite logic. - Ensured alphabetical ordering of Flow XML elements by type. - Maintained deployment/test scripts for Bash and PowerShell compatibility. --- ## Additional Document Updates Needed - **README.md/introduction:** Should add a summary of these composite envelope changes, new flow architecture, and authentication approach. - **requirements.md:** May want to clarify new minimum requirements for envelope sending, reduced maintenance burden due to composite logic, and authenticate only via dfsle package. - **DEPLOYMENT_AND_TESTING.md:** Remove instructions relating to now-deleted classes; ensure steps are clear for current deploy/test cycle with new flow and class setup. --- **Action**: Please review and update these docs as needed. This features update provides a reference for stakeholders and future work.