JSON Validation?
Comments
-
[font=Calibri, sans-serif]Does Decisions do input JSON validation? Can this be enabled/disabled on a case-by-case basis?[/font]
-
[font=Roboto, Arial, Helvetica, sans-serif]If the JSON sent to a flow via POST is malformed, the flow itself will not notice it. There is a system default rule named Test JSON Is Valid that can validate JSON text, however. If the input of a flow is found to be invalid with this rule, its false path can have a Throw API Exception step send a response code and some specified error message - e.g. 400: invalid JSON: asdf. (FlowWithJSONValidation)[/font]
[font=Roboto, Arial, Helvetica, sans-serif]
[/font]
[font=Roboto, Arial, Helvetica, sans-serif]If you want to validate some inputs [i]but not all[/i], you can [/font]achieve this by adding steps to check on the values of all other fields in a JSON input except those that do not need to be validated. (ADifferentApproachToJSONValidation)I have attached two example flows for these cases.
Howdy, Stranger!
Categories
- 4.5K All Categories
- 86 General
- 13 Training
- 212 Installation / Setup
- 1.2K Flows
- 112 Rules
- 277 Administration
- 215 Portal
- 502 General Q & A
- 720 Forms
- 355 Reports
- 3 Designer Extensions
- 47 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 8 Javascript Controls
- 189 Pages
- 5 Process Mining
- New Features
- 187 Datastructures
- 72 Repository
- 237 Integrations
- 30 Multi-Tenant
- 27 SDK
- 81 Modules
- 60 Settings
- 26 Active Directory
- 12 Version 7
- 36 Version 8
- 143 Lunch And Learn Questions