CRT-450 - Salesforce Certified Platform Developer I (SP23)

The with sharing keyword on the class declaration enforces the sharing rules that apply to the current user. This means that the user can only see and modify the records that they have access to based on the organization-wide defaults, role hierarchy, sharing rules, manual sharing, teams, and territories. The without sharing keyword, on the other hand, ignores the sharing rules and allows the user to access all records, regardless of ownership or sharing settings. This can pose a security risk and should be used with caution. The schema describe calls and the UserInfo Apex class do not directly affect the sharing rules, but rather provide information about the object and field permissions, and the user’s profile and role, respectively. These can be used to check the user’s access level, but not to enforce the sharing rules on the custom search tool. References:

• Apex Developer Guide: Using the with sharing, without sharing, and inherited sharing Keywords, pages 13-14
• Trailhead: Platform Developer I Certification Study Guide: Apex Basics and Database, unit 3

A screen-based flow is a type of flow that allows you to create a guided, visual experience for users to collect and update data, execute logic, call Apex classes, and more. Screen-based flows are ideal for creating interactive processes that require user input and feedback, such as the scenario of processing damaged or stolen credit cards. A screen-based flow can be embedded in a Lightning page, a Visualforce page, a utility bar, or a custom tab, and can be launched from various places, such as a button, a link, a Lightning component, or a process. A screen-based flow can also leverage standard and custom objects, variables, formulas, and other elements to create dynamic and complex business logic. References: Screen-Based Flows Salesforce Platform Developer 1 Exam Guide, page 7.

 To make a Lightning web component available for a specific page type, such as the Account record page, the developer needs to do two things: expose the component and target the page type. Exposing the component means setting the  tag to true in the component’s metadata file (statusComponent.js-meta.xml). This makes the component visible in the Lightning App Builder and other tools. Targeting the page type means adding the  tag with the appropriate value in the same metadata file. For the Account record page, the value should be lightning__RecordPage. This specifies that the component can be used on any object’s record page. The  tag is optional and defines the display name of the component in the Lightning App Builder. The  tag should not be added to the component’s JavaScript file (statusComponent.js), as this is not a valid syntax and will cause an error. References:

• Configure Components for Lightning Pages and the Lightning App Builder from the Lightning Web Components Developer Guide
• Metadata for Lightning Web Components from the Lightning Web Components Developer Guide
• Lightning Web Components from the Salesforce Developer Center