Partition Your (Apex) Trigger Logic Using Metadata

Partition Your Trigger Logic Using
Metadata
Mitch Spano
Application Engineer - Google
@mitchspano

This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the
assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we
make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber
growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any
statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new
products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in
our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the
immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new
releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise
customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the
most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures
are available on the SEC Filings section of the Investor Information section of our Website.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be
delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
Statement under the Private Securities Litigation Reform Act of
1995
Forward-Looking Statement

Speakers
Mitch Spano
Application Engineer - Google
@mitchspano

If you are an Architect...
• Consider how this framework
can enable your organization
to grow and scale
• Listen for strategies to better
partition your application
If you are a Developer...
• Learn how a metadata driven
trigger framework can allow
you to deliver higher quality
Apex code
• Observe the techniques used
to test Apex used in this
project
If you are a Manager...
• Gain an understanding of the
complexities of working in an
Apex trigger
• Imagine ways this could be
used in a multiple team
environment
Intended Audience
What should you take from this discussion?

Apex Triggers
Background and History

Many Automation Tools
Relative Risk and Power
Flow
Process Builder
Workflow
No Automation
Triggers
Less
Risk/Power
More
Risk/Power

Trigger Logic
Things can get messy

public class OpportunityTriggerHandler extends TriggerHandler {
public override void beforeUpdate() {
for(Opportunity o : (List<Opportunity>) Trigger.new) {
// do something
}
}
// override additional contexts as necessary
}
Existing Frameworks
Separate Trigger from Logic

public override void afterInsert() {
this.handleWholesaleInsert((List<Opportunity>) Trigger.new);
this.handleRetailInsert((List<Opportunity>) Trigger.new);
}
private void handleWholesaleInsert(List<Opportunity> newList) {
for(Opportunity o : newList) {
// do something
}
}
private void handleRetailInsert(List<Opportunity> newList) {
// do something
}
}
}
Existing Frameworks
Handlers Require Modification

public override void afterInsert() {
this.handleWholesaleInsert((List<Opportunity>) Trigger.new);
this.handleRetailInsert((List<Opportunity>) Trigger.new);
this.recalculateAccountValues((List<Opportunity>) Trigger.new);
this.notifyAMEASales((List<Opportunity>) Trigger.new);
this.setDefaultAccountType((List<Opportunity>) Trigger.new);
this.defineOpportunityContactRoles((List<Opportunity>) Trigger.new);
}
private void handleWholesaleInsert(List<Opportunity> newList) {
// do something
}
}
// More methods are implemented and called for every action :(
}
Existing Frameworks
Becomes Unmaintainable

Trigger Actions Framework
A Metadata Driven Approach

Trigger Framework
GitHub Information
https://github.com/mitchspano/apex-trigger-actions-framework

Trigger Framework
Classes and Metadata Types

Work Together in Teams
Strategies for Working in a Multiple-Team Environment

Working in Multiple Teams
New Package Directories
{
"packageDirectories": [
{
"path": "application/base"
},
{
"path": "application/opportunity-automation"
},
{
"path": "application/retail"
},
{
"path": "application/wholesale",
"default": true
}
],
"namespace": "",
"sfdcLoginUrl": "https://login.salesforce.com",
"sourceApiVersion": "50.0"
}

Use the Order
Order__c: 2.071
Team Prefix Order

Use the Order

Partition Your (Apex) Trigger Logic Using Metadata

Partition Your (Apex) Trigger Logic Using Metadata

More Related Content

What's hot (20)

Similar to Partition Your (Apex) Trigger Logic Using Metadata (20)

Recently uploaded (20)

Partition Your (Apex) Trigger Logic Using Metadata