Description
Data Action execution and test requests will ignore null input values. This is the current behavior experienced in the UI test mode and when executing and testing data actions through the Public API. This will eliminate data action execution failures due to inconsistent null value behavior between different architect flow types.
Change Category
API
Change Context
Customers have experienced difficult-to-troubleshoot data action errors in their flows because some types of Architect flows can include null input values in their data action execution requests.
Including a null input value in a data action execution request will typically result in the data action failing during the input schema check, as a “null” type won’t match the schema. This behavior is impossible to experience with the UI test mode as the test requests go through Public API, which removes null values. This has left customers who have tested their data actions in the UI test mode having to troubleshoot difficult action/flow failures due to this difference in behavior.
Change Impact
As the first step of action processing, an execution request with a body like:
{“input1” : null,
“input2” : “ABCD”}
Will be converted to:
{“input2” : “ABCD”}
Date of Change
Mar 15, 2024
Impacted APIs
POST /api/v2/integrations/actions/{actionId}/draft/test
POST /api/v2/integrations/actions/{actionId}/execute
POST /api/v2/integrations/actions/{actionId}/test
References
[BPIVR-3004]