Ensure an opportunity has at least one product added.
Approve expense reports automatically when less than $50
Update the PTO record field with the user's manager.
Require CFO to review the salary range for all job offers
The field can be unique based on case-sensitive or case-insensitive values.
The field must contain at least one number and at least one letter.
The field must be unique since duplicates are not allowed within salesforce
The field contains unique record identifiers from a system outside of salesforce.
Yes they cannot
No they can
Roll up summary fields can only be created on the master of master-detail relationship
The roll up summary field inherits the field level security of the child object.
Multi select picklist files can be used in the field column of the field column of roll up summary filters.
Changes to the value of a roll up summary field can trigger assignment rules to run
Loading page color
Action tab bar
Header and Search
Create an action in the Service object and add it to the Account page layout
Create an action in the Service object and add it to the Service page layout
Create an action in the Account object and add it to the Service page layout.
Create an action in the Account object and add it to the Account page layout.
Lighting process builder
To update descriptions of standard and custom objects
To modify custom field help text on standard objects
To enable field history tracking on standard objects
To create new lookup or master-detail object relationships
Create a custom Invoice object and connect SAP using data loader
Connect an OData Publisher Service for SAP database
Use SAP data export functions
Create an External object connected to an invoice table in SAP
Workflow rules cannot trigger a validation rule
Workflow rules occur after validation rules and thus override validation rules.
Field Level Security prevents the validation rule from running.
Users cannot view records assigned to a record type their profile does not have access to
The ability to create records of a specific record type is determined by the profile
Record types can only be assigned to one profile at a time
Record types can be used to define picklist values available for a given field
Field level security
Create a global action on Account
Create a feedback object as a parent account
Create predefined values for most of the fields
Create an object-specific action on Account
Clone records, add users, and assign permissions.
Send email, send outbound messages, and launch a flow.
Send email and delete or clone records.
Send email, create a task, and create or update records.
Master-detail relationship can be converted to a lookup relationship if no roll-up summary fields exist on the master subject
Master-detail relationships cannot be converted to a look-up relationship
A master-detail relationship cannot be created if the custom object on the detail side already contains data
Standard objects can be on the detail side of a custom object in a master-details relationship
Deleting a master record in a master-detail relationship deletes all related detail records
They allow cases to be assigned to a queue
They allow for more than one active rule at the same time
A predefined Case Team is mandatory for each rule entry
They allow for more than one rule entry for each assignment rule
Salesforce processes case assignment rules before workflow rules
URL / choose the URL
Press "validate and sync"
Choose "include as index field"
Choose "include in Salesforce searches" option
Viewing page layouts in a new window
Editing custom settings
Showing selected objects on a page
Creating a new record type
Lighting process builder
In the Chatter feed of the user who created the record
In the Chatter feed of the first user who follows the record on which the record was created
As the first entry in the feed for the new record
In the user profile feed for all users who can view the record
In the feed for the record on which the new record was created
Data can be lost when converting from auto-number to text
Data can be lost when converting from number to currency (assuming that field lengths are identical)
Information can be lost when converting from text area (rich) to text area (long)
Data can be lost when converting from simple picklist to multi picklist
Reports and Dashboards
Matching ID field
Trigger another rule
Out of hour limit (loop)
Create a partial copy sandbox from a partial copy sandboxes environment
Save a template for re-use when creating a partial copy sandbox environment
Specify the data range for data being replicated in a partial copy sandbox environment
Specify the objects whose data should be replicated in the partial copy sandbox environment
Lighting process builder
Action bar color
Header and search bar color
Notification and search icon
Background color on loading page
The image on loading page
Approval with Apex Trigger
Approval with Workflow
Assigning a user a role that allows read access to an object
Assigning a user a permission set that allows for read and Edit access to an object
Assigning a user a profile that allows read access to an object
Assigning a user a public group that allows for read and edit access to an object
No data is lost when changing Picklist to Multipicklist
Data is lost when changing Number to Currency
Rollup summary fields will stop calculate if Master Detail is changed to lookup
No data is lost when converting Text to auto number
Data can be lost when changing from Rich Text to Long Text
Open page layout in new window
To update descriptions of standard and custom objects
The contacts master detail field is deleted from the object
The contacts master detail also converts to lookup
The contacts master detail becomes the primary
The contacts master detail values are cleared from invoice
Matrix format with chart
Tabular format with a chart
Summary format with a chart
Joined format with a chart
Joined report blocks are formatted as matrix reports
Bucket field are not supported in joined reports
Report formula fields are not supported in joined reports
The rows to display filter is not supported in joined reports
Cross filter are not supported in joined reports
External Lookup Relationship
Master Detail Relationship
Indirect Lookup Relationship
The VF page references / fields that the user can't access
The menu configuration has not been set up correctly for the VF page
The smart search is not enabled for the VF page
A tab has not been created for the VF page
The record owner and those above the specialist role in their hierarchy
The record owner and the specialists in their hierarchy
The record owner and the managers in their hierarchy
The record owner and the directors in their Hierarchy
Check sharing rules
Check report filters
Check the report folder sharing settings
Check organization-wide defaults
Check the user's profile for object settings
Public or private groups
Owner based sharing rules
Criteria based sharing rules
Dynamic role hierarchy
Visualforce pages on a field set have attributes for width and height
Visualforce pages can only be placed in the visual force section in the page layout
Visualforce pages on a page layout have attributes for width and height
Visualforce pages can be placed anywhere in a page layout
Workflow rules trigger validation rules on field updates
A recursive loop potentially results in exceeding organizational limits
Cross-object workflow rules result in re-evaluation after field change
Workflow rules trigger more workflow rules to be re-evaluated
A namespace is not required to create an unmanaged package
A namespace is required to create an unmanaged package
The person who created the unmanaged package has no control over the installed components
The person who created the unmanaged package can change or upgrade installed components
Create separate home page and custom components and layouts; Assign to users by profile
Expose specific elements within a home page custom component determined by role
Create separate home page and custom components and layouts; Assign to users by role
Expose specific elements within a home page custom component determined by Profile
Use "prevent duplicates"
Include a column in the import file that has other record name(SF ID)
Run duplicate check
Build an approval process that requires unanimous approval from the manager and VP of sales
Build a validation rule that does not allow a user to save the opportunity record
Create a workflow rule that checks for close date less than 60 days and add an email alert
Create a lighting process builder flow that submits the record for an approval process
Force.Com Migration Tool
Force.Com IDE integrated development environment
Create three pages layout to determine the fields and picklist values for each user based on the division indicated on their user record. Use field level security to restrict access to division's fields
Create additional custom assessment objects, one for each division, to track their assessment so information can be tracked separately. Use profiles to restrict access to the three custom objects
Create a separate page layout for each division and assign them using profiles. Use the profile settings to configure each division's custom field list and picklist values for assessments
Create separate assessment record types for each division and use them to limit picklist values. Create separate page layout s for each record type and use profiles to restrict record type access
Lightning process builder
Custom AppExchange-app for product-pricing
Workflow on Opportunity/Opportunity Product
Formula fields on Opportunity/Opportunity Product
Custom Visualforce Component
Standard Lightning components
Object-specific publisher actions
Global publisher actions
Custom Lightning components
Active Validation rules
Previously fired workflow rules
Active Escalation rules
Cross-object workflow rules
Criteria-based sharing rules
For sale in App Ex
For move to production
For open source
Should be deployed from Dev Edition
If a picklist value is added to the master picklist, then the new value must be manually included in the appropriate record types
If a picklist value is removed from the master, then it is no longer available when records assigned to that value are unchanged
If a record type is renamed, then the list of values included in that record type are also changed to newly renamed record types
If values are added to the Opportunity Stage, Case Status, and Lead Status fields, then the values must be manually adjusted for each record type
Have the same icon as Business accounts
Are enabled via feature license
Can only be merged with other person accounts
Are enabled by default
Do use space in both account and contacts table
Developer pro sandbox
Design an approval process
Create a process using lightning process builder
Create a workflow rule
Use Visual Workflow
2 page layouts, 2 record types, 2 profiles
2 page layouts, 1 record type, 2 profiles
1 page layout, 1 record type, 1 profile
1 page layout, 2 record types, 2 profiles
Select and install an AppExchange product to meet the contract generation needs
Create the HTML template for contract and store it in the public folder
Store a template in the static resources and configure the action link template to use it
Enable the contracts feature and create a custom contract template based on the standard template
Organization-wide settings for the custom object do not grant access using hierarchy.
The supervisor's role is not above the subordinate's role in the hierarchy
Organization wide settings for the custom object grant access to their users with the same role
The supervisor requires a permission set in order to view the subordinate's record
Create criteria based sharing rules
Create standard role hierarchies.
Set organization wide sharing defaults to private
Set organization-wide sharing defaults to public read/only
The create action will ignore field requirements
The create action will respect validation rules
The create action allows a user to select a record type
The create action can pre-define contact field values
Lightning Process Builder
On a custom list view
On the person account
On a related list
On a web-to-case form
On the user object
Developer Pro Sandbox
Partial Copy Sandbox
By creating a custom "Create a record" action on the account.
By creating a custom "Detail page " Button on the account.
By creating a custom "Detail page" Button on the contract.
By creating a custom "Create a record" Action on the contract.
To create a custom visual flow
Navigate to Apex trigger
To create a record page
To a process to update current record
To external system using data of salesforce
Unmanaged packages can be upgraded
Unmanaged packages don't have a version number
Tests are executed during deployment
Unmanaged packages have a namespace prefix
Components of unmanaged packages can be edited
Selected publisher actions
Mini page layout
Enable field validation by sale process.
Create unique opportunity stages by sales process
Specify a different page layout by sales process
Prevent access to secure data fields by sales process
None of the above
Lighting process builder
Create different case record types for IT, HR, and Customer support. Assign different page layouts to each record type by role.
Create different case record types for IT, HR, and Customer support, Assign different page layouts to each record type by profile.
Create different case field sets for IT,HR and customer support. Assign different field sets by role
Create different case field sets for IT,HR and customer support. Assign different fields sets by profile
Include a column in the import file that has either record names, Salesforce ID's , or external IDs that can be used to match records
When importing the file, select the "prevent Duplicates" option on the last step of the import wizard and import the file.
After importing all of the custom objects, review all records created and manually merge any duplicate records.
After importing all of the custom objects, run a duplicate check report, export the report to CSV file and run a mass delete to purge any duplicates.
The updates create a loop and the org be blocked until the admin resolves the issue
The updates create a loop and the org limits for workflow time triggers per hour will likely be violated.
When the second trigger is saved a Imminent Loop Error message will be displayed and the workflow rule update will not save.
Loop is allowed to run 25 times within one hour. If it does not end on its own the process will be stopped by R&D.
Cross object field updates between the project and account records are not supported.
The account record can include roll up summary field with data from the project records.
The account lookup field on the project record can be made optional.
Users can only delete accounts in they have access to related project records
Web to case
The user uses a custom report type which does not include the industry field.
The user does not have industry field visibility in the field level security.
The industry field has no record values in the account.
The industry field is not enabled for the particular record type.
Auto response rule.
Feed quick Action
Approval process with Apex Trigger.
Process Builder with submit for approval action
Two-step Approval process
Approval process with Time -Dependent workflow action.
Custom tabs are default off for all the users.
Custom tabs are exposed for all users'
Custom tabs are hidden for all users
Custom tabs are default on for all the users
By adding actions in the salesforce1 action bar section.
By adding a mobile layout and assigning it to a profile.
By adding Quick actions in the publisher section.
By adding visualforce pages to the mobile cards section
Chatter data will be copied to the sandbox by default
Username will be modified uniquely for that sandboxes (
Default email deliverability is set to system email only
Users' email addresses will not be modified
Force.com Migration Tool
The master record can't be deleted if has a child record
The record is deleted and placed in the recycle bin.
The look up field on the junction object is cleared.
The record is permanently deleted and can't be restored.
Groups cannot be the last item in the navigation menu
Groups is showing up in the recent section and not in the navigation menu
Groups is included in the smart search items but not on the navigation menu
Groups is not included in the selected list of the navigation menu
Roll-up summary field
Use compare operator
Use NOT EQUAL operator
The data will be save but industry will not be saved
Validation will be ignored and Technology fully inserted
The data will not be saved and display an error
The data will be save but will display an error on industry
Radio buttons(multi select)
Picklist (multi select)
Salesforce lighting app
Lightning process builder
Salesforce1 mobile app
Create a criteria-based sharing rule using the project's department that grants access to users by permission sets.
Before UAT User Acceptance Testing
When a Production user is added
After a major update
Create a new opportunity quick action that validation account ownership
Set the organization wide default sharing on opportunities to private and recalculate sharing
Set the organization wide default sharing on opportunities to controlled by parent
Create an opportunity validation rule that compares the opportunity and account owner
Administrators may choose whether to enforce validation rules and triggers
The lead's most recent campaign record is automatically applied to "Primary campaign source" field on the opportunity
Users can convert leads that are associated with an active approval process
Multi-select picklist values on lead records overwrite values on the contact's corresponding field
The system automatically maps standard lead fields to standard account, contact, and opportunity fields
Use a custom image
Rollup Summary Field
Changing the datatype of a field used in a report from text to an encrypted field
As an external ID from number to text
In an apex class from number to text
In lead conversion from number to text
Request to join public groups
Mention other members of the group
Add them on FB,Twitter and Instagram
Invite other members to groups they are a part of
The record owner and the global marketing public group
The record owner and anyone above the owner in the role hierarchy
The global marketing public group and anyone above the owner in the role hierarchy
The global marketing public group, the record owner, and anyone above the owner in the role hierarchy
When the primary object is a custom object and is deleted, then the report type and any reports created from it must be deleted manually
Any object can be chosen unless the object is not visible to the person creating the report type through security settings
The detail object in a master-detail relationship cannot be added as a secondary object on a custom report type
Once a report type is saved with a standard or custom primary object, the primary object cannot be changed for the report type
Download all contacts to a CSV file and use an email client to send the emails
Develop apex code and Visualforce pages to sent the emails
Research and evaluate products available on appExchange to send mass emails
Request salesforce increase the number of maximum daily emails
Create mobile nav menus for both the sales and marketing profiles
Create sales and marketing profiles and ensure read access to different objects
Create roles for sales and marketing and assign a custom homepage layout for each role
Create public groups for sales and marketing and create mobile nav menus for each group
A summary report on the opportunity object
A tabular report on the account object
A tabular report on the opportunity object
A summary report on the account object
Use field-level security on page layouts to restrict editing fields
Use field-level security to mark fields as read=only on the sales profile
use record types with field sets and restrict editing fields using field-level security
Use multiple record types, page layouts, and profiles
Use a private sharing model granting record across using hierarchy, manage field access with record types and field-level security
Use a private sharing model granting access using customer settings, manage field access with page layouts and field-level security
Using custom settings, manage field access with record types and page layouts
Hierarchy, manage field access with field-level security
Roll-up summary field
Create a workflow rule on the user object to assign a permission set
Create a flow on the user object to assign permission set
Create a lighting process on the user object to launch a flow
Force.com Data Loader
Application Data Model Wizard
Contact Salesforce to have the component activated for the Lightning App Builder.
Navigate to Setup-Customize-User Interface to enable the component for the Lightning App Builder.
Purchase a license for the Lightning App Builder.
Join the pilot Lightning App Builder team.
Event (without invitees)
You have the correct email address
HTML does not work in sandbox, make sure your email has no HTML
Check the deliverability settings
Look at the system audit trail
In a batch update, workflow is only retriggered on the entities where there is a change
Only workflow rules on the same object as the initial field update will be re-evaluated and triggered.
Only workflow rules that didn't fire before will be re-triggered.
Cascade of workflow rule re-evaluation and triggering can happen up to ten times after the initial field update that started it.
Any workflow rules whose criteria are met as a result of the field update will be ignored.