Core Signature Service Thrust API 26.2 introduces several key enhancements designed to streamline integration and improve workflow efficiency.
Developers can now leverage Signing Group Support for Integrating Applications, allowing direct passing of signing groups to Core Signature from integrated applications. This eliminates the need for prior group synchronization or field mapping, simplifying the signing process for groups. Anyone from the group can sign the document and it will be considered as signed
Another significant update is Automatic Document Signing for Senders. This feature enables automated signing for eligible workflows based on predefined policies, addressing the manual effort previously required for high-volume or repetitive signing processes. This boosts efficiency while maintaining compliance.
Finally, Additional Parameters to Restrict Signer Actions on the Document Preparation Page have been added. These parameters provide more granular control, allowing document senders to disable forwarding and attachment capabilities for signers during document preparation, which helps enforce organizational security policies. These updates aim to provide more flexible and robust integration options for developers.