Question:
Last week, any value in the parameter signTextEntry is expected to be shown in the nemId-window like this…
In the example below it should display the text :
NEMID window text… Does work either
{{host}}/sign/orders
{
“clientReference”: “213412431234123”,
“tasks”: [
{
“profile” : “default”,
“daysToLive”: 7,
“language”: “da”,
“id”: “task-id”,
“documents”: [
{
“action”: “SIGN”,
“description”: “Sign”,
“documentRef”: “{{document_id}}”,
“id”: “doc-id”,
“source”: “SESSION”,
“signTextEntry”: “NEMID window text… Does work either”,
“sendResultToArchive” : false
}
],
“signatureMethods”: [
{
“name”: “nemid-sign”,
“type”: “SIGNED_STATEMENT”
}
],
"onTaskComplete": "https://en.wikipedia.org/wiki/Completeness",
"onTaskReject": "https://en.wikipedia.org/wiki/Cancel",
"notifications": [
{
"id": "callback-notification",
"recipient": "https://en.wikipedia.org/wiki/Cancel",
"schedule": [
{
"triggerStatus": "COMPLETED"
}
],
"type": "URL"
}
]
}
],
"daysUntilDeletion" : 14,
"packagingTasks": [
{
"id": "packaging-task-id",
"sendToArchive": true,
"method": "pades",
"documents": [
{
"taskId": "task-id",
"documentIds": [
"doc-id"
]
}
]
}
]
}
What do I do wrong??
regards Søren
Answer:
Hi Søren,
There are some things that should be clarified regarding the relationship between signText and signTextEntry.
- Configured sign text is whatever is set up in your service. It may have placeholders. Depending on language, it will be along the lines of the following: “I have read and understood the document ‘{0}’ and hereby accept and approve of its contents with my signature.” You can change this by contacting Signicat service desk, or your onboarding manager if you are currently being onboarded.
- signText is specified at task level, and will override any configured sign text. If configured, it will also override the consent text.
- signTextEntry is specified at document level, and will show up in the sign text if included in the configured signtext as the placeholder {1}.
Keep in mind that if you have more than one document, you can also have more than one signTextEntry. Considering the following configured sign text template:
I hereby declare that I have read and approve of the following documents:
{0}
Please read the accompanying description:
{1}
(You can set up different sign text templates for one document or several documents, but we will ignore that for now.)
Considering you also have the following documents:
“documents”: [
{
“id”: “doc-1”,
“description”: " Hello World ",
“action”: “SIGN”,
“source”: “SESSION”,
“documentRef”: “040520211u0lza4frwa8h13e3pwuuxb4wnmgeqk0s5pn8yq7kxvqhw7uz3”,
“signTextEntry”: " This is a document with simply the text ‘Hello World’ displayed prominently. "
},
{
“id”: “doc-2”,
“description”: " Bacon Ipsum ",
“action”: “SIGN”,
“source”: “SESSION”,
“documentRef”: “040520213g2012lh3vsoy873ixb3jctr4zvlvr0ljx646hvlyqqs43ntmt”,
“signTextEntry”: " A lorem ipsum type document with some of the text replaced by meat related words. "
}
]
Then the template will be populated in the following manner:
I hereby declare that I have read and approve of the following documents:
Hello World
Bacon IpsumPlease read the accompanying description:
This is a document with simply the text ‘Hello World’ displayed prominently.
A lorem ipsum type document with some of the text replaced by meat related words.
The default sign text does not have the {1} placeholder, which is why you’re not seeing the signTextEntry.
