The Salesforce Certified Platform User Experience Designer (Plat-UX-101) (User-Experience-Designer)

The best place for the team to explore Lightning component code, documentation, and specifications is the Components Library on developer.salesforce.com 1 .  The Components Library is the Lightning components developer reference, where the team can find code samples, SDKs, tools, metadata coverage information, and a developer guide for Lightning Web Components 1 .  The team can also use the live code environment to code their first Lightning web component and see the results in real time 2 . Salesforce Extensions for VS Code (A) is a powerful tool for developing Lightning components, but it is not a source of code, documentation, and specifications. Design Tokens on SLDS website (B) are a way to store and maintain consistent design attributes across different platforms, but they are not specific to Lightning Web Components.  References :

Components Library on developer.salesforce.com

Get Started Coding | Lightning Web Components Developer Guide

The tool that the UX Designer should use to plan and communicate the intended page layouts of a community portal is  wireframes . Wireframes are low-fidelity sketches or diagrams that show the basic structure, content, and functionality of a web page or app screen. Wireframes help the UX Designer to visualize the layout of the portal, arrange the elements according to their importance and relevance, and communicate the design concept to the stakeholders and developers.  Wireframes are one of the learning objectives for the Salesforce User Experience Designer certification  1 .  References : [Wireframes - Lightning Design System]

https://careerfoundry.com/en/blog/ux-design/website-app-wireframe-examples/

To optimize the relationship between two objects in Salesforce, such as Container and Container Bids, where there is a need for a tight relationship and cascading delete functionality, a Master-Detail relationship is most suitable. This type of relationship has the following characteristics:

Cascading Delete: When a record in the master (or parent) object is deleted, all related detail (or child) records are automatically deleted. This ensures data integrity and aligns with the requirement that Container Bids should be deleted when their associated Container is deleted.

Tight Coupling: A Master-Detail relationship creates a strong linkage between the two objects, where the detail (child) record ' s existence is dependent on the master (parent) record. This is appropriate for scenarios where the child record should not exist without its parent.

Options B (Hierarchical Lookup) and C (Many-to-one Lookup) do not provide the same level of dependency and cascading delete functionality inherent in a Master-Detail relationship.

Q Tabs are a type of SLDS component that can be used to organize and consolidate content on a record page. Q Tabs are a variant of the Tabs component that are designed for use in the Lightning App Builder. Q Tabs allow users to switch between different views of related information within the same context. Q Tabs can also be nested to create subtabs within a tab. Q Tabs can help UX designers to create content-rich record pages that are easy to navigate and consume. Q Tabs can also help to reduce clutter and scrolling on a record page by grouping related content into tabs. Q Tabs can be customized with different icons, labels, and badges to indicate the type and status of the content in each tab. Q Tabs can also be configured to load content dynamically or on demand, which can improve the performance and user experience of the record page.  References :  Q Tabs Component Blueprint | Lightning Design System ,  Tabs Component Blueprint | Lightning Design System ,  Tabs | Lightning Web Components Developer Guide | Salesforce Developers

When developers are building custom components in Salesforce and need to ensure that these components adapt to user preferences for density settings (Comfy or Compact), they should avoid using REM-based spacing values. This is because REM-based spacing does not automatically adjust based on the density setting chosen by the user, leading to a lack of consistency with the rest of the Salesforce UI, which does adapt to these settings. Instead, developers should:

A. Use the varSpacingMedium design token in CSS, as Salesforce Lightning Design System (SLDS) design tokens are context-aware and can adjust their values based on the density setting, ensuring a consistent user experience across different user preferences.

C. Use existing Lightning Components such as the card or page header, which are pre-built to adapt to density settings, ensuring that custom components align with the overall Salesforce UI and respect user settings for density.

Personalized Navigation Tabs are a navigational feature that allows the users to customize the navigation bar of the Salesforce mobile app with the items that they use most frequently. Users can add, remove, and reorder the tabs in the navigation bar, and access them with a single tap. Users can also mark their favorite items with a star icon, and access them from the Favorites tab.  Personalized Navigation Tabs can help Cloud Kicks (CK) employees to quickly access the apps, objects, and other items that they need in the Salesforce mobile app 1 2

Console Navigation is a navigational feature that allows the users to work with multiple records and objects on a single screen in the Salesforce desktop app.  Console Navigation is not avail able in the Salesforce mobile app, and it is not suitable for providing quick access to apps, objects, and other items 3

Utility Bar is a navigational feature that allows the users to access common productivity tools, such as notes, history, or macros, from a fixed footer at the bottom of the Salesforce desktop app.  Utility Bar is not available in the Salesforce mobile app, and it is not suitable for providing quick access to apps, objects, and other items 4

Themes and branding allow Salesforce app developers to customize the look and feel of their apps to match their company’s branding and accessibility standards. One of the features of themes and branding is the ability to select a brand color, which is the primary color used for buttons, links, and highlights. Salesforce automatically generates a color palette based on the brand color, which includes accessible colors that meet the WCAG 2.1 contrast ratio guidelines. This ensures that the app is visually appealing and accessible to users with different color vision abilities. Developers can also customize other aspects of the theme, such as the logo, page background, and default font.  References : [Themes and Branding Basics], [Accessibility in Salesforce]

Audience targeting is a page layout feature that allows admins to create different versions of a Lightning page for different audiences, such as user profiles, roles, or permissions. Audience targeting can be used to control the visibility of the entire page or specific components on the page, such as tabs, fields, or sections.  Audience targeting can help create personalized and relevant experiences for different types of users, and reduce the need for multiple page layouts 1 .

Audience targeting is the most suitable feature for the UX Designer to use in this case, because it can help them customize the Order record page layout for internal and external users, without creating separate page layouts. For example, the UX Designer can use audience targeting to show or hide certain fields, sections, or tabs based on the user’s profile or permission set. This way, the UX Designer can ensure that each user sees only the information that is relevant and appropriate for them.

Field-level security is a feature that allows admins to restrict the access and editability of fields for different users, based on their profiles or permission sets. Field-level security can help protect sensitive or confidential data, and enforce data quality and integrity. However, field-level security does not affect the visibility of fields on the page layout, only the access and editability.  Field-level security also does not apply to other components on the page, such as tabs or sections 2 .

Dynamic forms is a feature that allows admins to add, group, and reorder fields and sections on a Lightning page using the Lightning App Builder. Dynamic forms can help create flexible and dynamic page layouts that can adapt to different contexts and scenarios. Dynamic forms also support visibility rules, which can be used to show or hide fields or sections based on filters or conditions. However, dynamic forms are not available for all standard objects, and they do not support audience targeting.  Dynamic forms also do not affect the visibility of other components on the page, such as tabs 3 4 .

 Confirmation bias is the tendency to seek out and prefer information that supports our preexisting beliefs, while ignoring or rejecting information that contradicts them. Confirmation bias can affect the validity and reliability of user feedback, as it can lead to biased questions, selective interpretation, and skewed results. To avoid confirmation bias in user feedback, Cloud Kicks can follow these two strategies:

Interview users about the intended use of the product to support the questionnaire creation. This can help Cloud Kicks to understand the user needs, expectations, and goals, and to design questions that are relevant, clear, and unbiased.  By interviewing users, Cloud Kicks can also avoid making assumptions about the user behavior, preferences, and pain points, and instead base their questions on real user data and insights  1 .

Diversify feedback by ensuring it features as many unique perspectives as possible. This can help Cloud Kicks to reduce the risk of sampling bias, which occurs when the feedback is collected from a group of users that is not representative of the target population.  By diversifying feedback, Cloud Kicks can capture a wider range of user opinions, experiences, and feedback, and avoid overlooking or dismissing important user segments or viewpoints  2 .