Difference between revisions of "Codeunit/StatusAction/SignNemIdActionStatusGenerator"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
# Generates a document based on a defined template | # Generates a document based on a defined template | ||
# Will send a document from a document field to signing with NemID. | # Will send a document from a document field to signing with NemID. | ||
# The user will be notified via | # The user will be notified via email containing a link for where to sign the document | ||
# When signing a document is generated including a NemID signature | |||
# After signing the documentis saved in the same field carrying the postfix _signed | # After signing the documentis saved in the same field carrying the postfix _signed | ||
All steps after 1 are the same as [[Codeunit/StatusAction/SignNemIdActionStatus|SignNemIdActionStatus]] | |||
== How to setup == | == How to setup == | ||
Revision as of 10:50, 30 August 2021
What it does
- Generates a document based on a defined template
- Will send a document from a document field to signing with NemID.
- The user will be notified via email containing a link for where to sign the document
- When signing a document is generated including a NemID signature
- After signing the documentis saved in the same field carrying the postfix _signed
All steps after 1 are the same as SignNemIdActionStatus
How to setup
Follow the directions in SignNemIdActionStatus
In addition the following must be set
- Signer.TemplateID What template to use to generate the output
- Signer.FieldID Field to store the output in
- Signer.FileName What to name the output file (teh same as Signer.FieldFil)