Genesys Cloud - Main

Hello Andrew, 

I believe this is a limitation in Architect's JSON handling. Architect doesn't really provide a built-in way to validate JSON strings before parsing them. 

I can think of a "work" around for this by using the error handling block. The most reliable approach is to wrap your JsonParse operation in an error handling block. This way you can handle both blank strings and malformed JSON. You can then decide what to do when invalid JSON is received (example: log the error, use a default value, etc.)

 But I highly recommend submitting a feature request to our ideas lab for a built in way to validate json strings as this sounds like a great feature to have. 

Hope this helps!

Thanks for your response Cameron.

The error handling block sounds ideal. It sounds like a try/catch functionality. 

Sorry for my ignorance, but I am not familiar with the "error handling block".
Is it the "Event Handling" in the flow (I am using an email flow, so my only choice is to route to a fallback queue - or disconnect).
Or is it an object I should be able to select from the architect toolbox.
Or is it something completely different :-) ?

Thanks again.

Hello Andrew, 

I believe this is a limitation in Architect's JSON handling. Architect doesn't really provide a built-in way to validate JSON strings before parsing them. 

I can think of a "work" around for this by using the error handling block. The most reliable approach is to wrap your JsonParse operation in an error handling block. This way you can handle both blank strings and malformed JSON. You can then decide what to do when invalid JSON is received (example: log the error, use a default value, etc.)

 But I highly recommend submitting a feature request to our ideas lab for a built in way to validate json strings as this sounds like a great feature to have. 

Hope this helps!

Hello Andrew, 

Sorry about I made that sound confusing. Error handling is actually part of the flow's properties and not a separate block in the toolbox. 

Cheers, 

Thanks for your response Cameron.

The error handling block sounds ideal. It sounds like a try/catch functionality. 

Sorry for my ignorance, but I am not familiar with the "error handling block".
Is it the "Event Handling" in the flow (I am using an email flow, so my only choice is to route to a fallback queue - or disconnect).
Or is it an object I should be able to select from the architect toolbox.
Or is it something completely different :-) ?

Thanks again.

Hello Andrew, 

I believe this is a limitation in Architect's JSON handling. Architect doesn't really provide a built-in way to validate JSON strings before parsing them. 

I can think of a "work" around for this by using the error handling block. The most reliable approach is to wrap your JsonParse operation in an error handling block. This way you can handle both blank strings and malformed JSON. You can then decide what to do when invalid JSON is received (example: log the error, use a default value, etc.)

 But I highly recommend submitting a feature request to our ideas lab for a built in way to validate json strings as this sounds like a great feature to have. 

Hope this helps!