Learn about new and enhanced features in Zilliant's Summer 2025 release.
Zilliant Revenue Suite
Summer 2025 updates focus on flexibility, streamlined workflows, and embedded insights.
This release includes important security enhancements. Zilliant recommends you review these security upgrades immediately. To prevent integration issues, apply the upgrades as soon as they are released, in test and production environments.
CPQ user interface upgrade (Beta)
The Beta release of our enhanced UI experience continues to improve our UI framework with several visual, configuration, and interaction-level enhancements.
Key updates that support a more consistent and intuitive experience include:
Customizable record creation dialogs
Quote and agreement creation dialogs now support improved usability with field customization. Add standard and custom fields, control field visibility and order, and apply localization selections.
Customizable tabs in record detail views
You can now reorder and hide standard tabs, and add custom tabs in object record detail views. This makes it easier to organize and present business-specific data, such as invoicing or billing information, separately from core system data.
UI and UX enhancements
Several visual and interaction-level improvements align with the latest design standards, resulting in a more consistent and streamlined experience across key modules.
The Beta version of the enhanced UI experience is intended for early adopters. Keep in mind:
You may encounter bugs or limitations.
Some features may be incomplete or change in future releases.
Product documentation may not reflect the new UI experience.
You can easily switch between the new and classic user interfaces.
Sales agreements management
This release includes enhancements that enable you to more efficiently manage sales agreements.
Mass edit for line item tables
We’re introducing a powerful new enhancement to the CPQ Line Item table: customizable mass edit. Users with UI customization permissions can now enable mass edit support for any editable column in the Quote or Agreement Line Item tables.
When configured, Sales Reps can select multiple line items, launch the Mass Edit dialog, and apply changes to all selected line items in a single step.
This feature significantly streamlines bulk updates, enhancing user efficiency and reducing repetitive data entry. Admins can fine-tune which attributes are mass edit-enabled to ensure the feature is targeted and relevant to each business workflow.
Watch to learn more.
Sales agreements default currency
When you create a sales agreement, the currency type is now automatically selected based on a set of priorities, considering user preferences, account settings, and system defaults. The default logic depends on whether you have selected an account or enabled sales data determination.
|
|
|
|
|
---|---|---|---|---|
No account is selected | User-preferred currency | System default currency | ||
Account is selected but Sales Data Determination is not selected | Account currency | User-preferred currency | System default currency | |
Account and Sales Data Determination are selected | Sales data determination currency | Account currency | User-preferred currency | System default currency |
You can manually override the currency selection if allowed by configuration or profile rules.
Sales agreements default date range
When you create an agreement, Start Date now defaults to the next day’s date. End Date is set based on the duration you configure, such as 365 days. When editing either date, the system helps maintain valid ranges to prevent inconsistencies.
Sales agreements in account and opportunity views
We added Agreements (Negotiation) and Agreements (Published) tabs to the Account and Opportunity detail pages. These tabs display related agreements and allow you to view, filter, create, and delete records from a single context.
Multiple reports at each launch point
Embedded visual analytics now supports multiple reports at each launch point, displayed in a tabbed layout. This allows you to easily switch between related insights within a single context.
Important
If you embedded analytics reports before the Summer 2025 release, you must reconfigure them to align with the updates:
The Destination Name field should now contain a custom system name for the report instead of the UI location.
Add the following required parameters in the Additional Properties section:
LaunchPoint
Title
Sequence
For details, read our updated product documentation.
SSC upgrade
We fully refactored SSC integration to align with the latest released version, SAP SSC 3.3. This update ensures compatibility, improved stability, and support for the most recent SAP SSC capabilities.
Performance improvements
We improved the database performance through normalization of table indexes and refactoring of key queries. These changes enhance system responsiveness and support faster data operations across core workflows.
Security enhancements
This release includes security fixes to improve system stability and ensure continued compliance with internal security standards.
Zilliant recommends you apply validation and configuration updates immediately—in test and production environments—to prevent integration issues.
Customizable login method restrictions
Administrators can now control platform access by restricting login methods, such as UI, API, or SSO, for each user or through mass user updates. This allows for more flexible and secure access management. By default, no users are restricted unless explicitly configured.
Enhanced web application security headers
We added new HTTP security headers to strengthen browser-side protections against threats such as cross-site scripting (XSS), MIME-type sniffing, clickjacking, and insecure content delivery.
Customers using cross-origin integrations (such as C4C, Salesforce embedding through iframe, or API calls from external domains) must update the application.properties
file with the correct cross-origin resource sharing (CORS) and frame-ancestors settings. If not configured:
iframe embedding will be fully disabled (frame-ancestors
none
)External domains will be blocked from sending cross-origin requests, disabling CORS
Example configuration
app.allowed-origins=https://trusted.com,https://partner.example.com