Question
TATA CONSULTANCY SERVICES
US
Last activity: 23 Nov 2019 6:07 EST
Promoting Reuse exercise, Hotel Proxy case ID is wrong
I downloaded the exercise product, but still many things are not working.
- Hotel Proxy case id prefix supposed to be HPROXY- and i made sure that is mentioned in the application for the proxy case type. Still from REST POST, response C- prefix is getting created with class of Pega-API-CaseManagement-Case insteaf of PROXY class.
- Another problems with product zips, when installed Hotel application, there are 6 records from FSI-Data-Hotel which are failing.
- After proxy case created, parent case of Hotel- is not getting resolved. How to specially add optional action of Resolve Case. Added screenshotes for reference of flow.
Pegasystems Inc.
US
You are referring to the App Build exam starting point application, not the solution in the 7.3/4 LSA course. The goal of the starting point application was to add unit tests, etc., to eliminate warnings. Warnings created within the App Build would be easier to identify. The App Build does not grade based on warnings being eliminated but like any application, severe warnings should be heeded.
The starting point application wanted to improve the implementation of the Hotel Proxy case to show that it can and should be maintained separately. A separate Hotel Proxy application was created that is built on Hotel. Unfortunately the Pega API Service Package's Access Group was not changed from Hotel to HotelProxy as you noted.
Fixing this issue should address most of the problems you observed such as the HotelProxy case's prefix defaulting to C- as opposed to the prefix defined in the HotelProxy application, HPROXY-.
The pxObjClass for the POST response is fine. The "ID" property in the response is defined in the Pega-API class. A step page with a Pega-API applies-to class can call a generic @baseclass JSON Data Transform named "AutoMapAll". As the name implies, the Data Transform would map every JSON attribute in the received text to the DT's step page using putString(). After that, properties in that Pega-API step page can be mapped wherever you want.