View
240
Download
2
Category
Preview:
Citation preview
Report Builder Developer Preview
Thomas Tobin Product Manager
Umit Yalcinalp Developer Evangelist
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 – but are not limited to – 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, 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 April 30, 2010. This document and others 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.
Agenda where we’re going today
Setting up reporting for an app
What’s there today – the wizard
Customer feedback for the wizard
Result – Rethinking the user experience
The concept behind the builder
The builder in action
Setting up for the builder
Setting up reporting can you see what I see Toto?
You have an app with objects, fields, workflow, content, chatter, Apex, VisualForce pages
You need to build – Report types to cover object relationships not generated
automatically
– Reports to demonstrate what you can get out
– Reports as starting points for users
– Dashboards to bring the reports together
– Analytic snapshots to create trending data for data that changes
And package that all up
Building reports today visiting the wizard
1 part of a report per step
Steps have images and explanation
7 steps required to walk a user through the report creation process
Field order and section correspond to default page layout
Running a report is fast
Simple display of fields
Typical comment: – “I’ve used other CRM systems, but this is the first one I can
get a list of my contacts back out”
Existing report wizard
demonstration
Wizard Experience the man behind the curtain
The 5 or 7 steps aren’t in a logical order
The step order changes between the formats
Not WSIWYG: Users don’t see results until the end
Users often don’t know what’s in the fields in their org
Common analytics support call to salesforce.com: – “The results of a report weren’t what I expected”
Commonly Reported Issues
Unnecessary cycling Filter – Run Report - Back to customize
Users discouraged by the thought of 7 steps
Choosing too many columns rather than too few
Not utilizing filters et. Al., because filtering without seeing the data does not work. – Filtering delegated to Excel
The builder concept from black and white
Instant preview - Canvas to work on report results
Drag and drop field placement for any layout
Find fields like they find a dashboard
Presented at Dreamforce’09
The builder – to color
Builder – in living Technicolor™
demo
Builder future get on the yellow brick road
Just like dashboards – any new features will be builder-only – Common chart editor
The old wizard will be EOL – Today – profile control and shows two buttons
– Winter’11 – profile control, one button (either builder or wizard)
– Spring’11 – org setting – all users or none on builder
– End of wizard in Winter’12 (end of 2011)
What you have to do your call to action
Start using the builder now ! – Currently, everything but matrix reports – Feature complete in dev orgs by mid-August
– GA in Winter’11
– Report metadata structure is unchanged
Start here
Setting up for success - Demos
Make sure demo data fits in 50 rows – At least, sample of different values
Pre-build CSFs and disable them to leave them in the tree
Use CRTs that give you a reduced set of fields – No need to explain why you have 200 fields for your app
Setting your Apps up to success
CRT sections are still sections in the Report Builder
Try to use CRTs – And, if necessary, use custom links to existing
reports to get users to use the CRTs
– CRT limits same as number of objects per edition
For fields with short contents, pick short fieldnames – Field names don’t wrap in preview
Expect customer orgs to have both builder and wizard
Resources
Developer.force.com
Analytics Ideas under consideration
Developer blog
Analytics blog
Q&A
Recommended