Details
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Description
AT
- Set a map of variables to the process instance scope of the process instances after the migration (see
CAM-13406for reasoning) - Variables can be set via migration plan builder (see
CAM-13401for reasoning) - Reuse the batch variable concept (introduced with
CAM-12301)- Batch id is stored in the config of execution jobs to query for the variable by batch id on handler execution
- Batch id is stored in VAR_SCOPE_ and BATCH_ID_ column
- No history is written (follow-up ticket
CAM-12302) - Batch variables are deleted in monitor job handler
- Set variables are reflected in the operation log: nrOfVariables
- Transient variables are supported synchronously but not asynchronously (follow-up ticket
CAM-12332) - Prevent Java deserialization when javaSerializationFormatEnabled is false by throwing an exception
- The problem is reflected per each variable in the migration report
- REST API exists
- Docs exists
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-13435 When setting a serialized object variable via batch operation, class cannot be found on execution
-
- Closed
-