Getting 405 Response code for Perform Assignment DXAPI in Infinity 23'1
Hi,
When I am trying to run Perform assignment API, via Pega API it works good including to update properties on the case with resuming the flow.
I am trying to consume this API from another Pega application on the same instance. When i am trying with a Load DPage (I can't update the properties on my resuming case) it is working good and resuming the flow.
When I try to create a new connect via AppStudio by passing all params and everything correctly I am getting a success response using a savable DPage which helps me to update properties as well.
Now, when I am running this savable Dpage from the case I am getting 405 error:
the http response code of 405 indicated a client error. the response data may contain a reason. // the body of the service's response, which is set up for mapping in the connector rule, was empty for this service call.
When I am checking this 405 error, it says I am trying to connect to wrong HTTP method. the http method is "PATCH" which works good during rest consume via App Studio
Can anyone please help me on this? PATCH has to work with Savable DPage otherwise I can't update the properties on resume case
HCA Healthcare
US
@SonalV The 405 error here is not really about the savable data page itself, it is about how the REST connector is being called at run time. The PATCH call that you test from App Studio goes to a DX API URL that accepts PATCH, but when you run the same savable data page from the case the actual request is slightly different, so the server treats PATCH as “not allowed” for that URL. Open the REST connector and check that the method is PATCH and that the endpoint URL and all path or query parameters are exactly the same as in the working App Studio test. Make sure the savable data page save plan uses that same connector and does not override the HTTP method in the data save options. Ask your infrastructure team to confirm that PATCH is allowed on the web server or load balancer for that DX API URL; if PATCH is blocked there you will always get 405 when calling from the case. If you cannot allow PATCH on the server, change the connector to use POST and add the header X-HTTP-Method-Override=PATCH so that DX API still handles it as an update. Also double-check that assignment ID and case ID parameters are not blank when the case calls the savable data page, because a wrong or empty URL can also cause 405. Once the URL, method, and headers are aligned between the connector, the savable data page, and the server, the PATCH call will work and the case will resume with the properties updated.