LEARN. PRACTICE. GROW.Concept and mechanism
UI Policies adjust field presentation and behavior on forms. Business Rules execute server logic associated with data operations. To populate the current record before saving, a before rule avoids an unnecessary second update. An after rule can act on related data following the operation; async allows later work without blocking the transaction, but does not provide previous as a synchronous rule does. Select the mechanism by timing requirements and where it must apply. Hiding a field through interface logic does not replace the ACL controlling access. It also does not guarantee that an integration follows the form’s entry rules.
Guided application
Update sets transport captured customizations within the selected scope. They are not a complete copy of operational data: defining a catalog item differs from moving submitted requests. Select the correct set before editing, review its contents, complete it, and test transport in a test environment. Preview identifies problems such as missing dependencies and collisions. Compare versions and decide what to accept; do not assume the latest import represents the latest functional decision. This course’s internal assessment reuses practice items and does not reproduce the official exam. The January 2026 CSA blueprint defines sixty questions and ninety minutes; its passing threshold is not public. Use results to identify topics for review without turning an internal percentage into a promise of passing.
A collision requires comparing intent and versions before commit.
Common pitfalls
UI treated as security; async assumed to expose previous; update set treated as full backup; invented 70% threshold.
Related topics: Instance, navigation, and context · Configuration, access, and interfaces · Records, collaboration, and analytics
Run logic in the right place and review what is actually transported.
Reference: Create and select an update set as the current set · CSA blueprint January 2026