Question
WellsFargo
IN
Last activity: 18 Apr 2016 3:15 EDT
Can't we refer py,px properties in JSON request?
Hi,
I am building a service REST with the media type as application/JSON. In my data I have a embeded page which holds the address of the customer. In order to achieve this I am creating a Page property of Data-Party class , so I can use the OOTB properties.
And below is my JSON request. But when I pass these as part of my POST request, Pega is not able to recognize py properties and mapping of data is not done from Service page to work page.
Any thoughts?
Sample request:
{
"SourceSystem": "GPP",
"ExceptionCasesList": [{
"Amount": "100",
"ExternalTrackID": "UI022907432780122106",
"BankAccountNo": "1235459343",
"LoadNo": "3577823",
"CheckORCCNNo": "4326777",
"DoctTypeCode": "50",
"BankRoutingNo": "f",
"CustomerName": "JPMC",
"GLAccountNo": "1232323",
"PaymentRCVTS":"",
"ExceptionRCVTS":"",
"Reason": "1",
"Region": "US1",
"PartyAddress": {
"pyWorkAddress1": " 706 NW 89th Ave",
"pyCity": "Plantation",
"pyState": "Florida",
Hi,
I am building a service REST with the media type as application/JSON. In my data I have a embeded page which holds the address of the customer. In order to achieve this I am creating a Page property of Data-Party class , so I can use the OOTB properties.
And below is my JSON request. But when I pass these as part of my POST request, Pega is not able to recognize py properties and mapping of data is not done from Service page to work page.
Any thoughts?
Sample request:
{
"SourceSystem": "GPP",
"ExceptionCasesList": [{
"Amount": "100",
"ExternalTrackID": "UI022907432780122106",
"BankAccountNo": "1235459343",
"LoadNo": "3577823",
"CheckORCCNNo": "4326777",
"DoctTypeCode": "50",
"BankRoutingNo": "f",
"CustomerName": "JPMC",
"GLAccountNo": "1232323",
"PaymentRCVTS":"",
"ExceptionRCVTS":"",
"Reason": "1",
"Region": "US1",
"PartyAddress": {
"pyWorkAddress1": " 706 NW 89th Ave",
"pyCity": "Plantation",
"pyState": "Florida",
"Test":"test",
"pyPostalCode": "33324"
}
}]
}
MyServicePage inbound mapping: In the below highlighted section Test property is mapped properly , but not the pyProperties.
Pegasystems Inc.
US
I wonder if this is because the names are starting with reserved pega properties naming convention. Do you see any errors in the pega logs? If you use the sample rest request invoking your service-rest from a 3rd party tool (e.g., soap ui), is the behavior the same? If yes, then we need to focus on the pega side. Let's see from SMEs if this is expected behavior or a potential limitation.
Pegasystems Inc.
CA
This is a known limitation when you use Map to as JSON on the request tab of Service REST rule. As a workaround, map the entire JSON request to a single-value property or onto parameter page using Map to as Clipboard and use ClipboardPage.adoptJSONObject(String) API in a Java step to map the JSON request to your MyServicePage. Let me know if this helps.
Euroclear
BE
Hi Venkata,
Please create new properties to hold these details , instead of Data-Party.Application is not allowing the use of restricted keywords while you are doing the mapping.I have experienced the same in my application.Hope the below screenshots will be helpful.
