Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Adding a script file to the harness of customized rules

Updated on January 20, 2022

To have Pega Knowledge work properly in the CM Care Manager portal, if you customized certain harness rules, you need to add a script file to the harness of each customized rule.

Review all the rules in this table and follow the steps in the procedure if necessary.

Rule nameClass
  1. To check whether you customized the specified harness rules, follow these steps:
    1. In the navigation pane of Dev Studio, click RecordsUser InterfaceHarness.
    2. On the Instances of Harness page, in the Purpose column, click the Filter icon to filter the results and enter one of the harness rule names in the Search Text field.
      For example: Confirm
    3. In the Applies To column, locate the row with the class name of the rule that you are checking.
      For example: PegaHC-AG-Work-Appeal
    If the name in the RuleSet:Version column displays a ruleset name from your implementation layer, it means that you have 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.

  2. Click the rule name, such as Confirm.
  3. Check out the rule.
  4. On the Scripts & styles tab, in the Scripts section, click the Add a row icon.
  5. In the Name list, enter and select pega_CMA_EventManager.
  6. Click Save.
  7. Check in the rule.
  8. Repeat these steps for each rule that is listed in the table above.
  • Previous topic Modifying the harness layout in the UMCareMgrWAGadget rule section
  • Next topic Modifying the AddObservation and NewAllergyDetails section rules

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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