• NOT(ISPICKVAL(FieldName,"")) && ISCHANGED(FieldName)

   

• Custom Objects 

   

   
• Custom objects require special treatment so that they can participate in Relationship Queries. For the relationship field name of a custom object, “__r”

• updates all open invoices when the unit price of a merchandise item goes down.
• xecutes whenever a merchandise record is saved

• xpression1 != expression2

• IF(Maint_Amount__c + Services_Amount__c<> Amount,   "DISCOUNTED", "FULL PRICE")

   

  <!-- --> This formula displays “DISCOUNTED” on an opportunity if its maintenance amount and services amount do not equal the opportunity amount. Otherwise, displays “FULL PRICE.” Note that this example uses two custom currency fields for Maint Amount and Services Amoun
• BLANKVALUE

• BLANKVALUE(Department, “Undesignated”)

   
• ISBLANK
• IF(ISBLANK(Services_Amount__c), 0,1)
• If you use this function with a numeric field, the function only returns TRUE if the field has no value and is not configured to treat blank fields as zeroes.
• ISNULL
• This formula field checks five fields to see if they are blank. If so, a zero is counted for that field. A “1” is counted for any field that contains a value and this total is divided by five

7 more annotations...

• Declare a for loop.
• During development you typically leave a trigger inactiv
• li.Unit_Price__c = li.Merchandise__r.Price__c;

  •         if ( li.EmailBouncedDate(ISNULL(EmailBouncedDate, 0) =   li.EmailBouncedDate(ISNULL(EmailBouncedDate, 0)

  •         if ( li.EmailBouncedDate(ISNULL(EmailBouncedDate, 0) < li.Unit_Price__c ){
• The final statement
• Iterates over the list of open line item. As you iterate, the current line item is assigned to the variable li.
• You only want to take an action if this is true.
• Finally, update the unit price on the current line item

5 more annotations...

• efine a list variable that will hold a list of line items.
• select only those that are in the set of records that triggered this code to run and have their status set to Negotiating
• Between the square brackets, enter a query that pulls information
• Invoice_Statement
• Status
• openLineItems
• It pulls only the unique IDs of the records that are new.
• Trigger.new

6 more annotations...

• create the trigger definition, which contains the trigger name, the affected object, and an action that fires the trigger
• but it's now ready to accept any logic that you want to execute when a Merchandise record is updated.
• The trigger you defined fires after a record is updated.

  • does this have to be an actual human interaction?

1 more annotation...

• analogous
• Filter
• Can be used as filter criteria in a SOQL query FROM or WHERE clause.
• Nillable
• Sort    Indicates whether a query can sort on this field (true) or not (false).
• Update
•    

  Can be updated using the API.

   

   

5 more annotations...

• GetUpdatedResult

  • could this work as a work around? Set the enddate set time after email is sent to trigger?

• Results are returned for no more than 30 days previous to the day the call is executed.

• For custom objects, the custom flag—a Boolean field in the describeSObjectResult—is true.

• FirstOpenDate

  • maybe i have value backwards
• TaskId

• automatically updated during API operations.
• EmailStatus
• Parent Reference Fields
• Case has a Contact field that contains a reference to the contact parent of the case

  • task has parent: task.LeadId
• Case.ContactId

3 more annotations...

• Your application (endpoint) server's SSL/TLS may be configured to require client certificates (two-way SSL/TLS), in order to validate the identity of the Salesforce

• a message cannot be delivered, the interval between retries increases exponentially, up to a maximum of two hours between retries.
• Instead of polling, which was required in previous releases, you can now use outbound messaging to trigger execution logic when Salesforce raises an event. In previous versions of the API, client applications had to poll Salesforce to find out if relevant changes had occurred. Because most changes eventually trigger workflow if a rule exists for it, you can use this to trigger actions based on Salesforce events.

   

   
• The metadata needed for outbound messaging, including the definition of the notifications() call, which sends the outbound SOAP message to an external service, is in a separate WSDL.

1 more annotation...

• Sales Objects 

   

   

  • Lead Status is an ID