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

May R2 Fortnightly TAP Release

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 73 Next »

Production Release Date:

List of Jira tickets for Deployment: https://sydneyuni.atlassian.net/projects/TAPSS/versions/23027/tab/release-report-all-issues

Pre-Deployment Steps

  • Prepare Main package containing the following JIRAs (Ehanced Domain, TAPs, WB/Hogwarts). Here’s the source Bitbucket Branch: release/TAP-May-R2-Release-Package
  • Run validation in Bitbucket
    • Merge each branch approved for PROD Deployment to the Release branch for release/TAP-May-R2-Release-Package
    • Navigate to the release branch - release/TAP-May-R2-Release-Package and click the Create Pull Request button
    • Add the necessary approvers, and click Create Pull Request
    • The Validation Pipeline will run in the background. When the pipeline has no errors, it is ready for approval.
    • Once approved, merge the pull request. Merging to the Master branch will not trigger auto-deployment. Proceed to the Actual Deployment Steps

Combined Deployment Package / Components in Deployment

TAP May R2 Release Package merge commit ID: https://bitbucket.org/sydneyuni/uos-sfdx/commits/a1486927aa2f70bb0c9d1aaa168aadfb04624dff

TAP R2 Release Package ASR Profile merge commit ID: https://bitbucket.org/sydneyuni/uos-sfdx/commits/655742c5e1928aa9ef6bb0d2d33f834caa639d24

Actual Deployment Steps

  • Login to PROD. Go to Setup>Deployment Status. Click Quick deploy on validated package
  • Enable Enhanced Domain in PROD. Go to Setup>Company Settings>My Domain. Check the “Use enhanced domains” checkbox

Post Deployment Technical Validation Steps

  • For Close Batch Interim fix:
    • Verify if the following components are deployed:
      • USYD_AQBBatch_Trigger.trigger
      • USYD_AQBBatchTriggerHandler.cls
      • USYD_AQBBatchTriggerHandlerTest.cls
      • USYD_TriggerHandlerBase.cls
      • USYD_TriggerHandlerBaseTest.cls
      • USYD_Trigger_Setting__mdt
        • All_Settings.listView
        • After_Delete__c.field
        • After_Insert__c.field
        • After_Undelete__c.field
        • After_Update__c.field
        • Before_Delete__c.field
        • Before_Insert__c.field
        • Before_Update__c.field
      • USYD_System_Config__c.object
        • Retry_AQB_Smart_Batch_Batch_Size__c.field
        • Retry_AQB_Smart_Batch_On_Close_Error__c.field
        • Trigger_Handler_Logging__c.field
      • AQB__Batch__c.USYD_Batch_Closing_Retried__c.field
      • USyd_Application_Log__c.SmartBatch_Retry_Logs.listView
      • USYD_Trigger_Setting.USYD_ALL_TRIGGERS.md
      • USYD_Trigger_Setting.USYD_AQBBatch_Trigger.md
      • USYD_Trigger_Setting.USYD_TestClassConfig_DO_NOT_DELETE.md
  • Verify if Create a link to a Third Party Pledge Process Builder is turned OFF
  • Verify if USYD System Config custom settings is deployed.
  • For Enhanced Domain, verify the following:
    • Verify if the items listed here are deployed Enhanced Domain: List of Hard-coded URLs . Check at leaset one email temlate, flow and weblinks to verify if the dynamic formula for URL is there
    • Change the hyperlink on 3 Hogwarts Email Template
      • 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
  • For Swathi’s items, verify the following
    • TAPSS-260 - Batch Item has field history enabled now and batch history related list added to all the record type pages
    • TAPSS-222 - Two validation rules at Opportunity level “USYD_Email_Required “ & “USYD_Email_Required_ReceiptDeliveryEmail”
    • TAPSS-906 - Created new CASE fields:

  • Notified of Death by (free form text)

  • Corroborated Death Date (date format)

  • Date of Death (date format)

  • Date of Death Precision (picklist)

  • Date of Death Notification (date format)

Field history tracking enabled for the below new fields

  • Corroborated Death Date (date format)

  • Date of Death (date format)

  • Date of Death Precision (picklist)

  • TAPSS-912 - New version of the flow with new field and mapping along with URL change as part of enhanced domain hard code URL changes “NewCOA”
  • TAPSS-262 - Below are the new components

  1. Validation Rule: USYD_ChartOfAccountType_Change_Rule (Opportunity)

  2. Flow: USYD_OpportunityBeforeSave (Opportunity)

  3. New fields : AQB__OpportunityComponent__c.USYD_ProposedDesignationName__c & Opportunity.USYD_OppCompWithPendingAccount__c

Field access provided to below permissionsets and profile

  • Admin (Profile)

  • USyd_Opportunity_CRUD (permissionset)

  • AQC_Opportunity_to_Gift (permissionset)

  • TAPSS-239 - Deactivated picklist value “Advise Opportunity Owner when ready to collect" at Opportunity-AQC_ReceiptDelivery__c field
  • TAPSS-240 - New validation rule at Opportunity - “USYD_TypeRequired” & “USYD_SubTypeRequired”
  • TAPSS-901 - “Separate Utility” picklist value in the field “Void Notation” picklist should be available for all Record Types in Transaction object.
  • TAPSS-1181 - Record Type Gift In Will at Opportunity level should have the value “GIW Tick Box in Error” available in the field Loss_Reason__c
  • TAPSS-1185 - Opportunity Approval Process “GiftImplementationHandOver” Approval Step should have below users only

  • Duysal Artan

  • Genevieve Reeves

  • Cate Parsons

  • Jane Gordon

  • TAPSS-1060 - Three new flows : Usyd_Reopen_an_Alumni_Census_case_when_incoming_message_received, Usyd_Email_message_main_flow, USYD_Subflow_Custom_Case_Inbound_Email_Notification_Flow(WB flow)
  • Deactivate Flow: Usyd_Update_case_status_when_closed_case_receives_email
  • For WellBeing items, verify the following
    • SPI1-3945 - Getting issue details... STATUS
      • Verify if the Safer Communities Cases list view is deployed
      • Sexual Misconduct Cases should not be visible
    • SPI1-3882 - Getting issue details... STATUS
      • Verify if USYD_Subflow_Custom_Case_Inbound_Email_Notification_Flow.flow is deployed
      • Verify if WB_New_Email_Notification.notiftype custom notification is deployed
  • For Hogwart TAPSS-895 - Getting issue details... STATUS , verify if the following TASK validation Rules has been updated with filter on Record Type=”Milestone”
    • Milestone_RecurrenceFrequency
    • Milestone_RecurrenceLessThan2
    • Milestone_RecurrenceNumber
    • Milestone_Require_Resolution_Date
    • Milestone_Require_Resolution_Note
  • TAPSS-1083 - verify if new field Inclination can be seen below Interest Type with picklist values as requested in the ticket. Interest group has been moved to the system information.
  • TAPSS-1084 - verify if the new version of “USYD_Update_Legal_&_Gift_Recognition_Credit_Percentage” flow is deployed
  • TAPSS-1086 - verify if USYD Lightning Organization ASR Layout in Account object is deployed
  • TAPSS-1087 - verify if the components are deployed and updated. Pls refer here TAP-1108: MS - Creating a Pledge Payment Status field on Transaction object
  • TAPSS-259 - verify if the components are deployed and updated. Pls refer here TAP-1304: MS - Add validation rule
  • TAPSS-261 - verify if the components are deployed and updated. Pls refer here TAP-1303: Update Batch Logic

  • No labels