function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Radha Rathinavel PandianRadha Rathinavel Pandian 

How to write Trigger handler

Hi ,
How to write the trigger handler for my below code,

trigger CaseLegalUpdate on Legal_Description__c (after insert, after update) {
List<Id> legalId = new List<Id>();
for(Legal_Description__c lg : Trigger.new)
{
if(lg.Case__c!=NULL)
{
legalId.add(lg.Case__c);
}
}

List<Case> caseRecord = new List<Case>();
if(legalId!=NULL && legalId.size()>0)
{
for(Case c:[SELECT id,Check_Legal_Description__c,RecordType.Name FROM Case WHERE id IN:legalId])
{
c.Check_Legal_Description__c=true;
caseRecord.add(c);
}
update caseRecord;
}
}
Best Answer chosen by Radha Rathinavel Pandian
Amit Chaudhary 8Amit Chaudhary 8
Hi Radha,

Please check below post to learn about Trigger Framwork.
1) http://amitsalesforce.blogspot.in/2015/06/trigger-best-practices-sample-trigger.html

Create Trigger Like below
trigger CaseLegalUpdate on Legal_Description__c (after insert, after update) { 
    if (trigger.isAfter ){
		if( trigger.isInsert || trigger.isUpdate) 
		{
			LegalDescriptionHandler.CaseLegalmethod(trigger.new);
		}
	}	
}

Handler like below
public class LegalDescriptionHandler
{

	public static void CaseLegalmethod(List<Legal_Description__c> newLegal)
	{
		List<Id> legalId = new List<Id>();
		for(Legal_Description__c lg : newLegal)
		{
			if(lg.Case__c!=NULL)
			{
				legalId.add(lg.Case__c);
			}
		}

		List<Case> caseRecord = new List<Case>();
		if(legalId!=NULL && legalId.size()>0)
		{
			for(Case c:[SELECT id,Check_Legal_Description__c,RecordType.Name FROM Case WHERE id IN:legalId])
			{
				c.Check_Legal_Description__c=true;
				caseRecord.add(c);
			}
			update caseRecord;
		}	
	}
}


Let us know if this will help you
 

All Answers

Prashant Pandey07Prashant Pandey07
Hi Radha,

You can try with below code.
 
public class CaseLegalUpdateHelper{

public static void CaseLegalmethod(List<Legal_Description__c> newLegal){

List<Id> legalId = new List<Id>();
for(Legal_Description__c lg : newLegal)
{
if(lg.Case__c!=NULL)
{
legalId.add(lg.Case__c);
}
}
List<Case> caseRecord = new List<Case>();
if(legalId!=NULL && legalId.size()>0)
{
for(Case c:[SELECT id,Check_Legal_Description__c,RecordType.Name FROM Case WHERE id IN:legalId])
{
c.Check_Legal_Description__c=true;
caseRecord.add(c);
}
update caseRecord;
}
}
}

***************Trigger*************
 
trigger CaseLegalUpdate on Legal_Description__c (after insert, after update) { 
    if (trigger.isAfter && (trigger.isInsert || trigger.isUpdate)) {
        CaseLegalUpdateHelper.CaseLegalmethod(trigger.new);

    }


Note- I have not compiled this code..let me know if you have any issue.

--
Thanks,
Prashant
Amit Chaudhary 8Amit Chaudhary 8
Hi Radha,

Please check below post to learn about Trigger Framwork.
1) http://amitsalesforce.blogspot.in/2015/06/trigger-best-practices-sample-trigger.html

Create Trigger Like below
trigger CaseLegalUpdate on Legal_Description__c (after insert, after update) { 
    if (trigger.isAfter ){
		if( trigger.isInsert || trigger.isUpdate) 
		{
			LegalDescriptionHandler.CaseLegalmethod(trigger.new);
		}
	}	
}

Handler like below
public class LegalDescriptionHandler
{

	public static void CaseLegalmethod(List<Legal_Description__c> newLegal)
	{
		List<Id> legalId = new List<Id>();
		for(Legal_Description__c lg : newLegal)
		{
			if(lg.Case__c!=NULL)
			{
				legalId.add(lg.Case__c);
			}
		}

		List<Case> caseRecord = new List<Case>();
		if(legalId!=NULL && legalId.size()>0)
		{
			for(Case c:[SELECT id,Check_Legal_Description__c,RecordType.Name FROM Case WHERE id IN:legalId])
			{
				c.Check_Legal_Description__c=true;
				caseRecord.add(c);
			}
			update caseRecord;
		}	
	}
}


Let us know if this will help you
 
This was selected as the best answer
Radha Rathinavel PandianRadha Rathinavel Pandian
Thank you Both Prashant and Amit .

Both are Best Answers. It Works Excellently :-)
Radha Rathinavel PandianRadha Rathinavel Pandian
Can anyone assist me how to write the test class for the above code?
Amit Chaudhary 8Amit Chaudhary 8
I will recommend you to start using trailhead to learn about test classes
1) https://trailhead.salesforce.com/modules/apex_testing

Also please check below post
1) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_qs_test.htm
2) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_example.htm

sample Test classes
1) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html

Please follow below salesforce Best Practice for Test Classes :-

1. Test class must start with @isTest annotation if class class version is more than 25
2. Test environment support @testVisible , @testSetUp as well
3. Unit test is to test particular piece of code working properly or not .
4. Unit test method takes no argument ,commit no data to database ,send no email ,flagged with testMethod keyword .
5. To deploy to production at-least 75% code coverage is required
6. System.debug statement are not counted as a part of apex code limit.
7. Test method and test classes are not counted as a part of code limit
9. We should not focus on the  percentage of code coverage ,we should make sure that every use case should covered including positive, negative,bulk and single record .
Single Action -To verify that the the single record produces the correct an expected result .
Bulk action -Any apex record trigger ,class or extension must be invoked for 1-200 records .
Positive behavior : Test every expected behavior occurs through every expected permutation , i,e user filled out every correctly data and not go past the limit .
Negative Testcase :-Not to add future date , Not to specify negative amount.
Restricted User :-Test whether a user with restricted access used in your code .
10. Test class should be annotated with @isTest .
11 . @isTest annotation with test method  is equivalent to testMethod keyword .
12. Test method should static and no void return type .
13. Test class and method default access is private ,no matter to add access specifier .
14. classes with @isTest annotation can't be a interface or enum .
15. Test method code can't be invoked by non test request .
16. Stating with salesforce API 28.0 test method can not reside inside non test classes .
17. @Testvisible annotation to make visible private methods inside test classes.
18. Test method can not be used to test web-service call out . Please use call out mock .
19. You can't  send email from test method.
20.User, profile, organization, AsyncApexjob, Corntrigger, RecordType, ApexClass, ApexComponent ,ApexPage we can access without (seeAllData=true) .
21. SeeAllData=true will not work for API 23 version eailer .
22. Accessing static resource test records in test class e,g List<Account> accList=Test.loadData(Account,SobjectType,'ResourceName').
23. Create TestFactory class with @isTest annotation to exclude from organization code size limit .
24. @testSetup to create test records once in a method  and use in every test method in the test class .
25. We can run unit test by using Salesforce Standard UI,Force.com IDE ,Console ,API.
26. Maximum number of test classes run per 24 hour of period is  not grater of 500 or 10 multiplication of test classes of your organization.
27. As apex runs in system mode so the permission and record sharing are not taken into account . So we need to use system.runAs to enforce record sharing .
28. System.runAs will not enforce user permission or field level permission .
29. Every test to runAs count against the total number of DML issued in the process .

Let us know if this will help you

 
Radha Rathinavel PandianRadha Rathinavel Pandian

Thank you for the great clarrication  Amit