> 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/es/comandos-de-powershell/new-udprogress.md). # New-UDProgress New-UDProgress muestra un indicador de progreso determinado o indeterminado en PowerShell Universal, representado como un indicador circular o una barra lineal. ### Sinopsis Los diálogos de progreso pueden mostrar progreso determinado e indeterminado. También pueden ser circulares o lineales. ### Sintaxis ```powershell New-UDProgress [[-Id] ] [[-PercentComplete] ] [[-BackgroundColor] ] [[-ProgressColor] ] [-Circular] [[-Size] ] [[-Label] ] [] ``` ### Descripción Crea un diálogo de progreso. Los diálogos de progreso pueden mostrar progreso determinado e indeterminado. También pueden ser circulares o lineales. ### Parámetros #### -Id El ID del componente. De forma predeterminada, es un GUID aleatorio. ``` Required? false Position? 1 Default value [Guid]::NewGuid().ToString() Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -PercentComplete El porcentaje completado del progreso. ``` Required? false Position? 2 Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -BackgroundColor El color de fondo. ``` Required? false Position? 3 Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -ProgressColor El color de la barra de progreso. ``` Required? false Position? 4 Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Circular Si el progreso es circular. ``` Required? false Position? named Default value False Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Size El tamaño del progreso. Los valores válidos son: "small", "medium", "large" ``` Required? false Position? 5 Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Label Añade una etiqueta a un progreso circular. ``` Required? false Position? 6 Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### Parámetros comunes Este cmdlet admite los parámetros comunes: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable y OutVariable. Para obtener más información, consulte [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). ### Salidas ### Ejemplos #### Ejemplo 1: determinado ```powershell New-UDProgress -PercentComplete 75 -Id 'progress1' ``` Una barra de progreso determinada. #### Ejemplo 2: circular ```powershell New-UDProgress -Circular -Size large -Id 'progress2' ``` Una barra de progreso circular. #### Ejemplo 3: color ```powershell New-UDProgress -BackgroundColor 'red' -ProgressColor 'blue' -Id 'progress3' ``` Definir los colores de fondo y de progreso. #### Ejemplo 4: circular con etiqueta ```powershell New-UDProgress -Circular -Size large -Id 'progress4' -PercentComplete 75 -Label '75%' ``` Crear un progreso circular con una etiqueta #### Ejemplo 5 ```powershell New-UDProgress -Circular -Size large -Id 'progress4' ``` --- # 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/es/comandos-de-powershell/new-udprogress.md?ask=&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.