Skip to main content

Release 25.05.01 - Problem Solver, Revenue Cloud Metadata, Deployment Status Transparency, Deleted Custom Fields, Work Item Submission Bug Fixes

Release 25.05.01 - Problem Solver, Revenue Cloud Metadata, Deployment Status Transparency and Bug Fixes

T
Written by Tam Tran
Updated over 2 weeks ago

Problem Solver

Deployment errors can be time-consuming to troubleshoot. That’s why we’re launching Problem Solver — to help teams resolve errors faster.

With Problem Solver, you can:

  • Get in-app suggestions for common errors

  • Take direct action within the app

  • Identify missing components

  • Add missing items with one click

You’ll see an updated deployment results view that now includes in-app suggested resolutions, like the example below.

For certain error types, you can take corrective actions directly beside the errors, as shown below.


You can also add all suggested components with a single click., as shown below.

Note that this is the initial release of Problem Solver, powered by a new engine that analyzes errors and injects suggested actions into the app. Currently, it supports a limited set of errors and actions. We’re actively working to expand coverage for both suggestions and actions in the subsequent releases.


New Revenue Cloud Metadata

Support has been added for the following Revenue Cloud metadata types:

  • Product Specification Type

  • Product Specification Record Type

  • Pricing Action Parameters

Deployment Status Transparency

Many customers have asked for better visibility into deployment status, especially for longer-running deployments. We’ve added a new status section (shown below) that shows when processing is complete on our end and pending on Salesforce. This helps customers identify which system to check when deployments take longer than expected.

Bug Fixes

Deleted Custom Fields

Our customers have previously reported cases where some custom fields were incorrectly shown in the component list even though they were soft-deleted. This caused confusion since customers might mistakenly deploy deleted fields. This has been fixed, and soft-deleted fields are no longer listed in the app.

Work Item Submission

We've fixed an issue where users couldn't submit a work item for approval if its starting environment was changed after reaching the second stage. With this release, users can now submit work items for approval regardless of any environment changes.

Did this answer your question?