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...
Read MoreI 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 minutesPassing Score: 68%Registration Fee: USD 400; Retake Fee: USD 200Prerequisite: NoneIn 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 DifferenceProfile 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...
Read MoreWhile 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 TypesSalesforce 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...
Read MoreThis post is the continuation of my study notes for Sharing and Visibility Designer Architect Certification. Previous post was regarding Salesforce Sharing and Security Cheat Sheet. Enterprise Territory Management is a very important topic and having a clear understanding will definitely going to help in passing the certification as well as implementing it for your own project.Nice to check out: Salesforce Spring 21 Release FeatureSalesforce Certification NotesSalesforce Release Video TutorialsSalesforce Lightning Flow Video TutorialsImportant Note:Original Territory Management is only available with Customizable Forecast.Enterprise Territory Management works with Collaborative Forecast. It will not work with Customizable Forecast.Territory:Group of Accounts and Sales reps who work for those accounts.Territory Type:This is the criteria to group territories. Every territory must have one Territory Type, but it will never appear in the Territory HierarchyTerritory Type Priority:Helps you to create priorities for your territory type.Territory Model:Creates the entire Territory Hierarchy.It allows to create multiple territory hierarchy and test that before activating.Number of territory models depends on the Salesforce edition.Territory Hierarchy:Shows the model’s territory structure.You can run assignment rules at the model level or individual territory levels.Your territory hierarchy in active territory model also determines the forecast hierarchy for territory forecast.Territory Model State:Three states – Planning, Active or Archive.Only one territory can be in Active state.Multiple territories can be in either Planning or Active state.User Access for Territory Records:Define Account access in Territory Settings when enabling the...
Read More“Sharing is Caring”, right?? That’s the attitude I like most about Salesforce Ohana. As I am preparing myself for Sharing and Visibility Designer Architect certification, I thought of sharing some of my study notes regarding Salesforce Sharing and Security.Security is the main pillar of Salesforce eco system and it is complex. It will give you fine-grained control over data access. So it requires a very good understanding of the concepts to implement in correctly.I will suggest everyone to go through these below articles to understand it clearly.A Guide to Sharing ArchitectureAn Overview of Force.com SecurityRecord-Level Access: Under the HoodI am not going to write everything what is written in these documents, rather I would like to provide a concise, sharp cheat sheet which you can refer anytime. So let’s start -Sharing Metadata Objects/Records:For standard object -> “Object[Share]”For custom object -> “Object__[Share]”Contains three types of sharing -> managed sharing, User managed sharing and Apex managed sharingFields present in the share object – access level, record ID, user or group IDShare records are not created for OWDs, role hierarchies, or the “View All”/”Modify All”/”View All Data”/”Modify All Data” permissions.If the owner of the record changes, sharing record with reason “Manual” will also be deleted.Implicit Sharing:This is applicable only for Accounts, Contacts, Cases and Opportunities.Access to parent record – If you have access to one of the child record, you will have...
Read More