Question
Wipro Technologies
GB
Last activity: 8 Feb 2024 11:37 EST
Getting error "ID":"Pega_API_055" ,"message":"Validation messages found."
hi
I tried creating a case through Pega API - I do have the property configured as a page property and there is no validation on the property
While I am trying to create a case through Pega API - I get a 401 error message - please could someone guide me?
The Body I am trying to use is :
{ "caseTypeID": "XXX-XXX-Work-XXX", "processID": "pyStartCase", "content": { "Customer":{ "CustomerID":"1" } } }
"ID":"Pega_API_055" ,"message":"Validation messages found." and the error message is:
hi
I tried creating a case through Pega API - I do have the property configured as a page property and there is no validation on the property
While I am trying to create a case through Pega API - I get a 401 error message - please could someone guide me?
The Body I am trying to use is :
{ "caseTypeID": "XXX-XXX-Work-XXX", "processID": "pyStartCase", "content": { "Customer":{ "CustomerID":"1" } } }
"ID":"Pega_API_055" ,"message":"Validation messages found." and the error message is:
{ "pxObjClass":"Pega-API-CaseManagement-Case" ,"createCaseRequest":{ "caseTypeID":"XXX-XXX-Work-XXX" ,"processID":"pyStartCase" ,"pxObjClass":"Pega-API-CaseManagement" ,"content":{ "pxActiveChannelFromAPI":"Web" ,"pxCreatedFromChannel":"Web" ,"pxObjClass":"XXX-XXX-Work-XXX" ,"Customer":{ "CustomerID":"1" } } } ,"errors":[ { "ID":"Pega_API_055" ,"message":"Validation messages found." ,"pxObjClass":"Pega-API-Error" ,"ValidationMessages":[ { "pxObjClass":"Pega-API-Error-ValidationMessage" ,"ValidationMessage":"The page contains an undefined property: pyWorkPage.Customer\nValidation failed: Errors Detected." } ] } ] }
Please note if only Page property is given (not the embedded property within page - it works and I get a 201 created message
Accepted Solution
Wipro Technologies
GB
@JaghadishR: This is now solved - was a silly mistake but for others to note
While configuring the Service Package from which this API is run - the access group should have access to the properties defined - else this error would pop up - so careful in selecting the access group - cheers
Pegasystems Inc.
US
I also had this error (Pega_API_055) using Postman. In my case, i had to set the access group of Operator ID used for basic authentication (in Postman) to the one that had access to the case type that i was trying to create using POST/cases API. That fixed it.