Question : Time-based workflow is applicable for, Every time a record is created or edited
1. True 2. False
Correct Answer : 2
Explanation: Are there any restrictions for time-based workflow? You cannot configure time-dependent actions for workflow rules for which the evaluation criteria is set to "Every time a record is created or edited."
Question : . What is used for tracking changes to configuration of Salesforce CRM?
1. Setup Audit Trail 2. Setup Logging 3. Default Available
Correct Answer : 1
Explanation: Auditing Auditing features do not secure your organization by themselves, but these features provide information about usage of the system, which can be critical in diagnosing potential or real security issues. It is important that someone in your organization perform regular audits to detect potential abuse. The other security features provided by Salesforce are preventative. To verify that your system is actually secure, you should perform audits to monitor for unexpected changes or usage trends. Auditing features include: Record Modification Fields All objects include fields to store the name of the user who created the record and who last modified the record. This provides some basic auditing information. Login History You can review a list of successful and failed login attempts to your organization for the past six months. See Monitoring Login History. Field History Tracking You can also enable auditing for individual fields, which will automatically track any changes in the values of selected fields. Although auditing is available for all custom objects, only some standard objects allow field-level auditing. See Tracking Field History. Setup Audit Trail Administrators can also view a Setup Audit Trail, which logs when modifications are made to your organization's configuration. See Monitoring Setup Changes.
Question : Checkbox can be controlling field only and not a dependant field. 1. True 2. False
Correct Answer : 1
Explanation: Dependent Picklist Considerations Consider the following when defining dependent picklists: Checkboxes : Checkbox fields can be controlling fields but not dependent fields. Converting fields : Convert your existing fields to dependent picklists or controlling fields without affecting the existing values in your records. Going forward, dependency rules apply to any changes to existing records or new records. Default values : You can set default values for controlling fields but not for dependent picklists. Field-level security Field-level security settings for a controlling field and dependent picklist are completely independent. Remember to hide controlling fields whenever its correlating dependent picklist is hidden. Import : The import wizards do not consider field dependencies. Any value can be imported into a dependent picklist regardless of the value imported for a controlling field. Lead conversion : If you create a dependency for lead fields that map to account, contact, and opportunity fields for lead conversion, create the same dependency on the account, contact, or opportunity as well. Dependent picklists and controlling lead fields can be mapped to account, contact, or opportunity fields with different dependency rules. Multi-select picklists : Multi-select picklists can be dependent picklists but not controlling fields. Connect Offline : While controlling fields and dependent picklists are available in Connect Offline, the logic between them is not. Page layouts : Make sure controlling fields exist on any page layout that contains their associated dependent picklist. When the controlling field is not on the same page layout, the dependent picklist shows no available values. For visually-impaired users, make sure the dependent picklist is lower on the page layout than its controlling field. If a dependent picklist is required and no values are available for it based on the controlling field value, users can save the record without entering a value. The record is saved with no value for that field. Record types : The values in your controlling fields are determined by the record type selected. The values in your dependent picklists are determined by the record type and controlling field value selected. In short, the values available in dependent picklists are an intersection of the record type and controlling field selections. A checkbox screen field is of type boolean. Use a checkbox screen field to offer flow users a yes-or-no choice. Available in: Enterprise, Performance, Unlimited, and Developer Editions For example: " Whether to opt into a marketing campaign. " Whether to receive a follow-up call after a purchase or case resolution. " Whether an important policy is understood. In this case, you can validate that the user selects the checkbox before proceeding to the next screen.
1. The 15 digit Id is case sensitive, where the 18 digit Id is case Insensitive and should be used when analyzing data in case insensitive tools such as Excel 2. The 15 digit Id is case Insensitive, where the 18 digit Id is case sensitive and should be used when analyzing data in case insensitive tools such as Excel 3. Both 15 digit and 18 digit Id is case sensitive and should be used when analyzing data in case insensitive tools such as Excel 4. None of above