Camunda is potentially not fully utilizing local/process variable.

[kaladay]

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.

see:

mod-camunda/src/main/java/org/folio/rest/camunda/delegate/Input.java

Line 67 in f7dea00

private void defaultGetInputsLoop(EmbeddedVariable variable, String key, VariableType type, Object value, Map<String, Object> inputs) throws JsonProcessingException {

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