Bcmohad 25700 1 Update Report

[lilianenassar-bib]

Description

Bcmohad 25700 1 Update Report

Fixes # (Bcmohad 25700)

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

List high-level changes as bullet items

POST DEPLOYMENT STEPS TO RUN IN UAT,PROD ( QA ALREADY DONE)

To Update historical Data for Field Case_Team_Size__c on Case Object follow below steps:

1) if ticket BCMOHAD-25699 has been already deployed to UAT/PROD Comment out all reference to : ICY_CaseMember_Controller.updateReferralTeamMemberIds in trigger Case_Member.trigger ( 2 occurences : Line 16 ,line 29)

2) Run below Query to get the Extract the Data needed: Select Id,ICY_StatusC from case_member__C where ICY_Casec <> null

3) Run Data Import/update on same file extracted above

4) Remove the commented lines in step 1 (Line 16 ,line 29) in Trigger Case_Member.trigger

Checklist:

• [X] My code follows the style guidelines of this project
• [X] I have performed a self-review of my own code
• [X] I have commented my code, particularly in hard-to-understand areas
• [X] I have made corresponding changes to the documentation
• [X] My changes generate no new warnings
• [X] I have added tests that prove my fix is effective or that my feature works
• [X] New and existing unit tests pass locally with my changes
• [X] Any dependent changes have been merged and published in downstream modules

[cgijeffolsen]

The post-deployment step appears to be updating code directly in Production -- would this be better served by a dataload switch in the code as a custom setting? Has this been considered? "if ticket BCMOHAD-25699 has been already deployed to UAT/PROD Comment out all reference to : ICY_CaseMember_Controller.updateReferralTeamMemberIds in trigger Case_Member.trigger ( 2 occurences : Line 16 ,line 29)" @lilianenassar-bib @RanadheerRG @NataliaNikishina

[lilianenassar-bib]

@cgijeffolsen this is a one time load that will happen to update the historical data and since we don't have the solution implemented as proposed yet Plus we are tight on estimates and also it's not the trigger that we are deactivating it's references to a method within the trigger therefore it was proposed to happen by deployment from VSCODE temporary .