How to parse json string in Pega 6.2 sp2
I have a CONNECT REST Service returning me a json response. By creating the classes & properties I have mapped all the response data onto clipboard properties. One of the propertiy value itself is a string in json format. How can I parse this json string & set the name value pairs into sub-properties in that page? Java parsing code requires importing of JSON packages
import org.json.simple.JSONArray;
import org.json.simple.JSONObject;
import org.json.simple.parser.JSONParser;
which throws an error in Pega.
The JSON Response from REST service in SOAP UI is as below:
Note the selectedProviders element in red is the one containing the json string that needs to be parsed. I have shortened the json string so please excuse any sytax errors, but hope u understood what I am looking for
{
"result": {
"transactionId": "S5383520160702T061426191",
"selectedProviders": { "ts": "278571179974", "txnid": "123456789ABCDEF0", "network": "52", "psc": "199367", "fipsCountyCode": "NE1234", "cmsCountyCode": "5678"}
},
"status": {"messages": [ {
"code": "1000",
"name": "SUCCESS",
"severity": "INFO",
"description": "Successful service call",
"transactionId": "487d4f0f-aacc-42ca-b745-d273c955444a"
}]}
}
PLEASE don't ask me to upgrade which I will be doing next year!!
Accepted Solution
Ai4Process
GB
Thanks Praneeth, I already tried that but .adoptJSONObject API doesnt work in Pega 6.2.
For now, I have written a custom java function & imported some jars related to json parsers & included the jars in our classpath.
Pegasystems Inc.
CA
What you call "property value itself is a string in json format" is technically a JSON object inside another object J
Since you are on 6.2 SP2, you need to create classes and properties manually. In the example you provided,
selectedProviders would be an embedded page property in the result class. In selectedProvider's page class, you should create text type properties for ts, txnid, network, psc, fipsCountyCode, cmsCountyCode. You don't need to write custom Java for this. JSON data would automatically map to clipboard if your data model is created correctly. Just remember this:
Pega equivalent of JSON object is a Page property.
Pega equivalent of JSON array is a PageList property.
Updated: 4 Jul 2016 19:51 EDT
Ai4Process
GB
Thanks Praneeth. That helps. But having said that, I am still facing issues. I changed the SelectedProviders property to a pagelist & created all the properties & classes under it as per the json data structure. BUt the entire json sub-object is still being set on the pxobjclass property of SelectedProviders[1]. It could possibly be due to some escape characters & \n & \t characters present in the json object. This is still a valid json - I checked with an online json validator. But maybe Pega is not able to parse it due to these escape characters.
I have asked the backend team to check if they can eliminate these characters. But when u look at the page from the tracer it doesn't show these characters, but it does show up in SOAP UI. So ideally Parsing should also work correctly.
{
"result": {
"transactionId": "S23131020160704T213604208",
"selectedProviders": [
Thanks Praneeth. That helps. But having said that, I am still facing issues. I changed the SelectedProviders property to a pagelist & created all the properties & classes under it as per the json data structure. BUt the entire json sub-object is still being set on the pxobjclass property of SelectedProviders[1]. It could possibly be due to some escape characters & \n & \t characters present in the json object. This is still a valid json - I checked with an online json validator. But maybe Pega is not able to parse it due to these escape characters.
I have asked the backend team to check if they can eliminate these characters. But when u look at the page from the tracer it doesn't show these characters, but it does show up in SOAP UI. So ideally Parsing should also work correctly.
{
"result": {
"transactionId": "S23131020160704T213604208",
"selectedProviders": [
"\"{\n\t\"ts\": \"278571179974\",\n\t\"txnid\": \"123456789ABCDEF0\",\n\t\"network\": \"52\",\n\t\"psc\": \"199367\",\n\t\"fipsCountyCode\": \"NE1234\",\n\t\"cmsCountyCode\": \"5678\",\n\t\"providers\": [{\n\t\t\"providerId\": \"1234567\",\n\t\t\"providerType\": \"individual\",\n\t\t\"providerAddressId\": \"124\",\n\t\t\"providerName\": {\n\t\t\t\"lastName\": \"Rogers\",\n\t\t\t\"firstName\": \"Aaron\",\n\t\t\t\"middleName\": \"Angus\",\n\t\t\t\"suffix\": \"Sr.\",\n\t\t\t\"degree\": \"MD\"\n\t\t},\n\t\t\"providerAddress\": {\n\t\t\t\"street1\": \"198 2nd Street\",\n\t\t\t\"city\": \"Minneapolis\",\n\t\t\t\"state\": \"CA\",\n\t\t\t\"zip\": \"95064\",\n\t\t\t\"phone\": \"818-122-1539\"\n\t\t},\n\t\t\"gender\": \"m\",\n\t\t\"providerTier\": true,\n\t\t\"tierType\": \"2\",\n\t\t\"acceptingNewPatients\": \"E\",\n\t\t\"pcpQualifiedId\": true,\n\t\t\"additionalLanguages\": [\"Farsi\", \"Klingon\"],\n\t\t\"coverageDates\": [{\n\t\t\t\"startDate\": \"6487658794\",\n\t\t\t\"endDate\": \"291799996597\"\n\t\t}, {\n\t\t\t\"startDate\": \"138784872\",\n\t\t\t\"endDate\": \"194881238784\"\n\t\t}],\n\t\t\"medicalGroup\": {\n\t\t\t\"medicalGroupId\": \"1111\",\n\t\t\t\"medicalGroupDesc\": \"Rogers and Associates\"\n\t\t},\n\t\t\"specialties\": [\"Generalist\", \"Allergies\"],\n\t\t\"providerPlans\": [{\n\t\t\t\"planCode\": \"1234\",\n\t\t\t\"planDescription\": \"AARP Medicare\"\n\t\t}, {\n\t\t\t\"planCode\": \"4567\",\n\t\t\t\"planDescription\": \"AARP Advanced\"\n\t\t}]\n\t}]\n}\""
]
},
"status": {"messages": [ {
"code": "1000",
"name": "SUCCESS",
"severity": "INFO",
"description": "Successful service call",
"transactionId": "784f8f19-b823-4ce9-a118-d699d8cc4a94"
}]}
}
Attached is the screenshot from the clipboard
Updated: 5 Jul 2016 4:56 EDT
PEG
IN
In order to work on special characters "pyInboundIdentifierEncoder" and "pyOutboundIdentifierDecoder" decision tables are responsible.
Please refer https://community.pega.com/support/support-articles/connect-rest-json-mapping-issue-invalid-property-name
Based on Praneeth's response, I did strike off my response.
Pegasystems Inc.
CA
What is the value of Map to you configured on the response tab of Connect REST? Is it JSON or Clipboard? If it is JSON, try this alternative for a quick test:
1. Change Map to to Clipboard and use a parameter or a single value text property as Map to key.
2. Once the JSON response is available in the parameter or the property, call ClipboardPage.adoptJSONObject(<JSON_Here>) from a Java step in an activity.
Check if the issue still persists with this alternative.
Accepted Solution
Ai4Process
GB
Thanks Praneeth, I already tried that but .adoptJSONObject API doesnt work in Pega 6.2.
For now, I have written a custom java function & imported some jars related to json parsers & included the jars in our classpath.