> 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/da/portal/portal-widgets/forms.md).

# Formularer

Byg databundne formularer i portalwidgets i PowerShell Universal ved hjælp af Form-komponenten og en PowerShell-klassemodel med tilbagekald for indsendelseshændelser.

Formularer kan oprettes ved hjælp af komponenten `Form`. Den kan være en blanding af forskellige typer inputkomponenter, der bindes til en PowerShell-klassetype.

## Grundlæggende formular

En grundlæggende formular kræver en PowerShell-klassedefinition til at definere det objekt, der bruges som model for formularen. Nedenfor er et eksempel på scriptet bag denne Blazor-app. Det opretter en PowerShell-klasse, sætter den til variablen $Model og definerer derefter et hændelses-callback, der skal kaldes, når formularen indsendes.

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

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

function Submit {
    param($EventArgs)

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

For at bruge ovenstående PowerShell-script i en formular kan De bruge følgende PSBlazor-syntaks.

```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/da/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.