...
Table of Contents maxLevel 12
Introduction
You can specify how you want to enter messages from the Input Mode menu in message tools and responders like Request, Response, and Payload. The Form GraphQL input mode provides a tree view of the GraphQL message so that you can construct and review GraphQL messages in a graphical interface. This mode is a GraphQL-focused version of the Form Input mode.
GraphQL Messages Constrained to an SDL
| Anchor | ||||
|---|---|---|---|---|
|
You can constrain your GraphQL message to a schema definition by linking it to an SDL. To build a GraphQL message constrained to an SDL:
...
To remove a field, argument, or directive, select its parent node and uncheck it. To remove a variable, select it in the Variables table and click Delete.
Unconstrained GraphQL Messages
You can build an unconstrained GraphQL message manually or, if you have a GraphQL message available, use it to build your Form GraphQL. To do so, paste your GraphQL message into the Literal view, then switch to Form GraphQL view. The Form GraphQL view will automatically be populated with the provided values and show a graphical representation of the message.
...
To remove a field, argument, or directive, right-click the node and choose Delete. To remove a variable, select it in the Variables table and click Delete.
Editing Values
| Anchor | ||||
|---|---|---|---|---|
|
You can specify values using the fixed, parameterized, auto, and script options available across the various tree views.
Note that Form Input options which are applicable to GraphQL are available from this view (with relevant terminology changes, such as null vs nil). This includes populating the entire tree with values in a data source, generating a CSV data source template, replacing specific elements with data source values, and so on. For details, see Form Input.
Viewing the Literal GraphQL
Switching to the Literal view will apply the contents of Form GraphQL to the Literal view. Right-clicking GraphQL messages in the Literal view allows you to automatically "beautify" the GraphQL.
...