Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

PhillyForce 2018 - Salesforce Platform Keynote

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio

Eche un vistazo a continuación

1 de 28 Anuncio
Anuncio

Más Contenido Relacionado

Presentaciones para usted (20)

Similares a PhillyForce 2018 - Salesforce Platform Keynote (20)

Anuncio
Anuncio

PhillyForce 2018 - Salesforce Platform Keynote

  1. 1. Andrew Fawcett VP, Product Management Lightning Platform Twitter: andyinthecloud Platform Keynote PhillyForce 2018
  2. 2. Forward-Looking Statement 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.
  3. 3. Strong on their own, unbeatable together! Blazing the Trail Together Community APIsPlatform Open Source Apps Tools
  4. 4. Effective use of the Dependency API Org Composition Introduction to DX Packaging Packages and You New Features and Flow API Lightning Flow
  5. 5. Customer Focus (Beta) ● Capture your org applications and customizations in discrete well-defined packages. ● Versionable, installable, upgradable and also downgradable ● Updates and customizations are easier to manage and control in large orgs What is a Package? ISV Partner Focus ● Building and delivering commercial apps ● Require design patterns solving common problems ● More focus on protecting IP and rolling out upgrades to the install base Not just for Partners anymore...
  6. 6. Packaging and Installing the GIFter App and other Open Source (https://github.com/forcedotcom/GIFter)
  7. 7. Package Development ● Logical groups of related source/metadata ● Projects can be tested independently ● Projects can be released independently ● Increases Release Flexibility ● Increases Dev Productivity ● Packages for Dependencies Including Open Source fflib, Apex Mocks etc.. General Criteria for Metadata that can migrate into a Package
  8. 8. Introduction to DX Packaging Effective use of the Dependency API New Features and Flow API Packages and You Org Composition Lightning Flow
  9. 9. Org Composition What’s in the box? What health is your org in? ● What are your key objects or fields everything depends on? ● Can customizations be grouped easily? ● Do you need to do some housekeeping first? Questions to ask yourself... ● Any generally regarded “features/apps” you can try to isolate? ○ Key entry points? ○ By tab, by button, by object, by report? ● What things depend on these entry points? ○ And what things depend on those….
  10. 10. Introducing the Dependency API Pilot sfdx force:data:soql:query --usetoolingapi --query "SELECT MetadataComponentId, MetadataComponentName, MetadataComponentType, RefMetadataComponentId, RefMetadataComponentName, RefMetadataComponentType FROM MetadataComponentDependency" -u philllyforce
  11. 11. Visualizing Dependencies (Sample DX CLI Command)
  12. 12. But wait! What about this Idea?
  13. 13. Introduction to DX Packaging Effective use of the Dependency API New Features and Flow API Packages and You Org Composition Lightning Flow
  14. 14. Amazing new Features in Lightning Flow Allowing Developers and Admins to embrace the power of Flow together Summer’18 ● Flow Design: ○ More Ways to Use Lightning Components, Stages Generally Available, More Collection Assignment Operators ● Flow Distribution: ○ Launching Flows as Subtabs, Displaying Recommended Flows ● Process and Flow Debugging: ○ Debug Details at Runtime, Improved Error Emails, and More Log Lines ● Process and Flow Runtime: ○ Better Errors for Users, More Ways to Avoid Errors and Rollbacks Winter’18 ● Flow Distribution: ○ Add Flows Anywhere in Salesforce with the Flow Lightning Component Spring’18 ● Flow Design: ○ Richer Screens with Lightning Components and Stages ● Flow Distribution: ○ Subtabs in Console Apps, Object- Specific Actions, and Dynamic Apex ● Process and Flow Debugging: ○ Debug Details at Runtime, Improved Error Emails, and More Log Lines
  15. 15. Lightning Flow in your Components Adding Clicks not Code Extensibility to your Components with Lightning Flow lightning:flow Component
  16. 16. Components in your Lightning Flows Adding rich complex Components to your Lightning Flows lightning:availableForFlowScreens Interface
  17. 17. Lightning Flow in your Apex Flow.Interview.createInterview Method ● Allow parts of your logic to be extended by an auto-launch Flow configured and defined by your clicks-not-code colleagues! Adding Clicks not Code Extensibility to your Apex with Lightning Flow
  18. 18. Highlighting the Lightning Flow API powering Community Tools
  19. 19. How do i find out more?
  20. 20. Packaging Resources Documentation ● Salesforce DX Packaging ● Unlocked Packages for Customers ● Announcing Unlocked Packages Beta Community ● Packaging 2 Community Group Beta
  21. 21. Dependency API Resources Documentation ● Release Notes: Untangle Your Dependencies (Pilot) ● Tooling API : MetadataComponentDependency (Pilot) ● Building Custom CLI Commands Community and Open Source ● Trailblazer Community Group ● Dependency API DX CLI Sample Tool Pilot
  22. 22. Lightning Flow Resources Salesforce Documentation ● Apex Flow API ● Rest Flow API ● Use Lightning Components with Flows ● Trailhead Community and Open Source ● Mass Action Scheduler ● Dynamic Flow Component GA API’s and Community Tools
  23. 23. API and CLI driven Platforms rock! In conclusion…
  24. 24. Questions?
  25. 25. Appendix: Dependency API Demo Output
  26. 26. Package Development Isolate Vertically First ● Custom Force.com Apps built in-house ● Extensions of Sales Cloud, Service Cloud, etc ● Shared Libraries/Functionality Modularize Horizontally as Needed ● Schema, Business Logic, UI ● Ownership e.g. Business Unit or Process ● Shared Libraries/Functionality Identifying Metadata that can migrate into a Package
  27. 27. Packaging Adoption in Large Org ● First slice! ○ Simple well defined ○ Small team, willing to try new tools and approaches ○ Not mission critical roadmap ○ Implement full ALM, inc CI on mini scale ● Additional slices ○ Continue to form sub- packages as confidence grows ○ Full Org slice is reducing ○ Continue to add to CI each repo ○ May consider shared pkg ● Full modularization ○ Original org decomposed into packages ○ With remaining (minimal) overarching config in an org scoped package (minimal profiles, some layouts) Start small and broad, then iterate to greater depth and coverage Full Org Config and Code (Change Sets) DX POC #1 Full Org Config and Code (Change Sets) DX PKG #1 DX PKG #2 DX Shared PKG Permission Sets (Objects, Fields, Tabs) reflect functionality granted not roles DX Shared PKG PKG DX PKG DX Shared PKG DX PKG DX PKG DX PKG DX PKG DX PKG DX PKG Full Org Config (Change Sets)

×