[SalesForce] Update Opportunity Stage when DocuSign Envelope Status is ‘Signed’

I am very new to triggers but would like to set up a simple trigger. Any help is greatly appreciated! Pseudo code below.

on insert or update

if (Docusign Envelope Status is equal to 'Signed' AND Opportunity Status does not equal ‘Agreement Signed Pending Rollout’){

     update Opportunity Stage to ‘Agreement Signed Pending Rollout’

}

Will this work?
How should I go about compiling the trigger?

variables                        API Name
Docusign Envelope Status         dsfs__Envelope_Status__c   
DocuSign Oppty                   dsfs__Opportunity__c

Best Answer

This simple trigger will do the trick.

trigger opportunityStage on dsfs__Opportunity__c(before insert, before update){
    for(dsfs__Opportunity__c o : trigger.new){
        if(o.dsfs__Envelope_Status__c == 'Signed' && o.stage != 'Agreement Signed Pending Rollout'){
            o.stage = 'Agreement Signed Pending Rollout'
        }           
    }
}

Explanation:

Why used before triggers? When we use before triggers, the values are not yet saved to database and any changes we made in trigger will get saved to database without any extra DML.
What is trigger.new? It is trigger context variable which holds the list of currently modified or inserted records.
Why == in if condition but = in next line? == is comparison operator which is used to compare two values. = is assignment operator which is used to assign value in right hand side to left hand variable.

Hope it helps.

Related Solutions

[SalesForce] Apex trigger needs access to parent object fields

Information not directly on the Opportunity is not automatically available so you have two options...

One: Create formula fields on the Opportunity to get the information from Account then simply use those fields to directly populate the info on the new on boarding record.

Two: Or via code - Querying for the Opportunity and related Account fields:

trigger CreateOB on Opportunity (after insert, after update) {
    Onboarding__c[] inserts = new Onboarding__c[] {};
    for (Opportunity o : [
            Select StageName, Name, AccountID, Account.BillingStreet
            From Opportunity
            Where ID IN :trigger.new
            ])) {
        if (o.StageName == 'Closed Won') {
            Opportunity old = Trigger.oldMap.get(o.Id);
            if (o.StageName != old.StageName) {
                inserts.add(new Onboarding__c(
                        Account_Name__c = o.AccountId,
                        Name = o.Name,
                        BillingAddress__c = o.Account.BillingStreet
                        ));
            }
        }
    }
    insert inserts;
}

[SalesForce] Avoiding Recursion While Updating Trigger Records

If you are worried about recursive calls, a Boolean flag is a time tested strategy. Just set one in your @future method and don't rerun that logic if the flag is set. Using a handler pattern will greatly facilitate this strategy. Below is a simple outline of what mine would look like.

Handler

public class LeadTriggerHandler
{
    public static Boolean isCalledFromVetHelper = false;

    final List<Lead> newRecords;
    final Map<Id, Lead> oldMap;
    public LeadTriggerhandler(List<Lead> newRecords, Map<Id, Lead> oldMap)
    {
        this.newRecords = newRecords;
        this.oldMap = oldMap;
    }

    public void afterUpdate()
    {
        if (!isCalledFromVetHelper)
        {
            // VetHelper logic
        }
        // other update logic
    }
}

Callout Helper

public class VetHelper
{
    @future
    {
        LeadTriggerHandler.isCalledFromVetHelper = true;
        // existing logic
    }
}

Trigger

trigger Lead on Lead (after insert, after update)
{
    LeadTriggerHandler handle = new LeadTriggerHandler(trigger.new, trigger.oldMap);
    if (trigger.isBefore)
    {
        // events
    }
    if (trigger.isAfter)
    {
        if (trigger.isInsert) handle.afterInsert();
        if (trigger.isUpdate) handle.afterUpdate();
    }
}

Best Answer

Related Solutions

[SalesForce] Apex trigger needs access to parent object fields

[SalesForce] Avoiding Recursion While Updating Trigger Records

Related Topic