Checklist progress
0/194Learned
Platform Developer
Study Checklist
Checklist progress
0/194Learned
Identify the capabilities of the declarative process automation features.
0/8
Understand how to declare variables, constants, methods, modifiers, Apex interfaces, and the appropriate use cases for each.
0/15
Given a scenario, assess how Apex control flow statements will execute and when to apply different control flow statements.
0/8
Given a scenario, write SOSL, SOQL, and DML statements in Apex, and assess what they will return.
0/18
Given a scenario, follow best practices to write Apex classes and triggers.
0/6
Given a scenario, understand governor limits and their implications on Apex transactions.
0/5
Describe the relationship between Apex transactions, the save order of execution, and the potential for recursion and/or cascading.
0/10
Apex transaction atomicity and rollback
Learn this conceptRecord save order of execution
Learn this conceptBefore-save versus after-save automation
Learn this conceptValidation rules versus Apex triggers in the save order
Learn this conceptField updates that re-enter the save order
Learn this conceptTrigger recursion and recursion guards
Learn this conceptCascading DML and nested save orders
Learn this conceptSavepoints and transaction rollback control
Learn this conceptImmediate versus asynchronous work across transactions
Learn this conceptImplement exception handling in Apex, including custom exceptions as needed.
0/7
Given a scenario, use declarative functionality and Apex together to automate business logic.
0/7
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform Developer studiers.
When Salesforce saves a record, it runs some automation before writing the row and other automation after that write, still inside the same transaction until commit. Before-save flows and before Apex triggers exist to update or validate the triggering record so the change is part of the first write. After-save flows and after Apex triggers exist when you need the saved record's Id or system fields, must change other records, or must take extra actions, knowing that extra DML can send records through the save sequence again.