> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/fr/portal/portal-widgets/forms.md).

# Formulaires

Créez des formulaires liés à des données dans les widgets du portail PowerShell Universal en utilisant le composant Form et un modèle de classe PowerShell avec des rappels d'événement de soumission.

Les formulaires peuvent être créés à l'aide du composant `Form`. Il peut s'agir d'un mélange de divers types de composants de saisie qui se lient à un type de classe PowerShell.

## Formulaire de base

Un formulaire de base nécessite une définition de classe PowerShell pour définir l'objet utilisé comme modèle du formulaire. Voici un exemple du script derrière cette appli Blazor. Il crée une classe PowerShell, l'assigne à la variable $Model, puis définit un rappel d'événement à invoquer lorsque le formulaire est soumis.

```powershell
class MyClass {
    [string]$Str 
}

$Variables["Model"] = [MyClass]::new()

function Submit {
    param($EventArgs)

    $Message.Success($EventArgs.Model.Str)
}
```

Pour utiliser le script PowerShell ci-dessus dans un formulaire, vous pouvez utiliser la syntaxe PSBlazor suivante.

```markup
<Row>
    <Form Model="$Model" OnFinish="Submit">
        <FormItem>
            <Input bind-Value="$Model.Str" />
        </FormItem>
        <FormItem>
            <Button HtmlType="Submit">Submit</Button>
        </FormItem>
    </Form>
</Row>
```


---

# 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.devolutions.net/powershell-universal/fr/portal/portal-widgets/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.