Setting up the local Constellation application and service request
This demonstration shows you how to configure you Pega Customer Service™ Constellation local application to enable processing and launching of the remote Theme UI-Kit-based service request, as well as how to create a local case type for the remote Theme UI-Kit Change plan service request. The local service request type acts as a proxy for the remote service request, exposing it to the CSRs in the Constellation application.
To enable the coexistence of Theme UI-Kit service requests is the Constellation application, you need to turn on the EnableCoexistence toggle in both the remote Theme UI-Kit application and the local Coexistence application.
In the header of Dev Studio, click Configure > System > Release > Toggles. On the Toggle Management tab, set the status of the EnablemeCoexistence toggle with the Application context of CustomerService-Infrastructure to ON .
To properly configure the connection between the remote Theme UI-Kit application and the local Constellation application, make sure the same operator is configured in both applications.
Log in to the local Constellation application as an administrator. Create a local case type for the Change plan remote Theme UI-Kit service request to allow CSRs to process it in the Interaction Portal or the Back Office Portal. The local case type acts as a proxy for the remote case, exposing it to the CSRs in the Constellation application.
In the navigation pane of App Studio, click Case types, and then click New.
In the Case type name field, enter Change plan. Expand the Case template section, and then, in the Template list, select Customer Service Remote Template.
Expand the Advanced section, and then, in the Reuse assets from list, select Service case template. Selecting this value ensures that Pega Customer Service adds the new local case type to the Service-Work hierarchy or its corresponding implementation class. Click Next.
Now, connect your local Constellation application to the Web mashup channel that you set up in your remote Theme UI-Kit application and configure the authentication.
Click the Switch Studio drop-down and select Dev Studio. In the navigation pane of Dev Studio, click Records > Data Model > Data Transform. In the Data Transform Instances tab, search for and open the cySetMashUpGadgetAttributes data transform and save it in the same class as the newly created Change plan proxy case.
Now, populate the following rows in the data transform definition table with the values from the Web mashup code from the remote Theme UI-Kit application:
- For the Target value of pyClassName, enter the Source value of the
classnameelement from the Web mashup code.
- For the Target value of cxMashUpChannelID, enter the Source value of the
channelIDelement from the Web mashup code.
- For the Target value of cxRemoteAppSkinName, enter the Source value of the
pzSkinNameelement from the Web mashup code.
Click Save. Log out of the Constellation application.
Now, you need to reference the proxy case type class in the decision table of the remote Theme UI-Kit application.
Log into the remote Theme UI-Kit application. In the header of Dev Studio, search for and open the cySetCaseTypesToUpdateProxyCase decision table. In the Table tab, in the Case type class column, enter the case type class of the Theme UI-Kit service request: PegaCA-Work-ChangePlan. In the Return column, enter the corresponding Constellation application proxy case class: Service-Work-ChangePlan. Click Save as and override the decision table in the implementation application ruleset.
Now, search for and open the cyProxyRemoteEndPointURL application setting rule. Save the rule into the implementation ruleset and update the Value for each of the Production Levels to the URL of the Theme UI-Kit implementation application.
Log out of the application. You have reached the end of this video.