Details
-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
Description
It is illegal to have something like this in the payload of an event based process:
{
mappings: {Task_0f2cay4: {start: null, end: null}},
...
}
- The API should return a 400 when trying to save a process with such a mapping
- The frontend needs to remove empty mapping nodes when mapping events to processes
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
1.
|
Remove empty mapping nodes on update |
|
Done | Unassigned |
2.
|
Prevent mappings being accepted with null start and end values |
|
Done | Unassigned |