Difference between revisions of "Codeunit/StatusAction/SignNemIdActionStatusGenerator"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
Follow the directions in [[Codeunit/StatusAction/SignNemIdActionStatus|SignNemIdActionStatus]] | Follow the directions in [[Codeunit/StatusAction/SignNemIdActionStatus|SignNemIdActionStatus]] | ||
In addition the following must be set | In addition the following entity configurations must be set | ||
* '''Signer.TemplateID''' What template to use to generate the output | * '''Signer.TemplateID''' What template to use to generate the output | ||
* '''Signer.FieldID''' Field to store the output in | * '''Signer.FieldID''' Field to store the output in | ||
* '''Signer.FileName''' What to name the output file (teh same as Signer.FieldFil) | * '''Signer.FileName''' What to name the output file (teh same as Signer.FieldFil) | ||
Revision as of 13:16, 30 August 2021
What it does
- Generates a document based on a defined template
- Send a document from a document field to signing with NemID.
- The user will be notified via email. The message contains a link to where to sign the document
- When signing a document is generated including a NemID signature
- After signing, the document is saved in the same field carrying the postfix _signed
All steps after 1 are the same as SignNemIdActionStatus
How to setup
Add a status action and set the codeunit Classname to: dk.tempusserva.signing.nemid.SignNemIdActionStatusGenerator
Follow the directions in SignNemIdActionStatus
In addition the following entity configurations 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)