Hallo Nico,
thanks for reply. We are using embedded forms. The complex data type isn’t referenced by any field of the form. We only add a process variable with the complex data before the user task is active and try to use it afterwards by calling some business methods of the data type in subsequent flow conditions. But doing so breaks the form’s behavior as an error message appears and the values of the simple process variables are not shown in the form fields (seems to be null at all).
So there isn’t a real need for support, only putting a complex data type as a process variable should not break the otherwise working behavior of a form. Do you think this improvement (ignoring complex data types) has a change to be realized in one of the next releases of the process engine?
Regards--
You received this message because you are subscribed to a topic in the Google Groups "camunda BPM users & process application developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/camunda-bpm-users/5L_PtEI0ej0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-users/9eb380a1-34e2-49d8-a9b3-7141724ad520%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.