WIXLIB

Chapter 4: Approval Process ObjectsRemarksApproval Process is a very amazing feature in Salesforce to automate the business process. Anapproval process is a set of the steps necessary for a particular record to be approved or rejectedby approver or set of approvers.A step can apply to all records included in the process, or just records that meet certainadministrator-defined criteria. An approval process also specifies the actions to take when arecord is approved, rejected, recalled, or first submitted for approval.ProcessDefinition and ProcessNode objects act as a template and store the masterconfigurations for Approval Process itself.https://riptutorial.com/10

ExamplesProcessDefinitionRepresents the definition of a single approval process. Use this object to read the description of anapproval process. The definition is read-only. We can not modify the record created inProcessDefinition Object. But we can describe, query, search and retrieve the approval processesinformation. Query SELECT ptutorial.com/11

FROM ProcessDefinitionThe records are created when we create a new approval process using Salesforce user interfaceof Approval Process.ProcessNodeRepresents the Process Steps created for particular approval process(ProcessDefinition). Thisobject is used to read the description of process step. In simple words ProcessNode recordsdescribes a step in a process definition. We can describe, query, search and retrieve the approvalprocesses Steps. Query SELECT ,SystemModstamp,Id,FROM ProcessNodeAs we can see ProcessDefinitionId field is acting like a foreign key which is referringProcessDefinition Object or Table for which steps or process nodes are created. This object isalso read only as ProcessDefinition Object.ProcessInstanceRepresents an instance of a single, complete approval process. ProcessInstance record is createdevery time for particular object record which is submitted for approval. Its is also read-only object.We can describe, query and retrieve the approval processes Instance. Query SELECT emModstamp,TargetObjectId FROM ProcessInstanceAll ProcessInstance fields are automatically populated once the record is submitted for approval,with two exceptions fields: CompletedDate and LastActorId that are populated only after theapproval process instance is complete. The ProcessDefinitionId field is the reference or foreignkey ID of the ProcessDefinition Object.ProcessInstanceStep & ProcessInstanceWorkitemBoth objects ProcessInstanceStep & ProcessInstanceWorkItem are instances of process stepsthat are created for particular ProcessInstance. ProcessInstanceStep represents a step instance inan approval process (ProcessInstance) on which users has already acted andProcessInstanceWorkItem represents a step instance in an approval process(ProcessInstance) onwhich is pending and users has to perform some action next on it. We can describe, query andretrieve the approval processes steps and workItems.https://riptutorial.com/12

Query SELECT p FROM ProcessInstanceWorkitemSELECT pStatus,SystemModstamp FROM ProcessInstanceStepProcessInstanceHistory*The ProcessInstanceHistory is the object which is neither searchable nor queryable & this is theread-only object which shows all steps and pending approval requests associated with anapproval process (ProcessInstance). But we can use this object to replicate the related listfunctionality of the Salesforce user interface for approval processes which will be shown in mynext blog post soon. We can use ProcessInstanceHistory for a single read-only view of the bothProcessInstanceStep and ProcessInstanceWorkitem objects. We can queryProcessInstanceHistory by querying it in a nested soql query on the parent ProcessInstanceobject. The nested soql query references StepsAndWorkitems, which is the child relationshipname for ProcessInstanceHistory in the ProcessInstance object. This is very useful object to solvevarious business problems. Query SELECT CompletedDate, CreatedById, bmittedById,SystemModstamp,TargetObjectId, (SELECT ID, ProcessNodeId, stanceId,RemindersSent,CreatedDateFROM StepsAndWorkitems ) FROM ProcessInstanceRead Approval Process Objects online: ovalprocess-objectshttps://riptutorial.com/13

Chapter 5: Custom SettingsRemarksIntroductionUnlike custom objects which have records based on them, custom settings let you utilize customdata sets across your org, or distinguish particular users or profiles based on custom criteria. Thismeans, for example, that admins can edit hierarchy custom settings to deactivate Workflow /Validation Rules for single users or profiles, without having to switch them off for the whole org(see the Using Hierarchy Custom Settings To Disable Workflow / Validation Rules exampleabove).Validation rules commonly need to be disabled temporarily when: Code is updating old records, which were last edited before a validation rule was activated &therefore don't meet the newer rule's criteria. Code is inserting new records without the values required by a validation rule's criteria.Workflow rules commonly need to be disabled temporarily when: They would trigger an Email Alert or Field Update which would overwrite or interfere thechanges you are making to the record.Use of a custom setting grants admins some declarative control over code so one of the many usecases is that when utilized, they can make it unnecessary to deploy code in order to disabletriggers (see the Using Hierarchy Custom Settings To Disable Apex Code example above).A key benefit for developers is that custom setting's data is exposed in the application cache,which enables efficient access without the cost of repeated queries to the database. This data canthen be used by formula fields, validation rules, flows, Apex, and the SOAP API - see theSalesforce documentation.The limits & considerations for custom settings are documented here.List Custom SettingsIt is possible to create List Custom Settings too, common use cases include storing two-letter stateabbreviations, international dialing prefixes, and catalog numbers for products. HoweverSalesforce is now promoting the use Custom Metadata Types, instead of List Custom Settings.When you go to create a new Custom Setting, the following message will be displayedTip: Use Custom Metadata Types for App ConfigurationIf you're thinking of using list custom settings, consider using custom metadata typesinstead. Unlike list custom settings, you can migrate the records of custom metadatahttps://riptutorial.com/14

types using using packages or Metadata API tools.Custom Metadata Types have additional benefits vs List Custom Settings as described in thisanswer. And according to the lead developer of CMDs "There’s a lot more planned for custommetadata types than custom settings on steroids."ExamplesCreating & Managing Custom SettingsCreationTo create a Custom Setting, go to:ClassicSetup Develop Custom Settings NewLightningSetup Custom Code Custom Settings NewCreate your setting (see the Remarks later in this document for the differences between Hierarchy& List custom settings). You can ignore the Visibility picklist, unless you plan to deploy your settingin a managed package.To create your setting fields click the New button and follow the usual process for creating acustom field.ManagementOnce you have created your field(s) you can start configuring the setting by clicking the Managebutton.It's easier to manage the setting if you create a new view and include any fields that you'vecreated to give yourself a comprehensive overview of the setting, at a glance. The Setup Owner isthe user or profile that the setting applies to.To manage the setting at the org level, click the New button above the Default Organization LevelValue header (in red box below).To manage the setting at the user or profile level, click the New button in the blue box below.https://riptutorial.com/15

Using Hierarchy Custom Settings To Disable Workflow / Validation RulesCustom Settinghttps://riptutorial.com/16

Custom Setting FieldCustom Setting Field ValueWhen the field is checked the validation rule will be disabled, for the running user or in thishttps://riptutorial.com/17

example, their profile -The rule can also be disabled for a whole Salesforce org -Validation RuleAND(/* the below is the reference to the Val Rule Cntrlr c custom setting's checkbox fieldAll Opportunity Disabled c*/ Setup.Val Rule Cntrlr c.All Opportunity Disabled c FALSE,/* the below is the remainder of the validation rule's formula*/CloseDate TODAY())https://riptutorial.com/18

In the above rule, both pieces of criteria must evaluate to TRUE in order for the rule to be triggered.Since All Opportunity Disabled c checkbox will evaluate to TRUE when the running user's profile isSystem Administrator, the rule will evaluate to FALSE.Workflow RulesThe same approach can be applied in order to deactivate Workflow Rules.Using Hierarchy Custom Settings To Disable Apex CodeExplanationIn this example a simple Trigger has been created to change the Close Date of an Opportunity,that's about to be inserted or updated, to a date 10 days in the future.The Apex Controller custom setting's checkbox field enables the code to be disabled at the user /profile / org level.Apex Classtrigger CloseDateUpdate on Opportunity (before insert, before update) {Id userId;Apx Cntrlr c userApexController;Boolean userSetting;userId userinfo.getUserId();userApexController Apx Cntrlr c.getInstance(userId);userSetting userApexController.Close Date Update Disabled c;if (userSetting false) {for(Opportunity opp : Trigger.new) {opp.CloseDate date.today().addDays(10);}}}Unit Test@isTestpublic class CloseDateUpdateTest {@testSetupstatic void dataSetup() {Profile p [SELECT Id FROM Profile WHERE Name 'System Administrator' LIMIT 1];User u new User(LastName 'Test',Alias 't1',Email 'example@gmail.com',Username 'sotest@gmail.com',ProfileId p.Id,TimeZoneSidKey 'America/Denver',LocaleSidKey https://riptutorial.com/19

'en US',EmailEncodingKey 'UTF-8',LanguageLocaleKey 'en US');insert u;}static testMethod void testCloseDateUpdateEnabled() {User u [SELECT Id FROM User WHERE Username 'sotest@gmail.com'];// set the custom setting field to FALSE so that the trigger is not deactivatedApx Cntrlr c apexController new Apx Cntrlr c(SetupOwnerId u.Id,Close Date Update Disabled c false);upsert apexController;Opportunity[] opportunities1 new or(integer i 0; i 200; i ) {opportunities1.add(new Opportunity(Name 'Test Opp ' i,OwnerId u.Id,StageName 'Prospecting',CloseDate date.today().addDays(1),Amount 100));}insert opportunities1;}test.stopTest();List Opportunity opportunities2 [SELECT CloseDate FROM Opportunity];for(Opportunity o : ddDays(10), o.closeDate, 'CloseDateUpdatetrigger should have changed the Opportunity close date as it was not disabled by theapexController custom setting');}}static testMethod void testCloseDateUpdateDisabled() {User u [SELECT Id FROM User WHERE Username 'sotest@gmail.com'];// set the custom setting field to TRUE to deactivate the triggerApx Cntrlr c apexController new Apx Cntrlr c(SetupOwnerId u.Id,Close Date Update Disabled c true);upsert apexController;Opportunity[] opportunities1 new or(integer i 0; i 200; i ) {opportunities1.add(new Opportunity(Name 'Test Opp ' i,OwnerId u.Id,StageName 'Prospecting',CloseDate date.today().addDays(1),Amount 100));}insert opportunities1;}https://riptutorial.com/20

test.stopTest();List Opportunity opportunities2 [SELECT CloseDate FROM Opportunity];for(Opportunity o : ddDays(1), o.closeDate, 'CloseDateUpdate triggershould not have changed the Opportunity close date as it was disabled by the apexControllercustom setting');}}}Updating Hierarchy Custom Settings in Apex CodeYou may wish to update your custom setting's during the execution of your code, to switch offvalidation or workflow rules.In the below code, I have created a Schedulable Apex Class which will update the Close Date ofany Opportunities whose Close Date is less than or equal to 6 days from the current date,changing the date to 20 days in the future.I will use my Custom Setting Val Rule Cntrlr c to deactivate any validation rules which wouldprevent me from updating the Opportunities that meet my criteria.global class Scheduled OppCloseDateUpdate implements Schedulable {global void execute(SchedulableContext SC) {updOpportunityCloseDates();}global void updOpportunityCloseDates() {Id userId;Val Rule Cntrlr c setting;Boolean validationRulesAlreadyDisabled;List Opportunity processedOpps new List Opportunity ();Date d;// get running user's IduserId userinfo.getUserId();// retrieve Custom Setting status, for running usersetting Val Rule Cntrlr c.getInstance(userId);// if the setting field is false, update it to disable validation rulesif (setting.All Opportunity Disabled c false) {setting.All Opportunity Disabled c true;upsert setting;}// if the setting field was already true, there's no need to disable it// but it shouldn't be switched to false by this class once the process has beencompletedelse {validationRulesAlreadyDisabled true;}// execute code to manage business processhttps://riptutorial.com/21

d system.today().addDays(6);for(Opportunity o : [SELECT Id, CloseDateFROM OpportunityWHERE CloseDate :d// class only updates open OpportunitiesAND Probability 0 AND Probability 100]){o.CloseDate f (processedOpps.size() 0) {update processedOpps;}// reactivate validation rulesif (validationRulesAlreadyDisabled false) {setting.All Opportunity Disabled c false;upsert setting;}}}To make sure that my validation rules are being deactivated by the changes to my custom settingin my class, I have created a checkbox field Trigger Validation Rule c (which would not be visibleto users or added to page layouts) & a validation rule with this criteria:AND( Setup.Val Rule Cntrlr c.All Opportunity Disabled c FALSE,Trigger Validation Rule c TRUE,/* allow the above criteria to be met while inserting the Opportunities, without triggeringthe rule, in the @testSetup portion of the test */NOT(ISNEW()))I then set the checkbox field to true when creating my Opportunities so that the rules criteria wouldbe met, if the custom setting field is not edited by my code.@isTestprivate class WE ScheduledCloseDateUpdateTest {@testSetupstatic void dataSetup() {Profile p [SELECT Id FROM Profile WHERE Name 'System Administrator' LIMIT 1];User u new User(LastName 'Test',Alias 't1',Email 'example@gmail.com',Username 'sotest@gmail.com',ProfileId p.Id,TimeZoneSidKey 'America/Denver',LocaleSidKey 'en US',EmailEncodingKey 'UTF-8',LanguageLocaleKey 'en US');insert u;Val Rule Cntrlr c valRuleCntrlr new Val Rule Cntrlr c(SetupOwnerId u.Id,All Opportunity Disabled c false);https://riptutorial.com/22

upsert valRuleCntrlr;List Opportunity testOpps new List Opportunity ();// create the Opportunities that will be updated by the classfor(integer i 0; i 200; i ) {testOpps.add(new Opportunity(Name 'Test Opp Update' i,OwnerId u.Id,StageName 'Prospecting',CloseDate date.today().addDays(1),Amount 100,// set checkbox field to true, to trigger validation rules if they've not beendeactivated by classTrigger Validation Rule c true));}// create the Opportunities that won't be updated by the classfor(integer i 0; i 200; i ) {testOpps.add(new Opportunity(Name 'Test Opp Skip' i,OwnerId u.Id,StageName 'Prospecting',CloseDate date.today().addDays(15),Amount 100,Trigger Validation Rule c true));}insert testOpps;}// code required to test a scheduled class, us.apexcode.meta/apexcode/apex scheduler.htmfor more detailspublic static String CRON EXP '0 0 0 15 3 ? 2022';static testmethod void testCloseDateUpdates() {// execute scheduled classTest.startTest();String jobId System.schedule('ScheduleApexClassTest',CRON EXP,new Scheduled OppCloseDateUpdate());CronTrigger ct [SELECT Id, CronExpression, TimesTriggered, NextFireTimeFROM CronTriggerWHERE id :jobId];System.assertEquals(CRON EXP, ct.CronExpression);System.assertEquals(0, ct.TimesTriggered);System.assertEquals('2022-03-15 00:00:00', / test resultsInteger updateCount 0;Integer skipCount 0;List Opportunity opportunitys

Chapter 1: Getting started with Salesforce Remarks This section provides an overview of what salesforce is, and why a developer might want to use it. It should also mention any large subjects within salesforce, and link out to the related topics. Since the Documentation for salesforce is new, you may need to create initial versions of those related