SECTIONSNew Features and Enhancements in Revenue Management Summer 2023
The following new features have been introduced in the Summer 2023 release of Revenue Management.
If you are upgrading from a previous version, see Upgrading to Revenue Management Summer 2023. This provides a summary of the items that have been added for each feature and details of any required upgrade steps.
FinancialForce is Now Certinia
We have made the following changes to align with our new Certinia brand:
- The publisher name has been updated to Certinia
- Package names no longer reference FinancialForce
- In most cases, text referring to FinancialForce has been replaced with Certinia
For more information about these updates and related text changes, see the Package Name Updates article in the Certinia Community and the Technical Documentation Pack.
To learn more about our rebrand, visit the Certinia Community for a message from our CEO, Scott Brown.
Improved Discard Process
A new asynchronous Discard process allows you to discard larger recognition transactions individually, and up to 200 recognition transactions at once from the list view. The process runs in the background and notifies you when it is complete.
If you are upgrading to this version, you must enable the "Upgrade to Summer 2023" feature in Feature Console to use the new asynchronous Discard process. For more information, see Upgrading to Revenue Management Summer 2023 and Discarding Recognition Transactions.
Discard Transactions in Bulk via The discardAsync Method
Revenue Management's API has been updated to include the discardAsync method in the TransactionService. The discardAsync method accepts a list of IDs for "Committed" recognition transactions and discards them asynchronously.
The process stores log information via a Revenue Management background process record.
Asynchronous Processes Send Salesforce Notifications
Revenue Management's asynchronous processes (such as Discard and Generate Schedules) now send notifications to users via email and via Salesforce notifications. You can control which notification methods are used in your org by editing fields in the Revenue Management Notification Settings custom setting.
For more information, see Revenue Management Notification Settings.
Improved Support for Volumes in the Recognition Summary Grid
Improvements have been made to the Recognition Summary grid to support larger volumes. The benefits are that:
- The grid is no longer limited to summarizing 50,000 recognition schedule lines per period.
- More groupings (rows) can be displayed in the grid.
Automation Enhancements
The following enhancements have been made to Revenue Management's automation process.
Automation Configuration
The automation process now comprises enhanced configuration parameters within the Automate Processes window on the Revenue Recognition page.
Previously you could only select a process to start from and end at, and summarize transactions. You can now filter by specific companies, currencies (multi-currency orgs only), and recognition streams. When the Recognize Schedules process is included in the processes to run, you can also select the cutoff period for including schedule lines for recognition, and the period you want to commit recognized values into. This gives you more control when using the end-to-end process to recognize scheduled revenue and cost.
For more information, see Automate Processes Fields.
Automation configurations have been added to this version of Revenue Management. With this new feature, you can:
- Configure the automation process to run now.
- Configure the automation process to run at a later date.
- Run the automation process from a saved configuration.
For information about how to use automation configurations, see Using the Revenue Management Automation.
Previously you could only run the automation process as a one-off. Saving configurations provides consistency for running the automation process repeatedly, for example, at monthly intervals. For more information, see Automation Configuration Overview.
Enhancements to the Automation API
When running the automation via the API, you can now filter by recognition stream in addition to filtering by company and currency.
New input parameters also allow you to specify the cutoff period for selecting schedule lines for recognition, and the period into which recognized values are committed.
For more information, see Running the Automation via the API.
Change to the Summarize Transactions Process When Run via the Automation
The Summarize Transactions process that you can run via the automation process summarizes a recognition transaction if it meets all the following criteria:
- The transaction was created by the Recognize Schedules process.
- The transaction's status is "Committed".
- The transaction is not already summarized.
The additional criteria that a recognition transaction's Recognized Date had to be within the last 30 days has been removed.
For more information about which processes you can automate, see End-to-End Automation of Recognition Schedule Processes.
Recognize Schedules Process Not Blocked by "In Progress" Transactions
In earlier releases the Recognize Schedules process could not run if there were "In Progress" recognition transactions. This restriction has been removed which means you can now run multiple Recognize Schedules processes in parallel provided that they do not clash with any "In Progress" recognition transactions. For example, this allows you to run multiple Recognize Schedules processes for separate companies simultaneously instead of having to wait for one company's process to finish before you start the next one.
For more information about running the Recognize Schedules process, see Recognizing Revenue and Cost against Recognition Schedules.
Deferred Revenue True-Up Not Blocked When Recognizing against Recognition Schedules
You can now run deferred revenue true-up when the "Recognize against Revenue Schedules" feature is enabled in Feature Console. This was not supported in earlier releases.
For more information, see Running Deferred Revenue True-Up.
Lightning Page Assignments for Recognition Schedule Objects
Revenue Management's "Lightning Page Assignments" feature in Feature Console has been updated to include assignments for the Recognition Schedule and Recognition Schedule Line objects.
- If you are configuring a new installation of Revenue Management, enable this feature to assign the packaged Lightning pages as org defaults for all Revenue Management objects.
- If you are upgrading to this version of Revenue Management, re-run the feature to assign the packaged Lightning pages as org defaults for the Recognition Schedule and Recognition Schedule Line objects.
For more information, see Revenue Management Lightning Page Assignments.
Guidance on How to Display Recognition Information on Primary Source Records
We have provided information about how you can display values such as total revenue, and total revenue recognized to date, on your primary source records.
This is explained in Displaying Recognition Information on Primary Source Records.
Release Content
We want to help you find all of the information and help that you need to be productive with our products.
Certinia Trailhead
If you want to learn more about the new features in this release, see the ERP Cloud - Summer 2023 Release Highlights Trailhead module. This module will guide you through the new features in Foundations.
In-App Guidance
Certinia In-App Guidance uses Salesforce user engagement features to deliver Certinia content, such as tutorials, and walkthroughs directly from our products.
In this release, we've updated several in-app guidance prompts. For a full list of the updates, see New Features and Enhancements in In-App Guidance Summer 2023.
If you are upgrading from a previous version, see Upgrading to In-App Guidance Summer 2023. This provides a summary of the items that have been added for each feature and details of any required upgrade steps.
Fixes
Fixes are listed on the Known Issues page of the Certinia Community. You can access this page from the Community Support Hub. For a brief description of the issues that have been fixed in this version of Revenue Management, see the relevant section of the Known Issues page.