CPQ Presenter action types

Introduction

The CPQ Presenter Integrator introduces a new action type called Form, enabling presenters to render actions based on specified render modes. This feature facilitates seamless form-based interactions within the CPQ ecosystem, ensuring backward compatibility while maintaining independence between pricing plan forms and action forms.

Actions primarily facilitate subscription management and are rendered as additional functionalities according to specified render modes. These actions enable the operation and management of available subscriptions, allowing AppXite system to communicate with vendor services through specific actions, URLs, and APIs

The Form Actions feature is essential for enhancing subscriptions by enabling the configuration of specific actions within the CPQ Presenter. This feature aims to address CPQ designer limitations.

In this article:

• Key Features
• Action Type as Form
• Action Type as Form with Text Design & Action Button
• Form Example with Action Button to send data to external services
• Form Action as Redirect

Key Features

• New Form Action Type: Introducing a new "Form" action type with specific field considerations for enhanced customization.
• Show as Popup: Enabling a user-friendly interaction by rendering the form as a popup for seamless engagement.
• Backward Compatibility: Ensuring continued support for legacy pricing plans that do not include enabled form actions, maintaining a smooth user experience.
• Independent Form Rendering: Action forms are designed to operate independently from pricing plan forms, while still utilizing the available form values for flexibility.
• State Management Collaboration: Efficiently managing state across different sections while keeping the Pricing Plan Designer and Action Form Designer isolated for better organization.
• Front-End Validations: Implementing robust front-end validation mechanisms to ensure form actions are processed correctly and error-free.
• Existing and New Offers": For existing offers, form action functionality is hidden by default, while for new offers, it is enabled by default for better usability.
• Limitations: There are no restrictions on the number of actions that can be added to a product, providing full flexibility.

Enabling Form Actions Functionality:

To enable Form Actions on existing offers, the "Enable form actions" option should be ticked on Design tab (bottom of the right-side pane):

Action Type as Form:

• Allows adding all functionalities from the Standard Design Section to the Form Action Designer.
• Requires an Action Button for each form to send data to external services.
• Key mandatory fields include Tooltip, Label, and Icon properties for proper UI consistency.

Action Type as Form with Text Design & Action Button added:

Form Example with Action Button to send data to external services:

Form Actions as redirect:

• Form actions can be configured as redirect actions, enabling various redirection options:
  Open the linked document in a new window.
  Include query parameters for dynamic data transfer.
  Specify the URL destination (e.g., https://google.com or any vendor-defined URL).

Summary

The Form Action Type significantly enhances CPQ by introducing a structured mechanism for executing form-based actions. This approach ensures seamless data flow, subscription awareness, and authentication compliance, making it easier for users to interact with external services.

By clearly distinguishing between pricing plan forms and action forms, CPQ provides a flexible yet structured solution for integrating vendor-specific actions into the subscription ecosystem.