Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
150 Cards in this Set
- Front
- Back
Introduction to Force.com |
Data that describes data |
|
Introduction to Force.com |
False - Upgrades occur 3 times a year. |
|
Introduction to Force.com |
A browser based powerful point and click tool. |
|
Introduction to Force.com |
Write custom business logic |
|
Introduction to Force.com |
Create pages with custom look and feel |
|
Introduction to Force.com |
True - With Metadata API you can move configuration changes between sandbox and production environments |
|
Introduction to Force.com |
Load large amounts of data into the system |
|
Designing Applications |
A. User Interface |
|
Designing Applications |
True |
|
Designing Applications |
1. User Interface |
|
Designing Applications |
B. Applications |
|
Designing Applications |
1. Workflow |
|
Designing Applications |
1. Objects |
|
Building your Data Model |
1. Standard objects |
|
Building your Data Model |
True |
|
Building your Data Model |
True |
|
Building your Data Model |
Validation rules |
|
Building your Data Model |
Users with the "View Encrypted Data" permission |
|
Building your Data Model |
Cannot be unique |
|
Building your Data Model |
C. Custom objects come with an infrastructure including reporting, auditing and access control. |
|
Building your Data Model |
A. Standard picklists can be controlling fields but not dependent fields. |
|
Building your Data Model |
25 |
|
Building your Data Model |
A. Clear the value of this field |
|
Building your Data Model |
False - A Master Detail Relationship CANNOT contain a standard object on the detail side |
|
Building your Data Model |
True |
|
Building your Data Model |
False - the parent field on the child record is ALWAYS required |
|
Building your Data Model |
2 |
|
Building your Data Model |
False - cross-object field updates and roll-up summary fields can ONLY be done in a master-detail relationship |
|
Building your Data Model |
True - Reports can only display 1 child object at a time |
|
Building your Data Model |
True |
|
Building your Data Model |
B. A lookup relationship can span to multiple layers |
|
Building your Data Model |
False - a lookup relationship can be used to related 2 records from the same object. |
|
Building your User Interface |
1. Custom object tab |
|
Building your User Interface |
Helps you store objects in 1 logical and easy to access location |
|
Building your User Interface |
Defines the organisation of fields, custom links and related lists on an object detail or edit page |
|
Building your User Interface |
You can use the Enhanced Page Layout Editor |
|
Introducing Business Logic |
Formulas that span to related objects and reference fields on those objects. |
|
Introducing Business Logic |
False - The currency value returned is converted to the currency on the record where the formula is used. |
|
Introducing Business Logic |
10 unique relationships per object across all formulas and rules |
|
Introducing Business Logic |
True - You cannot reference cross-object formulas in roll-up summary fields. |
|
Introducing Business Logic |
Calculates values from a set of related records. |
|
Migrating Configuration Changes |
A. Change Sets |
|
Migrating Configuration Changes |
You might need to migrate customizations like apps, objects, code, reports or email templates from a development sandbox to a training sandbox or production environment |
|
Migrating Configuration Changes |
True - Approval processes are not available in a change set |
|
Migrating Configuration Changes |
Related |
|
Migrating Configuration Changes |
C. The entire change set fails to deploy |
|
Migrating Configuration Changes |
False - Change sets move metadata, not data |
|
Controlling Access to Records |
Public Read/write - View and edit all records |
|
Controlling Access to Records |
Used to define the most restrictive access level for all users in the organisation for records not owned by them. |
|
Controlling Access to Records |
All Internal Users |
|
Controlling Access to Records |
1. Record Owner |
|
Controlling Access to Records |
False - Sharing rules are used to extend record access and cannot be more restrictive than the Organisation-Wide Defaults |
|
Controlling Access to Records |
Created to grant access to records between users when access does not roll-up through the role hierarchy |
|
Controlling Access to Records |
Read/Write |
|
Controlling Access to Records |
When a user needs access to an Individual record, a user will full access to the records can add manual sharing to a record |
|
Controlling Access to Records |
Can be created declaratively but are used by developers to define reasons for access. |
|
Controlling Access to Records |
Full Access |
|
Controlling Access to Records |
B. Role hierarchy |
|
Controlling Access to Records |
D. Manual Sharing |
|
Controlling Access to Records |
c. Private (users can only see records they own) |
|
Controlling Access to Records |
B. Org-wide defaults can be set for both standard and custom objects. |
|
Controlling Access to Records |
A. System Administrators |
|
Controlling Access to Records |
1. Organisation-wide defaults |
|
Managing your Users' Experience |
Use profiles to assign the most restrictive access settings |
|
Managing your Users' Experience |
1000 |
|
Managing your Users' Experience |
A. View All Data |
|
Managing your Users' Experience |
False - Standard profiles can be cloned and then customised |
|
Managing your Users' Experience |
A. If you remove access to an app from a profiles, the users in that profile will still be able to see the tabs in that application. |
|
Managing your Users' Experience |
False - the API user has a profile and field-level security is applied to profiles. |
|
Managing your Users' Experience |
B. Record Types |
|
Designing Data Access Security |
C. Page Layouts |
|
Designing Data Access Security |
D. Page Layouts with Record Types |
|
Designing Data Access Security |
B. Field-level security |
|
Designing Data Access Security |
B. Organisation-wide defaults |
|
Designing Data Access SecurIty |
A. Field-level security on positions |
|
Designing Data Access Security |
A. By changing the organization-wide defaults |
|
Building Business Processes |
The ISNEW function checks if a formula is running during the creation of a new record and |
|
Building Business Processes |
The VLOOKUP function returns a value by looking up a related value in a custom object. This |
|
Building Business Processes |
C. REGEX |
|
Building Business Processes |
A. The ISCHANGED function compares the value of a field with its previous value and returns TRUE if the values are different. If the values are the same, this function returns FALSE. |
|
Building Business Processes |
The Developer Console is a collection of tools that you |
|
Building Business Processes |
20 - when the maximum is reached, the oldest log is overwritten |
|
Building Business Processes |
A workflow field update doesn't seem to be taking place: |
|
Building Business Processes |
A. Database changes |
|
Preserving Data Quality |
Postal/Zip Codes |
|
Preserving Data Quality |
Validation rules in conjunction with a roll-up summary field can be used to prevent users from adding or deleting records. |
|
Preserving Data Quality |
A. When a user saves a record. |
|
Preserving Data Quality |
Error message |
|
Preserving Data Quality |
Before the user can save the record. |
|
Automating Business Processes with Workflow |
A. It triggers an action when a record meets the criteria for the rule. |
|
Automating Business Processes with Workflow |
False - Time-Dependent workflow CANNOT be used when a workflow rule is set to evaluate Every time a record is created or updated. |
|
Automating Business Processes with Workflow |
A. Send an email |
|
Automating Business Processes with Workflow |
False - You can monitor the time-based workflow queue in the setup menu |
|
Automating Business Processes with Workflow |
True - If a record that has an action pending against it in the time-based workflow queue is modified so that the record no longer meets the criteria or the timing |
|
Automating Business Processes with Workflow |
False - If a record no longer meets the time based workflow rule criteria, the action is removed from the queue |
|
Automating Business Processes with Approval Processes |
True - The option to skip to the next step is available only if a step has subsequent steps. |
|
Automating Business Processes with Approval Processes |
C. Deciding step definition |
|
Automating Business Processes Using Visual Workflow |
A. 1 |
|
Automating business Processes Using Visual Workflow |
A. Custom button |
|
Automating business Processes Using Visual Workflow |
Variable |
|
Automating business Processes Using Visual Workflow |
Record Create |
|
Auditing Process |
It tracks modification to any standard or custom field, whose history is set to be tracked in the object's history related list |
|
Auditing Process |
Values are not tracked for: |
|
Auditing Process |
20 fields per object |
|
Auditing Process |
Activities performed and results generated by end users or code |
|
Auditing Process |
180 days |
|
Auditing Process |
Setup Audit Trail is the only tool that will track changes to the setup and configuration of Salesforce. |
|
Auditing Processes |
B. It allows developers to choose up to 20 fields per object for tracking changes. |
|
Auditing Processes |
A. Tracks setup changes made by developers and administrators |
|
Data Management |
Exporting data |
|
Data Management |
ONLY on initial data upload to Salesforce and ONLY when this feature has been enabled by Customer Support |
|
Data Management |
The first 3 characters |
|
Data Management |
The 15 digit Id is case sensitive, where the 18 digit Id is case Insensitive and should be used when analysing data in case insensitive tools such as Excel |
|
Data Management |
• From a URL |
|
Data Management |
ALL of the following are required: |
|
Data Management |
False - This can only happen on an Insert operation, not update |
|
Data Management |
A. URL |
|
Data Management |
50,000 |
|
Data Management |
Accounts |
|
Data Management |
In the Monitor section in the Setup menu |
|
Data Management |
True - Import wizards can only import up to 50,000 records and do not support all object data |
|
Data Management |
False - Data Loader does use the SOAP-based Web services by default. |
|
Enhancing the User Interface using Visualforce |
Visualforce - you should create a custom page to display a map component and include it in a page layout. |
|
Enhancing the User Interface using Visualforce |
Page layout - the chatter field can be included by using the page layout without the need for a custom page. |
|
Enhancing the User Interface using Visualforce |
Page layout with Record Type - create a record type for certain types of job application records and select to display pertinents fields using page layouts for each record type |
|
Enhancing the User Interface using Visualforce |
Visualforce - This requirement can only be fulfilled using Visualforce. |
|
Enhancing the User Interface using Visualforce |
• Inline editor |
|
Enhancing the User Interface using Visualforce |
Development mode |
|
Enhancing the User Interface using Visualforce |
The developer console is another tool for coding, |
|
Enhancing the User Interface using Visualforce |
Up to 1Mb of content, can display up to 15Mb of data |
|
Enhancing the User Interface using Visualforce |
A set of instructions that specify what happens when a user interacts with the components specified in the page. |
|
Enhancing the User Interface using Visualforce |
....... |
|
Enhancing the User Interface using Visualforce |
entityId |
|
Enhancing the User Interface using Visualforce |
relatedList |
|
Enhancing the User Interface using Visualforce |
sidebar |
|
Enhancing the User Interface using Visualforce |
Uploaded content that can be referenced in a Visualforce page |
|
Enhancing the User Interface using Visualforce |
In the Setup menu, under Develop, Static Resources |
|
Enhancing the User Interface using Visualforce |
A. Inline editor |
|
Enhancing the User interface Using Visualforce |
A. Text |
|
Enhancing the User interface Using Visualforce |
A. A set of instructions specifying what happens when a user interacts with the components specified in the page. Available for all standard and custom objects. |
|
Enhancing the User interface Using Visualforce |
C. Components are the smallest part of the Visualforce mark-up language and are used to |
|
Additional Uses for Visualforce |
A. Static resource |
|
Additional Uses for Visualforce |
True - Script tags do allow you to create JavaScript (or other types of) functions that can be used within your pages. |
|
Additional Uses for Visualforce |
False, you can use style tags OR use a CSS style sheet, uploaded as a static resource |
|
Additional Uses for Visualforce |
True - You can use the component to deploy a flow within a Visualforce page |
|
Additional Uses for Visualforce |
To include Web content or other Visualforce pages use: |
|
Additional Uses for Visualforce |
Creates public websites using Visualforce that can include data and content from a Salesforce application. |
|
Additional Uses for Visualforce |
A. Enables developers to build Web sites. |
|
Additional Uses for Visualforce |
Site.com is a Web content management system |
|
Additional Uses for Visualforce |
1. Upload site assets. |