Fix AcctDemo_NamedCreds note — exists in org, not yet retrieved to source
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
148854ff1e
commit
091b1870b6
|
|
@ -61,10 +61,13 @@
|
|||
|
||||
## Manual post-deploy steps
|
||||
|
||||
### Named credentials requiring org-side setup
|
||||
The following are not deployable via source and must be configured in the target org:
|
||||
### Named credentials not yet in source
|
||||
The following exist in the target org but have not been retrieved into `force-app/`:
|
||||
|
||||
- **`AcctDemo_NamedCreds`** — eSignature OAuth/userinfo credential referenced by `DTC_CLM_Demo` account setting. Create a Named Credential pointing to the DocuSign account server (e.g., `https://account-d.docusign.com`) with the appropriate OAuth settings.
|
||||
- **`AcctDemo_NamedCreds`** — eSignature OAuth/userinfo credential referenced by `DTC_CLM_Demo` account setting. Retrieve it with:
|
||||
```bash
|
||||
sf project retrieve start --metadata "NamedCredential:AcctDemo_NamedCreds"
|
||||
```
|
||||
|
||||
### DocusignJWT external credential
|
||||
`force-app/main/default/externalCredentials/DocusignJWT.externalCredential-meta.xml` contains demo values for `iss` (integration key) and `sub` (user GUID) targeting `account-d.docusign.com`. Replace these with your org's actual integration key and impersonation user GUID before use.
|
||||
|
|
|
|||
Loading…
Reference in New Issue