Declarative Design 27% - 16 Questions Flashcards
Declarative component to assist in on-boarding
Field-level Help
When should a floating prompt be used?
When your goal is to have readers acknowledge information without
specifically completing an action.
Message (user engagement journey)
What you say to the
user
Purpose (user engagement journey)
Why you say the message to the user.
A component that provides getting started resources the first time that users log in to Lightning Experience
Welcome Mat component
A feature replaces a blank section with instructions on next steps
Empty State feature
User engagement: When users may not notice or seek out help, but would benefit from assistance
Push method
User engagement: When the user is motivated to seek
help
Pull method
Two types of Salesforce prompts
Floating
Docked
Distributed Marketing
Distributed Marketing can be used to send email to Lead, Contact or Person Account from right with in Salesforce (Sales, Service, Financial Services, or Experience Cloud) using email templates created in Marketing Cloud.
It helps customers bridge the gap between corporate marketing, employees, channel partners, and their brand to deliver consistent experiences across corporate marketing and partner networks
Creating a Branded App – Branding changes allowed:
App Icon
App Name
Launch Screen
Color Scheme
Application Store Listing (Name, Description, Images, Screenshots, Support URL, Marketing URL)
Authentication URL (Salesforce app only)
Help URL (Salesforce app only)
Use of Path
Create paths to guide your users through steps of a business process, such as working an opportunity from a fresh lead to a successfully closed deal. At each step of a path, you can highlight key fields and include customized guidance for success.
Use of Kanban View
Kanban views show records in a graphical way that helps you monitor your work and keep deals moving ahead.
Arrange a kanban view to show a graphical view of records in a list view. Each kanban view is based on a list view, and kanban view settings are applied separately for each list view.
Use of Dynamic Lightning Page
Control when a component appears on a Lightning page by adding filter conditions and logic to its properties in the Lightning App Builder. For example, you can construct a filter that causes a rich text component on an opportunity page to display when the opportunity’s amount is greater than or equal to $1 million.
Use of Quick Actions
Quick actions enable users to do more in Salesforce and in the Salesforce mobile app. With custom quick actions, you can make your users’ navigation and workflow as smooth as possible by giving them convenient access to information that’s most important. For example, you can let users create or update records and log calls directly in their Chatter feed or from their mobile device.
Object-specific quick actions
Object-specific actions have automatic relationships to other records. Users can quickly create or update records, log calls, send emails, and more in the context of a particular object. For example, you add an object-specific action on the Account object that creates contacts. If a user creates a contact with that action on the detail page for the Acme account, that new contact is associated with Acme.
Global quick actions
You create global quick actions in a different place in Setup than object-specific actions. They’re called global actions because they can be put anywhere actions are supported. Users can log call details, create or update records, or send email, all without leaving the page they’re on.
Compact Layouts
Compact layouts control which fields appear in the header. For each object, you can assign up to 10 fields, including the Name field, to display in that area.
Creating and customizing compact layouts for your objects isn’t required because system defaults are provided out of the box. However, we recommend using compact layouts to put important fields into record headers to help your mobile users get the information they need quickly.
What is Screen Flow
Screen flows are the flows where we have the user interaction and user will see a UI where they can either enter some inputs or select of records. For Example, You wanted to create an Account record using Screen Flow where the user need to input all the required fields and then on click on submit button the account is created.
A guided screen flow can do many things for us. We can reduce the amount of validation rules that we need for data entry. It provides us with a logical flow of data entry that can dynamically change based on the values inputted. A nice screen flow allows us to guide a user through a business process and avoid giant top to bottom screens.
