WS SFDC App: Automated Post-Deployment Steps (Expanded)

Follow

Table of Contents

1. Overview
2. Security Considerations
3. Post-deployment Steps for Specific Version Upgrades
    3.1. Create the Connected App
    3.2. Update the Search Layout of the ‘Partner Opportunity Referral’
    3.3. Replace the Help Text for ‘Account Owner Email’
    3.4. Replace the Help Text for ‘Referral Creation Method’
    3.5. Replace the Help Text with ‘Description’
    3.6. Update the Picklist Values for the ‘AWS Use Case‘
    3.7. Create Solutions and Set Default
    3.8. Set the Default Value for Sales Activities with the Customer
    3.9. Update Amazon Page Layouts


1. Overview

When Salesforce packages are getting upgraded, some aspects (most notably, page layouts and picklist values) cannot be changed, Salesforce will not allow this. These changes are mandated by the hyperscalers (AWS / MSFT / Google); as such, they must be performed in one way or another in order to maintain functionality. In addition, WorkSpan releases frequent small improvements, which would also impact the ability to upgrade (most notably, field help texts).

In the past, our customers had to perform the necessary post-deployment steps manually.  This process was labor-intensive and error-prone and required dedicated attention from a customer’s Salesforce admin. In order to help reduce this manual effort, we have introduced an automated Post-deployment Wizard in v.1.14. The wizard carries out the same processes that an admin would have to do manually but in a more efficient and reliable manner.

In v.1.19, we have repurposed this time-saving wizard to streamline one of the configuration steps that is required to accommodate ACE v.2 changes. WorkSpan strongly recommends enabling and using the wizard for both existing and new customers. The initial setup of the wizard ("Create the Connected App" section) only needs to be performed once. After that, the customer can reap the benefits of speeding through subsequent upgrades, which will undoubtedly be required by the hyperscalers in the future.

This document describes the steps that have been coded into the wizard, i.e., it explains which metadata change is behind every action. 

Note: If the first version of the WorkSpan package that you have installed is later than 1.10, some of the steps might not be visible to you or may be marked as completed right away. This is related to the version you originally installed.  For example,  if the first version installed was 1.14, then you do not need to perform the steps that were required when upgrading from version 1.12 to 1.13.

2. Security Considerations 

To enable the PDW, creating a new Connected App with extensive access is necessary due to Salesforce's limitations. This unconventional method, reflecting the complexity of Salesforce customization, may be unfamiliar to many. This additional Connected App has few technical limitations, but strict governance constraints from the Salesforce Security Review team prohibit it from accessing anything outside our managed package. Every change must be explicitly included in the package and triggered from within the package by a user in the specific Salesforce org. Additionally, each package version must go through this Security Review process.

If there are still concerns, customers can enable the PDW, execute the steps, and then either block or delete the Connected App.

For more details, please read this FAQ about the PDW and Connected App.

3. Post-deployment Steps for Specific Version Upgrades

3.1. Create the Connected App

The initial set of steps guides the admin through creating a new Connected App and providing the admin access to it. This App is required so that metadata changes can be deployed in the background through a single button click, replacing manual changes to the same metadata.

3.2. Update the Search Layout of the 'Partner Opportunity Referral'

This step updates the default search layout of the Partner Opportunity Referral object so that the following fields are added:
>> Referral
>> APN CRM ID

This step is intended to improve the UX.

Note: Due to a known issue, this step (v.1.19.2) does not work correctly. It throws an error the first time you try to execute it, so you have to refresh the page and run it again. Then it checks off as successful, but in fact, the search layout of the Partner Opportunity Referral doesn’t change.

3.3. Replace the Help Text for 'Account Owner Email'

This step replaces the help text for the Account Owner Email field on the Opportunity Referral object with the following value:

>> Email of the Account Owner as well as the email of the Opportunity Owner for receiving an introductory email for the Referral.

This step is intended to improve the UX.

3.4. Replace the Help Text for ‘Referral Creation Method’

This step replaces the help text for the Referral Creation Method field on the Opportunity Referral object with the following value:

>> The Referral Creation Method field is populated automatically depending on how the Referral was created. If the Referral was bulk created, the value should be ‘Bulk’; if the Referral was created using automation, the value should be ‘Flow’; and if the Referral was created manually from the interface, the value should be ‘UI.’

This step is intended to improve the UX.

3.5. Replace the Help Text for ‘Description’

This step replaces the help text for the Description field on the Opportunity Referral object with the following value:

Please provide the following details: 

1. What is the customer's pain point? 

2. What solution are you proposing to the customer? 

3. What is the end customer looking to do? What's the role of each partner? 

4. What are the software applications and tools used to support the solution? 

5. Specific department or subsidiary of the end customer you are working with? 

6. What was the pre-sales engagement you had with this customer during this opportunity?

This step is intended to improve the UX.

3.6. Update the Picklist Values for the ‘AWS Use Case‘

This step replaces the picklist values in the AWS Use Case field on the Opportunity Referral object with the following values:

This step is required for the ACE v.2 upgrade and is intended to improve the admin experience (AX) during the upgrade.

3.7. Create Solutions and Set Default

This step does multiple things based on the CSV file that you provide:
1. Creates new picklist values in the AWS Solution Offered ID field on the Opportunity Referral object.
2. Marks one of the picklist values as the default value.
3. Creates records of the packaged solution object. 

This step is required for the ACE v.2 upgrade and is intended to improve the AX during the upgrade.

3.8. Set the Default Value for Sales Activities with the Customer

This changes the default picklist value in the Sales Activities with the Customer field on the Opportunity Referral object. This step is required for the ACE v.2 upgrade and is intended to improve the AX during the upgrade.

3.9. Update Amazon Page Layouts

This step replaces two-page layouts on the Opportunity Referral object (Incoming Amazon Referral Layout and Outgoing Amazon Referral Layout) with completely new layouts. There are 13 new fields being added and 12 deprecated fields being removed.

Note: Any customizations that you might have done to these page layouts previously (e.g., added your own custom fields, marked additional fields as required, moved fields around) will be lost after executing this step.

This step is required for the ACE v.2 upgrade and is intended to improve the AX during the upgrade.

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.