Problem or use case
Currently, signature request lwc (docGenSignatureSender) is cluttered compared to Portwood Runner.
There is a lot of config that should be done on the template, and auto populated when running.
Proposed solution
Ideally, Portwood Runner can also send for signature instead of docGenSignatureSender.
If that is not possible, then make Portwood Signature Runner that pulls all config from template:
- Signature Roles
- Signed Document Title
- Signing Order
- Link Expiration Days
- etc.
Problem or use case
Currently, signature request lwc (docGenSignatureSender) is cluttered compared to Portwood Runner.
There is a lot of config that should be done on the template, and auto populated when running.
Proposed solution
Ideally, Portwood Runner can also send for signature instead of docGenSignatureSender.
If that is not possible, then make
Portwood Signature Runnerthat pulls all config from template: