Skip to main content


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

Modifying call treatment rules

Updated on September 11, 2020

To review and modify the Call Treatment rules from the Pega Call administration landing page, perform the following steps.

  1. In the header of Dev Studio, click Configure Channel ServicesPega CallAdministration & Configuration.

  2. Click the Call Treatment tab to display a list of call treatment rules, along with the specific circumstance, class, and ruleset version they apply to.

    The landing page displays only the call treatment that are rules applicable to offering events. Pega Call includes several call treatment rules that you can use as starting points. The rules are named for the CTI events that trigger processing. Modify the offering call treatment rules.
  3. To review or modify configuration details associated with a particular call treatment, click Details for the rule.

  4. To modify the rule, copy it to your application ruleset and then modify it to suit your needs.

    Make sure that the service package that processes CTI events (CTILinkEvent for local CTI links, CTILinkRemoteEvent for remote CTI links) has access to your ruleset.

    Note: As of release 8.2, remote links are deprecated and supported only for legacy implementations.

    Ensure that the service packages that processes CTI events (CTIAACCLINKEVENT1 thru CTIAACCLINKEVENT10) have access to your ruleset.

    You can circumstance the offering rule to vary call treatment based on a property (for example, pyCallType). A circumstanced rule is included for consultation and transferred calls (pyCallType=CONSULT).

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us