As we’ve seen from this case, it is possible to make sure signatures can work with digital signing integrations:
This is done by adding sign markers tags, which allows for an integration to “print” (for a lack of a better word) their signing mechanism on the generated PDF from Silverfin.
However, we need to be sure that the digital signing matches on our PDF. There’s a limited space available in our legal texts for example in the signatures section, which the signing integration should respect.
If not, there might be cases in which the digital signing will overlap with other printed text.
With this case, we share the fixed sections which we are holding onto in every of our templates that are available for digital signing.
As one can see, all of our signatures are created with a maximum of 2 signatures next to each other.
Each signature has a fixed placement of where the digital signature can be put.
It is quite important that these sections are respected so all signing integrations can work with any template (not just the ones of Silverfin) and their signing part.
Below an example, of where the signmarkers should be made available for signing integrations:
So any signing partner will place the digital signature on that signmarker upwards.
To make sure all signing integrations can work with any template in Silverfin, the following guidelines should be followed when creating the placement of the signmarker:
- 5 breaks before each signmarker (which will be used to add the digital signature on)
- 3 breaks after each signmarker (to make sure it’s not too close either to the next signature)
An example of code:
{% stripnewlines %}
{% newline %}
|------
{% for i in (1..aantal_kolommen) %}
----{{ 100/aantal_kolommen | integer }}%------|
{% endfor %}
+
{% newline %}
|
{% for signature in zkv_signatures %}
<br><br><br><br><br>
{{ signature }}
|
{% assign modulo = forloop.index | modulo:2 %}
{% if modulo == 0 %}
{% unless forloop.last %}
{% newline %}
|
{% endunless %}
{% endif %}
{% endfor %}
{% newline %}
| <br>
{% endstripnewlines %}
The signmarkers themselves are actually created in one array that holds all info of signatures (function, name, …) and it’s in there where we place the 3 additional break tags:
{% assign signatures = signatures | append: signmarkers | append:"<br>" | append:"<br>" | append:"<br>" | append:current_signature %}
