Loading
PHP Vulnerability Monitoring Read More
Media Cloud
Deploy Advertising Sales Management Winter '26

Deploy Advertising Sales Management Winter '26

If you're a new customer deploying Advertising Sales Management Winter '26, complete these steps.

Prepare to Deploy Advertising Sales Management Winter '26

Complete these prerequisite steps to set up your target org before you deploy Advertising Sales Management.

Required Editions

Available in: Lightning Experience
Available in: Enterprise, Performance, and Unlimited editions with Media Cloud
User Permissions Needed
To access Media Cloud advanced features: MediaCloudPlusRuntime
To create, read, update, and delete Flexcards: Omnistudio Admin

Before you deploy Advertising Sales Management Winter '26, perform these steps.

  1. If you haven't signed up for automatic upgrades, then manually upgrade your target org to the latest Communications, Media, and Energy managed package.
    You can view the latest release version in the Industries Communications, Media, and Energy Release Summary.
  2. Install the Alpha version of IDX Workbench.
    Salesforce recommends that you use macOS with the Alpha version of IDX Workbench.
  3. Make sure that your user prodile has all the required permission sets and permission set licenses to complete the Advertising Sales Management deployment.
  4. Download a Advertising Sales Management Winter '26 YAML file based on whether you use Omnistudio for Managed Packages or Omnistudio:
    Omnistudio for Managed Packages YAML file
    Omnistudio YAML file
    The YAML files contain the list of Advertising Sales Management components available in this release.
  5. Manually update the Remote Site Settings for Flexcards.
  6. (Optional) Set up advanced visualizations for account relationships. See Actionable Relationship Center (ARC) in Media Cloud.

Download Advertising Sales Management Static Resource Files for Winter '26

Download and reorganize the static resource files into folders before you use IDX Workbench to deploy the Advertising Sales Management components to your target org.

Advertising Sales Management components are built using the capabilities of either Omnistudio for Managed Packages or Omnistudio. Depending on whether you use Omnistudio for Managed Packages or Omnistudio, you must download either of the relevant static resource files:

Omnistudio Type Resource Type Static Resource File
Omnistudio for Managed Packages Flexcards Media_ASM_Cards
Data mappers Media_ASM_DataRaptors
Data packs
  • Media_ASM_Datapacks
  • Media_ASM_sfdx_datapacks
Omnistudio Flexcards Media_ASM_OS_Core_RT_Cards
Data mappers Media_ASM_OS_Core_RT_DataRaptors
Data packs
  • Media_ASM_OS_Core_RT_Datapacks
  • Media_ASM_OS_Core_RT_sfdx_datapacks

To learn about the differences between Omnistudio and Omnistudio for Managed Packages, see Differences Between Omnistudio and Omnistudio for Managed Packages.

  1. From Setup, in the Quick Find box, enter Static Resources and select it.
  2. Click either Media_ASM_Cards or Media_ASM_OS_Core_RT_Cards static resource file and click View File to download the file.
  3. Similarly, download the other files that you require based on whether you use Omnistudio or Omnistudio for Managed Packages.
  4. In your local system, create a folder named IDx Workbench, and create a child folder named vlocity.
  5. Extract the contents of the ZIP files that you've downloaded to the vlocity folder under IDX_Workbench.
  6. In the IDX_Workbench folder, create a file named sfdx-project.json, and copy this code in the file.
    {
    
        "packageDirectories": [
            {
                "path": "salesforce_sfdx",
                "default": true
            }
        ],
        "namespace": "",
        "sfdcLoginUrl": "https://login.salesforce.com",
        "sourceApiVersion": "65.0"
    }
    

    The folder structure in your local system should look like this.

    Screenshot showing static resource folder structure in local system

Deploy Advertising Sales Management Winter '26 Components

After you download the Advertising Sales Management static resource components, use IDX Workbench to deploy them to your target org.

  1. In the IDX Workbench application, add the IDX_Workbench folder from your local system as a new repository.
  2. Select the newly created repository as the source.
  3. Set up the target org as the org that you want to upgrade to the latest version.
  4. After you select the repository in IDX Workbench, go to the repository path.
  5. To view hidden files, press Command + Shift + . on your Mac.
  6. Move the YAML file that you downloaded earlier into the hidden .vlocity folder in the repository.
  7. Go back to IDX Workbench and click Cancel.
  8. Click Edit and in confgiure Workspace, select the repository.
  9. In Project, select the YAML file that shows up in the list, and click Save.
  10. Select All changed items, and then from the Actions menu, click Migrate with Dependencies.
    Deploy all the components in this order.
    1. Integration Procedures and DataRaptor
    1. RecordTypes, Fields, CompactLayouts, ListViews, StandardValueSets, CustomLabels, and Custom Metadata
    2. VlocityPicklist and ObjectClass
      Before you deploy ObjectClass components, run the Install Default Vlocity Objects and Layout EPC job.
    3. AttributeCategory and ObjectLayout
    4. Vlocity Cards
      Before you activate the Flexcards, update the Flexcard Object's default Lightning record page to access the Flexcard Designer. Activate all the deployed Flexcards. If you see an activation error, and if the error message indicates any missing dependent Flexcards, first activate the dependent Flexcard before activating the current one.

      Check whether all the Flexcards listed in the YAML file are active. If any of the Flexcards isn't active, then activate only those cards.

      If Omnistudio is enabled in your Salesforce org, use the Omnistudio Build Tool to deploy Flexcards.

    5. Omniscripts
      After the migration is complete, deactivate the vplAdsMediaPlanDetails Omniscript. In the Outline, Add Plaement, and View Summary steps, for vplAdsDisplayTotalCalculatedValue and vplAdsMediaPlanOsNavigation Lightning Web Components, select the option with the namespace vlocity_cmt__. Reactivate the Omniscript.
    6. PricingPlan, Pricebook2, and PricingVariable
    7. System and catalog
    8. VlocityUITemplate, VlocityUILayout
    9. Email, reports, and reportTypes
      Before you deploy reports, enable Translation Language Settings from Setup in your org.
    10. WebLinks and QuickActions
    11. FlexiPages and layouts
      Before you deploy FlexiPages, for the Status field in the contract object, create a picklist with the values Awaiting Approval, Negotiating, and Rejected Internally. See Add Contract Status Picklist Values for CME.

      Before you deploy FlexiPages, make sure that you create the KPI Summary Lightning Page.

      When you deploy FlexiPages, if you see an error message related to Flexcards, reactivate the Flexcard specified in the error message, and try again.

    12. Tabs, Triggers, Static Resources
    13. OrchestrationPlanDefinition
    14. OrchestrationItemDefinition
      Before you begin to deploy OrchestrationItemDefinition components, manually create the Data Mapper bundle in your org. If you face an error when you deploy OrchestrationItemDefinition components, then open GAMArchiveLineItemService_DataPack.json from the OrchestrationItemDefinition, and set the value of %vlocity_namespace%__RetryPolicy__c to null for those particular components.
    15. OrchestrationDependencyDefinition
      Deploy these OrchestratioDependencyDefinition components in this order (without dependencies). Deploy all the remaining OrchestrationDependencyDefinition components together.
      • GAMPauseOrder - GAMUpdateOrderLineItemService
      • GAMPauseOrder - GAMAddNewLineItemService
      • GAMOrderService - GAMOrderLineItemService
      • GAMOrderLineItemService - GAMLineItemCreativeAssociationService
      • GAMLineItemCreativeAssociationService - GAMApproveOrderService
      • GAMApproveOrderService - GAMActivateOrderLineItemService
      • GAMAddNewLineItemService - GAMAddLineItemCreativeAssociationService
      • GAMAddLineItemCreativeAssociationService
      • GAMActivateNewLineItemService
      • GAMActivateorderlineitemservice - GamEnd
      • GAMActivatenewlineitemservice - GamResumeorder
      • GAMStart - GAMPauseorder
      • GAMStart - GAMOrderService
    16. OrchestrationQueueAssignmentRule and ManualQueue
      Before you deploy the OrchestrationQueueAssignemtnRule components, configure the Order Management (OM) and OM Plus Interfaces.
    17. Document Template
    18. Flows and Workflows
      Before you deploy workflows, update the Workflow datapacks with valid usernames in the assignedTo and recipient tags. These users must exist in your Salesforce org. The Contract Workflow datapack contains two alert flows, which contain three recipient users. Enter a unique username for each recipient. Before you deploy workflows, for the Task field in the quote workflow, add the picklist value Not Started.
    19. Approval Process
      When you deploy Approval Processes, replace the name of the user in PartyRelationship__c.Party_Relationship_Mapping_Approval_Flow.approvalProcess-meta and Account.PartnerAccountApprovalFlow.approvalProcess-meta with a valid user that exists in your Salesforce org.

      If you deployed documentation templates and your flows and approval processes do not work as expected, then open the deployed templates and activate them.

    20. Interface Implementations
      To disable the rounding off feature in your Standard Cart API enabled orgs, activate the CpqPricingVariableCalcHook interface implementation.
  11. Deploy all expression sets and decision matrices.
  12. To make sure that the parameters are in the correct sequence, edit Flexcard parameters.
  13. If necessary, set up Actionable Relationship Center in Media Cloud.
  14. For optimized performance, enable explicit pricing.
  15. Salesforce recommends that you enable the optimized fetch products feature for enhanced performance and user experience.
  16. Set the appropriate field level security for all the fields related to these objects.
    1. Ad Buy Server Account
    2. Ad Creative Size Type
    3. Ad Demo Code
    4. Ad Opportunity
    5. Ad Order Item
    6. Ad Order Item Creative Size Type
    7. Ad Order Line Ad Target
    8. Ad Order Items Units Split
    9. Ad Product Target Category
    10. Ad Quote Line
    11. Ad Quote Line Ad Target
    12. Ad Quote Line Creative Size Type
    13. Ad Quote Line Hiatus
    14. Ad Quote Line Units Split
    15. Ad Server
    16. Ad Server Account
    17. Ad Server User
    18. Ad Space Creative Size Type
    19. Ad Space Group Member
    20. Ad Space Specification
    21. Ad Spec Media Print Issue
    22. Ad Target Category
    23. Ad Target Category Segment
    24. Media Channel
    25. Media Content Title
    26. Media Print Issue
  17. Assign Lightning Pages in your target org.
  18. Assign page layouts in your target org.
  19. Update profile settings.
  20. Set up pagination.
  21. When a quote is converted to an order, the data from the quote, quote line item, and ad quote line item must be copied to the order, order line item, and ad order line item, respectively. To make sure the mapping between these fields is correctly configured, see Maintain Advertising Sales Management Object and Field Mapping.
  22. Disable Lightning Web Security.
  23. Create RollbackIPChanges and RollbackDRChanges, with values set to true, from Omni Interaction Configuration under Setup.
  24. If necessary, create sample product and price data in your Advertising Sales Management org.
 
Loading
Salesforce Help | Article