Five Admin Tips Every Developer Should Know

22
Five Admin Tips Every Developer Should Know Rebecca Dente, Achievers Nick Hamm, Appirio

Transcript of Five Admin Tips Every Developer Should Know

Page 1: Five Admin Tips Every Developer Should Know

Five Admin Tips Every Developer

Should Know

Rebecca Dente, Achievers

Nick Hamm, Appirio

Page 2: Five Admin Tips Every Developer Should Know

Safe Harbor

Safe harbor statement under the Private Securities Litigation Reform Act of 1995:

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 intellectual property and other l itigation, risks associated

with 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-Q for the most recent fiscal quarter ended July 31, 2012. This

documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.

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.

Page 3: Five Admin Tips Every Developer Should Know

Nick Hamm

Cloud Solutions Architect,

Salesforce MVP

Page 4: Five Admin Tips Every Developer Should Know

Rebecca Dente

Director of Cloud Technology

Salesforce MVP

Page 5: Five Admin Tips Every Developer Should Know

You're a Developer

You guys are all devs. You spend your time in code. You live Apex

and breathe visualforce.

Page 6: Five Admin Tips Every Developer Should Know

You are not an Admin

Admins are those people in the business suits on the

other side of the office.

You know the ones that get all the credit for your

work?

Page 7: Five Admin Tips Every Developer Should Know

Why do I care about how Admins work?

We want to share with you some tips that will make your life easier,

but also make more people release the kickass stuff you do.

Working together means you can get more code, and more apps

through testing and into the hands of users to let you start writing

the next cool app.

Page 8: Five Admin Tips Every Developer Should Know

Agenda

Common Clicks vs Code scenarios

Visibility of work between a team of Admins and Devs

Importance of Change Management

Takeaways

Q & A

Page 9: Five Admin Tips Every Developer Should Know

Problem:

I need to enforce data quality

Common developer solutions:

Write a trigger to validate data inputs

Page 10: Five Admin Tips Every Developer Should Know

Admin Solution!

Validation Rules

Formula Fields/Cross-object Formula Fields

Page 11: Five Admin Tips Every Developer Should Know

Problem:

I need to update or summarize data when a user makes changes

Common developer solutions:

Write a trigger to update field values

Write a trigger to summarize child object data

Page 12: Five Admin Tips Every Developer Should Know

Admin Solution!

Workflow Rules

Roll up summary fields

Page 13: Five Admin Tips Every Developer Should Know

Problem:

I have to make Visualforce changes when new

fields are added or moved on the page layout

Developer solutions:

Edit the Visualforce page and reposition the

fields

Add new Visualforce code to display new

fields

Page 14: Five Admin Tips Every Developer Should Know

Admin Solution!

Fieldsets!

These will help you to leverage even your entry-level Admins

Page 15: Five Admin Tips Every Developer Should Know

Problem:

Deployment/promotion of changes between environments

Common developer solutions:

Eclipse IDE

Fire up some ANT scripts!

Page 16: Five Admin Tips Every Developer Should Know

Admin Solution

Leverage change sets.

Shared insight

Allows admins to help with the

deployment process

EXTRA CREDIT – create a release

schedule that all admins &

developers stick to

Page 17: Five Admin Tips Every Developer Should Know

Problem:

My users want a 7 step wizard for data entry

I don't have the bandwidth

Common developer solutions:

300+ lines of code that will require heavy editing

every time the business changes their minds

I'll get that to you next month

Page 18: Five Admin Tips Every Developer Should Know

Admin Solution

Visual Workflow

Page 19: Five Admin Tips Every Developer Should Know

Developer AND Admin Problems

Development Amnesia

No one is using my stuff!

Page 20: Five Admin Tips Every Developer Should Know

Working Together

Implement a change management process that

everyone adheres too

Communication is key

Knowledge-sharing

Page 21: Five Admin Tips Every Developer Should Know

Take Aways

Clicks before Code

Validation Rules and Formula Fields

Workflows/Approvals

Field Sets

Change Sets

Visual Workflow

Page 22: Five Admin Tips Every Developer Should Know

Rebecca Dente Nick Hamm

Director, Cloud

Technology

Cloud Solutions

Architect