Difference between revisions of "Codeunit/StatusAction/SignNemIdActionStatusGenerator"
Jump to navigation
Jump to search
m (13 revisions imported) |
|||
| (9 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== What it does == | == What it does == | ||
# Generates a document based on a defined template | # 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 | # The user will be notified via email. The message contains a link to where to sign the document | ||
# After signing the | # 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 [[Codeunit/StatusAction/SignNemIdActionStatus|SignNemIdActionStatus]] | |||
== How to setup == | == How to setup == | ||
Add a status action and set the codeunit Classname to: | |||
'''dk.tempusserva.signing.nemid.SignNemIdActionStatusGenerator''' | |||
In addition the following must be set | Set the following entity configurations (same as [[Codeunit/StatusAction/SignNemIdActionStatus|SignNemIdActionStatus]]) | ||
* '''Signer.FieldFil''' Field NAME containing the file to be signed | |||
* '''Signer.FieldFilID''' Field ID containing the file to be signed | |||
* '''Signer.FieldEmail''' Field NAME containing the email of the signer | |||
* '''Signer.FieldCPR''' Reserved for future use (specify any field) | |||
* '''Signer.ServerToken''' Code to connect to the server (ask your TS contact) | |||
* '''Signer.StatusError''' StatusID to set on the data if failed | |||
* '''Signer.StatusSigned''' StatusID to set on the data if succes | |||
* '''Signer.EmailSubject''' Header on the email sent to the signer | |||
* '''Signer.EmailBody''' Content of the email sent to the signer | |||
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''' | * '''Signer.FileName''' Name of the output file (ex. "contract.docx") | ||
Latest revision as of 11:51, 10 December 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
Set the following entity configurations (same as SignNemIdActionStatus)
- Signer.FieldFil Field NAME containing the file to be signed
- Signer.FieldFilID Field ID containing the file to be signed
- Signer.FieldEmail Field NAME containing the email of the signer
- Signer.FieldCPR Reserved for future use (specify any field)
- Signer.ServerToken Code to connect to the server (ask your TS contact)
- Signer.StatusError StatusID to set on the data if failed
- Signer.StatusSigned StatusID to set on the data if succes
- Signer.EmailSubject Header on the email sent to the signer
- Signer.EmailBody Content of the email sent to the signer
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 Name of the output file (ex. "contract.docx")