# Next Steps — DocuSign CLM Launch Path

I added a placeholder Quick Action metadata file so there is an explicit place in the project for the document generation launch pattern.

## Reality check

DocuSign CLM launch configuration varies by package and org setup. Because of that, the action in this repo is a scaffold/placeholder, not a guaranteed final production action.

## Recommended implementation path

### Option A — Screen Flow (recommended first)
- Create a Screen Flow or autolaunched Flow that accepts `recordId`
- Call an Apex invocable or Apex action that builds the payload
- Hand that payload to your DocuSign CLM mechanism
- Redirect user to resulting document or status page

### Option B — LWC / Aura quick action
- Use a Lightning Web Component quick action on `Appraiser_Case__c`
- Call `AppraiserCaseDocGenService.buildDocGenRequestJson(recordId, templateKey)`
- Send the payload to the installed DocuSign CLM endpoint or orchestration layer

### Option C — Button / URL hack
- Usually fast, usually brittle. I don’t recommend it unless your CLM package explicitly documents it.

## What to confirm in your org

1. Exact DocuSign CLM package/API available in Salesforce
2. Whether generation is initiated by package component, Flow action, Apex callout, or named credential call
3. Template identifier format (`templateKey`, template Id, or external document key)
4. Returned artifact behavior (attach to record, email, save to CLM repository, etc.)

## Good next move

Once you know the exact DocuSign package artifact available in the org, I can wire the placeholder into a real Flow/LWC/Apex launch path.