Question
TCS
IN
Last activity: 29 May 2017 3:28 EDT
adoptJSONObject is not supported for html tags
Hi, I have email content that needs to be parsed received via rest connector. I am using pxConvertStringToPage to convert the content but this is not supported for html content. Below is my request content, here body is in html format. getting content not supported exception "Exception occurred while adopting data onto the target page"
{"CaseID":"O-4253",
"To":"gopal@Pega",
"Sent":"Apr 26, 2017 10:02:05 AM",
"FromAddress": "<fromemailaddress>",
Hi, I have email content that needs to be parsed received via rest connector. I am using pxConvertStringToPage to convert the content but this is not supported for html content. Below is my request content, here body is in html format. getting content not supported exception "Exception occurred while adopting data onto the target page"
{"CaseID":"O-4253",
"To":"gopal@Pega",
"Sent":"Apr 26, 2017 10:02:05 AM",
"FromAddress": "<fromemailaddress>",
"Body":"<span style="color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; background-color: rgb(236, 236, 236);">Hi Order Status Team,</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; -webkit-tap-highlight-color: transparent !important;" /> <br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; -webkit-tap-highlight-color: transparent !important;" /> <span style="color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; background-color: rgb(236, 236, 236);">Could you provide me the status of my SO : 17116202 &nbsp;</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; -webkit-tap-highlight-color: transparent !important;" /> <br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; -webkit-tap-highlight-color: transparent !important;" /> <span style="color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; background-color: rgb(236, 236, 236);">Regards</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; -webkit-tap-highlight-color: transparent !important;" /> <span style="color: rgb(0, 0, 0); font-family: OpenSans, sans-serif; font-size: 14px; background-color: rgb(236, 236, 236);">Customer abcd</span>"}
***Updated by moderator: Lochan to add Categories; edited proprietary information***
Accepted Solution
Pegasystems Inc.
GB
The JSON you posted isn't properly formed; I just saved the attachment as 'request.txt' and loaded it into 'node.js' to test: this is what I get:
/home/prpc/request.txt:1
(function (exports, require, module, __filename, __dirname) { { "CaseID": "O-4253",
^
SyntaxError: Unexpected token :
at exports.runInThisContext (vm.js:53:16)
[...]
I can't quite work out what is wrong with this JSON at this point - but in any case : no JSON parser is going to be able to read this, never mind just PRPC.
Thanks !
John
(You might be able to find some online JSON parsers which will give you a more accurate error here: or failing that - you probably want to 'chop-up' your JSON and retest it to isolate the syntax error).
Pegasystems Inc.
GB
Hi - can you please *attach* your file to your post - we need to avoid the possible issue wherein the *forum* post itself has applied additional 'escaping'.
Thanks !
John
Accepted Solution
Pegasystems Inc.
GB
The JSON you posted isn't properly formed; I just saved the attachment as 'request.txt' and loaded it into 'node.js' to test: this is what I get:
/home/prpc/request.txt:1
(function (exports, require, module, __filename, __dirname) { { "CaseID": "O-4253",
^
SyntaxError: Unexpected token :
at exports.runInThisContext (vm.js:53:16)
[...]
I can't quite work out what is wrong with this JSON at this point - but in any case : no JSON parser is going to be able to read this, never mind just PRPC.
Thanks !
John
(You might be able to find some online JSON parsers which will give you a more accurate error here: or failing that - you probably want to 'chop-up' your JSON and retest it to isolate the syntax error).
Pegasystems Inc.
GB
I just re-read your problem description: I think PRPC has created this JSON right ? (you are using a Function "pxConvertStringToPage" to generate this ?)
If so: can you dump the contents of the *input* property to a text file; and provide the outline of how you are using the 'pxConvertStringToPage' page; so we can try and reproduce this issue ?