The input variables (and possibly output variable) are treating everything as a String.
This happens regardless of "Spin".
Camunda (not mod-camunda) appears to support Objects via additional properties.
Such as with variables of type local, there are three properties: value, type, and valueInfo.
This appears to support objectTypeName and we may support the following types:
string, number, boolean, array or object.
Implementing this feature may help solve the 4000 character limit bug but more research is need and so the spike label is also added.
The input variables (and possibly output variable) are treating everything as a String. This happens regardless of "Spin".
Camunda (not mod-camunda) appears to support Objects via additional properties. Such as with variables of type local, there are three properties:
value
,type
, andvalueInfo
. This appears to supportobjectTypeName
and we may support the following types:string
,number
,boolean
,array
orobject
.Implementing this
feature
may help solve the 4000 character limitbug
but more research is need and so thespike
label is also added.see: https://github.com/TAMULib/mod-camunda/blob/f7dea00e90877620727fa46d7190b6be712360c0/src/main/java/org/folio/rest/camunda/delegate/Input.java#L67 see: https://docs.camunda.org/rest/camunda-bpm-platform/7.22-SNAPSHOT/#tag/External-Task/operation/handleFailure see: https://forum.camunda.io/t/error-while-starting-process-instance/19433