Meera R Nair - Salesforce Insights

 As part of the Spring 23 release, Salesforce introduced a beta feature, using which we can make HTTP callouts from flow without writing a single line of code. This is definitely great news for all the flow lovers. Let us see this using a Google Blogger API. 1. Introduction I want to consume Google Blogger API in a screen flow to see my blogger-related details. Let us see the step-by-step approach to set up this 2. Google API Access Set Up 1. Open your Google console   2. Create a new project 3. Open the Consent screen from Navigation Menu and do the basic set up 4. Add the basic detail including the App name, developer email, test user, etc and create the App 5. Once consent setup is completed, go to Credentials and create a new credential 6. We are going to consume OAuth authentication 7. Give a name for now and save it. We can update other details later. 8. You can see your client id and client secret. Take note of these values 9. Next step is to enable Blogger API for consumption F

1. Introduction  In the last few years, a significant change happened in how user permissions are getting handled in Salesforce. When I started my career in Salesforce as a Developer, it was just profiles, and later Salesforce introduced p ermission sets - when there was a need to give additional permission to specific users who belong to the same profile.  Later Salesforce introduced the Permission Set Groups where we can combine multiple Permission Sets and assign them to a specific user. Now the direction from Salesforce is to use minimal profiles and assign Permission Set Groups to users based on their job description or Persona.  The advantage here is that the same permission set can be assigned to multiple groups, and we can control access very easily, not like earlier- whenever we need to have some additional features for a specific user, we will end up creating a new profile.  In this post let us see some latest features from Salesforce to handle Permission Sets and Permission