Question
STAIDLOGIC LLC
CA
Last activity: 24 Feb 2023 8:54 EST
Not able to map integration property in JSON request in REST API
We have consumed REST API 2 years ago via Connect REST wizard. After 2 years external system has new page list type attribute. Below is example. We did not re consume REST API via wizard instead just created properties in pega on integration layer and map it to Request Data transform. We found run time in tracer newly mapped properties did not added into JSON request. So finally, We re consumed REST API and now it map correctly.
We would like to know is it Pega OOB behaviour/limitation on REST API side? In future do we have to re consume every time when new attribute get added into existing JSON?
Another question I have is in SOAP services we have XML stream rule where we can add/modify/delete new attribute/elements. Where does Pega system stores actual JSON request after running REST wizard?
"attributesCriterion": [
{
"_ALL": {
"eq": ["*2550000493M*"]
}
We have consumed REST API 2 years ago via Connect REST wizard. After 2 years external system has new page list type attribute. Below is example. We did not re consume REST API via wizard instead just created properties in pega on integration layer and map it to Request Data transform. We found run time in tracer newly mapped properties did not added into JSON request. So finally, We re consumed REST API and now it map correctly.
We would like to know is it Pega OOB behaviour/limitation on REST API side? In future do we have to re consume every time when new attribute get added into existing JSON?
Another question I have is in SOAP services we have XML stream rule where we can add/modify/delete new attribute/elements. Where does Pega system stores actual JSON request after running REST wizard?
"attributesCriterion": [
{
"_ALL": {
"eq": ["*2550000493M*"]
}
}
]
Maantic Inc
US
@BHAVESHP1853 when you manually add new properties, it should work.
for new json elements, could you compare manually created properties and wizard created properties. that will explain the rootcause.
HF Management Services, LLC
IN
@BHAVESHP1853 The properties you created should match with the json fields. Please try this it will work.