> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/request-management/request-and-service-management-service-catalog/create-forms.md).

# Build service forms with dynamic fields

Customize the request form employees fill in Slack or Teams: choose visible, optional or mandatory request attributes and add dynamic fields per service

When an employee submit a request on Slack or Teams, a short form pop-up appears where the employee can fill-up and modify :

* Modify the title of its request,
* Add a description to the request
* Categorize the request to the right service or Application

Modify the title of its request,

Add a description to the request

Categorize the request to the right service or Application

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-80bfa04ecdb60f6836c8f486ae25932ef2dfb835%2FCapture-d-%C3%A9cran-2024-01-11-%C3%A0-10.21.42.png?alt=media" alt=""><figcaption></figcaption></figure>

Still, you've got the possibility to custom this form, add dynamic fields and choose optional or mandatory fields.

### Change the requests attributes

Regarding the generic fields displayed on the form, you can do some modifications on it.\
​\
To do so, on the Admin side, you just have to :

1. Click on ***the settings*****&#x20;⚙️** (top right of the page)
2. On the left-hand menu, select "***Request attributes***"
3. Select the fields you want to put visible, the ones you want to put as mandatory

Click on ***the settings*****&#x20;⚙️** (top right of the page)

On the left-hand menu, select "***Request attributes***"

Select the fields you want to put visible, the ones you want to put as mandatory

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-51b5fd9442cae8230715677c5a17e09c1d2d4c3d%2FCapture-d-%C3%A9cran-2024-01-11-%C3%A0-10.27.57.png?alt=media" alt=""><figcaption></figcaption></figure>

### Create custom and dynamic fields

Based on the category ("[**Services**](https://app.siit.io/services?tab=all)") you have created, you can create custom forms with dynamic fields.\
​\
To do so, on the Admin side, you have to click first on the **People tab** > [**Services**](https://app.siit.io/services)

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-ccd5ff77540ed817bcf3fdcf8e8295ac611c3410%2FCapture-d-%C3%A9cran-2024-01-11-%C3%A0-10.31.10.png?alt=media" alt=""><figcaption></figcaption></figure>

Then, all you have to do is selecting the "Service" you want to custom. And follow the steps as presented in the video below ⤵️

{% embed url="<https://www.youtube.com/watch?v=3IpGwYccRYw>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/guides/request-management/request-and-service-management-service-catalog/create-forms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
