Talk to An Expert Series: Workflow by Salesforce.com

Talk to An Expert Series: Workflow Sarah Franklin

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 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 â&#x20AC;&#x201C; but are not limited to â&#x20AC;&#x201C; risks associated with developing and delivering new functionality for our service, 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 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, 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 filed on April 30, 2008 and in other filings with the Securities and Exchange Commission. These documents 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 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.

Force.com is the Platform that Runs Your CRM

Customization in the Cloud  Build applications point and click in a browser  With Force.com, developers can customize declaratively or programmatically.  Declarative customizations require an understanding of Force.com, but no coding knowledge.  Programmatic customizations require coding skills and allow developers to extend beyond the native Force.com capabilities.

Customization in the Cloud Applications Tabs Page Layouts Record Types

User Interface

Visualforce Pages Web Controls Sites

Workflow Validation Rules Assignment Rules

Business Logic

Visualforce Controllers Apex Web Services API

Objects Fields Relationships

Data Model

Web Services API Metadata API

Declarative

Programmatic

Simplicity + Speed

Control + Flexibility

Force.com Development Model Business User

Administrator

Business Analyst

Web Developer

Professional Developer

Browser user

Excel user

Excel power user

Basic DB knowledge Light HTML or JavaScript

SQL expertise Java / .NET

Personalize apps Configure apps Customize apps

Develop apps

Typically Force.com IDE Procedural Code Developer target 6

Business Logic

Application Building Blocks Applications Tabs Page Layouts Record Types

User Interface

Visualforce Pages Web Controls Force.com Sites

Workflow Validation Rules Assignment Rules

Business Logic

Visualforce Controllers Apex Web Services API

Objects Fields Relationships

Data Model

Web Services API Metadata API

Declarative

Programmatic

Simplicity + Speed

Control + Flexibility

Workflow Rules  Automate business processes – Triggered on record write – Execute Actions • Immediately and/or • Later (only if record still meets entry criteria)

Entry Criteria

Immediate Actions

Time Dependent Actions

Workflow Rule Configuration  Entry criteria: which records – Object Type – Evaluation Criteria – Rule Criteria

 Timing: when to execute actions

Workflow Rule Immediate Actions

– Immediately – Time Dependent

 Actions: what to do – Assign Task

Time Triggered Actions

– Update Field – Send Email Alert – Post Outbound SOAP Message

Time-Dependent Workflow  Time-dependent actions have a time trigger  With time-dependent actions, the action is queued to fire as soon as the workflow criteria is met; however, the action will not occur until it meets the time trigger.  Time-dependent workflow cannot be used when a rule is set to be evaluated Every time a record is created or updated.  Developers can monitor and remove pending actions by viewing the time-dependent workflow queue.  If a record with pending actions in the time-based workflow queue is modified the, the action in the queue is modified or removed accordingly. © 2009 salesforce.com, inc. All rights reserved.

Approval Processes Approval processes are single or multi-step process which require end user authorization for record promotion. Final Approval Actions Entry Criteria

Initial Submission Actions

Approval Steps

Recall Actions Final Rejection Actions

How Do I Define an Approval Process? Process Definition Which records should enter this process? What settings should apply to the whole process? Initial Submission Actions What happens when a record is submitted for approval?

Step Definition Who should records be routed to?

Recall Actions

Final Rejection Actions

Final Approval Actions

What happens when a record is rejected?

What happens when a record is approved?

What happens if a record is recalled from the process?

Process Visualizer  Provides a visual representation (read-only) of your approval processes  Hover over or expand steps to see details  The Process Visualizer is currently in BETA – send us your feedback!

Let’s Compare… Workflow Rules & Approval Processes Workflow Rules

Approval Processes



Are triggered upon save



Consist of one set of criteria and actions

Are triggered only when a user clicks “Submit for Approval”



Consist of multiple steps

Can be modified or deleted



Have entry criteria, step criteria, and step actions



Have initial submission actions, rejection and approval actions, and actions for each step



Some attributes can’t be modified, processes must be deactivated before they can be deleted Workflow Rules and Approval Processes can be used together.

Demo: Recruiting Application

Recruiting Application Requirements  Track Positions, Candidates, Job Applications, Interviewers, and Reviews.  Enforce company-wide procedures for submitting, approving, and posting new Positions.  Post Positions on corporate web site consistent with data stored in Recruiting app.  Capture Candidate Job Applications from corporate web site and integrate with Recruiting app.  Monitor all recruiting activities in real time through Reports and Dashboards. © 2009 salesforce.com, inc. All rights reserved.

Demo Scenarios: Workflow & Approvals  Recruiters need to be notified when a new position is created  Recruiters need to get approval for jobs that are created  Recruiters need to be notified if a position is not filled within a specified period of time

Recap: Creating Workflow Rules

Recap: Approval

Admin to App Builder Update

www.salesforce.com/hero Free Starter Kit 2 Hour Modularized, Online Training 5 App Templates Download Now

Thank You