Use Schema.PicklistEntry returned by Case.Status.getDescribe().getPicklistValues()
Use Schema.RecordTypeInfo returned by Case.SObjectType.getDescribe().getRecordTypeInfos()
Use SOQL to query Case records in the org to get all the RecordType values available for Case
Use SOQL to query Case records in the org to get all values for the Status picklist field
Enter an object specific action to Account and put it in the Account Layout
Enter an object specific action to Service and put it in the Account Layout
Enter an object specific action to Service and put it in the Service Layout
Enter an object specific action to Account and put it in the Service Layout
By using a helper class that can be invoked from multiple triggers
By performing DML transactions on lists of SObjects
By using the Database class to handle DML transactions
By using Maps to hold data from query results
CSS styles scoped to the component.
Custom Client-side rendering behavior.
Build scripts for minification.
Properties files with global settings.
Change field values using the Trigger.new context variable
Update the original object using an update DML operation
Display a custom error message in the application interface
Delete the original object using a delete DML operation
Loading the standard Pricebook ID using a system method
Executing methods as different users
Executing methods for negative test scenarios
Loading test data in place of user input for Flows
Cross-object sharing rules
Other Workflow types
The updates create a loop and the org limits for workflow time triggers per hour will likely be violated.
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.
The updates create a loop and the org be blocked until the admin resolves the issue
When the second trigger is saved an Imminent Loop Error message will be displayed and the workflow rule update will not save.
By using ApexMessage.Message() to display an error message after the number of DML statements is exceeded
By using PageReference.setRedirect() to redirect the user to a custom Visualforce page before the number of DML statements is exceeded
By using Limits.getDMLRows() and then displaying an error message before the number of DML statements is exceeded
By using Messaging.SendEmail() to continue the transaction and send an alert to the user after the number of DML statements is exceeded
Better performance for custom Salesforce1 Mobile apps
Better integration with Force.com sites
More pre-built components to replicate the Salesforce look and feel
More centralized control via server-side logic
Validation Rules, Before Triggers, After Triggers, Assignment Rules, Workflow, Commit
Before Triggers, Validation Rules, After Triggers, Assignment Rules, Workflow, Commit
Validation Rules, Before Triggers, After Triggers, Workflow, Assignment Rules, Commit
Before Triggers, Validation Rules, After Triggers, Workflow, Assignment Rules, Commit
Use the test menu on developer console to run all test classes for the account trigger.
Use Execute Anonymous feature on developer console
Use New button on Account tab to create new record
Use force.com IDE
Because roll-up summary fields are not displayed on edit pages, you can use them in validation rules but not as the error location for you validation.
Validation errors can display when saving either the detail or master record.
Once created, you cannot change the detail object selected or delete any field referenced in your roll-up summary definition.
Advanced currency management has no affect on roll-up summary fields.
Automatically derived fields, such as current date or current user, are allowed in a roll-up summary field.
Partial copy sandbox
Developer Pro Sandbox
StandardController system methods that are referenced by Visualforce
A static resource that contains CSS and images
Salesforce UI Apex Test Execution
Workbench Metadata Retrieval
ANT Migration Tool
Sub-blocks cannot reuse a parent block's variable name
Parallel blocks can use the same variable name
A variable can be defined at any point in a block
Sub-blocks can reuse a parent block's variable name if its value is null
A static variable can restrict the scope to the current block if its value is null
A custom exception
A try/catch construct
Data can be lost when converting from autonumber to text
Data can be lost when converting from number to currency (assuming that field lengths are identical)
Data can be lost when converting from simple picklist to multi picklist
Information can be lost when converting from text area (rich) to text area (long)
Model: Standard and Custom Objects; View: Visualforce Pages; Controller: Apex Code
Model: Standard and Custom Objects; View: Visualforce Pages; Controller: s-Controls
Model: Schema Builder; View: List Views; Controller: Setup Console
Model: Apex Code; View: List Views; Controller: Setup Console
In a Controller Extension
In a Custom Controller
In a Standard Extension
In a Standard Controller