LSA 7.3 - Exercise: Hotel Case is not resolving
Hi,
I was implementing the Hotel application according to the LSA 7.3 Exercise. It's seen that the Hotel case is not getting resolved from Hotel Proxy by REST api PUT. I see the Hotel Proxy case is resolved.
While tracing the api/v1/cases, the tracing happened up to GET service not PUT service. Is there anyway can I trace PUT service too. Any help will be greatly appreciated.
Maantic Inc
US
Hi,
If you are getting a 500 error, this could be one of the reasons. The actionID pyResolveAndCloseCase is basically a flow action which calls activity pxForceCaseClose. This activity needs a resolution status which is normally passed from the section that is rendered from that flow action. Alternatively when you run the activity manually, you pass the parameter. If the resolution status does not start with Resolved- the activity throws an error. Since you are invoking the flowaction from the put service there was no provision to pass that parameter.
To trace the service, you will need to open the service package and open the rest api and trace the particular api. Before tracing you might need to follow the below steps:
1) Run the Get service with your Hotel case key and copy the etag that is generated.
2) In the confirm rooms activity hard code the e tag that you receive and comment the get call
3) Submit the proxy case and trace the api rule. If you get an error of etag mismatch run step 1 again to check if the etag is same. If different, correct etag and run step 2.
Once you trace and identify the problem, you can take the below steps:
Hi,
If you are getting a 500 error, this could be one of the reasons. The actionID pyResolveAndCloseCase is basically a flow action which calls activity pxForceCaseClose. This activity needs a resolution status which is normally passed from the section that is rendered from that flow action. Alternatively when you run the activity manually, you pass the parameter. If the resolution status does not start with Resolved- the activity throws an error. Since you are invoking the flowaction from the put service there was no provision to pass that parameter.
To trace the service, you will need to open the service package and open the rest api and trace the particular api. Before tracing you might need to follow the below steps:
1) Run the Get service with your Hotel case key and copy the etag that is generated.
2) In the confirm rooms activity hard code the e tag that you receive and comment the get call
3) Submit the proxy case and trace the api rule. If you get an error of etag mismatch run step 1 again to check if the etag is same. If different, correct etag and run step 2.
Once you trace and identify the problem, you can take the below steps:
1) some comments say actionID should be in header and not in query string params but that does not work . So I put it in both places for now:
https://collaborate.pega.com/question/lsa-73-exercise-creating-rest-integration-interface
2) Customize pyResolveAndCloseCase flow action in your application and add a pre data transform.
