MapRequestData: The MapRequestData data transform rule provides the parameter(s) passed in the request API.

MapResponseData: The MapResponseData data transform maps the response received from the source system. The data received as JSON format is stored in Param. Response which is then mapped to appropriate object class in your application. In this example, the returned authorization information is mapped to Authorization data class using the MapToEntityWrapper data transform rule.

MapToEntityWrapper: MapToEntityWrapper accepts a single Page Name parameter called Integration Page. In this case the parameter will be the ‘Authorization’ page of type ‘PegaHC- Data-Authorization.

The data transform serves as a control point for making calls out to a series of three additional Data Transform rules that provide the core mapping functionality as well as the appropriate extensibility needed by customers:

MapToEntity: a single MapToEntity rule exists in @baseclass and this rule is overridden in each of the classes that need to supply their own definitions. In the new implementation ‘MapToEntity’ would exist in the ‘Int’ classes and have the corresponding mappings. In the current example, we have the ‘MapToEntity’ data transform in the ‘PegaHC-Int-Authorization’ class. It contains the mappings related the authorization object.

The ’MapToEntityWrapper’ paradigm will be extended to all the embedded pages/objects as well. In the example, the authorization JSON response has a ‘requester’ page with page definition ‘PegaHC-Int-AuthorizationRequester’. We intend to map this page to the ‘Requester’ page on the PFHC Authorization object. The ‘Requester’ page is set as the parameter to the ‘MapToEntityWrapper’, which in turn invokes the ‘MapToEntity’ in the ‘PegaHC-Int-AuthorizationRequester’ class.