Skip to main content

Modifying the harness layout in the UMCareMgrWAGadget rule section

Suggest edit Updated on August 27, 2021

If you previously customized the UMCareMgrWAGadget rule, you need to modify the harness layout of the rule section so that you can view Pega Knowledge articles in the CM Care Manager portal.

  1. Log in to your application by using the credentials that you previously established.
  2. To check whether you customized the UMCareMgrWAGadget rule, follow these steps:
    1. In the navigation pane of Dev Studio, click RecordsUser InterfaceSection.
    2. On the Instances of Section page, in the Purpose column, click the Filter icon to filter the results and enter UMCareMgrWAGadget in the Search Text field.
    In the results, if the name in the RuleSet:Version column displays a ruleset name from your implementation layer, it means that you customized the rule and you need to complete the remaining steps in the procedure.

    If the ruleset name is not the name of your implementation rule, you have not customized the rule and you can skip the remaining steps.

  3. In the RuleSet:Version column, double-click the name of the customized rule.
  4. On the Section page, click to the right of the Dynamic Container - Include Harness field to view the icons, and then click the View properties icon to open it.
  5. In the Layout Properties dialog box, select the Render as Single Page check box.
  6. Click Submit.
  7. Click Save.
  8. Check in the rule.
What to do next: Check other rules to ensure that you can view Pega Knowledge articles in the CM Care Manager portal. For additional information, see Adding a script file to the harness of customized rules.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us