Here we share our selection of the highlights we’ve identified in the Salesforce Winter'23 Release Notes. Check out this presentation to get all the details.
These are the slides from a presentation given to the San Diego Salesforce Developer Group on September 16, 2014.
The presentation highlights why coding standards and design patterns are important parts of creating a scalable, maintainable Salesforce Enterprise Org. A series of specific implementation and architecture recommendations are outlined. Finally, models for process and governance are provided to help the viewer take steps to bring about change in their Org.
How to Use Salesforce Platform Events to Help With Salesforce LimitsRoy Gilad
Presented at Israel User Group December 2019: Mixed DMLS Operations, Too Many SOQL Queries, Too Many DML Statements, CPU Timeout: Salesforce's Governor limits are there for a reason but even when you employ best practices you may still exceed them. A good developer will look at all tools available on the platform and find the best approach to solving the problem they are facing. Join us to add the newest tool to your developer toolbelt. Use Platform Events to change the rules of the game, process more, and faster within governor limits.
Link to GitHub repository:
https://github.com/RoyGilad/Dreamforce-2019-Do-more-within-Salesforce-Governor-Limits-using-Platform-Events
Salesforce Sales Cloud: Best Practices to Win More DealsCloud Analogy
Salesforce Sales Cloud includes a variety of services and products that help salespeople close more deals and develop stronger customer connections. Check out this presentation for more details on Sales Cloud.
Here we share our selection of the highlights we’ve identified in the Salesforce Winter'23 Release Notes. Check out this presentation to get all the details.
These are the slides from a presentation given to the San Diego Salesforce Developer Group on September 16, 2014.
The presentation highlights why coding standards and design patterns are important parts of creating a scalable, maintainable Salesforce Enterprise Org. A series of specific implementation and architecture recommendations are outlined. Finally, models for process and governance are provided to help the viewer take steps to bring about change in their Org.
How to Use Salesforce Platform Events to Help With Salesforce LimitsRoy Gilad
Presented at Israel User Group December 2019: Mixed DMLS Operations, Too Many SOQL Queries, Too Many DML Statements, CPU Timeout: Salesforce's Governor limits are there for a reason but even when you employ best practices you may still exceed them. A good developer will look at all tools available on the platform and find the best approach to solving the problem they are facing. Join us to add the newest tool to your developer toolbelt. Use Platform Events to change the rules of the game, process more, and faster within governor limits.
Link to GitHub repository:
https://github.com/RoyGilad/Dreamforce-2019-Do-more-within-Salesforce-Governor-Limits-using-Platform-Events
Salesforce Sales Cloud: Best Practices to Win More DealsCloud Analogy
Salesforce Sales Cloud includes a variety of services and products that help salespeople close more deals and develop stronger customer connections. Check out this presentation for more details on Sales Cloud.
One of the most important aspects for a new Salesforce implementation is setting up the correct security structure. Join us as we explain design considerations for setting up Security in a Salesforce instance. We'll explain usage of OWD, Role Hierarchy, Sharing Rules, Permission Sets with scenarios and discuss the impact of security for Community users.
The Salesforce platform offers system as well as application level security capabilities for building robust and secure applications. Join us as we introduce the system-level security features of Salesforce, like authentication and authorization mechanisms that include various Single Sign-On and OAuth flows. We'll also cover declarative application-level security features, like user profiles, roles and permissions, and how an Organization Wide Security and record-sharing model enforces a finer level of access control over the data.
Earlier when you required a custom feature in your Salesforce installation to support your business process, the only available options were to create a brand new app and integrate it in your Salesforce or to use existing features in a creative way to achieve the same objective. However Salesforce evolved and we now have got Salesforce Visual Flow, also known as Salesforce Visual Workflow or simply Salesforce Flow.
Visual flow can be summed up as an app inside the Salesforce app. Analogically, what methods are to object oriented programming, visual flow is to Salesforce. To be more precise, a Flow is a wizard or a set of screens in sequential order which can be used to complete a business process. This business process can be anything like filling out a form, or working on a script, or even filling out a survey. The Flow has the ability to fetch, edit, and create all Salesforce information in an appealing, quick and smart manner.
Difference between Salesforce.com Flow and Workflow
Salesforce Flow or Visual Workflow is often confused with a feature named Workflow in Salesforce and that’s forgivable! They may be similar in certain fashion such as assisting in automating a business process, but in essence they both are different. Here is how:
- Visual Workflow is more of a front-end based tool. It is mainly used when you have to display or collect information through screens making it more visible to the users. Workflow on the other hand execute pre-defined rules behind the scenes. They are used to process information rather than collecting it.
- While Workflows are mainly triggered by events, Visual Workflows are triggered by user actions. However in Visual Workflows, you can also Autolaunch Flows i.e. start a Flow without user interaction. Since they are triggered without user interactions you cannot include steps, choices, screens or dynamic choices in your Autolaunch Flow.
- Flows can fetch, delete, update or even create records on multiple objects but Workflows are defined to affect only a single specified object. The exception to this is the case of Workflows having to update fields on specified object’s related master records.
How to create and trigger Flow?
Flows can be used to execute a business logic, interact with Salesforce Databases, call defined Apex classes and guide user through screens. There are three main aspects of a Flow creation process:
- Designing
- Management
- Flow Runtime
You can create Flows and open Cloud Flow Designer by going through the following steps
Name-> Setup-> App Setup-> Create-> Workflow & Approvals-> Flows-> New Flow.
Once you have defined your Flow you can easily add it to any Visualforce page or you can add your Flow’s URL link to your Salesforce installation’s homepage.
You can create your Flow triggers by going through the same above process and instead of clicking Flow, click Flow Trigger.
What You Need to Know About Salesforce Customer 360Cloud Analogy
Salesforce Customer 360 enables organizations to connect Salesforce applications and create a unified customer ID to build a single view of the customer. In this presentation, you will get all the necessary details you need to know about Salesforce Customer 360.
In the short presentation, I have briefly described about the difference in between Salesforce Classic and Lightning along with the changes that have been introduced.
Lightning message service is a JavaScript library that implements a client-side cross-DOM messaging bus. As described here, it shows the use and features of the message service as implemented on the Salesforce platform.
The presentation for the community event on September 09 2021. Covers few winter 22 release features and strategies. Content is pulled from different official SFDC sources. This is educational material for the developers community to prepare for the release and win some swag on the way :)
One of the most important aspects for a new Salesforce implementation is setting up the correct security structure. Join us as we explain design considerations for setting up Security in a Salesforce instance. We'll explain usage of OWD, Role Hierarchy, Sharing Rules, Permission Sets with scenarios and discuss the impact of security for Community users.
The Salesforce platform offers system as well as application level security capabilities for building robust and secure applications. Join us as we introduce the system-level security features of Salesforce, like authentication and authorization mechanisms that include various Single Sign-On and OAuth flows. We'll also cover declarative application-level security features, like user profiles, roles and permissions, and how an Organization Wide Security and record-sharing model enforces a finer level of access control over the data.
Earlier when you required a custom feature in your Salesforce installation to support your business process, the only available options were to create a brand new app and integrate it in your Salesforce or to use existing features in a creative way to achieve the same objective. However Salesforce evolved and we now have got Salesforce Visual Flow, also known as Salesforce Visual Workflow or simply Salesforce Flow.
Visual flow can be summed up as an app inside the Salesforce app. Analogically, what methods are to object oriented programming, visual flow is to Salesforce. To be more precise, a Flow is a wizard or a set of screens in sequential order which can be used to complete a business process. This business process can be anything like filling out a form, or working on a script, or even filling out a survey. The Flow has the ability to fetch, edit, and create all Salesforce information in an appealing, quick and smart manner.
Difference between Salesforce.com Flow and Workflow
Salesforce Flow or Visual Workflow is often confused with a feature named Workflow in Salesforce and that’s forgivable! They may be similar in certain fashion such as assisting in automating a business process, but in essence they both are different. Here is how:
- Visual Workflow is more of a front-end based tool. It is mainly used when you have to display or collect information through screens making it more visible to the users. Workflow on the other hand execute pre-defined rules behind the scenes. They are used to process information rather than collecting it.
- While Workflows are mainly triggered by events, Visual Workflows are triggered by user actions. However in Visual Workflows, you can also Autolaunch Flows i.e. start a Flow without user interaction. Since they are triggered without user interactions you cannot include steps, choices, screens or dynamic choices in your Autolaunch Flow.
- Flows can fetch, delete, update or even create records on multiple objects but Workflows are defined to affect only a single specified object. The exception to this is the case of Workflows having to update fields on specified object’s related master records.
How to create and trigger Flow?
Flows can be used to execute a business logic, interact with Salesforce Databases, call defined Apex classes and guide user through screens. There are three main aspects of a Flow creation process:
- Designing
- Management
- Flow Runtime
You can create Flows and open Cloud Flow Designer by going through the following steps
Name-> Setup-> App Setup-> Create-> Workflow & Approvals-> Flows-> New Flow.
Once you have defined your Flow you can easily add it to any Visualforce page or you can add your Flow’s URL link to your Salesforce installation’s homepage.
You can create your Flow triggers by going through the same above process and instead of clicking Flow, click Flow Trigger.
What You Need to Know About Salesforce Customer 360Cloud Analogy
Salesforce Customer 360 enables organizations to connect Salesforce applications and create a unified customer ID to build a single view of the customer. In this presentation, you will get all the necessary details you need to know about Salesforce Customer 360.
In the short presentation, I have briefly described about the difference in between Salesforce Classic and Lightning along with the changes that have been introduced.
Lightning message service is a JavaScript library that implements a client-side cross-DOM messaging bus. As described here, it shows the use and features of the message service as implemented on the Salesforce platform.
The presentation for the community event on September 09 2021. Covers few winter 22 release features and strategies. Content is pulled from different official SFDC sources. This is educational material for the developers community to prepare for the release and win some swag on the way :)
Stephen Stanley's very popular presentation of the latest Salesforce release - Spring 23. Includes all his personal favourites.
Presented to the Salesforce Wellington Trailblazer community group virtual meeting February 22, 2023
Fort Worth Community - Record Triggered Automations.pdfAmeyKulkarni84
Tom Leddy, Principal Evangelist with Architect Relations at Salesforce, will lead a discussion about best practices and tool recommendations for various triggered automation use cases. We'll also discuss how Flow automatically handles scalability, bulkification, and recursion control and share some performance and automation design pointers.
Orchestrator and Flow in Slack: Antoine Cabot - Jacksonville Architects - Sal...A. Engin Utkan
This is an event for all Architects and aspiring Architects who are interested in the developments of Salesforce Automation. You can join this meeting to hear how Orchestrator and Flow on Slack can be used to automate your business processes. You can ask your questions and get answers from Antoine who is one of the few experts in Salesforce on this topic. A few questions that come to mind (forward-looking statements permitting):
- What is the roadmap for the Orchestrator? How is the adoption?
- What is the roadmap for Flow in Slack? What are the resources you can rely on when building your automation using this functionality?
- Should we expect automation to come together on the platform in the future, and how do Einstein NBA, Mulesoft, and RPA come into play?
Last year was eventful for Salesforce Developers - we started with the launch of Lightning Web Components (LWC), open-sourced it, enabled local development, and ended the year by open-sourcing Base Lightning Components. In this webinar, we will explore exciting new developments within Base Components and we will show you how to use open-source Base Components to build engaging applications faster with local development.
In this session we will,
- Spin up a local development environment to build Lightning web components
- Use and customize the base components and recipes to build pages and apps quickly
- Explore the latest features of VS Code developer tooling while coding for a use case
Salesforce Wellington user group hosted by PwC for lunch, June 29, 2022, featuring Salesforce Summer 22 release highlights with various speakers. Natalie Savell, Bill Wu, Mark Barcham, Afzal Khan
During this session we'll have Alex Dumitrache from Salesforce joining us for a presentation on the major updates from TrailheaDX.
In the second part of the meeting we'll be discussing about how we can avoid disasters by putting on our consultant hats and pushing back on requirements that go against Salesforce best practices.
The new version of Salesforce, Summer '20, was released in July 2020.
Discover the most important new features, including Dynamic Forms and Service Cloud Voice, the two new core features of this release.
Lightning Components 101: An Apex Developer's GuideAdam Olshansky
Don't hesitate to get into front end development on Salesforce! Check out the principles of backend code you already know as well as some of the new tricks to developing front end code on the Salesforce platform using the new Lightning Web Components model!