Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au

Skip to end of banner
Go to start of banner

Enhanced Domain: How to Test

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 26 Current »

Section 1: Hardcoded Salesforce URLs

Hogwarts Item (c/o Lesley Millar (Unlicensed) )

email\Spend_Plan_Email_Templates\Delegate_Decision_Changes_Needed.email

email\Spend_Plan_Email_Templates\General_Purpose_Template.email

email\Spend_Plan_Email_Templates\Review_Spend_Plan_Request_a_Review.email


TAP - Flows

flows\NewCOA.flow-meta.xml

 How to Test

How to Test: link to TAP-1405

flows\Opportunity_After_Save_On_Create_On_Update.flow-meta.xml

 How to Test

NOTE: The aim of this test guide is only to trigger the email notification that is being sent to Advancement-Services.Gifts@sydney.edu.au when Chart of Account type field in Opportunity record is changed.

Testing Steps:

  1. Log in as Gift Admin (user with Gift Administration permission set group assignment).

  2. Create a new Opportunity record (fill-in all the required fields, and address all validations) and save.

  3. Set the Opportunity Stage to “Gift Handover” and save.

  4. In the same Opportunity record, locate the “Implementation/Administration” tab and open the related GIN record.

  5. Put the GIN record on the side and prepare a batch with no set Review Status.

  6. Create a batch item with no Link to Opportunity.

  7. Re-open the batch item record, and update the Link to Opportunity of the child batch item(s). Use an Opportunity that has related Gift Implementation records (hint: use the opportunity created in step #2).

  8. Once the batch item(s) is saved, a batch item record-triggered flow is fired and updates the Gift Implementation Stage. Notice that the related Gift Implementation Stage of the Link to Opportunity is updated to: 3. GA-Entry.

  9. Open again the related Opportunity record (the one that was created in step #2) and edit it.

  10. Change the “Chart of Account Type” field to any value other than its current and “--None--” and save. An email should fire and sent to Advancement-Services.Gifts@sydney.edu.au. Check the content of the email.

  11. Once the email is received, click the link to open the Opportunity record.

Expected Result:

After clicking the link in the email, the same Opportunity record that was created in step #2 is opened.

Screenshots:

flows\Usyd_Contact_Address_History_Tracking.flow-meta.xml

NOTE: This flow is to be deactivate/deprecated as part of the Contact’s flow consolidation/optimization drive. The supposed adjustment will be part of TAPSS-834 - Getting issue details... STATUS

 How to Test

Refer to TAP-1118 (TAPSS-834) Confluence page’s UNIT TESTING STEPS section

flows\Usyd_Delegate_Acceptance_when_checked_send_alert.flow-meta.xml

 How to Test

Testing Steps:

  1. Log in as a Uyd Standard User or any user who can update an opportunity.

  2. Go to Opportunity Tab

  3. Select any opportunity that has an existing GIN record having a “1. GI-Handover” Stage

4. Update/Check the Acceptance from Delegate checkbox

Expected Output: advancement-services.gifts@sydney.edu.au will receive an email

Note: Please also verify the links from the email if they redirect you to the sandbox where you conducted your test.

flows\USYD_Service_Portal.flow-meta.xml

 How to Test

Testing Steps

  1. Login to Salesforce as USyd Standard User, and open the Affinaquest app.

  2. Once the logged in and in the Affinaquest app, ensure that you are in the Home tab.

  3. In the browser’s address bar, take note of the current page’s domain (base/root URL), i.e.:
    - SIT: https://sydneyuni-adv--bluesky.sandbox.lightning.force.com/
    - UAT: https://sydneyuni-adv--uat.sandbox.lightning.force.com/
    - PROD: https://sydneyuni-adv.lightning.force.com/

  4. In the Home Page, click the Service Portal link. A new tab/window will open. If not yet logged in Service Portal, the login page will be presented; otherwise, the user is taken directly to the Service Portal page where the user can start creating case.

  5. Start creating a case by clicking one of the available (blue) buttons/links.

  6. Fill all the required fields in the Case form in different screens (via Next button - depends on the selected Type), until you reach the “Case Created” screen. Note the Case Number.

  7. Click the link next to (or below the) “Here’s a link to your case:” text. A new tab/window should open show the case that was just created. Check its Case Number.

Expected Result:

  1. In step #6, the link presented to the user has the same base URL as noted in step #3

  2. In step #7, the newly opened tab/window has the same base URL as noted in step #3

  3. In step #7, the Case record show has the same Case Number as noted in step #6.

Screenshots:


 How to Test

Testing Steps:

  1. Login to Salesforce as a user who is a member of the Business Insights Team or Data Reporting and Systems (public group).

  2. Open “Batches” tab and open an existing Batch record (or create one if none exists - requires additional permission).

  3. Once the Batch record opens, in the browser’s address bar, take note of the current batch record’s domain (base/root URL), i.e.:
    - SIT: https://sydneyuni-adv--bluesky.sandbox.lightning.force.com/
    - UAT: https://sydneyuni-adv--uat.sandbox.lightning.force.com/
    - PROD: https://sydneyuni-adv.lightning.force.com/

  4. In the Batch record page, locate and click the “Pledge Schedule Review” button.

Expected Result:

The report titled “USYD Batch Pledge Schedule Review” should open in the same window where the Batch record was opened, and the report’s base URL is the same as the Batch record’s based URL (as noted in step #3)

Screenshots:

 How to Test

Testing Steps:

  1. Login to Salesforce as a user who is a member of the Business Insights Team, Data Reporting and Systems, Gifts Administration or Advancement Portfolio (public group).

  2. Open “Batches” tab and open an existing Batch record (or create one if none exists - requires additional permission).

  3. Once the Batch record opens, in the browser’s address bar, take note of the current batch record’s domain (base/root URL), i.e.:
    - SIT: https://sydneyuni-adv--bluesky.sandbox.lightning.force.com/
    - UAT: https://sydneyuni-adv--uat.sandbox.lightning.force.com/
    - PROD: https://sydneyuni-adv.lightning.force.com/

  4. In the Batch record page, locate and click the “Batch Account Phone Report” button (if it is not shown, click the drop-down button next to “Pledge Schedule Review” button).

Expected Result:

The report titled “Lists Account Phones of Batch Items” should open in the same window where the Batch record was opened, and the report’s base URL is the same as the Batch record’s based URL (as noted in step #3)

Screenshots:

 How to Test

Testing Steps:

  1. Login to Salesforce as a user who is a member of the Business Insights Team, Data Reporting and Systems, Gifts Administration or Advancement Portfolio (public group).

  2. Open “Batches” tab and open an existing Batch record (or create one if none exists - requires additional permission).

  3. Once the Batch record opens, in the browser’s address bar, take note of the current batch record’s domain (base/root URL), i.e.:
    - SIT: https://sydneyuni-adv--bluesky.sandbox.lightning.force.com/
    - UAT: https://sydneyuni-adv--uat.sandbox.lightning.force.com/
    - PROD: https://sydneyuni-adv.lightning.force.com/

  4. In the Batch record page, locate and click the “Batch Review Report” button (if it is not shown, click the drop-down button next to “Pledge Schedule Review” button).

Expected Result:

The report titled “Gift Processing Validation” should open in the same window where the Batch record was opened, and the report’s base URL is the same as the Batch record’s based URL (as noted in step #3)

Screenshots:

 How to Test

Testing Steps:

  1. Login to Salesforce as a user who is a member of the Business Insights Team, Data Reporting and Systems, Gifts Administration or Advancement Portfolio (public group).

  2. Open “LL-Chart of Accounts” tab and open an existing LL- Chart of Account record (or create one if none exists).

  3. Once the LL- Chart of Account record opens, in the browser’s address bar, take note of the current batch record’s domain (base/root URL), i.e.:
    - SIT: https://sydneyuni-adv--bluesky.sandbox.lightning.force.com/
    - UAT: https://sydneyuni-adv--uat.sandbox.lightning.force.com/
    - PROD: https://sydneyuni-adv.lightning.force.com/

  4. In the LL- Chart of Account record page, locate and click the “COA Report” button.

Expected Result:

The report titled “Chart of Accounts Report” should open in the same window where the Batch record was opened, and the report’s base URL is the same as the LL- Chart of Account record’s based URL (as noted in step #3)

Screenshots:

 How to Test

Testing Steps:

  1. Login to Salesforce as a user who is a member of the Business Insights Team, Data Reporting and Systems, Gifts Administration or Advancement Portfolio (public group).

  2. Open “LL-Chart of Accounts” tab and open an existing LL- Chart of Account record (or create one if none exists).

  3. Once the LL- Chart of Account record opens, in the browser’s address bar, take note of the current batch record’s domain (base/root URL), i.e.:
    - SIT: https://sydneyuni-adv--bluesky.sandbox.lightning.force.com/
    - UAT: https://sydneyuni-adv--uat.sandbox.lightning.force.com/
    - PROD: https://sydneyuni-adv.lightning.force.com/

  4. In the LL- Chart of Account record page, locate and click the “Open Pledge Records” button.

Expected Result:

The report titled “Open Pledge with Trans of Updating COA” should open in the same window where the Batch record was opened, and the report’s base URL is the same as the LL- Chart of Account record’s based URL (as noted in step #3)

Screenshots:

 How to Test

Testing Steps:

  1. Login to Salesforce as USyd Standard User, and open the Affinaquest app.

  2. Open “Receipts” tab, and locate and open an existing Affinaquest Receipt (create a new one if there’s no existing Receipt record).

  3. Once the Receipt record opens, in the browser’s address bar, take note of the current record’s domain (base/root URL), i.e.:
    - SIT: https://sydneyuni-adv--bluesky.sandbox.lightning.force.com/
    - UAT: https://sydneyuni-adv--uat.sandbox.lightning.force.com/
    - PROD: https://sydneyuni-adv.lightning.force.com/

  4. In the Receipt record page, just below the “Details” tab, click the “New Task” link.

Expect result:

  1. A “New Task” pop screen should open within the same window/tab where the current Receipt record is displayed.

  2. The based URL remains the same as the Receipt records base URL as noted in step #3.

Screenshots:

Section 2: Hardcoded Salesforce URLs that Need Fixing

Wellbeing - Email Templates

email\sumoapp__SUMO_Templates\USYDAppointmentBookedSumoUser.email

 How to Test

As a System Admin user, switch to classic. Go to Settings > Classic Email Templates. Open each of the highlighted email templates. NOTE: This should apply to those 4 templates highlighted in red

2. Hover to the safer-communities.officer@sydney.edu.au. On the lower left portion of the screen, the URL should be: “mailto:safer-communities.officer@sydney.edu.au

email\sumoapp__SUMO_Templates\USYDAppointmentCanceled.email

 How to Test

[test guide goes here]

email\sumoapp__SUMO_Templates\USYDAppointmentReminder.email

 How to Test

[test guide goes here]

email\sumoapp__SUMO_Templates\USYDAppointmentUpdatedCustomer.email

 How to Test

[test guide goes here]

email\sumoapp__SUMO_Templates\USYDAppointmentUpdatedSumoUser.email

 How to Test

[test guide goes here]

Section 3: Hardcoded Salesforce URLs that CANNOT Be Converted to Configurable Settings

TAP

flexipages\Home_Page1.flexipage-meta.xml

Note: The existing RichText container with hard-coded link was replaced with a Screen Flow so that the service portal’s base URL can be automatically checked.

 How to Test

Testing Steps

  1. Login to Salesforce as USyd Standard User, and open the Affinaquest app.

  2. Once the logged in and in the Affinaquest app, ensure that you are in the Home tab.

  3. In the browser’s address bar, take note of the current URL’s sub-domain, i.e.
    - in SIT’s full base URL/domain (https://sydneyuni-adv--bluesky.sandbox.lightning.force.com) the sub-domain will be “sydneyuni-adv--bluesky”
    - in UAT’s full base URL/domain (https://sydneyuni-adv--uat.sandbox.lightning.force.com/) the sub-domain will be “sydneyuni-adv--uat”
    - in PROD’s full base URL/domain (https://sydneyuni-adv.lightning.force.com/) the sub-domain will be “sydneyuni-adv”

  4. In the Home Page, click the Service Portal link. A new tab/window will open. If not yet logged in Service Portal, the login page will be presented; otherwise, the user is taken directly to the Service Portal page where the user can start creating case.

Expected Result:

In step #4, the URL of the newly opened tab/window should have the same sub-domain as the internal Salesforce page (Affinaquest), as noted in Step #3, followed by “.sandbox.my.site.com” if in SIT/UAT, or “.my.site.com” if in PROD.

Screenshots:

  • No labels