Example Trigger for Step Creation Condition
Below is an example trigger for a step creation condition that drills down to the opportunity product and uses the Reevaluate When field with the process object (opportunity).
trigger OpportunityLineItemTrigger on OpportunityLineItem (after insert, after update, before delete) { Set<Id> parentObjectsIds = new Set<Id>(); List<OpportunityLineItem> childObjects = Trigger.isDelete ? Trigger.old : Trigger.new; for(OpportunityLineItem childObject : childObjects){ parentObjectIds.add(childObject.OpportunityId); } FSTR.ForceReevaluateSrvc.forceReevaluatePreFuture(parentObjectIds);}Below is an example trigger for a step creation condition that drills down to the CPQ quote product and uses the Reevaluate When field with the process object (CPQ quote)
trigger QutoeLineTrigger on SBQQ__QuoteLine__c (after insert, after update, before delete) {Set<Id> parentObjectIds = new Set<Id>();List<SBQQ__QuoteLine__c> childObjects = Trigger.isDelete ? Trigger.old : Trigger.new;for(SBQQ__QuoteLine__c childObject : childObjects) {parentObjectIds.add(childObject.SBQQ__Quote__c); }FSTR.ForceReevaluateSrvc.forceReevaluatePreFuture(parentObjectIds);}Tip: Optimizing drill-down criteria
If you introduce drill-down criteria on large definitions or if there is a large number of drill-down objects to look through for the criteria, Conga Orchestrate can give Apex CPU timeout issues. To prevent those issues:
- Split the definitions into smaller definitions to reduce the overall process of drill-down criteria.
- Conga recommends that you use = or != operators whenever possible. When you use these operators, the number of objects to check is reduced, leading to faster performance. Using "contains" or > operators may degrade your query performance.
