Mapping service requests and properties between Theme UI-Kit and Constellation applications
When enabling coexistence, it is crucial to understand how to map data between the remote Theme UI-Kit and local Constellation applications. The following topic guides you through the process of mapping data between the applications to allow for processing a Theme UI-Kit service request in a Constellation portal.
Log in to the local Constellation application as an administrator and open Dev Studio. In the header of Dev Studio, search for and open the cySetMashUpGadgetAttributes data transform. When the interaction is created in the Constellation application, all the details related to it will be stored in the local proxy case. To propagate those interaction details back into the Theme UI-Kit application, you need to update the data transform with the required source and target properties.
Pega Customer Service application comes with the out of the box mapping of ContactID and ServiceAccountID properties. Steps 8 and 9 of the data transform contain the mapping, with the pySourcePropertyName value corresponding to the remote Theme UI-Kit application property and the pyTargetPropertyName value corresponding to its local Constellation application counterpart.
Now, map one more property between the systems, ContactName. In the Definition tab of the data transform, right-click row 9 and select Copy. Right-click the same row again and paste the copied step below. Now, update the newly added row with the .pySourcePropertyName Theme UI-Kit application property value and the .pyTargetPropertyName Constellation application property value. Click Save.
Now, log into the remote Theme UI-Kit application. To allow for the interaction context details to be stored back into the remote Theme UI-Kit service request, configure the cyMapMashUpAttributes data transform. In the header of Dev Studio, search for and open the cyMapMashUpAttributes data transform and then override it in the implementation application layer class. Since the ContactID and AccountNumber properties are mapped out of the box, add the remaining Name property to the data transform. Click the Add button and enter the following values to the new row in the definition table:
Now, setup the initialization properties required when the case is created in the Theme UI-Kit application. In the header of Dev Studio, search for and open the cyRequestToCreateProxyCase data transform and ensure that the required properties are listed in the Definition tab.
Next, set up the reporting case details update from Theme UI-Kit to the Constellation proxy case. In the header of Dev Studio, search for and open the cyRequestToUpdateProxyCase data transform and ensure that the required properties are listed in the Definition tab.
Log out of the remote application and log back into the Constellation application. In the header of Dev Studio, search for and open the AllowedStartingFields data transform. Ensure that the properties that you listed in the cyRequestToCreateProxyCase data transform are added to the Definition table.
Lastly, open the Change plan proxy case type and update the Edit view with a set of remote fields. Click Case types > Change plan. On the Change plan tab, select the UX tab. In the configuration panel, click the Other Views tab. In the Form section, click Edit. In the Edit View panel, in the Fields section, click Add. Select Views > Update remote fields on proxy.
You have reached the end of this video.