> 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/commandes-powershell/new-udradio.md).

# New-UDRadio

New-UDRadio crée une seule option de bouton radio dans PowerShell Universal, destinée à être utilisée dans un New-UDRadioGroup pour une sélection exclusive.

### Synopsis

Crée un bouton radio.

### Syntaxe

```powershell
New-UDRadio [[-Id] <String>] [[-Label] <String>] [-Disabled] [[-Value] <String>] [[-LabelPlacement] <String>] [[-Color] <String>] [[-Aria] <ScriptBlock>] [<CommonParameters>]
```

### Description

Crée un bouton radio. Les boutons radio doivent être inclus dans un New-UDRadioGroup.

### Paramètres

#### -Id

L'ID du composant. Sa valeur par défaut est un GUID aléatoire.

```
Required?                    false
Position?                    1
Default value                ([Guid]::NewGuid())
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Label

L'étiquette à afficher à côté du bouton radio.

```
Required?                    false
Position?                    2
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Disabled

Indique si le bouton radio est désactivé.

```
Required?                    false
Position?                    named
Default value                False
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Value

La valeur du bouton radio.

```
Required?                    false
Position?                    3
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -LabelPlacement

La position où placer l'étiquette par rapport au bouton radio.

```
Required?                    false
Position?                    4
Default value                end
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Color

La couleur du thème à appliquer à ce bouton radio

```
Required?                    false
Position?                    5
Default value                default
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Aria

Un bloc de script d'appels `New-UDAriaAttribute` qui fournit les attributs ARIA ou de rôle de ce bouton radio.

```
Required?                    false
Position?                    named
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### Paramètres communs

Cette applet de commande prend en charge les paramètres communs : Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable et OutVariable. Pour plus d'informations, consultez [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).


---

# 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/commandes-powershell/new-udradio.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.
