28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
# 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.
|
|
|
|
## Implementation status
|
|
|
|
### Option B — LWC / Quick action ✅ Complete
|
|
The `clmDocGenWorkbench` LWC quick action is fully implemented and deployed. It uses `CLMAdminService` and `CLMDocGenCallout` for the full generate → poll → attach workflow.
|
|
|
|
### Option A — Screen Flow (alternative entry point)
|
|
If a Flow-based launch is preferred (e.g., to add approval steps or prefill inputs):
|
|
- Create a Screen Flow that accepts `recordId`
|
|
- Call `CLMAdminService.generateDocument()` via an Apex Action step, passing account code, template href, destination folder href, and destination filename
|
|
- Show task status by polling `CLMAdminService.getTaskStatus()`
|
|
|
|
### Option C — Button / URL hack
|
|
Not recommended.
|
|
|
|
## What to confirm before extending to additional letter types
|
|
|
|
1. CLM template hrefs for NOD, Education, and Intent to Remove letters
|
|
2. Whether those letters use the same destination folder structure or need separate `CLM_Letter_Definition__mdt` folder overrides
|
|
3. Any differences in deficiency display or field set for those letter types
|