I'm not sure you can directly map from the JSON to response class in 2017. I think in the new Intersystems you can  here do this direct mapping where you add it into your message class how it maps. It's not available in 2017 as far as I'm aware. 

Id go for something like after you have the JSON Object 

set objJson = ##class(%DynamicObject).%FromJSON(response)

Set pResponse = ##class(MyMsg.PartialJson).%New()

set pResponse.ext_customer_id=objJson .ext_customer_id

...

Hi:

I see in the digest from this week this link . It sounds to be like what you are trying to do. 

Note this is built in IRIS not Ensemble 2018 so it may need tweaking in order to work in your build , i think it will still import with errors in the code. I don't see any headers that say Iris in it, if there is then change the word in the headers to cache. 

I believe you may encounter issues with the code in the link stating .%ToJSON. I think this may have been introduced in IRIS or at least after our version which was 2017,  there's a chance it is in 2018. You may need to use the method  .%WriteJSONStreamFromObject from the  %ZEN.Auxiliary.altJSONProvider or typing up manually the JSON string itself to avoid use of ZEN classes. If you look on my profile i asked a question recently of the .%WriteJSONStreamFromObject

Thanks on further testing it looks like E=S was added to a business  operation that called a sync request to another business operation as well as the one that was being called from the business  Process. As the BPL sync call is an a-syncronous call with a sync block after simply adding this to the business  operation that is called from BPL will do the job. Previously when this was tested the endpoint system was still down. This should be a more out of the box way to do the suspend queues. 

Hi:

The file gets automatically archived using the archive path. It gets passed to a bp which then validates the filename and then copies the document to a working directory before it converts the document to a tiff file. It fails as it tries to copy the file to the working directory. 

I do assume it is a fileshare availability/network issue but it is something we need contigency for to minimise manual intervention. 

Have logged to WRC. 

Mark