Simply Say NO to Onerous-Coded ID

Final Up to date on October 31, 2022 by Rakesh Gupta

Huge Thought or Enduring Query:

• How will you keep away from exhausting coding of ID in Salesforce Circulation? 

Goals:

This weblog submit will assist us to know the next

• Perceive the way to use customized Labels to keep away from exhausting code of ID within the Circulation
• Perceive the way to use Customized Settings to keep away from exhausting code of ID within the Circulation
• Perceive the way to use Customized Metadata Sorts to keep away from exhausting code of ID within the Circulation

Donna Serdula is working as a System administrator at Gurukul On Cloud (GoC). She has acquired a requirement from the administration at any time when an account is created for Business Not For Revenue, auto-create a case and assigns it to Nonprofit Specialists queue to confirm the group’s nonprofit standing. 

Automation Champion Strategy (I-do):

Sure, it’s typically a good suggestion to hard-code values (for instance, whereas studying Apex or Salesforce Circulation or exhausting code Pie worth i.e. 3.14), however there’s no easy rule as to when; it relies upon utterly on context. In case you’re exhausting coding the worth of the earth’s gravitational fixed, nobody’s going to care. In case you exhausting code the document ID (Queue, Group or Salesforce document Id, and many others.), you’re in for bother. 

Time and time once more, I see Apex code or Flows that include hard-coded Ids, whether or not it’s the Description area, a consumer ID, or perhaps a group ID, and many others. The issue with exhausting coding IDs is that any adjustments have to be made to the Circulation itself, check once more, after which deploy to manufacturing org.

The document IDs can change, for instance between a sandbox and a manufacturing atmosphere. It may be attainable {that a} queue (Nonprofit Specialists) has a distinct ID in a sandbox and a manufacturing org. 

Now you may refer the Nonprofit Specialists queue id whereas making a case by means of Salesforce Circulation.

The issue with this strategy (Onerous-coding queue ID) is, If you’re creating within the Sandbox, the IDs of the newly created Queue will change while you get to Manufacturing, and it’s important to do the rework. 

–> As per Salesforce greatest apply, everybody will counsel you don’t Hardcode IDs, Query for them. It’s at all times good to observe Salesforce greatest practices the place attainable. 

So What Subsequent? Find out how to Keep away from Onerous coding of IDs in Flows? 

A number of the methods to keep away from hard-coding are as follows

1. Customized Label: – Customized labels are customized textual content values that may be accessed from Apex courses, Visualforce pages, Flows, or Lightning elements. Whereas deploying a customized label, its information additionally will get deployed. To keep away from surprising habits be sure to replace the customized label worth post-deployment.   
2. Customized Setting: – Customized Settings are variables that you just use in your code however set and modify exterior of your code. Customized settings are cached. It’s particularly helpful to retailer info that might be typically accessed from Apex code or Circulation as it should carry out higher than a customized object. It doesn’t rely in opposition to SOQL limits when fetched. The customized setting doesn’t convey information over while you deploy them.
3. Customized Metadata Sort: – Customized Metadata Sorts are much like Customized Settings. Whereas deploying a customized metadata kind, its information additionally will get deployed. 

Earlier than discussing the answer, let me present you a diagram of a Course of Circulation at a excessive degree. Please spend a couple of minutes going by means of the next Circulation diagram and understanding it. Let’s start constructing this automation course of.

Guided Follow (We-do):

There are 2 steps to unravel Donna’s enterprise requirement utilizing After-Save Document-Triggered Circulation. We should:

1. Create a Nonprofit Specialists Queue
2. Salesforce Circulation Steps:
   1. Outline Circulation properties
   2. Formulation to find out whether or not the document is created or up to date
   3. Add a choice aspect to test account trade
   4. Add a get document aspect to search out queue Id
   5. Add a choice aspect to test the queue discovered or not
   6. Add a create data aspect to create a brand new case

Step 1: Making a Queue Nonprofit Specialists

1. Click on Setup.
2. Within the Consumer Interface, kind Queues.
3. Click on on the New button.
4. Enter Label the Queue Title will auto-populate. 
5. Click on Save.

Step 2.1: Outline Circulation Properties

1. Click on Setup.
2. Within the Fast Discover field, kind Flows.
3. Choose Flows, then click on on the New Circulation.
4. Choose the Document-Triggered Circulation choice, click on on Create and configure the circulation as follows:
   1. Object: Account
   2. Set off the Circulation When: A document is created or up to date
   3. Set Entry Standards
      1. Situation Necessities: None

   4. Optimize the Circulation For Motion and Associated Data

5. Click on Accomplished.

Step 2.2: Formulation to Decide Whether or not the Consumer is Created or Up to date

1. Underneath Toolbox, choose Supervisor, then click on New Useful resource to find out whether or not the document is new or outdated.
2. Enter the next info:
   1. Useful resource Sort: Formulation
   2. API Title: forB_IsNew
   3. Information Sort: Boolean
   4. Formulation: IsNew()

3. Click on Accomplished.

Step 2.3: Add a Determination Ingredient to Examine the Account Business

We’ll use the Determination aspect to test whether or not the account trade is Not For Revenue.

Step 2.4: Add a Get Document Ingredient to Discover Queue Id For Nonprofit Specialists

The following step is to search out the Nonprofit Specialists Queue.

1. On Circulation Designer, under the Not For revenue node, click on on the +icon and choose the Get Data aspect.
2. Enter a reputation within the Label area; the API Title will auto-populate.
3. Choose the Document Group object from the dropdown record.
4. Choose All Situations Are Met (AND). 
5. Set Filter Situations
   1. Row 1:
      1. Subject: Title
      2. Operator: Equals
      3. Worth: Nonprofit Specialists
         

   2. Click on Add Situation
   3. Row 2:
      1. Subject: Sort
      2. Operator: Equals
      3. Worth: Queue

6. How Many Data to Retailer:
   1. Choose Solely the primary document

7. Find out how to Retailer Document Information:
   1. Select the choice to Robotically retailer all fields. 

8. Click on Accomplished.

Step 2.5: Add a Determination Ingredient to Examine the Queue from the Document Variable

Now we are going to use the Determination aspect to test the Document Variable from step 2.4 to search out if it returns the queue or not.

1. On Circulation Designer, click on on the +icon and choose the Determination aspect.
2. Enter a reputation within the Label area; the API Title will auto-populate.
3. Underneath End result Particulars, enter the Label the API Title will auto-populate.
4. Situation Necessities to Execute End result: All Situations Are Met (AND)
   1. Row 1:
      1. Useful resource: {!Get_Queue}
      2. Operator: Is Null 
      3. Worth: {!$GlobalConstant.False}

   2. Click on Accomplished.

Step 2.6: Create Data – Create a Case and Assign it to Nonprofit Queue

To create a case and assign it to Nonprofit Specialists queue, we are going to use Create Data aspect. 

1. On Circulation Designer, click on on the +icon and choose the Create Data aspect.
2. Enter a reputation within the Label area; the API Title will auto-populate.
3. Enter the next info:
   1. How Many Data to Create: One
   2. Find out how to Set the Document Fields: Use separate sources, and literal values
   3. Object: Case
   4. Set Subject Values for the Case
      1. Row 1:
         1. Subject: Standing
         2. Worth: New

      2. Click on Add Subject
      3. Row 2:
         1. Subject: OwnerId
         2. Worth: {!Get_Queue.Id}
            

      4. Click on Add Subject
         
      5. Row 3:
         1. Subject: CurrencyIsoCode
         2. Worth: USD
            

      6. Click on Add Subject
         
      7. Row 4:
         1. Subject: Description
         2. Worth: Confirm Group’s Nonprofit Standing
            

      8. Click on Add Subject
         
      9. Row 5:
         1. Subject: AccountId
         2. Worth: {!$Document.Id}
            

4. Click on Save.

In the long run, Donna’s Circulation will appear like the next screenshot:

As soon as every thing appears to be like good, carry out the steps under: 

1. Click on Save.
2. Enter the Circulation Label the API Title will auto-populate.
3. Click on Present Superior.
4. API Model for Working the Circulation: 56
5. Interview Label: Don’t Onerous Code Id {!$Circulation.CurrentDateTime}
6. Click on Save. 

Nearly there! As soon as every thing appears to be like good, click on the Activate button.  

Proof of Idea

Now onwards, if a enterprise consumer creates an account with Business Not For Revenue, the record-triggered circulation will robotically create a brand new case. It’s time to check out the method.

1. Navigate to the Account tab, and create a brand new account for Business Not For Revenue, as proven within the following screenshot:
2. As soon as executed, click on on the Save button. It should open the account element web page and test case associated record, as proven within the following screenshot:

Formative Evaluation:

I wish to hear from you!

What’s one factor you realized from this submit? How do you envision making use of this new data in the actual world? Be at liberty to share within the feedback under.