- Newest
- Most votes
- Most comments
The optimized service integrations accept BOOL, however there is a difference between how AWS SDK integrations handle request parameters. If you switch from "BOOL"
to "Bool"
it will work. All parameters for AWS SDK integrations must be in PascalCase.
Source:
The API action will always be camel case, and parameter names will be Pascal case. For example, you could use Step Functions' startSyncExecution API action and specify the parameter StateMachineArn.
https://docs.aws.amazon.com/step-functions/latest/dg/supported-services-awssdk.html
According to this, you should change
":scheduled": { "BOOL":true }
to
":scheduled": true
Did not try it.
Querying is not supported in SFN, just get, put, delete, and update.
Query is supported by StepFunctions.
oops i was looking at optimized integrations. sorry!
Relevant content
- Accepted Answerasked a year ago
- asked 2 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
Thanks for your suggestion. But unfortunately this doesn't work as its javascript. Looks like internally the step-function uses JAVA SDK. Was able to figure this out from the error:
Here is the Java doc for Filter Expression. Its like chicken and egg situation here: