Kitchener Canada Developer Group Event: Introduction to DevOps with Salesforce DX by René Winklmayer

Special thanks to our speaker, René Winklmayer, for the session on Introduction to DevOps with Salesforce DX.

Here comes the presentation and recording.

Presentation:

Kitchener Salesforce Developer Group Event - Introduction to dev ops with SalesforceDx from Sudipta Deb ☁

Recording:

Please register to Kitchener, Canada Developer Group for all our future events.

https://goo.gl/yLm9Sd

Share:

Read More

Understanding JavaScript Promises

Introduction to Promises

Dealing with asynchronous code? Promises is the way to deal with it without writing multiple callbacks. Promises were standardized and introduced in ES2015, but in ES2017 they have been superseded by async function. Understanding of Promises is the foundation of learning Async functions.

Way Promises work

Once a promise has been called, it always start with Pending state. At this point, caller function waits for the promise function to finish it's job and then return either in Resolved or Rejected state. But as we know Javascript executes in asynchronous mode, so caller function will still continue doing it's job in parallel with promise doing it's job.

Creating Promises

The Promise API exposes a constructor which you can use to create Promise -

const printSomething = (isValid) => {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      if (isValid) {
        console.log('Yes I am valid');
        resolve();
      } else {
        console.log('Sorry I am invalid');
      }
    }, 1000);
  });
}

Here promise is checking a the passed Boolean value isValid. If the isValid is true, then promise is returning resolved promise , other returning rejected promise.

Promise provides resolve and reject to return values to the calling function in case of success or error respectively.

Consuming Promises

Let's now consume the promise with below code -

const printSomething = (isValid) => {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      if (isValid) {
        console.log('Yes I am valid');
        resolve();
      } else {
        console.log('Sorry I am invalid');
      }
    }, 1000);
  });
}

printSomething(true)
  .then(() => printSomething(true))
  .then(() => printSomething(false));

Here I am calling printSomething function which is returning Promise either in Resolve or Reject state based on the function parameter isValid.

Here is the outcome -

Yes I am valid
Yes I am valid
Sorry I am invalid

You can execute the code here.

Chaining Promises

You can chain promises by returning result from one promise and then using the same in the next promise.

const printSomething = (name, textToAdd) => {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      var retValue = '';
      if (name != null) {
        retValue = name + ' ' + textToAdd;
      } else {
        retValue = textToAdd;
      }
      console.log(retValue);
      resolve(retValue);
    }, 1000);
  });
}

printSomething(null, 'Hello')
  .then((result) => printSomething(result, 'Sudipta'))
  .then((result) => printSomething(result, 'Deb'));

As you can see in the above example, I am using the result from the first promise which is "Hello" and the using the same in the second promise to append "Sudipta" with "Hello", thus returning "Hello Sudipta". Finally using this in the third promise to append "Deb", this returning "Hello Sudipta Deb"

Here is the result

Hello
Hello Sudipta
Hello Sudipta Deb

You can execute the code here.

Handling Errors

Handling error can be done by either returning Promise is reject mode or throwing an error.

Let's understand the below example with Reject returning an error.

const printSomething = (name, textToAdd) => {
  return new Promise((resolve, reject) => {
    try {
      setTimeout(() => {
        if (textToAdd == null) {
          reject(new Error('textToAdd can not be null'));
        } else {
          var retValue = '';
          if (name != null) {
            retValue = name + ' ' + textToAdd;
          } else {
            retValue = textToAdd;
          }
          console.log(retValue);
          resolve(retValue);
        }
      }, 1000);
    } catch (e) {
      reject(e);
    }
  });
}

printSomething(null, 'Hello')
  .then((result) => printSomething(result, 'Sudipta'))
  .then((result) => printSomething(result, 'Deb'))
  .then((result) => printSomething(result, null))
  .then((result) => printSomething(result, 'From Canada'))
  .catch(err => console.log('Error occured: ' + err.message));

In the above example, I am returning Reject promise with new Error. Then using the same with catch statement while consuming the Promise. Here is the output -

Hello
Hello Sudipta
Hello Sudipta Deb
Error occured: textToAdd can not be null

You can execute the code here.
Now let's modify the same example, where instead of returning Reject promise, I will throw the error. This is helpful to handle runtime error.

const printSomething = (name, textToAdd) => {
  return new Promise((resolve, reject) => {
    try {
      setTimeout(() => {
        if (textToAdd == null) {
          throw "textToAdd can not be null";
        } else {
          var retValue = '';
          if (name != null) {
            retValue = name + ' ' + textToAdd;
          } else {
            retValue = textToAdd;
          }
          console.log(retValue);
          resolve(retValue);
        }
      }, 1000);
    } catch (e) {
      reject(e);
    }
  });
}

printSomething(null, 'Hello')
  .then((result) => printSomething(result, 'Sudipta'))
  .then((result) => printSomething(result, 'Deb'))
  .then((result) => printSomething(result, null))
  .then((result) => printSomething(result, 'From Canada'))
  .catch(err => console.log('Error occured: ' + err.message));

One important fact is that reject DOES NOT terminate control flow like a return statement does. In contrast throw does terminate control flow.

Let's have the below code with reject

const printSomething = (name, textToAdd) => {
  return new Promise((resolve, reject) => {
    try {
      setTimeout(() => {
        if (textToAdd == null) {
          reject(new Error('textToAdd can not be null'));
        } else {
          var retValue = '';
          if (name != null) {
            retValue = name + ' ' + textToAdd;
          } else {
            retValue = textToAdd;
          }
          console.log(retValue);
          resolve(retValue);
        }
      }, 1000);
    } catch (e) {
      reject(e);
    }
  });
}

printSomething(null, 'Hello')
  .then((result) => printSomething(result, 'Sudipta'))
  .then((result) => printSomething(result, 'Deb'))
  .then((result) => printSomething(result, null))
  .then((result) => printSomething(result, 'From Canada'))
  .catch(err => console.log('Error occured: ' + err.message))
  .then(() => console.log('I will still execute even after the error'));

Output:

"Hello"
"Hello Sudipta"
"Hello Sudipta Deb"
"Error occured: textToAdd can not be null"
"I will still execute even after the error"

You can execute the code here. Here you can see that catch and then statement are getting executed even after reject promise return.

Now let's have the same code with throw statement

const printSomething = (name, textToAdd) => {
  return new Promise((resolve, reject) => {
    try {
      setTimeout(() => {
        if (textToAdd == null) {
          throw "textToAdd can not be null";
        } else {
          var retValue = '';
          if (name != null) {
            retValue = name + ' ' + textToAdd;
          } else {
            retValue = textToAdd;
          }
          console.log(retValue);
          resolve(retValue);
        }
      }, 1000);
    } catch (e) {
      reject(e);
    }
  });
}

printSomething(null, 'Hello')
  .then((result) => printSomething(result, 'Sudipta'))
  .then((result) => printSomething(result, 'Deb'))
  .then((result) => printSomething(result, null))
  .then((result) => printSomething(result, 'From Canada'))
  .catch(err => console.log('Error occured: ' + err.message))
  .then(() => console.log('I will still execute even after the error'));

Output:

"Hello"
"Hello Sudipta"
"Hello Sudipta Deb"
"Uncaught textToAdd can not be null (line 6)"

You can execute the code here. You see this time the catch and then statements are not getting executed. The reason is that throw statement terminate the control flow.

Promise.all()

Promise.all() will return a promise when all the promises are resolved. If one of the promise is failed, it will reject immediately with the error message from the failed promise irrespective of whether other promises are resolved or not.

Let's have this below example: 

var returnDouble = (value) => {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      if (value > 0) {
        resolve(value * 2);
      } else {
        reject(resolve);
      }
    }, 1000);
  });
};

var promisesToMake = [returnDouble(20), returnDouble(10), returnDouble(5)];
var finalPromise = Promise.all(promisesToMake);

finalPromise.then(function (results) {
  console.log('Final Result: ' + results);
});

Output:

"Final Result: 40,20,10"

You can execute the code here. With promise.all(), instead of three different returns, it will return one single promise once all the promises are resolved.

Now let's forcefully reject one promise in the below example -

var returnDouble = (value) => {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      if (value > 0) {
        resolve(value * 2);
      } else {
        reject(resolve);
      }
    }, 1000);
  });
};

var promisesToMake = [returnDouble(20), returnDouble(0), returnDouble(5)];
var finalPromise = Promise.all(promisesToMake);

finalPromise
  .then((results) => console.log('Final Result: ' + results))
  .catch(err => console.log('Error occured'));

Output:
"Error occured"
You can execute the code here. In this example, the second call is failed, even though the first and third call is successful. But still the final result is failure.

Promise.race()

Promise.race() runs as soon as one of the promises you pass to it resolves, and it runs the attached callback just once with the result of the first promise resolved.

Here is the example 

var returnDouble = (value,time) => {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      if (value > 0) {
        resolve(value * 2);
      } else {
        reject(resolve);
      }
    }, time);
  });
};

var promisesToMake = [returnDouble(20,100), returnDouble(200,50), returnDouble(5,500)];
var finalPromise = Promise.race(promisesToMake);

finalPromise
  .then((results) => console.log('Final Result: ' + results))
  .catch(err => console.log('Error occured'));

Output:
"Final Result: 400"

You can execute the code here.

Further Study

• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises
• https://promisesaplus.com/

Share:

Read More

Quick Reference of Arrow Function in JavaScript

Arrow functions were introduced with ES6 as a new way of writing JavaScript functions. This post will cover basic syntax of Arrow functions, common use cases.

What is Arrow Functions?

Arrow functions, sometimes referred as Fat Arrow is a new concise way of writing functions. They utilize a new syntax, => which looks like Fat Arrow. Arrow functions are anonymous and change the way this binds in functions. By using arrow functions, we can avoid typing function and return keyword and also curly brackets.

Basic Syntax of Arrow Function with Multiple Parameters

const multiplyFunction = (x,y) => (x*y);
console.log(multiplyFunction(5,6));

You can execute the code here.

Syntax of Arrow Function with Single Parameter

const splitString = text => text.split(" ");
console.log(splitString("My name is Sudipta Deb"));

You can execute the code here.

Syntax of Arrow Function with No Parameter

const functionWithNoParam = () => {
  console.log('This function with no parameter');
}

functionWithNoParam();

You can execute the code here.

Syntax of Arrow Function with Object return

Arrow functions can be used to return an object literal expressions. 

var funcWithObject = (empName, empNumber) => ({
  empName : empName,
  empNumber : empNumber
});
console.log(funcWithObject("Sudipta Deb",101));

Here is the output

[object Object] {
  empName : "Sudipta Deb",
  empNumber : 101
}

You can execute the code here.

Use Cases for Arrow Functions

One very common use case for Arrow function is Array manipulation. In the below example, each array items will be converted to upper case.

const countries = ['India', 'Canada', 'Switzerland', 'Germany'];
const countriesWithCaps = countries.map(country => country.toUpperCase());

console.log(countriesWithCaps);

You can execute the code here.

Another little advanced example is when you want to return something from array which meets the criteria. So in the below example, I would like to return only those tasks which is completed.

const myTasks = [{
  description: "Write Blog Post",
  status: "Completed"
}, {
  description: "Study Architect Certification",
  status: "Pending"
}, {
  description: "Go for walk",
  status: "Completed"
}];

const completedTask = myTasks.filter((myTask) => myTask.status === 'Completed');

console.log(completedTask);

You can execute the code here.

Now if I want to just print the description instead of everything, we can use another Arrow Function to do that like below

const myTasks = [{
  description: "Write Blog Post",
  status: "Completed"
}, {
  description: "Study Architect Certification",
  status: "Pending"
}, {
  description: "Go for walk",
  status: "Completed"
}];

const completedTask = myTasks.filter((myTask) => myTask.status === 'Completed');
completedTask.forEach(singleTask => console.log(singleTask.description));

You can execute the code here.

Promises and Callback

Promises make it easier to manage async code. This is the perfect situation to use Arrow function. Here is the syntax

this.doSomething().then((result)=>{
  this.handleResult(result);
});

Places not to use Arrow Function

Let's consider the below object which is having one method describeMe() which is returning a String. 

const Car = {
  brand : 'Honda',
  price : 132000,
  describeMe : function(){
    return `I am ${brand} car with price ${price}`;
  }
}

console.log(Car.describeMe());

If you execute the above code, you will get undefined error while accessing brand and price. To solve that, let's use This now to bind brand and price with the Car object context. So now the code looks like -

const Car = {
  brand : 'Honda',
  price : 132000,
  describeMe : function(){
    return `I am ${this.brand} car with price ${this.price}`;
  }
}

console.log(Car.describeMe());

And this time you will see the correct message. You can execute the code here.
Now if you think of replacing describeMe function with Arrow function, it will look like below -

const Car = {
  brand : 'Honda',
  price : 132000,
  describeMe : () => `I am ${this.brand} car with price ${this.price}`
}

console.log(Car.describeMe());

But this time you will get again the undefined error. Why???
This keyword is bound to different values based on the context in which it is called. With Arrow Function, it is little different. Here This is lexically bound i.e. it uses this from the code that contains the arrow function. So Arrow Function should not be used in Object methods.

Wrapping up

Arrow function is a great addition to JavaScript language and with this for concise code can be written.

Further Reading

• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions
• https://stackoverflow.com/questions/22939130/when-should-i-use-arrow-functions-in-ecmascript-6

Share:

Read More

Class-based vs Prototype-based Programming using JavaScript

Douglas Crockford described JavaScript as the world's most misunderstood language. Like many developers, when I started learning JavaScript, to me also, this was not a "proper" language. But I quickly understood that JavaScript comes with a rich system of object-oriented programming.

There are many concepts that makes JavaScript unique, but prototype model is definitely the most important one and it creates many confusions. So having a clear understanding of prototype model is very important. And in this post, I would like to explain the concept of prototype based programming in JavaScript.

The prototype based programming is a very easy to understand concept, but the source of confusion is the syntax. When a new developer looks at the JavaScript code and sees new, class or constructor it makes them think that object instantiation works the same way as other languages. But in reality, they are nothing more than syntactic sugar in JavaScript. Behind the scenes, things are working in different way. So it is very important to have a clear understanding how things works which will help you to predict their behavior.

Class Based Language

A class based language (Java, C++, C# etc.) has two important concepts:

• class - the interface which defines the properties and methods.
• entities - instantiations of the class (objects)

 An instance is exact same copy of the class, you cannot dynamically add/remove properties/methods from the instance as declared in the class.  You can definitely override them, but then it comes to inheritance. In this model, one instance belongs to one class only. Of course, those classes can also inherit from others. This is how Class Bases language works.

Note - There are some programming language like Python and Ruby which provide the way of dynamically change the attributes.

Prototype Based Language

Here we don't have the concept of classes or entities. It's only objects. An object can specify it's properties either at declaration or at runtime.

Let's see the below example:

//Property name at declaration
var student = {
  "name":"Sudipta Deb"
}

//This will throw an error as the function is not yet defined.
student.sayFullName(); 

//Let's add the function as runtime
student.sayFullName = function(){
  console.log('FullName: ' + this.name);
}

//This time it will print the fullname
student.sayFullName();

Check example here. Initially the method sayFullName() was declared, but it was added dynamically later.

Understand Prototype Object

Without classes in JavaScript, inheritance is only possible due to Prototype objects. Here are few important pointers to understand Prototype object.

• A prototype is an object which is used as template from which all new objects will get their properties.
• Any object can be used as a prototype for another object and share the properties with that object.
• The object can override the inherited methods/properties, but it will not impact the prototype.
• The prototype can change it's methods/properties or add new ones, which will impact the objects which was created from the same prototype.

So basically we create copies from one object and then all copies will move with their own life. The new object will have access to all the methods/properties of the prototype as long as they are not overridden. Even if there is any method/property being added to the prototype class after the object creation, object will still have access to those newly added method/property. Any changes in the object will not impact prototype, but any change in prototype will impact all objects. This is the core of prototype based programming. Let's understand this below example.

Vehicle Example

Let's create the hierarchy in JavaScript. 

First the Vehicle definition.

 function Vehicle(){  
  this.manufacturers = '';  
  this.year = '';  
 }  

Let's the create the two sub classes for Vehicle i.e. Bus and Car as below

//Definition of Vehicle Object
function Vehicle(){  
  this.manufacturers = '';  
  this.year = '';  
} 

//Definition of Bus Object
function Bus(){
  Vehicle.call(this);
  this.routeNumber ='';
}
Bus.prototype = Object.create(Vehicle);
Bus.prototype.constructor = Bus;

//Definition of Car Object
function Car(){
  Vehicle.call(this);
  this.type = '';
}
Car.prototype = Object.create(Vehicle);
Car.prototype.constructor = Car;

Every object in JavaScript has a __proto__ attribute which basically points to its prototype. This attribute creates the link in prototype chain. In Javascript, you add a prototypical instance as the value of the prototype property of the construction function and then override the prototype.constructor to the construction function.

So prototype property holds the parent object. When an object is created through Object.create, the passed object is meant to be the prototype of the new object. 

So now let's extend the example above and create GasolinCar and ElectricCar. 

//Definition of Vehicle Object
function Vehicle(){  
  this.manufacturers = '';  
  this.year = '';  
} 

//Definition of Bus Object
function Bus(){
  Vehicle.call(this);
  this.routeNumber ='';
}
Bus.prototype = Object.create(Vehicle);
Bus.prototype.constructor = Bus;

//Definition of Car Object
function Car(){
  Vehicle.call(this);
  this.type = '';
}
Car.prototype = Object.create(Vehicle);
Car.prototype.constructor = Car;

//Definition of Gasolin Car
function GasolinCar(){
  Car.call(this);
  this.mileage = '';
}
GasolinCar.prototype = Object.create(Car);
GasolinCar.prototype.constructor = GasolinCar;

//Definition of Electric Car
function ElectricCar(){
  Car.call(this);
  this.batteryCapacity = '';
}
ElectricCar.prototype = Object.create(Car);
ElectricCar.prototype.constructor = ElectricCar;

The new Operator

Let's start with the below example:

//Let's create new objects now
var teslaGasolinCar = new GasolinCar();
teslaGasolinCar.mileage = 12;
teslaGasolinCar.type = 'Car';
teslaGasolinCar.manufacturers = "Tesla";
teslaGasolinCar.year = 2018;
console.log('Mileage:' + teslaGasolinCar.mileage);
console.log('Type:' + teslaGasolinCar.type);
console.log('Manufacturer:' + teslaGasolinCar.manufacturers);
console.log('Year: ' + teslaGasolinCar.year);
console.log('__proto__: ');
console.log(teslaGasolinCar.__proto__);

console.log('prototype: ');

onsole.log(teslaGasolinCar.prototype);

When using the new operator to create object from a function, below things happen behind the scene:

• A generic object is created.
• The __proto__ is set to GasolinCar.prototype
• Finally GasolinCar function is called, with this representing the newly created object

Now when the above example is executed, here is the output in the console. 

Note - 

__proto__ is holding the GasolinCar.prototype, and prototype is holding Car object. This is how the inheritance is created in JavaScript.

It's important to understand that the constructor/function role is to help creating prototype chain between the newly created instance and it's parent object. After that, it is having no other job. Therefore, there is no direct link between the instance and the function/constructor. 

teslaGasolinCar instance and GasolinCar function have no direct reference to each other.

You can run this example here.

Create Multiple Objects with new Operator

You can create multiple objects with new operator, but each object will get their own property.

In the below example, I have created two objects of same type as -

//Definition of Vehicle Object
function Vehicle(){  
  this.manufacturers = '';  
  this.year = '';  
} 

//Definition of Bus Object
function Bus(){
  Vehicle.call(this);
  this.routeNumber ='';
}
Bus.prototype = Object.create(Vehicle);
Bus.prototype.constructor = Bus;

//Definition of Car Object
function Car(){
  Vehicle.call(this);
  this.type = '';
}
Car.prototype = Object.create(Vehicle);
Car.prototype.constructor = Car;

//Definition of Gasolin Car
function GasolinCar(){
  Car.call(this);
  this.mileage = '';
}
GasolinCar.prototype = Object.create(Car);
GasolinCar.prototype.constructor = GasolinCar;

//Definition of Electric Car
function ElectricCar(){
  Car.call(this);
  this.batteryCapacity = '';
}
ElectricCar.prototype = Object.create(Car);
ElectricCar.prototype.constructor = ElectricCar;

//Let's create Tesla objects
var teslaGasolinCar = new GasolinCar();
teslaGasolinCar.mileage = 12;
teslaGasolinCar.type = 'Car';
teslaGasolinCar.manufacturers = "Tesla";
teslaGasolinCar.year = 2018;
console.log('Printing Tesla Car:==>');
console.log('Mileage:' + teslaGasolinCar.mileage);
console.log('Type:' + teslaGasolinCar.type);
console.log('Manufacturer:' + teslaGasolinCar.manufacturers);
console.log('Year: ' + teslaGasolinCar.year);

//Let's create Ford objects
var fordGasolinCar = new GasolinCar();
fordGasolinCar.mileage = 11;
fordGasolinCar.type = 'Car';
fordGasolinCar.manufacturers = "Ford";
fordGasolinCar.year = 2019;
console.log('Printing Ford Car:==>');
console.log('Mileage:' + fordGasolinCar.mileage);
console.log('Type:' + fordGasolinCar.type);
console.log('Manufacturer:' + fordGasolinCar.manufacturers);
console.log('Year: ' + fordGasolinCar.year);

You can run this example here.

Conclusion

I hope you have a much clear understanding of how prototype based programming is used in JavaScript. In JavaScript, you can create objects in multiple ways, but as long as you understand the basic, it will be easy for you to understand and pick the correct way.

Thank you for your time and please feel free to provide your feedback in comments below.

Further Reading

• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Details_of_the_Object_Model
• https://alistapart.com/article/prototypal-object-oriented-programming-using-javascript

Share:

Read More

Kitchener Developer Group Event: Introduction to Lightning Web Component by Mohith Srivastava

Special thanks to our speaker, Mohith Srivastava, for sharing his knowledge on Lightning Web Component. 

Here comes the presentation and recording.

Presentation:

Introduction to lightning web component from Sudipta Deb ☁

Recording:

Please register to Kitchener, Canada Developer Group for all our future events.

https://goo.gl/yLm9Sd

Share:

Read More

Notes on passing Salesforce Certified Sharing and Visibility Designer

I have cleared Salesforce Sharing and Visibility Designer certification on Jan 11th, 2019 and it helped me to become Salesforce Application Architect.

Let me quickly share the Exam Outline:

• Total Number of Questions: 60 multiple-choice/multiple-select questions.
• Time: 120 minutes
• Passing Score: 68%
• Registration Fee: USD 400; Retake Fee: USD 200
• Prerequisite: None

In this blog post, I will share my notes and experience during the preparation and also during the exam. I hope it will help you in your #JourneyToCTA.

To me questions were very straight forward, but very descriptive, which took a lot of time to go through the entire question. Going through the entire question is very important because one single work can totally change your answer. 

Before I start preparing myself, I have gone through the below blog posts which helped me to create a consolidated list which I am going to share here.

• How to Prepare For and PASS Sharing and Visibility Designer Exam.
• Preparing For The Salesforce 'Sharing and Visibility Designer' Exam.
• Salesforce Sharing & Visibility Designer Certification.
• Ladies Be Architect: Study Group.

Below are the topics from where I have received questions:

Understanding Profile and Permission Difference

• Profile is user’s base level permission and all users having the same profile will have the same permission. 
• Permission Set is assigned to individual users on top of profiles to extend their visibility.
• You can set Login Ip, Hour, Session Settings, Password policies in Profiles, where these are not possible in permission sets.
• Profiles are having hidden permission sets.
• You can set default apps in Profiles, whereas setting default app is not possible in Permission Sets. You can provide app access to both Profiles and Permission Sets.

Difference Between Login Hour and Trusted IP

• Login IP is set at the profile level. Use case: You want your internal employees will be allowed to login to your org only from corporate network. Anybody trying to login from outside will not be allowed to login.
• Trusted IP is set at the Network Access / Org level. Anybody trying to login from the defined IP range, will not be asked to verify their identity. Otherwise, they need to verify their identity either through mobile authenticator or through email code.

Usage of System.runAs()

• It is only applicable in test methods.
• Since Apex always runs in System mode, user’s sharing settings is not enforced. That is why we need to use System.runAs() to change the user context and then that user’s sharing settings will  be enforced.
• runAs() method doesn’t enforce user permission or field level permission. It only enforce record sharing.
• runAs() ignores user licence limits means in test class you can still create users with runAs() even though you don’t have license in your organization.
• runAs() will allow you to get rid of Mixed DML exception in Test Class.

Sharing Questions:

• I have written this cheat sheet for reference: https://www.sudipta-deb.in/2019/01/salesforce-sharing-and-security-cheat.html

Sharing for Communities:

• I have written this blog post for reference: https://www.sudipta-deb.in/2019/01/sharing-options-and-user-licenses-in.html

Enterprise Territory Management:

• I have written this blog post for reference: https://www.sudipta-deb.in/2019/01/salesforce-enterprise-territory.html

Identify Security threats and mitigation approaches:

• SOQL Injection
• XSS

Account Team:

• Account team shares role with Opportunity Team. So removing account team role will eventually remove the role from Opportunity Team as well.
• Account owner and users above the account owner in the role hierarchy can add, edit, and delete team members.
• To add account team member, you just need edit access to the account.
• To edit/delete team members, you have to be -
• Account owner
• Above the owner in the role hierarchy
• Any user who is having full access to the account
• And administrator
• Access Levels for Account teams:
• Only account owners and users above the account owner in the role hierarchy can:
  • Add team members who don’t have even read permission to the account record.
  • Grant team member some access which is higher than account owd. Note - You can only grant greater access, but you will never be able to restrict access.
• Disabling Account Team:
• Disabling account team removes the team from all the accounts and also deletes user’s default account team.
• Removing Account Team Members
• Removing one user from the account team will not remove the user from opportunity team
• If a user in your default account team and you remove the user from one account team, then it will impact only that account, not your default account team.
• Default Account Team
• This is default account team for each users. User can select their default account team by going to the advanced settings.
• While defining default account team, you have the option to apply the default account team to all your open accounts.
• Clicking on “Add Default Team” from the account page layout’s related list will add the default team of the account owner, not the person who is clicking the button. Only Admin and users above the account owner in role hierarchy can add default team in the account.
• The access level can be set to the same or wider than your owd access.

Other Topics:

• Encryption in rest and transit
• Usage of Protected Custom Metadata, Protected Custom Settings, Crypto Class.
• Apex Managed Sharing and reason to avoid deletion of share record in case of record owner change.
• How reports, dashboards and folders are shared.
• List view accessibility.

Recommended Reading:

• Record Level Access: Under The Hood.
• Designing Record Access for Enterprise Scale.
• Guide to Sharing Architecture.
• Trailmix: Architect Journey: Sharing and Visibility.

Best of Luck.

Share:

Read More

Sharing Options and User Licenses in Salesforce Communities

While implementing Salesforce Community, identifying the record access requirements is an important steps which we all should do before procuring user licenses or setting up the communities. The reasons why I am telling this are -

• Sharing options in Communities depends on the type of Community User License (Customer or Partner)
• Even with the most open user license (Partner), there are few "gotchas" when it comes to sharing in a Community.
• You need to adjust internal sharing settings to make sure you are not giving unwanted record access to your community users.

License Types

Salesforce has a great chart here which compares features between Customer and Partner user license. But I prefer the below picture while deciding the license types.

In short, Customer licenses are designed for high-volume applications with any complex sharing requirements. Customer licenses are not having any roles. That is why sharing rules, Apex sharing and manual sharing are not available for Customer licenses.

On the other hand, Partner licenses are having access to more object types. For example, if you want community users should have access to Leads, Opportunities, Campaigns, upload contents then you need Partner license. Partner licenses are having roles so sharing options are available.

In addition to the above two licenses, Salesforce has Customer Plus license which is kind of middle between Customer and Partner license. So if your requirement is that you want your customers to have full access to Accounts, view access to Contents, ability to create Tasks, view access to Reports and Dashboards, and role-based sharing, then you should got for Customer Plus license.

So the difference between Customer Plus license and Partner license is that users with Partner license can access "premium" standard objects Leads, Campaigns, Opportunities.

Sharing Options with Customer License:

We basically have two options here: Sharing Sets and Share Groups. So let's explore both with some use cases so that it will become easier to understand.

Sharing Sets:

Sharing Sets will allow you to grant a external user access to records based on relationship with the user's contact or account (or a contact or account related indirectly to the user through some lookup relationship).

Use Case: Requirement is to share all cases created under the same account to all users in the same community.

Share Groups:

Share Groups allow to share records owned by community users with internal users. Basically you can use Share Groups to share records owned by an External user (with a Customer Community or High-Volume Customer Portal License) with Internal users, partner users, or other High-Volume external users in the same account). 

Use Case: Requirement is to share cases created by external community users with Call Center Reps (Internal users). (Account restriction applies to High-volume external users only).

Important Point to Remember:

• Sharing Sets:   External User   ->   External User
• Sharing Group:   External User   ->   Internal User

Sharing Options with Partner License/Customer Community Plus License:

With Partner license, you have five options - Role Hierarchy, Super User Access, Sharing Rules, Manual Sharing, Apex Sharing.

Role Hierarchy:

Each partner account can have 3 roles (Executive, Manager and User). Using record ownership and role hierarchy is the simplest way to share records among Partner users in the same account.

Use Case: Requirement is to allow some partner users to see only those records which they create, whereas for other partner users they should be able to see records created by others below them in role hierarchy.

Super User Access:

Partners with Super User access will be able to see records created by other users in their account at the same level or lower in the role hierarchy, for Cases, Leads, Opportunities and Custom objects only. For Customer Plus users, this can be given through permission sets.

Sharing Rules:

Owner and Criteria based sharing rules can be used to share records within Partner community. You can use Partner Role and public groups in these rules.

Use Case: Requirement is to share all Opportunities related to a particular partner account with all users in the partner account, but don't want to open up the full super user access. Here you can create a criteria-based sharing rule where the AccountId is the partner account and then sharing with partner account executive role and subordinates. 

Manual Sharing:

External users with Customer Community Plus and Partner License can use manual sharing but only on VF Communities. It's in the Salesforce roadmap to add support for lightning communities. Another mechanism for manual sharing is Opportunity team i.e. a reseller shares the opportunity with his SI (co-seller use case).

Use Case: Partners work closely with internal users on few opportunities.

Apex Sharing:

Apex sharing should be used when the sharing requirements are too complex which cannot be implemented with criteria-based sharing rule. Basically this is the last resort you have.

Recommended Reading:

• Share CRM Data with your Partners
• Video (HIGHLY RECOMMENDED)

Recent Changes:

• Sharing Sets for Customer Community Plus and Partner License: https://releasenotes.docs.salesforce.com/en-us/winter19/release-notes/rn_networks_sharing_sets_ppu.htm
• Extended object support on Sharing Sets: https://releasenotes.docs.salesforce.com/en-us/spring19/release-notes/rn_networks_sharing_sets_coo.htm
• Partner Account Relationship: https://releasenotes.docs.salesforce.com/en-us/spring19/release-notes/rn_networks_account_rel_data_sharing.htm
• Community User Visibility: https://releasenotes.docs.salesforce.com/en-us/spring19/release-notes/rn_networks_community_user_visibility.htm

Share:

Read More