> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/s-sign/template-configuration-fields-profiles-settings/how-to-generate-various-inputs-using-component-templates.md).
# How to: Generate various inputs using Component Templates
### Setting the scenario:
Imagine you are an S-Docs Admin that needs someone to review and approve a set of data. This set of data is repeated throughout numerous records in Salesforce. Generating individual E-Signature requests would be time consuming and cumbersome. Furthermore, we want limit the manual effort of looking for each record individually to ensure all the data is correctly gathered.
Using S-Sign in combination with method 2 will allow our S-Docs Admin to gather the data efficiently, generate an E-Signature, and collect an approval signature for each data that needs review.
### Before you start:
Before setting up the templates, the user should have a working knowledge of:
* How to create and call component using Component Queries
* How to create and configure S-Sign Templates
* How to generate an S-Sign Request
***
### Phase 1: Construct the Parent Template
Construct a template that queries for information using Component Query Method 2. Define the signer profile. No S-Sign Fields are required to be defined in the parent template.
***
### Phase 2: Construct the Component Template
Add the queried information. Define the S-Sign Input Field for the respective profile. Format should resemble:
```
[[SSIGN_INPUT Profile='Profile Name' Type='Field Type']]
```
### Phase 3: The Signing Experience
The Component Query using Method 2 will query all records that match the critera and return the specified data for each record. The Signer Inputs that are specified in the component will be present and unique for each record.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://help.sdocs.com/s-sign/template-configuration-fields-profiles-settings/how-to-generate-various-inputs-using-component-templates.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.