Spring 25 Release Notes

Assigning Unique Names When Multiple Rules Share State, Statute/Bill, and Drug Type

As a suggested good practice, it is highly recommended to assign a unique name to the Statute/Bill column when creating multiple rules for the same State, Statute/Bill, and Drug Type. This practice becomes particularly useful when the rules have different parameters (e.g., Threshold, Effective Date, Template’s submission type, etc.). A unique name enhances the clarity and readability of the rules, making it easier to manage and distinguish between them.

Example: For a Statute/Bill HB2658, if you have multiple rules with different parameters, using a unique name such as HB2658-Annual can make it much easier to identify the specific rule at a glance. 

Ability to Add the Current Price and Previous Price Fields in the Disclosure Output

A new field set, DisclosureFields, has been added to the Disclosure Output Object MnLegislationReportOutput__c. This field set contains the following fields:

• CurrentPrice__c: Represents the current price of the Product SKU.
• PreviousPrice__c: Represents the previous price of the Product SKU.

This field set allows flexibility for users to choose and display these fields as needed in their reports. By default, these fields are not visible to users. Administrators must manually add fields to the field set to display them. The Disclosure page automatically reflects the fields after the layout is saved and the page is refreshed.

Note: No price-related fields are displayed for FDA disclosures as there is no pricing data is included for an FDA event.

Fixing SPTM Start/End Date Issues from Time Zone Differences

For SPTM customers experiencing start and end date alignment issues, prices will be updated based on the respective country's time zone to ensure accurate date and time values.

Ensure that the Start Date GMT (StartDateGMT__c) and End Date GMT (EndDateGMT__c)fields in the Master Prices Object (MnPrice2__c) are correctly populated with GMT time zone (For SPTM Customers Only).

A pseudo update must be performed on all records to apply the necessary corrections. This update runs the same logic used during data insertion to fix the data.

The SkipTimezoneInPrice custom setting must be set to Falsefor any manual uploads to ensure dates are converted correctly during the pseudo update and for any future data uploads. This setting is crucial for maintaining proper date and time alignment.

GPM Setup--> Custom Settings-->SkipTimezoneInPrice-->False

For more information, refer to Ensuring Accurate and Consistent Pricing Data Across Time Zones in Administration.

Introducing the Percentage Change Field in Disclosure Output

The field set Disclosure Fields includes a new formula field, Percentage Change, in the Disclosure Output Object.

This field calculates the percentage difference between the current price and the proposed price, providing users with greater transparency and flexibility in tracking price adjustments.

For more information, refer to the following topics:

• Introducing the Percentage Change Field in Disclosure Output in Using State Price Transparency Management.
• Setting up and Modifying Fields in the Disclosure Output in Administration.

Max Non-Reportable Price Tab: Dynamic Labeling and Data Display

When there is no data in the Max Non-Reportable Price tab. The previous label "No data available" has been updated to "Any price increase will generate reporting requirements. There is no max non reportable price or percent change found.".

This label can be modified by the admin if needed.

User Preference-Based Page Size Retention in Price Compliance

Users can choose how many records they see per page (pagination) in the "Price Compliance" tabs for both PCR (Price Change Request) and Events, allowing them to retain their preferred pagination settings. However, large SKU lists continue to follow the existing behavior of displaying only one rule.

The available page size options are 5, 10, 15, and 20.

For Example:

• When a user selects a value (for example, 15 records per page), it gets saved as user preference.
  

• The next time they open the Price Compliance tab; it will default to the last selected page size (15).
  

Note: If there are too many SKUs (above 150), the system only displays one rule per page to prevent performance issues. This behavior remains unchanged and is separate from the new page size setting.

Pop-Up Message When Setup Configuration Is Clicked for Health Check

A streamlined setup confirmation process has been introduced without modifying existing functionalities. This process is designed for the SPTM Health Check Setup to enhance new customer onboarding.
The system now includes a setup confirmation option for the SPTM Health Check, simplifying new customer onboarding with a one-click metadata copy process for the SPTM module.
A confirmation message is displayed to inform users about the affected Custom Settings. When the Setup Configuration button is clicked, the following message is displayed:

For more information, refer to Displaying a Pop-up Message on Setup Configuration Click in Health Check in Administration.

Auto-Saving of Disclosure Data

The system automatically saves the price compliance data when a PCR is submitted or resubmitted, provided no prior disclosures exist. This implementation ensures that the price compliance is saved automatically if there is some reporting to be done.

• If a PCR is in draft status, price compliance data is not saved.
• Upon submission of the PCR, the system auto-saves the price compliance data.

Key Points:

• Draft PCR: Price compliance data is not saved.
• PCR Submission: Auto-saves price compliance data.
• MPCR Submission: Auto-saves price compliance data.
• MPCR Recall and resubmission- Deletes and re-saves the price compliance data.
• PCR Submission with Positive Price: Auto-saves disclosure data.
• PCR Resubmission with Negative Price: Clears disclosure data.
• PCR Recall & Resubmission After Reports Created: No automation; manual regeneration required.

For more information, refer to Auto-Saving of Disclosure Data in Using State Price Transparency Management.

Email Notifications for Manually Created Disclosures

An automated email notification is triggered to Disclosure Owners upon saving a disclosure. The email contains a link that navigates the user to the disclosure page.

Custom Label Changes in Spring '25

Several custom labels have been either updated or deprecated to support product enhancements, improve UI consistency, and enhance the overall user experience.

To help track changes across environments, these updates are documented in two sections:

• Updated Custom Labels
• Deleted Custom Labels

For more information, refer to Custom Label Changes in Spring '25.