Versions Compared

Old Version 1

changes.mady.by.user Chieko Sugizaki

Saved on

compared with

New Version Current

changes.mady.by.user Robert Andelin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2023.2

...

You can specify how you want to enter messages from the Input Mode drop-down list in message menu in message tools and responders (e.g., like Request, Response, and Payload). The Form JSON input mode provides a tree view of the JSON message so that you can construct and review JSON messages in a graphical interface. This mode is a JSON-focused version of the Form Input mode.

...

Additionally, you can build out the tree to reflect the appropriate message structure (i.e.that is, by inserting, removing, copying, and pasting nodes). You can copy and paste into arrays and objects.

...

Info
iconfalse
titleParameterizing Number or Boolean Fields in a Literal Message

With all message formats, including JSON, you can use the ${} syntax to access data source values from data sources or data banks—for banks. For example, you could use ${title} to reference the title column from a data source or use ${books:publisher} to reference the publisher column from the books sheet of an Excel data source.

Specifically for JSON, a special notation is used for parameterizing a number or boolean field within a JSON message: ${number:<value>} or ${boolean:<value>}. For example, to parameterize a number field with the column Count, you would use ${number:Count}.

If you forget to use this format for number or boolean fields and switch from Literal view to Form JSON view, you will see a warning dialog such as the following:

...