Sahitya Tarumani
MemberForum Replies Created
-
https://help.salesforce.com/articleView?id=sf.process_advanced_considerations.htm&type=5
This post has some examples. Worth a read.
This is what I gathered:
If you have a process builder that is set to fire when "a record is created / updated",
And in the actions, you are actually updating a field on the same record,
When a new record is created, it fires the PB the first time,
Then a field gets updated and the PB fires for the same record for the second time.This is powerful and dangerous at the same time. 🙂 The design considerations mentioned in that post are worth considering!
Popular Salesforce Blogs
Top Salesforce Service Cloud Einstein Features For B2B Business
The Salesforce CRM platform is the world leader in customer relationship management and doesn't stop at optimizing its performance. It is a powerful service that…
An Introduction to Salesforce App Builder: Revolutionizing Business with Custom Applications
In the digital age, the ability to quickly adapt and innovate is crucial for businesses seeking to maintain a competitive edge. Salesforce, a global leader…
To Lead or not to Lead, that is the question! | Salesforce Guide
Back when things were normal and we were able to go on-site and talk with our clients, there were a significant number of them who…
Popular Salesforce Videos
Salesforce User Stories in Action
Join this interactive session to understand how to write Salesforce-specific user stories, how to prioritize user stories, and learn some guidelines around story estimation. Topics:…
How Salesforce Industries can Help Organizations to Save Millions?
Salesforce Industries i.e Vlocity empowers businesses with powerful platforms to boost collaboration and makes it easy to deliver great customer experiences. It provides tailored solutions…
See the Future of APIs at Salesforce
Salesforce APIs are a way for other applications (or code in other applications) to programmatically access data within your Salesforce org, in a simple and…