- Remove storeOutputAutomatically from InputField (not supported on that fieldType)
- Fix assignment reference to use screen-qualified path
SMS_Phone_Screen.recipientSmsPhone_Input instead of bare recipientSmsPhone_Input
Screen InputField name cannot match a flow variable name. Renamed field to
recipientSmsPhone_Input, added Store_SMS_Phone assignment element to copy
the field value into the recipientSmsPhone variable after the screen.
InputField screen components do not support <outputParameters>. Replaced with
<storeOutputAutomatically>true</storeOutputAutomatically> and renamed the field
to match the target variable (recipientSmsPhone) so the value is stored directly.
Variable was appended after <choices> at end of file, creating a second
<variables> block and causing 'Element variables is duplicated' deploy error.
Moved into the existing variables group before <choices>.
Get_Recipient_Contact was in a separate <recordLookups> block before <environments>
and SMS_Phone_Screen was in a separate <screens> block before <environments>,
both causing 'Element ... is duplicated' deploy errors. Moved both into their
respective contiguous element groups alongside the existing V3 elements.
Salesforce Flow XML requires all elements of the same type to be grouped
together. Is_Recipient_Email_Blank was in a separate <decisions> block after
<recordLookups>, causing 'Element decisions is duplicated' deploy error.
Moved it into the existing decisions group and removed the orphaned block.
- Add recipientSmsPhone InvocableVariable to DocusignEnvelopeRequest
- Add SMS_PLACEHOLDER_EMAIL constant to DocusignCompositeEnvelopeBuilder
- Update resolveRecipients() and buildRecipient() to accept smsPhone param
- Chain .withSmsDelivery(smsPhone) on recipient when smsPhone is provided
- Substitute placeholder email when recipient has no email and SMS phone given
- Add Flow V4 with Get_Recipient_Contact lookup, Is_Recipient_Email_Blank
decision, and SMS_Phone_Screen to collect phone for no-email recipients
- V3 left untouched for existing Salesforce deployments
When the 'Authorization to Release Information' template (English or
Spanish) is selected, a new screen prompts the user to choose how many
copies (1, 2, or 3) to include in the envelope via radio buttons.
New flow elements:
- Scan_For_Auth_Release_Template loop: iterates selected rows to detect
the target template
- Does_Row_Contain_Auth_Release decision: Contains check on row Name
- Flag_Auth_Release_Selected assignment: sets authReleaseTemplateSelected
- Is_Auth_Release_Selected decision: routes to copies screen or skips
- Authorization_Copies_Screen: displays radio buttons (1/2/3 copies)
- Store_Auth_Release_Copies assignment: writes radio selection into the
authReleaseFormCopies flow variable
- authReleaseFormCopies variable (Number, default 1)
- authReleaseTemplateSelected variable (Boolean, default false)
- AuthCopies_1/2/3 choices
authReleaseFormCopies is passed to the Apex action as a new input param.
Template name string lives in a single Contains condition for easy update.
- Updated DocusignCompositeEnvelopeBuilder.cls to sort documents and subject by Short_Name__c
- Modified Docusign_Envelope_Templates_V3.flow-meta.xml: repositioned elements and added filter for Short_Name__c not null
Salesforce requires elements of the same type (recordLookups, decisions,
screens, etc.) to be grouped together. Reordered all elements alphabetically
by type to comply with Flow metadata schema.
Paul Huliganga