Skip to main content
All CollectionsRelease Notes
Release 24.10.02--Upgraded to API version 62, New components, Approval Process Improvements
Release 24.10.02--Upgraded to API version 62, New components, Approval Process Improvements

Metadata API version, OmniStudio, new metadata components, Approval, Azure, Diff View, Refresh, Pipeline, Deploy Options, History, Clone

Do Quoc Dat avatar
Written by Do Quoc Dat
Updated over a month ago

Salesforce Metadata API Update

  • Upgraded to Salesforce Metadata API version 62 (Winter '25) to support the latest features and metadata components.

New Metadata Components

  • Added support for new metadata types:

    • Omni Studio: Users can now view, compare and deploy Omni Studio components including FlexCards, OmniScripts, OmniStudio Data Mappers, Integration Procedures.
      โ€‹
      We have also added a new view (-- Omni Studio --) so users can view all these 4 components in one click.

    • Additional types: WebStoreTemplate, FuelType, SustainabilityUOM, FuelTypeSustnUOM, SustnUOMConversion, DataWeaverResource.

Approval Process Improvements

We've enhanced approval process for work items, reduced multiple manual steps involved and making it more streamlined and consistent.

  • Pipeline reviewers configuration: Default reviewers can now be specified for each stage in the pipeline settings.

  • Automatic reviewer addition: Upon requesting approval, default reviewers are automatically added, with auto-sharing enabled for work items with reviewers.

Bug Fixes

  • Azure organization fetch error: Fixed an issue when fetching work items from large Azure organizations.

  • Cloning deploy options: Resolved issue with deploy options not copying over when cloning deployments.

  • Deployment history visibility: Deployment history is now visible to colleagues with shared access, not just to the deployment owner.

  • Pipeline accessibility: Fixed issue preventing parts of the pipeline from functioning even when both source and target are accessible.
    โ€‹

  • Diff view refresh: Diff flags for Flow and Global Value Set with the same last modified date between source and target were previously reported to be the same, even though their contents are different.


    This has now been fixed. A full refresh will force content comparison between source and target, and will show the correct diff flags, even when the last modified dates haven't changed between source and target.

Did this answer your question?