# Configure PDF-Upload Fields as S-Sign Fields

## 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:

<figure><img src="/files/z2y2bRV1h0CTT7ukzduU" alt=""><figcaption></figcaption></figure>

* **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:

<figure><img src="/files/RzAS4dgT5wLOOfUXzQ9f" alt=""><figcaption></figcaption></figure>

## Phase 3: Building the S-Sign Field

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

```
[[SSIGN_INPUT Profile='Signer 1' Type='Text' Required='TRUE' AdditionalStyle='font-size: 14px; color: red; font-weight: bold; background-color: #ffff00;']]
```

```
[[SSIGN_INPUT Profile='Signer 1' Type='Signature' Required='TRUE' AdditionalStyle='font-size: 14px; color: red; font-weight: bold; background-color: #ffff00;']]
```

```
[[SSIGN_INPUT Profile='Signer 1' Type='Checkbox' Required='TRUE' AdditionalStyle='font-size: 14px; color: red; font-weight: bold; background-color: #ffff00;']]
```

```
[[SSIGN_INPUT Profile='Signer 1' Type='Initials' Required='TRUE' AdditionalStyle='font-size: 14px; color: red; font-weight: bold; background-color: #ffff00;']]
```

```
[[SSIGN_INPUT Profile='Signer 1' Type='Date' Required='TRUE' AdditionalStyle='font-size: 14px; color: red; font-weight: bold; background-color: #ffff00;']]
```

{% hint style="success" %}
Note: If additional styling is needed on the S-Sign Fields, incorporate that directly into S-Sign Field syntax as a parameter. The Additional Styling field on the PDF-Upload Field UI will not incorporate styling changes for fields configured in this manner at document generation.&#x20;
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sdocs.com/s-sign/template-configuration-fields-profiles-settings/s-sign-with-pdf-upload/configure-pdf-upload-fields-as-s-sign-fields.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.