Skip to main content

Setting up the remote Theme UI Kit application and service request

Learn how to configure the remote service request in the Constellation application so that Pega Customer Service™ can make that service request available from the Interaction Portal of the Theme UI-Kit application.

Note: The following demonstration uses the Change plan service request workflow and properties as an example to illustrate the configuration procedure.


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 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.


Create the Web mashup channel in the remote Theme UI-Kit application. With this channel, you can display remote case types in the Interaction Portal or Back Office Portal of the local Constellation application.

Log in to App Studio. In the navigation pane of App Studio, click Channels. In the Create new channel interface section, click Web mashup. In the Name field, enter Change plan. In the Action list, select Create a new case. In the Case type list, select Change plan. Click the Allow passing dynamic parameters toggle to enable it. Click Save. Now, click the Back to previous page arrow to go back to the Channels page. In the Current channel interfaces section, click the Change plan channel icon to re-open the channel.

Click Generate mashup code.

Copy the Web mashup code to a file so that you can access it later, when you configure the cySetMashUpGadgetAttributes data transform in the local application. Configuring the data transform with the values from the mashup code allows you to display the Change plan service request type in the Constellation application.

Close the Show Web Mashup Code Snippet window.

Now, add the PegaCS-C11NConnector ruleset to the implementation application stack. Click the Switch Studio drop-down and select Dev Studio. In the header of Dev Studio, click Application > Definition. In the Application rulesets section, click Add ruleset. In the Open Rule field, enter PegaCS-C11NConnector:08-23. Click Save.

Now, verify if the newly added ruleset is listed under System Runtime Context. In the header of Dev Studio, click Configure > System > General > System Runtime Context. In the System Runtime Context tab, click Resolved rulesets. In the Resolved rulesets dialog box, ensure that the PegaCS-C11NConnector ruleset is displayed.

Note: If your implementation application includes custom harness rules, it is essential to override all of the harness rules which are used when a given service request is launched in the Constellation application. To do this, use the harness rules available in the PegaCS-C11NConnector ruleset and save them into your implementation application class.

In order to customize the display of other rules within the Constellation application, you can utilize the ChannelType circumstance template along with the WebMashUpChannel definition.

If the implementation work class is not inherited from PegaCA-Work, add the czMapMashUpAttributes data transform to the pyDefault data transform and OpenDefaults activity rules of the implementation work class. Then, enable the parameters checkbox for the added data transform and move the czCreateUpdateProxyCase declare trigger rule to the implementation work class.

Now, you need to configure a unified work list and workbasket for the remote service request type. Search for and open the cyRemoteAppEndpointUrl application settings 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.

Note: For Non-SSO login, use the value of Application URL alias in the Theme UI-Kit implementation application definition. For example:
For SSO login, append the value of Application URL alias in the Theme UI-Kit implementation application definition with the authentication service name. For example:

Click Save.

Next, you need to configure the remote cases to display in the local application widgets with the correct case ID from the remote application. To do so, override a set of report definitions into the work pool class of the implementation application:

  1. cyMyWorkListForRemote
  2. cyMyWorkbasketsForRemote
  3. cyMyTeamWorklistForRemote
    Note: If you need to include additional columns to the worklist or workbasket, use the extension data transform rules provided in the following data pages: D_MyWorkListForRemote, D_MyWorkbasketsForRemote, D_MyTeamWorklistForRemote.

Log out of the application.

You have reached the end of this video.

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice