These are examples of settings and setting formats when specifying variables and Data Items in the setting of Tasks.
Embeddable System Variables
Title
Syntax (Expression Language) | Example (Result to be embedded) |
---|---|
#{processInstanceTitle} | foo |
Process ID
#{processInstanceId} | 12345 |
- Prefix "p" is not embedded
Process Start User
#{processInstanceInitQuserName} | NAKAMURA Haruko |
Process Start Organization
#{processInstanceInitQgroupName} | Sales |
Process Start DateTime
#{processInstanceStartDatetime} | 2020-03-14 09:45 |
Process Sequence Number
#{processInstanceSequenceNumber} | 12 |
App ID
#{processModelInfoId} | 50 |
App Name
#{processModelInfoName} | Inquiry-handling flow |
Embeddable Data-type
String-type
Syntax (Expression Language) | Example (Result to be embedded) |
---|---|
#q_string | ABC |
- Multi-line input causes an error
Numeric-type
#q_numeric | 5,678 (1234.56) ($99.99) |
- Prefix/suffix, point notation, etc. will follow the process data setting
Select-type
#q_select_check | Japan (Japan Brazil Spain Germany) |
- Separated by a space if more than one Choice was checked when using a Check Box
Date-type
#q_date | 2020-03-14 (2020-03) (2011) (03-14) |
#{#format(#q_date, 'dd.MMM,yyyy')} | 14.Mar,2020 |
- Follows the sub-type settings in the Data Item
Datetime-type
#q_datetime | 2020-03-14 23:45 |
#{#format(#q_datetime, 'EEE. dd MMMM, yyyy aH:mm')} | Mon. 14 March, 2020 PM11:45 |
File-type
#q_file | file name (fileA, fileB) |
- The file name is embedded
- Delimited by a comma if there is more than one file
User-type
#q_user | YAMADA Taro <yamada@example.com> |
Organization-type
#q_organization | Sales <sales@example.com> |
(Discussion-type)
#q_discussion | --- |
- Can be specified but not used
Table-type
#q_table | 2 row(s) |
- The number of rows of input data
(Guide Panel-type)
--- | (Display only) |
Comments
0 comments
Article is closed for comments.