Difference between revisions of "NemID signing"
Jump to navigation
Jump to search
old>Admin |
m (13 revisions imported) |
||
| (8 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
Before using the signing setup the signing service in Modules > Configuration. | Before using the signing setup the signing service in Modules > Configuration. | ||
Note: Among the configurations is an customer key, you can aquire from Tempus Serva support. | |||
On each entity you will need to add the following configurations | On each entity you will need to add the following configurations | ||
| Line 11: | Line 13: | ||
* Signer.FieldEmail | * Signer.FieldEmail | ||
* Signer.FieldFil | * Signer.FieldFil | ||
* Signer.StatusError | * Signer.StatusError (ID) | ||
* Signer.StatusSigned | * Signer.StatusSigned (ID) | ||
In case you want to automatically generate the documents before signing, include | |||
* Signer.FieldID | |||
* Signer.TemplateID | |||
All field refernces should use the system name (allways in uppercase). | |||
=== Manual signing === | === Manual signing === | ||
Manual signing will allow a user to click a button that starts the signing proces. | |||
# Follow steps in '''Configuration''' | # Follow steps in '''Configuration''' | ||
# Create a new button with parametrized URL | # Create a new button with parametrized URL | ||
?command=dk.tempusserva. | ?command=dk.tempusserva.signing.nemid.SignNemIdActionPage&SagID=402&DataID=[DataID] | ||
=== Automated signing === | === Automated signing === | ||
Automated signing will start the signing process when a certain status is assigned | |||
# Follow steps in '''Configuration''' | # Follow steps in '''Configuration''' | ||
| Line 27: | Line 38: | ||
# Insert a new codeunit execution | # Insert a new codeunit execution | ||
dk.tempusserva.signing.nemid.SignNemIdActionStatus | |||
OR | |||
dk.tempusserva.signing.nemid.SignNemIdActionStatusGenerator | |||
The later will generate the file from a defined template before sending to sending | |||
Latest revision as of 12:55, 10 December 2021
Configuration
Before using the signing setup the signing service in Modules > Configuration.
Note: Among the configurations is an customer key, you can aquire from Tempus Serva support.
On each entity you will need to add the following configurations
- Signer.EmailBody
- Signer.EmailSubject
- Signer.FieldCPR
- Signer.FieldEmail
- Signer.FieldFil
- Signer.StatusError (ID)
- Signer.StatusSigned (ID)
In case you want to automatically generate the documents before signing, include
- Signer.FieldID
- Signer.TemplateID
All field refernces should use the system name (allways in uppercase).
Manual signing
Manual signing will allow a user to click a button that starts the signing proces.
- Follow steps in Configuration
- Create a new button with parametrized URL
?command=dk.tempusserva.signing.nemid.SignNemIdActionPage&SagID=402&DataID=[DataID]
Automated signing
Automated signing will start the signing process when a certain status is assigned
- Follow steps in Configuration
- Create a new status action
- Insert a new codeunit execution
dk.tempusserva.signing.nemid.SignNemIdActionStatus
OR
dk.tempusserva.signing.nemid.SignNemIdActionStatusGenerator
The later will generate the file from a defined template before sending to sending