Versions Compared

Version Old Version 3 New Version Current
Changes made by

bob.alicante

bob.alicante

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

with Syed, Yeng, Swathi and Managed Services Team

May 5, 2023

Summary of Discussion:

Action Item

Remarks

List of Impacted Components

Status

Experience Sites Affected URL: https://sydneyuni-adv.force.com/serviceportal

Old: https://sydneyuni-adv.force.com

New: https://sydneyuni-adv.my.site.com

  •  Need to check Well Being experience Site

Metadata Component
flexipages\Home_Page1.flexipage-meta.xml

All hard-coded URLs needs to be updated.

  •  We need to look for more robust/dynamic approach to prevent manual maintenance in the future
  •  Categorize list of hard coded URLs per team (WB, TAP, Hogwarts).

Email templates

URLs

List of Hard-coded URLS HERE

SSO

  •  Need to involve Saima on this from a Release perspective
  •  What sandbox to be used for testing SSO (SIT/QA/UAT)?

Automated Test Script

  •  Check automation testing script to capture hard coded URLs

Prepare for and Schedule a My Domain Change

To prepare for a My Domain change, first gather the key information: the required updates, testing, and participants. Then review the deployment process for a My Domain change, identify your testing environment, and schedule your testing and production deployment.

#

TASK

REMARKS

Determine the Scope

1

  •  Learn about enhanced domains

2

  •  Review the My Domain provisioning and deployment process

3

  •  Determine the hostnames that change

Enhanced Domain: Production Org URL Format Changes

Enhanced Domain: List of Hard-coded URLs

4

  •  Note whether your login URLs change

Default login URLs don’t change for both production (https://login.salesforce.com) and sandboxes/test (https://test.salesforce.com)

Domain specific login for sandboxes change. To check with integration team if using domain specific login URL (i.e. https://sydneyuni-adv--uat.my.salesforce.com for UAT sandbox)

5

  •  Identify the features that require an update

6

  •  Review recommended practices and identify any additional changes

Determine Your Project Participants

7

  •  Identify participants for the required updates

8

  •  Identify testers

9

  •  Identify communication owners

10

  •  Identify go-live participants

11

  •  Collect contact information

Develop Testing, Communication, and Go-Live Plans

12

  •  Identify any features that automated tests cover

13

  •  Create a test plan

14

  •  Determine how to capture testing results

15

  •  Develop a communication plan

16

  •  Create a go-live plan

17

  •  Develop a rollback plan

Schedule Your My Domain Change

18

  •  Identify or create a sandbox for testing

19

  •  Determine your target project dates and dependencies

20

  •  Choose your testing and deployment windows

21

  •  Finalize and share your schedule