Salesforce Developer User Group Munich - October 2016
•Download as PPTX, PDF•
0 likes•403 views
The document summarizes Salesforce DX, a new developer experience that allows for continuous delivery and improved collaboration. Key points include: - Salesforce DX uses scratch orgs for development, testing, and user acceptance testing and the Salesforce Environment Manager for managing environments. - Metadata, code, and org shape are managed together, and source control allows for tracking changes. - Developers can use the command line interface or Force.com IDE to develop and the Heroku Flow for continuous integration and delivery. - The workflow involves authorizing, pulling changes, developing, pushing changes, testing, and deploying to orgs.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (14)
Similar to Salesforce Developer User Group Munich - October 2016
Similar to Salesforce Developer User Group Munich - October 2016 (20)
More from René Winkelmeyer
More from René Winkelmeyer (13)
Recently uploaded
Recently uploaded (20)
Salesforce Developer User Group Munich - October 2016
- 1. Developer User Group München – 19.10.2016 @muenzpraeger René Winkelmeyer Senior Developer Evangelist
- 2. Forward-Looking Statements 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. Ein Überblick über das Ökosystem
- 4. Vertical Split Layout Subtitle placeholder Lorem ipsum dolor sit amet, consectetur Cras egestas mauris ut faucibus cursus Pellentesque et risus ac turpis maximus
- 5. Text, images, charts, tables can be put in this placeholder. Third Split Sign Layout Subtitle placeholder
- 6. Lightning
- 7. Base Lightning Components (BLC) Übersichtlichere Lightning-Components Man muss SLDS nicht mehr so detailliert lernen Mit SLDS ”wächst” BLC
- 8. Base Lightning Components (BLC) Gemischte Produktions- und Beta-Components <lightning:xxx> vs. <ui:xxx>
- 9. Base Lightning Components (BLC) https://github.com/msrivastav13/Base-Lightning-Components/wiki/Lightning-Base-Components- Designer-Guide
- 10. Lightning Data Service (Developer Preview)
- 11. Lightning Data Service (Developer Preview) CRUD-Unterstützung (signifikante Performance-Verbesserungen bei Read-Operations) Ausschließlich in Lighning Experience oder Salesforce1 Immer nur ein Record!
- 12. Base Lightning Components (BLC) https://developer.salesforce.com/docs/atlas.en- us.204.0.lightning.meta/lightning/data_service_load_record.htm
- 13. Weitere Verbesserungen SLDS kann zu jeder Lightning App(!) via extends=“force:slds” hinzugefügt werden – keine statischen Resourcen mehr!
- 14. Salesforce DX
- 15. Salesforce DX Bestmögliche Developer-Experience Unterstützung für Entwicklung im Team Versions-Kontrolle, Versions-Kontrolle, Versions-Kontrolle
- 16. Salesforce DX Metadata, code und org shape Continous Delivery Heroku Flow / CI (optional)
- 17. Salesforce DX - Environments Scratch orgs für Development, Test, UAT Salesforce Environment Manager für die Verwaltung
- 18. Salesforce DX – Metadata und Source-Control Alles wird über Metadata gesteuert Source-Control ermöglicht die bestmögliche Nutzung – inklusive dem Tracking von Changes
- 19. Salesforce DX – Developer Tools Alles über Command Line Interface (CLI) - oder doch nicht? Force.com IDE 2
- 20. Salesforce DX – Continuous Integration und Delivery Bring your own CI/CD Heroku Flow und Heroku CI Testrunner für Apex, Selenium und JUnit inkludiert Dataloading
- 21. Salesforce DX – Workflow authorize pull do your dev stuff push open test deploy
- 23. 3-Column Layout These three placeholders can hold text, table, charts, smart art, or media. These three placeholders can hold text, table, charts, smart art, or media. These three placeholders can hold text, table, charts, smart art, or media. Subtitle placeholder
- 24. Salesforce Content Salesforce Content Salesforce Content Lorem ipsum dolor sit amet, consectetur Cras egestas mauris ut faucibus cursus Pellentesque et risus ac turpis maximus Lorem ipsum dolor sit amet, consectetur Cras egestas mauris ut faucibus cursus Pellentesque et risus ac turpis maximus Lorem ipsum dolor sit amet, consectetur Cras egestas mauris ut faucibs cursus Pellentesque et risus ac turpis maximus Subtext placeholderSubtext placeholder Subtext placeholder 3-Column With Titles Subtitle placeholder
- 25. Placeholder for textPlaceholder for text Placeholder for text Subtitle placeholder 3-Column Photos Layout
Editor's Notes
- Key Takeaway: We are a publicly traded company. Please make your buying decisions only on the products commercially available from Salesforce. Talk Track: Before I begin, just a quick note that when considering future developments, whether by us or with any other solution provider, you should always base your purchasing decisions on what is currently available.
- As you can see here we’re offering everything from No-Code development to full-code development. It goes from visual builders for workflows in the no code area up to our own Frameworks to access the platform via any mobile device up to IoT and Artificial Intelligence using Salesforce Einstein. Let us take a quick look about the broad set of capabilities.
- As you can see on this – quite overwhelming chart - Salesforce offers a broad set of capabilities. Be it source-driven development via Salesforce DX, App Management via our PaaS offering Heroku or the programmatic or declarative development options. As integration is key the platform has a broad set of integration capabilities – be it via SOAP, REST or other APIs. And for that we’re focusing here on the access via REST.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.
- There are several ways of authentication and authorization possible when it comes to connecting different systems. We’ve listed here the most used techniques. SAML is often used – especially in enterprise scenarios – to allow Single-Sign-On across different web-based on a single Identity Provider (IdP in short). That can in example be an Active Directory. I want to point out here that Salesforce itself can act as an IdP too (with or without AD). We’re focusing in this webinar for the sake of simplicity on Oauth in Version 2.