SFDC Know How

Summer '22 release is round the corner. Below is my top pick from Service Cloud perspective:- Get the Improved Entitlements and Milestones Experience Improve your service-level agreement (SLA) reporting experience and provide excellent customer service with enhanced milestone timers and changes to the entitlement process entry and reentry behavior. How :  The milestone timer now stops when a record exits the entitlement process. It’s no longer necessary to stop the milestone timer manually by selecting Is Stopped. The milestone timer stops based on the first action taken to stop it and not the most recent one. For example, if a record exits the entitlement process, but a user clicks Is Stopped afterwards, the milestone timer is stopped at the time that the entitlement exits and not when Is Stopped is selected. If the record reenters the entitlement process, the timer resumes from the time that the record exited the entitlement process. Use Service Cloud Voice with an Existing Amazo

Summer '22 release is round the corner. Below is my top pick from Sales Cloud perspective: - Enable Person Accounts Without Contacting Salesforce Support You can now enable Person Accounts without reaching out to Salesforce Support. Person accounts store information by combining certain account and contact fields into one record. This allows you to store information about a person in a record that can act like an account when necessary. How :  You can enable person accounts after you meet these prerequisites. The account object has at least one record type. User profiles that have read permission on accounts have read permission on contacts. The organization-wide default sharing is set so that either Contact is Controlled by Parent or both Account and Contact are Private. Gotcha -   Person accounts can’t be disabled after they’re enabled. Choose More Opportunity Fields to Include or Exclude from Your Forecasts With custom filters, your sales team can filter by standard number, cur

Create a record variable called recordId and mark it as available for input . Don’t forget to select the object . When it is a record variable and not just a text variable, action automatically passes the entire record to the variable.

Use Case There is a highly customized Salesforce org having Community enabled. Along with other customizations, Community is using Page Variance with the Audience. The Audience feature is used to target a set of audiences based upon defined criteria. As an Architect, I am evaluating if SFDX based Source-driven (Scratch Org based) development workflow will support Audience metadata or not. Recap In my previous article ExperienceBundle support in Scratch Org based (Source - driven) Development Workflow , I explained how ExperienceBundle will help in effectively versioning the metadata related to Communities and eventually another step close towards the adoption of Source-Driven development. Since ExperienceBundle supports themes, routes, brandigSets related metadata, I was under impression that Audience specific metadata will be supported too. Audience support in Salesforce CLI I did a small POC for this use case. I set up a Scratch Org using my repo V1.1 . I created an Aud