For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configure PDF-Upload Fields as S-Sign Fields

This page will walk the user through configuring a standard PDF-Upload Field as a S-Sign Merge Field in order to leverage the Render If Functionality

Phase 1: Consideration

As an S-Docs User, there are many template formats to consider when planning out document generation. PDF-Upload offers a low-effort process to quickly build out templates by uploading a previously generated PDF Document and drag and drop functionality.

PDF-Upload's compatibility with S-Sign allows user's to quickly build out templates and drag and drop different S-Sign Fields that active signers can engage.

In more complex use cases, individual signer inputs should be conditionally rendered based on customizable logic. Due to the nature of the PDF-Upload format, conditionally rendered fields within the template is not achievable through a render block. In this scenario, we can configure a standard PDF-Upload Field to be recognized as an S-Sign Field.

Phase 2: Understanding the syntax

The standard PDF-Upload Field has specific parameters the user can configure:

  • Merge Field: The data that will be collected and displayed in the rendered document

  • Additional Style: Any additive CSS to be generated in the document (CSS 2.1 and below supported)

  • Render If: Conditional Logic that must evaluate to TRUE for the field to be generated

In order to configure these fields to be recognized as S-Sign Fields during generation, the user will have to declare the Profile, Field Type, and any other configuration offered by the standard S-Sign Field into the Merge Field Input:

Phase 3: Building the S-Sign Field

The following are working examples of different S-Sign Fields that are available as merge field inputs:

Last updated

Was this helpful?