Details
-
Feature Request
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
-
None
Description
The chain of interaction when evaluating a DMN table in BPMN is as follows:
- BPMN engine calls DMN engine to evaluate a decision table; hands in a couple of Object-type variables
- DMN engine works with deserialized object value (e.g. to be able to resolve properties in expressions)
- DMN engine hands Java objects to the history listeners for historic decision input and output instances. The listeners conver the value to an untyped value.
- BPMN engine looks up a serializer for untyped values and writes value to database
The above interaction may be undesired behavior, because the serialization information is lost in steps 2 and 3. A JSON-serialized process variable can end up XML-serialized in the decision history (since the XML serializer attempts to serialize any object). There are cases in which the XML serializer claims to be able to serialize a value, but actually is not.
To avoid such issues, it should be possible to define the serialization data format for object values returned by the DMN engine (or persisted by history listeners). This could go as a custom extension into the decision table XML.
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-4984 Historic Decision Input/Output Instance cannot handle serialized Values
-
- Closed
-