# How to: Use many S-Sign Enabled PDF-Upload Templates as Components

### Before you start:

Before setting up the templates, the user should have a working knowledge of:

* How to create and call component templates
* How to call PDF-Upload Templates as components
* How to create and configure S-Sign Templates

***

{% hint style="warning" %}
When developing this use case, it is good to keep scalability in mind. The more Components that are used make document generation more complex, which can lead to encountering Governor Limits such as APEX CPU Time Limit. Additionally, the larger the list of components to be merged in, the larger the list of S-Sign Fields and Profiles will need to be defined. 
{% endhint %}

### Pattern 1: Configure the Parent Template

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

In the template body of the parent, add all the PDF-Upload templates that are to be merged in.

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

In S-Sign Fields, list out all of the fields that are to be used throughout ALL of the component templates. This means if there are a total of 20 fields throughout all of the components, the parent template will define all 20 of the fields.&#x20;

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

Define all of the signer profiles to be used throughout the components. The Profile Name, Email Address, Signing Name, and Signing Order must match the profile that is listed in the component.&#x20;

{% hint style="info" %}
Note: Not every profile defined in the parent must be used in a component, but any profiles to be listed in the components must be listed and identical in the parent template.&#x20;
{% endhint %}

***

### Pattern 2: Configure the Component Templates

**S-Sign Fields must be unique** throughout document generation and E-Signature Requests.&#x20;

This means that two fields can both require signature, but one input field must have I**nput Field ID 1** and the other **Input Field ID 2**.&#x20;

As we are pulling each of the PDF-Upload Components into a single Parent Template, we **must define each field within the component templates uniquely**.&#x20;

Take for example a use case where we have 3 components with 6 total fields. If the first component defines fields 1 and 2, the consecutive templates would have S-Sign Fields defined as follows:

{% columns %}
{% column %}

<figure><img src="/files/4eSY3tTpLbep0wUYphbJ" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="/files/vDSiOM53H3lAuGOdaCe8" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}


---

# 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/how-to-use-many-s-sign-enabled-pdf-upload-templates-as-components.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.