Role and Signer should be one to one mapping, although it’s presented in an array. There’s a blog talking about the relationship between them: Role vs Signer
Role is more like a placeholder and is binded to the signature. While Signer contains the actual personal information of the signer.
Take the “create and apply layout” scenario as an example. In different packages, although actual signers are different, but when applying the same layout to the package, OneSpan Sign will recognize the role regardless of the signer and map/clone the signatures and fields to the corresponding role.
Hope this could help!
Duo Liang OneSpan Junior Technical Evangelist
This reply was modified 1 week, 5 days ago by Duo_Liang.
No, unfortunately there’s no method to remove the sender from the “roles” array. But you can hide sender from Designer View and from the dropdown list in Signing Ceremony if you were using in-person signing.
You can find more information regarding in-person signing on this page.
It is sometimes convenient for a package’s documents to be signed by the package owner and all other signers on the same device. For example, a life insurance agent may visit clients in their homes. Using a mobile device such as a tablet, the agent can prepare the insurance package while meeting with the clients, and both agent and clients can sign all documents during their meeting.
Such scenarios are called in-person signing. When that OneSpan Sign feature is enabled for a package, all the package’be s documents must signed on the same device by all signers.
So please let me know whether in-person signing fits your case. Or you can share me more on your use case.
Yes! that’s exactly what we need, as we have some scenarios that the agent needs to collect the signatures on the same device and being able to switch between different signers and pass the device to them while they are on premise.