CPQ Presenter – Form action types

Introduction

This article explains how Form actions work in the CPQ Presenter, what action types are available, and how to configure them. It covers the setup of form-based actions, redirect actions, and the use of draggable Form Action buttons — giving Vendors full control over subscription management workflows presented to customers.

In this article:

Key features

Form actions enable Vendors to attach structured, form-based interactions to subscriptions inside the CPQ Presenter. These actions communicate with Vendor services through specific actions, URLs, and APIs, and are rendered as additional controls within the subscription flow according to specified render modes.

• New Form action type — a dedicated action type with specific field considerations for enhanced customization.
• Show as popup — the form renders as a popup for seamless user engagement.
• Backward compatibility — legacy pricing plans without enabled form actions continue to work without changes.
• Independent form rendering — action forms operate independently from pricing plan forms while still using available form values.
• State management — the Pricing Plan Designer and Form Action Designer are isolated for better organization.
• Front-end validations — form actions are validated client-side before processing.
• Draggable Form Action button — the Form Action button can be positioned freely within the form panel, consistent with all other controls.
• No limit on actions — there is no restriction on the number of actions that can be added to a product.

Enabling Form actions on existing offers

To enable Form actions on an existing offer, open the offer in the CPQ Presenter, navigate to the Design tab, and scroll to the bottom of the right-side properties pane. Check the Enable form actions option.

Action type: Form

When the action type is set to Form, the Actions tab in the CPQ Presenter exposes the same controls available in the standard Design section. This allows you to build fully custom form layouts for each action.

Key requirements for this action type:

• Each form requires at least one Action Button to submit data to external services.
• The Tooltip, Label, and Icon fields are mandatory for consistent UI appearance.

Action type: Form with text design and Action Button

Once you have added text fields and an Action Button to the form layout, the Actions tab reflects the complete design. The Action Button is configured with an action name that maps to the external service endpoint (for example, add-company-info).

Additional options available in the Action Button properties:

• Specific custom Platform Integration route — routes the action to a custom integration endpoint.
• Configure integration — opens further integration settings for the action.

Form action as redirect

Form actions can also be configured as redirect actions. Instead of submitting form data to an API, the action navigates the user to a specified URL. Available redirect options:

• Open the linked document in a new window.
• Include query parameters for dynamic data transfer.
• Specify any URL destination (for example, a Vendor-defined provisioning portal).

To configure a redirect action, set the Action type to Redirect in the Configure section of the properties pane, then enter the target Redirect link.

Result of this configuration in the Offer page overview:

Draggable Form Action button

All controls in the CPQ Presenter form designer are draggable — they can be placed freely within panels to create the desired layout. The Form Action button follows the same behaviour: the Form Action button can be dragged to any position within the form panel, just like any other control.

To reposition a Form Action button:

1. Open the offer in the CPQ Presenter and navigate to the Actions tab.
2. Locate the Form Action button in the form layout.
3. Drag it to the desired position within the panel using the drag handle.
4. Select Save plan to confirm the new layout.

Customer view – Offer page

Once a Vendor has configured Form actions on an Offer, Customers see the resulting buttons directly on the Offer page. Each configured action appears as a distinct button that triggers the corresponding form or redirect.

The example below shows an Offer with three configured actions visible to the customer: Create customer account, Create Workspace Identity, and Update Domain. The highlighted Create Customer Account button in the lower-right corner is a Form Action rendered in the Customer View.

Summary

Form actions in the CPQ Presenter give Vendors a structured way to attach subscription management workflows directly to offers. Using the Form action type, a Vendor can build custom input forms and wire them to external services via an Action Button. Using the Redirect action type, a Vendor can send customers to any URL with optional query parameters.

The Form Action button is now fully draggable within the form panel, consistent with all other controls in the designer. This gives Vendors complete control over the layout of actions on the Customer Offer page.