Year: 2018

Happy New Year and Keep Learning

Once again, the start of a brand new year has come upon us. As we enter into new possibilities, may we all be reminded that we have the ability to be, do, and have anything that we want; that there are no mistakes, only lessons; and that the love and happiness we seek is already within our grasp.  It’s easy to make resolutions and renew our commitments.As we begin 2019, my prayer is that we continue to grow and find the space within ourselves to know, beyond all doubt, that there is nothing more that we need to do in order to be complete. We don’t need a new exercise plan, more money, a better job, a new car or a bigger house. All we need is a willingness to allow ourselves to feel good and to be at peace in the present moment. All we need is gratitude for all that we have, and all that we have had the pleasure to be and to experience. That is the starting point from which all other things will flow into our existence.Thank you for the wonderful support that you have given me through the past year! Wishing you a wonderful new year!2018 was great journey for me both professionally and personally. I would like to share some really important moments -I left Cognizant and joined Appirio Inc., a Wipro...

Read More

SalesforceDX : Explaining Scratch Org Definition File

Scratch Org definition file is getting used to create the shape of your scratch org. I would say it is the blueprint of your scratch org. You can use this definition file to create multiple scratch org from your repository.Scratch org definitions come from JSON text files that are stored in your project’s repository and directory structure. When an SFDX project is first created, it comes with a config/project-scratch-def.json file that defines an extremely basic org “shape” for an empty scratch org.That default scratch org likely looks nothing like your production org. You can use it for developing functionality that isn’t dependent on your org’s settings, or you can customize it using the settings that are available as part of the configuration file, or you can script your process to perform Metadata API deploys or other API actions to control settings that DX does not support yet.Ideally, the combination of your DX source code (including all your programmatic and declarative customization) with your scratch org definition gets you close enough to Prod instance.This definition file contains three main important information about your scratch org.Which Edition? As of Winter’19, it supports Developer, Enterprise, Group or ProfessionalAdd-on features: Functionalities you want to include while creating the scratch org like communities, StateAndCountryPicklist, LiveAgent etc.Settings: Org and Feature settings used to configure Salesforce products, such as nameSettings, ideaSettings, caseSettings, omniChannelSettings.Let’s dig into a Scratch Org definition...

Read More

Action Plan in Financial Services Cloud || Winter ’19 New Feature

In Winter ’19 release, Salesforce introduced Action Plans for Financial Services Cloud. It captures repeatable tasks in templates and then automate the task sequences with an action plan.Example: Processing Loan application, Customer on-boarding process etc. It will also give you the option to create reports and dashboards to monitor progress and ensure compliance.It consists of three parts -Action Plan Template: Power consistent customer experiences with configurable task templates.Process Automation: Increase productivity by automatically generating tasks with due dates and role based assignment.Plan Execution: Drive collaboration and complaint task completion with analytics and enforcement of required tasks.Let’s explain in details -Action Plan TemplateAn action plan template is nothing but a list of tasks to complete a business process. In a template, each task is given a priority, the deadlines (the number of days in which it should be completed – data offset), and who is responsible. Then this action plan template is used to create action plans with each task assigned to a user with a completion date.Below picture will give you a great view of Action Plan Template and Action Plan -Now let’s start creating one Action Plan:Pre-requisitePermission Set: You need to assign permission set – ActionPlans to the users. Without this permission set, you will not be able to assign action plan task to those users.Extra Permission: You can provide below standard object permission so that users can...

Read More

Apex Code to Assign Territories to Opportunities

Assigning Territories to Opportunities can be done manually, but there is an option by which you can automate this process. This blog post is all about writing Apex class to automate the Territory assignment to Opportunity record.Before I start explaining the Apex code, let me explain two important objects -Territory2Type: This represents the category of Territories(Territory2). Every territory must have a Territory2Type. The important field within this object is Priority, which is used in Opportunity filter to assign Territory to Opportunity.ObjectTerritory2Association: This represents the association between Territory and Object record, which is Account. This is available only if Enterprise Territory Management is enabled.The Apex code is written here in the Salesforce Developer’s guide. The logic is as follows -If the Opportunity’s Account record is assigned to no Territory, then Opportunity’s territory2Id field will be null.If the Opportunity’s Account record is assigned to 1 Territory, then Opportunity’s territory2Id field will be assigned to same Territory record.If the Opportunity’s Account record is assigned to more than 1 Territories, then Opportunity’s territory2Id field will be assigned to that territory record which is having highest priority.If multiple territories are having the same priority, then Opportunity’s territory2Id field will null.Once you have the apex class written, you can configure the Opportunity Territory assignment filter by going into Setup -> Territory Settings and there providing the apex class name. The screenshot is given below -Few important...

Read More

Getting Started with Salesforce DX

What is Salesforce DX?Salesforce DX is a way to shift your development lifecycle and to manage your source of truth. But don’t consider Salesforce DX is going to do any magic, as a developer/release manager/lead you need to come up with your own strategy to manage your releases, other challenges like code conflict, urgent fix etc.Why we need Salesforce DX?I think the best way to answer this is with some real time scenarios.Recently I was working with one of my customer who was having multiple sandboxes like DEV, SIT, QAT, UAT. A typical scenario. Now every time there was any kind of production issues, development team tried to find out the root cause and also tried to find out if the issue was due to some of the recent releases. But since all sandboxes were having the same code as Production, there was no way to find out previous code base. So in this situation normally developer request for a new sandbox with production code and fix the issue. This type of development is known as “Org Based Development”.But consider if the code was present in some source control repository then developer can easily get the previous code base, compare code between recent releases (basically comparing between master and branches). But does that really solve our problem? Somehow, but not fully. So basically we need to create an org...

Read More

Archives