1 Minute Tips
Salesforce Announces Q3 FY23 Results
#1MinuteTip Salesforce has announced its Q3 FY23 Results. Here are my key observations from this report.
- Revenue by region
- Americas – 68%
- Europe – 22%
- APAC – 9%
- Revenue by product
- Subscription & support – 92%
- Professional Services and other – 8%
- Subscription & support revenue breakup by product category
- Sales – 24%
- Service – 26%
- Platform & Others (includes Slack) – 21%
- Marketing & Commerce – 16%
- Data (includes MuleSoft & Tableau) – 14%
References & Useful URLs
End of Life for Permissions on Profiles
#1MinuteTip The future of user management in Salesforce is Permission Sets & NOT Profiles. It will soon be the end of life for granting permissions on Profiles as per the following tweet from Salesforce’s Product Manager.
#SalesforceWinter23 – Automate Testing of Record Triggered Flows
#1MinuteTip #SalesforceWinter23 Before you activate a record-triggered flow, you can now test it to quickly verify its expected results and identify flow run-time failures. This feature is now generally available.
In Flow Builder, you create, save, and run flow tests. Previously, you debugged a flow manually to troubleshoot failures each time they occurred. Now, you create and save a flow test from a debug run. Then each time you modify the flow, you can run the test.
References & Useful URLs
- Related Winter ’23 Release Note Article – https://sforce.co/3DCsfii
- Blog Post: Step-by-Step Guide to Automate Testing of Salesforce Flows Declaratively
Naming Convention for Your Salesforce Developer Edition Orgs
#1MinuteTip If you are a Salesforce Professional (e.g. admin, consultant, developer, architect) chances are that you have registered multiple developer edition orgs. And chances are that you have often struggled to come up with the My Domain name URL for your Org and the username. And as you keep on registering different orgs for developer purposes, you end up having a bunch of variety of Salesforce Orgs and the usernames with no standardization whatsoever.
- Come up with a prefix keyword for your Developer Edition Orgs. Like for me, it is ” asagarwal “. For you it can be your first name + last name (e.g. ” annaparker”, ” aparker “) or any combination on these lines. If you have a blog or company, you can use those as the prefix. But just come up with something.
- Then use the second word for the purpose of the org. Like if it is for trailhead modules then call it “trailhead”. If it is for learning a specific topic likes Flows or Field Service Lighting, then use that. So the string becomes ” annaparker-flow” or “annaparker-fsl” or “annaparker-cpq”
- For developer edition orgs, Salesforce will automatically add the suffix “-dev-ed”. So, your URL becomes
- annaparker-flow-dev-ed
- annaparker-trailhead-dev-ed
- annaparker-fls-dev-ed
- annaparker-cpq-dev-ed
- If you need multiple Salesforce Developer Edition Orgs for the similar purpose (like multiple developer edition orgs for trailhead modules) then just add a number starting with “2” to your second word. Like “annaparker-trailhead02”, “annaparker-trailhead03 ” and so on.
- Once you have the naming convention for the My Domain URL of your org, coming up with the username is pretty straightforward. Just use the format “first-name@my-domain-url.com” For example:
- anna@annaparker-trailhead-dev-ed.com
- anna@annaparker-flow-dev-ed.com
- anna@annaparker-cpq-dev-ed.com
- The benefit of taking this approach will that you will have a standard naming convention, it will have your branding (just in case if you need to share the screenshots with someone or somewhere like a blog) and you will not need to spend much time thinking about it.
- If you already have a bunch of Developer Edition Orgs, you can also apply this naming convention to those orgs. Just make changes in “My Domain” URL under Setup and the username.
Feel free to modify the naming convention as per your preference. The objective of this post is just to give you some ideas and get your creating juices flowing.
#SalesforceWinter23 – Einstein Bots Learning Map
#1MinuteTip #SalesforceWinter23 Whether you’re a bot admin or a bot developer, the new learning map identifies the must-see bots content to launch your bot. This learning map guides you through every step of creating an Einstein bot: planning for bot tasks, creating or customizing your new bot, connecting to channels, and extending your bot with new channels and clouds.
References & Useful URLs
- Related Winter ’23 Release Note Article – https://sforce.co/3zlYmAd
- Blog Post – Step By Step Guide On Getting Started with Einstein Bots In Salesforce
What is Salesforce Code Analyzer?
#1MinuteTip Salesforce Code Analyzer is a source code analysis tool. Run this tool on the code written by your developers and detect violations against best practices to ensure high quality codes. It is generally integrated in the CI/CD process to ensure quality before the code is deployed to upstream environments like QA, UAT or Production.
Salesforce Code Analyzer was previously known as Salesforce CLI Scanner. It is Salesforce’s in-house, open-sourced, code quality and security tool that can analyze multiple languages.
References & Useful URLs
- Salesforce Code Analyzer Home Page
- Salesforce Developer Blog Post – Develop Even More Secure Code with Salesforce Code Analyzer
#SalesforceWinter23 – Direct Cases to Qualified Agents with Omni-Channel Flows
#1MinuteTip #SalesforceWinter23 Use automation in Omni-Channel flows to route cases to the right agents. When Email-to-Case generates cases from incoming emails, your Omni-Channel flow can determine where to direct them. Previously, Omni-Channel flows didn’t support case routing unless you created a record-triggered flow.
References & Useful URLs
- Related Winter ’23 Release Note Article – https://sforce.co/3gAvI82