Advanced Apex Programming for Salesforce.com and Force.com

At the floor, this is often extremely simple. reflect on a state of affairs the place you must create a job while the likelihood of a chance adjustments from 10 to any greater quantity. chances are you'll enforce this performance utilizing a mode that will be referred to as in the course of an after-update set off reminiscent of the AfterUpdateOpportunityCreateTask1 technique proven the following: public static void afterUpdateOpportunityCreateTasks1( List newList, Map newMap, Map oldMap) { List newTasks = new List(); for(Opportunity op: newList) { approach. debug('old likelihood ' + oldMap. get(op. id). likelihood + ' new chance ' + op. Probability); if(oldMap. get(op. id). chance == 10 && op. likelihood > 10) { newTasks. upload( new Task(ownerId = op. OwnerID, WhatID = op. identification, ActivityDate = Date. Today(). addDays(2), Subject='Opportunity level update', Type='Other')); } } insert newTasks; } this can be a regular bulk implementation of an answer to this type of challenge. And if you happen to have been a specialist development an answer for a specific association, that will be the top of the tale. All that's left is to construct a few try equipment, one in all that is proven the following: inner most static ultimate Integer numberOfOpportunities = five; static testMethod void testTaskCount() { List ops = new List(); for(Integer x=0; x opMap = new Map(ops); List projects = [Select identity, WhatID from job the place WhatID in :opmap. keyset() And topic ='Opportunity degree update']; method. AssertEquals(numberOfOpportunities, projects. size()); } Let’s flip our awareness for a second to the workflow proven in determine 6-8. This workflow exams for a chance elevate from 10% each time a checklist is modified. A box replace then units the NextStep box to a precise price. determine 6-8 – an easy workflow may cause accidental effects What occurs to the unique answer if anyone prompts this workflow? You’ll get initiatives on each one chance, and the try out will fail with the next message: method. AssertException: statement Failed: anticipated: five, real: 10 the explanation why this occurs is refined and is proven in determine 6-9. the 1st time in the course of the set off, the previous chance price is proven as 10 and the hot worth as ninety (as laid out in the try out code). determine 6-9 – set off item fields will not be up-to-date among set off invocations Logically, chances are you'll count on that the second one time during the set off the previous price of the chance will be ninety - taking over the recent worth from the 1st time via. yet actually, the outdated set off price is still an analogous – it displays the sphere worth at the beginning of the execution context. whilst the workflow box replace explanations one other set off invocation, the code sees this as one other box switch, and creates one other activity.