Skip to main content


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

Inbound Channel Processing

Updated on August 4, 2022

The Inbound Channel Processing strategy handles all inbound channel processing; a separate sub-strategy is called for each of Web, Mobile, Agent Assisted (Call Center or Retail), and Other (everything else).

Pega Customer Decision Hub
The InboundChannelProcessing strategy

The Process Web and Mobile Channel strategies

The Process Web Channel and Process Mobile Channel strategies are effectively identical. Each determines if the Channel treatment processing switch is on, and if so passes actions and treatment without alteration, otherwise the Apply Action Limits strategy is called to perform any channel specific filtering based on preset limits.

Note:

From version 8.5 onwards, Assign Treatment Placements processing has been moved to Final Action Limits And Bundling, and the extension strategies for implementing channel specific processing logic have been moved to Treatment Placements (within Final Action Limits And Bundling).

The Process Web Channel strategy is shown below.

Process Web Channel strategy

Assisted and Other Inbound Channel strategies

The Assisted Inbound Channel and Other Inbound Channel strategies follow the same pattern. Each calls the Apply Action Limits strategy to perform any channel specific filtering based on preset limits.

An extension point strategy called Assisted / Other Inbound Channel Extension is provided after action limits processing to allow for any additional processing for the channel.

The following example is for the Other channel.

AssistedOtherChannel strategy

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