This section gives settings samples of parameters and values when receiving data by HTTP communication for each Data type.
BPMN Icons: [Message Start Event (HTTP)], [Catching Message Intermediate Event (HTTP)]
The old format using data number (such as data[9].input) is scheduled to be discontinued in 2026-04. Please take action on the HTTP request sending side.
String type
|
Style of Parameter Name |
Sample | Description |
|---|---|---|
| q_string (data[9].input) |
foo bar |
Numeric type
| q_numeric (data[9].usdecimal) |
1234.56 | Thousands separator: None Decimal separator: Dot (.) (Do not include the prefix or suffix.) |
＊ Data which has digits after the decimal place results in a receive error. Therefore, please set up to carry out prior processing such as integer rounding and truncation
Select type
| q_selects (data[9].selects) |
true ja |
Specify 'Choice ID' If the input type is [check boxes] and you wish to specify multiple choices, multiple transmissions are made with the same parameter name. (q_selects=ja&q_selects=en) |
Date type
|
q_date |
2011-10-27 2011-10 2010 10-27 |
Follows the Sub-type setting in Data Item |
Date Time type
| q_datetime (data[9].datetime) |
2011-10-27 12:34 |
File type
| q_file (data[9].upload) |
<form action=”https://xxx.yyy/” method=”post” enctype=”multipart/form-data”> <input type=”file” name=”q_file” /> |
File is sent by POST multipart |
User type
|
q_user |
sample@example.com | Specify 'Email address' of User |
Organization type
| q_org (data[9].qgroupName) |
Sales | Specify 'Name' of Group |
Discussion type
| q_discuss (data[9].console) |
test comments | To be appended instead of overwritten. Only one comment can be added |
Table type
| q_table (data[9].input) |
<list><row><col>Apple</col><col>2.5</col><col>3</col><col>7.50</col></row><row><col>Orange</col><col>1.3</col><col>2</col><col>2.60</col></row><summary><col></col><col></col><col></col><col>10.10</col></summary></list> | Arithmetic column is required but can be empty/ Sum row (<summary>) is not a must |
Example of 'Table-type' input
Spaces and line breaks included in the input value of a table-type sub-data item (<col> element) are handled as follows:
- String-type sub-data item: Spaces are maintained as is, and an input error occurs if there is a line break
- Numeric-type sub-data items: Even if the numeric text contains spaces or line breaks before or after it, it will be interpreted as a number
- Even though the contents of the element can contain spaces and line breaks, it is recommended that only numeric text is included
- Select-type sub-data item: Spaces are maintained as is, and an input error occurs if there is a line break (regarding the value of the selection ID)
- Date-type sub-data item: Even if there are spaces or line breaks before or after the date text, it will be interpreted as a date
- Even though the contents of the element can contain spaces and line breaks, it is recommended that only date text is included
Guide Panel type
| (Display Only) |
Title
| title | foo bar |
(Language specification)
| locale | en/ja | (Error messages are returned in the specified language) |
Comments
0 comments
Article is closed for comments.