This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
ns-configview
The following operations can be performed on “ns-configview”:
| switch | show |
switch ns configview
Changes configview setting for the client.
Synopsis
switch ns configview
Arguments
state State is a session-level setting that controls the configuration shown to the user. Based on the selected option user will be able to see only the configuration created through Classic Interface (CLI/API) or Only Configurations created through Next-Gen API, Or both Classic & Next-Gen API interfaces.
Configurations created by Nextgenapi are read-only and can only be modified via Next-Gen API REST endpoints. Configurations created by classic interfaces (CLI, NITRO) are editable for CLASSIC or ALL views. Possible values:
- CLASSIC: Config view is limited to the configuration entities created through classic interfaces (CLI, NITRO). This is the default behaviour.
- NEXTGENAPI: Config view is limited to the configuration entities created through Next-Gen API Interface.
- ALL: Configurations created by both Classic and Next-Gen API interfaces are visible.
Possible values: CLASSIC, NEXTGENAPI, ALL Default value: CLASSIC
Example
switch ns configview nextgenapi
show ns configview
Shows configview setting for the client
Synopsis
show ns configview
Arguments
Output
state State is a session-level setting that controls the configuration shown to the user. Based on the selected option user will be able to see only the configuration created through Classic Interface (CLI/API) or Only Configurations created through Next-Gen API, Or both Classic & Next-Gen API interfaces.
Configurations created by Nextgenapi are read-only and can only be modified via Next-Gen API REST endpoints. Configurations created by classic interfaces (CLI, NITRO) are editable for CLASSIC or ALL views. Possible values:
- CLASSIC: Config view is limited to the configuration entities created through classic interfaces (CLI, NITRO). This is the default behaviour.
- NEXTGENAPI: Config view is limited to the configuration entities created through Next-Gen API Interface.
- ALL: Configurations created by both Classic and Next-Gen API interfaces are visible.
_nextgenAPIResource
Example
show ns configview
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.