Salesforce User-Experience-Designer Online Access

 The best way for the designer to help mitigate pushback from developers is to work together on setting up UX Indicators. UX Indicators are a set of metrics that measure the user experience of a product or feature, such as usability, satisfaction, engagement, and adoption1. By working together on setting up UX Indicators, the designer and the developers can align on the goals and expectations of the design changes, and use data and evidence to evaluate their impact. This can help to reduce the subjective opinions and assumptions that might cause pushback, and foster a collaborative and user-centered culture. Sharing research notes from previous projects with them (A) might not be very helpful, as the research might not be relevant or applicable to the current project, and the developers might not trust or understand the research methods or findings. Getting buy-in from the development lead first and let them persuade others (B) might not be very effective, as it might create a top-down or hierarchical approach that does not involve the developers in the design process, and might make them feel excluded or ignored. References:

• UX Designer Certification Prep: UX Indicators

 Styling hooks are CSS custom properties that allow developers to customize the appearance of base and custom components in a consistent and supported way. They work with web components and shadow DOM, which provide encapsulation and modularity for LWC. Styling hooks use the --slds namespace and follow a naming convention that reflects the component, category, property, attribute, and state of the element being styled. For example, --slds-c-button-brand-color-background-hover is a styling hook for the button component, brand category, color background property, and hover state. Styling hooks can be declared in the CSS file of the LWC or in a global CSS file that affects all components on the page. Styling hooks are not standard CSS properties, but custom ones that are defined by SLDS and applied to the components using the var() function. References:

• Styling Hooks - Lightning Design System
• SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers
• –dxp Styling Hooks | LWR Sites for Experience Cloud | Salesforce Developers

The Salesforce Lightning Design System (SLDS) styling hooks use standard CSS properties to easily style base and custom components. Salesforce documentation states that “SLDS styling hooks are CSS classes that give you access to the same styling used in the Salesforce Lightning Design System. They make it easy to style base and custom components with the same look and feel” [1].

Lightning console apps are designed to help users work faster and more efficiently by providing a workspace where they can access multiple records and their related records on the same screen. Users can complete actions with a single click, such as creating records, logging calls, sending emails, and updating fields, without losing context or switching tabs. Lightning console apps also support keyboard shortcuts, macros, and quick text to speed up common tasks. Lightning console apps are especially useful for sales representatives who need to provide quick, competitive pricing and close deals faster. They can also use Lightning console apps to view and manage their pipeline, collaborate with team members, and track their performance. Organizing items in the utility bar and adding records to Favorites are features that are available in any Lightning app, not just Lightning console apps. References: Salesforce Console in Lightning Experience, Create and Edit a Custom Lightning Console App, Create a Lightning Console App

A docked utility bar is a Salesforce configuration feature that allows users to access common productivity tools, such as notes, history, or macros, from a fixed footer at the bottom of the screen1. A list view - split view is a Salesforce configuration feature that allows users to see a list view and a record side by side in a split-screen layout2. These two features can help the IT help desk team quickly resolve queued cases by providing them with a persistent place to create notes and the ability to view their case queue while working a particular case. Dynamic forms and activity timeline are not relevant for this scenario, as they do not address the requirements of the IT help desk team.

References: Utility Bar - Salesforce Help and Split View - Salesforce Help