[SalesForce] How to lock down an opportunity and prevent edits after generating a sales order

I'm new to Salesforce and even newer to apex, so I'm struggling a bit here.

My goal is to lock down an Opportunity once a sales order has been generated on my company's side. My current idea is to have a custom read-only "Locked" field within the Opportunity object. I want to use the SOAP API to update this value and then have an Apex Trigger (after update) set all the fields in the Opportunity to read-only.

Where I am getting slowed down is in writing an Apex trigger to set fields to read-only, currently I only have the boilerplate code

trigger lockOpportunity on Opportunity (after update) {
    for (Opportunity myOpp : Trigger.new){
        myOpp.setAllMyFieldsToReadOnly;
    }
}

I can get as far as setting specific values, along the lines of myOpp.Description = "opp description"; but I don't know how to access field properties to set them to read-only. Or, if there's a way to lock down the entire object in a single call, that would be even better.

Thanks.

Best Answer

You can't set fields to Read-Only for a specific record. There are two possible solutions and neither of them require code.

Add a validation rule to the Opportunity object that has criteria something like

Locked__c && !ISCHANGED(Locked__c) && ISCHANGED(LastModifiedDate)
Create a page layout that has all the fields marked as read-only and then have a record type called Locked that has the read-only layout assigned to it. When the Locked field is checked, then have a workflow rule update the record type.

In most cases you should really use both. The validation rule is great for ensuring that it's locked in the myriad alternative ways to edit records, i.e. list view mass edit and data loader. The page layout will improve the end user experience by not letting them do a huge number of edits only to block them on save (in other words, wasting their time).

Also, in most cases you'll need to adjust the criteria for the workflow rule to allow edits by certain profiles, i.e. finance teams and system administrators.

Related Solutions

[SalesForce] Relating a task when an opportunity is updated. Before or After Update trigger

You can absolutely use an before trigger for that and it will work. That said, I typically leave the before trigger to the simpler functionality. IMO, updates to and validations against the records being acted on should happen in the before trigger, most everything else like cross object logic and callouts/emails/etc. should happen after. But there is nothing that says you can't create records before if you desire.

[SalesForce] Unit Test is Providing 0% Coverage for Apex Trigger

The trigger code is having lot of redundancy, So I modified it. before posting the modified code few lines of explanation what I changed. you collected account Ids twice and did the condition check twice where once is more enough. I am also made changes to the test class, where Task data is provided which is not required because the trigger has to create it once the necessary conditions are met. I am expecting this trigger should work for you, if there is any errors feel free to post as a comment.

trigger OpportunityAfter on Opportunity (after update){

    Set AccountIDs = new Set();

    for(Opportunity o : trigger.new){
        if(opp.StageName == 'Closed - Lost' && opp.Business_Line__c == 'Workforce' && 
            opp.Survey_Type__c != 'APulse' && trigger.oldMap.get(opp.Id).StageName != opp.StageName){

                AccountIDs.add(o.AccountId);
         }
    }

    Task[] tasksToInsert = new Task[]{};

    for (Account acc : [Select Id, Name, OwnerId from Account where Id IN :AccountIds]){
        for (Opportunity opp : trigger.new){
            if(opp.AccountId == acc.Id){
                Task tas = new Task();
                tas.WhatId=acc.Id;
                tas.OwnerId=opp.OwnerId;
                tas.Subject='Follow-up: ' + opp.name + ' - ' + acc.name;
                tas.ActivityDate=(opp.CloseDate + 180);
                tas.Description='Follow up to see how engagement initiatives are going and if Avatar can help. Refer to lost opportunity: ' + opp.name;
                tasksToInsert.add(tas);                                                         
            }
        }
    }
    if(tasksToInsert != null && !tasksToInsert.isEmpty())
    Database.insert(tasksToInsert);

}

@isTest
public class TestClass {

    static testMethod void myUnitTest() {

    //Set up user
    User u1 = [SELECT Id FROM User WHERE Email='abc@sampleemail.com'];
    test.startTest();  
    //Run As U1
    System.RunAs(u1){

    System.debug('Testing trigger... (single record validation)');

    //NEW Account record
    Account acc = new account();
    acc.Name = 'Test Account';
    acc.Industry = 'Healthcare';

    insert acc;

    //NEW Opportunity record
    Opportunity opp = new Opportunity();
    opp.Name = 'Test Opportunity'; 
    opp.CloseDate = System.today();
    opp.StageName = 'S1 - Investigative';
    opp.Type = 'Repeat Business - Wrkforce HC';
    opp.AccountId = acc.Id;
    opp.Survey_Type__c = 'Product Name';

    insert opp;

    opp.StageName = 'Closed - Lost';
    opp.Reason_Won_Lost__c = 'Relationship';
    opp.Business_Line__c = 'Workforce'  //added this line to meet the if condition while collecting the set of id in the trigger.

    update opp;
   test.stopTest();
    // Here I am expecting the task has been inserted and doing a query for it         and check it in the assert statement.
   Task  testTask=[Select Id, WhatId from Task where WhatId=:acc.Id];
    //Validate single insert
    System.assertEquals(acc.Id, testTask.WhatId);

    }
    }
}

Best Answer

Related Solutions

[SalesForce] Relating a task when an opportunity is updated. Before or After Update trigger

[SalesForce] Unit Test is Providing 0% Coverage for Apex Trigger

Related Topic