22
The Visual Delta Force Dynamic Visualforce Components Kyle Thornton, Mavens Consulting, Technical Architect @knthornt John Daniel, Mavens Consulting, Technical Architect @JohnDTheMaven

The Visual Delta Force: Dynamic Visualforce Components

Embed Size (px)

DESCRIPTION

Join us to learn how to manage those outlier issues when standard Visualforce, and all other options, will simply become too burdensome to manage. We'll build on use cases with Dynamic Visualforce Components, speaking to these technologies, demoing them, and showing real-life use cases where these have been used in production.

Citation preview

Page 1: The Visual Delta Force: Dynamic Visualforce Components

The Visual Delta ForceDynamic Visualforce Components

Kyle Thornton, Mavens Consulting, Technical Architect@knthornt

John Daniel, Mavens Consulting, Technical Architect@JohnDTheMaven

Page 2: The Visual Delta Force: Dynamic Visualforce Components

Kyle Thornton

Technical Architect, Mavens ConsultingSalesforce MVPCertified Force.com Advanced Developer@knthornt

Page 3: The Visual Delta Force: Dynamic Visualforce Components

John M. Daniel

Technical Architect, Mavens ConsultingCertified Force.com Advanced Developer@JohnDTheMaven

Page 4: The Visual Delta Force: Dynamic Visualforce Components

All about Mavens Consulting

Mavens Consulting is the Life Science industry’s premier salesforce.com implementation partner focused exclusively on delivering optimized Force.com solutions.

▪ Certified Force.com and Veeva Experts

▪ Unparalleled Global Knowledge in Life Sciences

▪ Specialists in Service Cloud Implementations for MedInfo Contact Centers and Multi-Channel Portals for Physicians and Reps

Page 5: The Visual Delta Force: Dynamic Visualforce Components

Safe harborSafe 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 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 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 6: The Visual Delta Force: Dynamic Visualforce Components

Unsafe harbor

Page 7: The Visual Delta Force: Dynamic Visualforce Components

Rendering objects in Visualforce

Page 8: The Visual Delta Force: Dynamic Visualforce Components

What about an object with an unknown number of levels and peers?

Page 9: The Visual Delta Force: Dynamic Visualforce Components

Social Influence Mapping

Page 10: The Visual Delta Force: Dynamic Visualforce Components

Social Influence Mapping

Page 11: The Visual Delta Force: Dynamic Visualforce Components

Social Influence Mapping

Page 12: The Visual Delta Force: Dynamic Visualforce Components

How do we view this information?

Page 13: The Visual Delta Force: Dynamic Visualforce Components

Viewing Budget Plans in an Enterprise

Global Budget

National Budget 1 National Budget 2

Regional Budget 1

Regional Budget 2

Regional Budget 3

Regional Budget 4

$ $ $ $ $ $ $ $ $$ $ $

Page 14: The Visual Delta Force: Dynamic Visualforce Components
Page 15: The Visual Delta Force: Dynamic Visualforce Components

Visualforce = Army of tags

Page 16: The Visual Delta Force: Dynamic Visualforce Components

Dynamic Visual “Delta” force components

Page 17: The Visual Delta Force: Dynamic Visualforce Components

What are Dynamic Visualforce Components?

Rather than using standard markup, dynamic Visualforce components are designed in Apex and can be defined like:

Component.Component_namespace.Component_name

Page 18: The Visual Delta Force: Dynamic Visualforce Components

Dynamic Visualforce Components - ExamplesComponent.Apex.OutputPanel aPanel = new Component.Apex.OutputPanel(layout=‘block’, styleClass=‘column’);

<apex:outputPanel layout=“block” styleClass=“column></apex:outputPanel>

Account a = new Account(Name=‘Mavens Consulting’);Component.Apex.OutputText someText = new Component.Apex.OutputText();someText.expressions.value = a.Name;

<apex:outputText value = “{!a.Name}”></apex:outputText>

Page 19: The Visual Delta Force: Dynamic Visualforce Components

How do you organize Dynamic Visualforce Components?

Use the childComponents list which is a property of each Dynamic Visualforce Component

childComponents is a list of Apex Components

Component.Apex.Outputpanel thePanel = new Component.Apex.Outputpanel();Component.Apex.Outputtext theText = new Component.Apex.Outputtext(value=“foo bar”);thePanel.childComponents.add( theText)

Page 21: The Visual Delta Force: Dynamic Visualforce Components

Kyle Thornton

Technical Architect,Mavens Consulting

@knthornt

John Daniel

Technical Architect,Mavens Consulting@JohnDTheMaven

Page 22: The Visual Delta Force: Dynamic Visualforce Components