Get User-Experience-Designer Dumps : Verified Salesforce Certified User Experience Designer (SP24)

Cloud Kicks’ new design solutions would be described by the conceptual approach of desirable, feasible, and viable. This approach is based on the human-centered design (HCD) methodology, which aims to create solutions that meet the needs, preferences, and expectations of the users or customers, while also being technically possible and economically sustainable. HCD is a creative problem-solving process that starts with identifying the user’s problems and ends with creating solutions that address them. The desirable, feasible, and viable framework helps designers evaluate their solutions according to these three criteria:

• Desirable: A solution that people want or need, that solves a real problem for them, and that provides a meaningful and relevant experience.
• Feasible: A solution that can be created with new or existing technology, that is within the scope and capabilities of the organization, and that can be tested and validated.
• Viable: A solution that fits the organization’s business model, that generates value for the stakeholders, and that is sustainable in the long term.

By applying this framework, Cloud Kicks can ensure that its new design solutions for its sales processes in Salesforce are not only user-friendly, but also technically sound and profitable. This can help Cloud Kicks achieve its business goals, while also delivering more satisfying and delightful customer experiences.

References:

• Explore Human-Centered Design
• IDEO’s Desirability, Viability, Feasibility Framework: A Practical Guide

Changing the role hierarchy and reassigning account owners can have a significant impact on the data visibility and performance of Salesforce. An architect should consider the following points in this situation:

• Changing complex role hierarchy can cause a high level of sharing recalculation. Depending on the sharing settings, roles can control the level of visibility that users have into the Salesforce data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless the sharing model for an object specifies otherwise. When the role hierarchy is changed, Salesforce must recalculate the sharing rules and group membership for all the affected users and records, which can take a long time and consume a lot of system resources. Therefore, changing a complex role hierarchy should be done carefully and preferably during off-peak hours1.
• Replacing account records ownerships massively can cause data skew. Data skew occurs when more than 10,000 child records are related to the same parent record, or more than 10,000 records of any object are owned by a single user. This can cause performance issues, such as locking, timeouts, and failures, when updating or sharing those records. When account owners are reassigned massively, it can create or worsen data skew, especially if the accounts have many child records, such as contacts and opportunities. Therefore, replacing account records ownerships massively should be avoided or minimized23.

References:

• : [Design Your Data Model Unit | Salesforce Trailhead]
• : [Data Skew in Salesforce - Why it Matters | Salesforce Ben]
• : [Ownership Data Skew | Designing Record Access for Enterprise Scale | Salesforce Developers]

Inclusive design is a design approach that aims to create products and services that are accessible and usable by as many people as possible, regardless of their abilities, preferences, or circumstances. Some of the benefits of inclusive design are :

• Extending access to more users: By considering the diverse needs and situations of users, inclusive design can expand the reach and impact of the product or service. For example, designing a website that is compatible with screen readers can benefit not only users who are blind or visually impaired, but also users who are in low-light environments or have low bandwidth.
• Reducing friction for users in achieving their goals: By removing unnecessary barriers and providing multiple ways of interaction, inclusive design can enhance the user experience and satisfaction. For example, designing a mobile app that supports voice input and output can benefit not only users who have difficulty typing or reading, but also users who are multitasking or have their hands busy. References: : [UX Designer Certification Prep: Designing for Accessibility and Inclusion | Trailhead] : [Inclusive Design | Salesforce Developer Guide]

Inclusive design is a practice of designing products, services, and experiences that are accessible and usable for as many people as possible, regardless of ability, age, gender, race, language, or culture. By incorporating inclusive design practices, you can extend access to more users and reduce friction for users in achieving their goals. Salesforce provides more information on the benefits of inclusive design here: https://www.salesforce.com/blog/2020/11/what-is-inclusive-design.html.

The utility bar is a fixed footer that gives users quick access to productivity tools, such as notes, history, and recent items. It can be customized for each Lightning app to enhance the user experience and efficiency. Some of the standard use cases for using the utility bar are:

• Perform common tasks without navigating away from the page: Users can use the utility bar to perform tasks such as creating notes, logging calls, or sending emails without leaving their current context. This reduces the need for switching tabs or opening new windows, and saves time and clicks.
• Access to view a list of records favorited for quick access: Users can use the utility bar to access their favorites, which are records, lists, groups, or other items that they have marked with a star icon for easy access. This allows users to quickly navigate to the items they use most frequently, and organize them in a personalized way.
• Access at any time to a customized set of items specific to an app: Users can use the utility bar to access items that are relevant and useful for the app they are using. For example, in the Sales app, users can access the Lightning Dialer, the Assistant, or the Today’s Events utility. In the Service app, users can access the Omni-Channel, the Macros, or the Case Timer utility. The utility bar can be configured to show different items for different apps, depending on the user’s needs and preferences.

References:

• : User Experience Designer Certification Prep: Module 5: Design User Interfaces
• : Lightning App Builder: Utility Bar

Dynamic Forms is a feature that allows users to customize the form fields and sections displayed to users on a page layout. Dynamic Forms can be used to create user-centric, intuitive,and dynamic record creation screens for custom objects, such as Appointment. When creating a record using Dynamic Forms, the UX designer should consider the following two aspects12:

• The use of tabs when creating the record is not allowed. Dynamic Forms does not support the use of tabs within the form, as tabs are not compatible with the record creation process. Tabs are only available for viewing or editing existing records, not for creating new ones. Therefore, the UX designer cannot use tabs to separate the fields for different record types or software options on the record creation screen.
• Fields can be organized into sections. Dynamic Forms allows the UX designer to group fields into sections, and place them anywhere on the page layout. Sections can have labels, collapsible headers, and visibility rules. The UX designer can use sections to create a logical and clear structure for the form, and to show or hide fields based on user input, data, or profile. For example, the UX designer can create a section for each software option, and use visibility rules to display only the relevant section based on the user’s selection.

The following two aspects are not true when creating a record using Dynamic Forms, and should be disregarded:

• The form will not be available on mobile devices. Dynamic Forms is compatible with mobile devices, and the UX designer can preview and test the form on different device sizes and orientations. The form will automatically adjust to the screen size and layout of the mobile device, and provide a responsive and consistent user experience3.
• All software option sections of the form will always be visible. Dynamic Forms allows the UX designer to use visibility rules to control the visibility of fields and sections on the form. Visibility rules can be based on user input, data, or profile. The UX designer can use visibility rules to show or hide software option sections based on the user’s selection of the record type or the software option. This can reduce the clutter and complexity of the form, and provide a personalized and flexible user experience4. References: Get Started with Dynamic Forms Unit | Salesforce Trailhead, Salesforce Dynamic Forms: Overview & Deep DiveTutorial, Dynamic Forms and Actions FAQ | Salesforce Help, Create Dynamic Forms with Visibility Rules | Salesforce Trailhead