Install Advertising Sales Management Spring '24

If you're performing an installation of this outdated version of Advertising Sales Management, follow these steps.

This is an Advertising Sales Management on Managed Package feature. For Advertising Sales Management on Salesforce Platform, see Advertising Sales Management on Salesforce Platform.

Note Spring '24 is an older version of Advertising Sales Management. To install the latest version, see the current installation instruction for Advertising Sales Management.

Before you begin:

• Install the Alpha Version of IDX Workbench. See Install IDX Workbench.

  Salesforce recommends that you use macOS with the Alpha version of IDX Workbench.

• Download the YAML file containing the list of Advertising Sales Management core components for this release. You can download the YAML file from Deploy Older Releases of Advertising Sales Management.

• Update Remote Site Settings for FlexCards.

• Maintain Advertising Sales Management Object and Field Mapping

• Download and import the Advertising Sales Management Relationship Graphs into your org.

  • Extract the contents of the Advertising Sales Management Relationship Graphs.

  • In your Salesforce org, navigate to Vlocity Cards, and import each relationship graph from the downloaded folder.

• Download the additional Spring '24 Metadata Data Pack.

1. In your Salesforce instance, click Settings and then Setup.
2. In Quick Find search for and click Static Resources.
3. Click the Media_ASM_Cards static resource files, and click View file to download the file. Complete this step for the following files: Media_ASM_Datapacks, Media_ASM_DataRaptors, and Media_ASM_sfdx_datapacks.
4. In your local system, create a folder named IDX_Workbench, and create a child folder named vlocity.
5. Extract the contents of the Media_ASM_Cards ZIP file to the vlocity folder under IDX_Workbench.
6. Extract the contents of the Media_ASM_Datapacks ZIP file, and merge the contents of the vlocity folder from the expanded folder with the vlocity folder under IDX_Workbench.
7. Extract the contents of the Media_ASM_DataRaptors ZIP file to the vlocity folder under IDX_Workbench.
8. Extract the contents of the Media_ASM_sfdx_datapacks ZIP file, and move the salesforce_sfdx folder under IDX_Workbench.
9. Extract the contents of the additional metadata datapack containing the Spring '24 components, and replace applicable static resource folders with the folders from the datapack.
10. In the IDX_Workbench folder, create a file named sfdx-project.json, and copy the following code in the file.

    {
        "packageDirectories": [
            {
                "path": "salesforce_sfdx",
                "default": true
            }
        ],
        "namespace": "",
        "sfdcLoginUrl": "https://login.salesforce.com",
        "sourceApiVersion": "<sourceAPIVersion>"
    }

    

    Note For Spring '24, the Source API version is 59.0.
11. In IDX Workbench, add the IDX_workbench folder from your local system as a new repository.
12. Select the newly created repository as the source.
    If you have an org that was set up using static resources, then you can set that org as the source, and migrate components from the source org to your target org.
13. After you select the repository in IDX Workbench, navigate to the repository path.
14. Display hidden files. On a Mac, press Command + Shift + .. On a Windows system, click View and then select Hidden Files.
15. Copy the YAML file you downloaded earlier and paste them into the hidden .vlocity folder in the repository.
16. Go back to IDX Workbench and click Cancel.
17. Click the Edit icon and in Configure Workspace, select the repository.
18. In Project, select the YAML file that shows up in the list, and click Save.
19. In the left pane of IDX Workbench, select All changed items, and then from the Actions menu, click Migrate with Dependencies.
    

    Note If the migration of any or more components fails, move only the failed components to Selected datapacks and migrate with dependencies again.

    Migrate the components in the following order:

    1. Integration Procedures, Data Mapper, and Apex Classes
    2. Record Types, Fields, Compact Layouts, List View, and Custom Metadata
    3. VlocityPicklist and ObjectClass
    4. AttributeCategory and ObjectLayout
    5. Vlocity Cards
    6. Pricing Plan, Pricebook, Pricing Variable, and Pricelist
    7. System
    8. VlocityUITemplate, VlocityUILayout
    9. Email, report, and reportTypes
    10. CustomLabels, QuickActions, weblink
    11. FlexiPages and PageLayouts
        

        Note Before you migrate FlexiPages, ensure that you Create the KPI Summary Lightning Page.
    12. Tabs, Triggers, Static Resources
    13. OrchestrationPlanDefinition
    14. OrchestrationItemDefinition
        

        Note

        • Manually Create the Omnistudio Data Mapper Bundle in your org before you migrate OrchestrationItemDefinition.

        • Open GAMArchiveLineItemService_DataPack.json from the OrchestrationItemDefinition, and set the value of %vlocity_namespace%__RetryPolicy__c to null.

    15. OrchestrationDependencyDefinition
        Migrate the OrchestrationDependencyDefinition in the following order (migrate without dependencies):

        • GAMPauseOrder - GAMUpdateOrderLineItemService

        • GAMPauseOrder - GAMAddNewLineItemService

        • GAMOrderService - GAMOrderLineItemService

        • GAMOrderLineItemService - GAMLineItemCreativeAssociationService

        • GAMLineItemCreativeAssociationService - GAMApproveOrderService

        • GAMApproveOrderService - GAMActivateOrderLineItemService

        • GAMAddNewLineItemService - GAMAddLineItemCreativeAssociationService

        • GAMAddLineItemCreativeCreativeAssociationService - GAMActivateNewLineItemService

        • GAMActivateorderlineitemservice - GamEnd

        • GAMActivatenewlineitemservice - GamResumeorder

        • GAMStart - GAMPauseorder

        • GAMStart - GAMOrderService

        • Depends on Start

        • Depends on Create Order

    16. OrchestrationQueueAssignmentRule
    17. Document Template
    18. Flows, Workflows, and Approval Process.
        

        Note When you migrate 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 .
    19. Quick Actions
    1. Interface Implementation
20. Add the Contract Status Picklist Values.
21. For the Status field in the Contract object, create a picklist with the values Awaiting, Approval, Negotiating, and Rejected Internally.
22. For the Task field in the Quote workflow, add the picklist value Not Started.
23. For the email alert, ensure that the values in the assigned To and Recipients fields are valid users in the org.
24. If you see errors around Lightning Web Component activation for the following FlexCards, use the FlexCards Data Pack to deploy them.

    • sfiAdsLinearTargeting

    • sfiAdsLinearViewSummaryPagination

    • sfiAdsPrintViewSummaryPagination

    • sfiAdsTvGrid

    • sfiAdsTvGridChild

    • sfiAdsTVKPISummary

    • vplAdsTargetingChildClone

    • vplAdsViewSummaryTab

25. Deploy Expression Sets and Decision Matrices for Advertising Sales Management Deployment.
26. Edit Flexcard Parameters to ensure that the parameters are in the correct sequence.
27. Set the appropriate field level security for all the fields related to the following Advertising Sales Management objects.

    • Ad Quote Line

    • Ad Order Item

    • Ad Space Specification

    • Ad Order Item Creative Size Type

    • Ad Quote Line Creative Size Type

    • Ad Demo Code

    • Ad Quote Line Hiatus

    • Ad Order Line Hiatus

    • Media Channel

    • Ad Creative Size Type