Skip to main content
LinkedIn
Copied!

Table of Contents

Specifying the context for inbound applications with the Inbound Call Center shape

Version:

Only available versions of this content are shown in the dropdown

The Inbound shape provides a means to specify the content that should be returned when an inbound application, such as Next-Best-Action Advisor (NBAA), requests this action to display within their application.

The following configuration options are available for this shape:

Name Purpose
Section Name of the Section rule to use. The content of this section is returned when an inbound application (such as NBAA) requests action content from the system.
Channel Inbound channel for the Treatment (Default value for this shape is CallCenter).
Work Status Status of the action after executing this step in the flow.
There should be only one Inbound shape in a flow. Having multiple Inbound shapes in the same flow could cause non-deterministic behavior in resolving the content that should be returned to the inbound application.

The Inbound shape, by itself, simply serves as a determining point for the content to be returned for external requests. However, this shape can be (and typically is) combined with the InboundTicket ticketing mechanism to provide a branch of flow execution for processing an inbound request. Refer to Branching the action flow based on the channel for more details.

Did you find this content helpful?

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.

Pega Community 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
Contact us