Difference between revisions of "Codeunit/StatusAction/SignNemIdActionStatus"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
Set the following entity configurations | Set the following entity configurations | ||
* '''Signer.FieldFil''' Field containing the file to be signed | * '''Signer.FieldFil''' Field NAME containing the file to be signed | ||
* '''Signer.FieldFilID''' Field containing the file to be signed | * '''Signer.FieldFilID''' Field ID containing the file to be signed | ||
* '''Signer.FieldEmail''' Field containing the email of the signer | * '''Signer.FieldEmail''' Field NAME containing the email of the signer | ||
* '''Signer.FieldCPR''' Reserved for future use (specify any field) | * '''Signer.FieldCPR''' Reserved for future use (specify any field) | ||
* '''Signer.ServerToken''' Code to connect to the server (ask your TS contact) | * '''Signer.ServerToken''' Code to connect to the server (ask your TS contact) | ||
Revision as of 12:55, 30 August 2021
What it does
- 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
How to set up
Add a status action and set the codeunit Classname to: dk.tempusserva.signing.nemid.SignNemIdActionStatus
Set the following entity configurations
- 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