For instance, a usual use case is to define a data type like the following:
record MyDataType {
string[] field1 // a list of strings
int[][] field2 // a matrix of integers
...
}
Currently, such a datatype can't be defined in the BPMN viewer.
Also, data types names only make sense for sorts. Lists of strings do not need a name, neither maps from integers to Booleans, etc... Actually, it may make sense to only allow sorts definitions, while for their fields we allow to use lists, maps, sorts and basic types.
Finally, I would like to be able to nest data types for fields, such as int[][][] or map<int,map<String,list[Bool]>.
For instance, a usual use case is to define a data type like the following:
Currently, such a datatype can't be defined in the BPMN viewer.
Also, data types names only make sense for sorts. Lists of strings do not need a name, neither maps from integers to Booleans, etc... Actually, it may make sense to only allow sorts definitions, while for their fields we allow to use lists, maps, sorts and basic types.
Finally, I would like to be able to nest data types for fields, such as int[][][] or map<int,map<String,list[Bool]>.