Ad
More Related Content
What's hot (20)
Similar to Salesforce developer (20)
Ad
Recently uploaded (20)
Ad
Salesforce developer
- 2. Agenda Bienvenidos a la Lightning Week Presentaciones Lightning Component Lightning Process Builder Lightning App Builder
- 3. Lightning week – Bienvenidos!! ¿Qué es SDG? (aka DUG) ¿Nuevos miembros? Lightning week
- 5. Preguntas y Respuestas Q: Is Lightning an MVC framework? A: No, it’s a component-based framework. Q: Why am I not seeing Lightning Components in my Org? A: It’s being rolled as we speak. Currently new Orgs and few others have it. Q: When will Lightning Components be GA? A: We’re not commenting publicly about our release timeline. Q: What’s the current release status of Lightning Components framework and Lightning App Builder? A: Lightning Components framework is in Beta. Lightning App Builder is in Pilot. Q: How do I use Lightning Components with the Salesforce1 Mobile App? A: Either as Tabs or as Lightning Extensions.
- 6. Preguntas y Respuestas Q: Why am I not seeing Lightning Components in my Org? A: It’s being rolled as we speak. Currently new Orgs and few others have it. Q: When will Lightning Components be GA? A: We’re not commenting publicly about our release timeline. Q: What’s the current release status of Lightning Components framework and Lightning App Builder? A: Lightning Components framework is in Beta. Lightning App Builder is in Pilot. Q: How do I use Lightning Components with the Salesforce1 Mobile App? A: Either as Tabs or as Lightning Extensions.
- 7. Preguntas y Respuestas Q: If Salesforce1 uses Lightning Components, will those Lightning Components (for example, the calendar component, input fields, etc.) be exposed as “standard components” for developers to use in the future with standard Salesforce styling? A: We’re not commenting publicly about our release plan. Q: Which parts of Lightning Components are server-side and which are client-side? A: Lightning Components can use JavaScript on the client side and Apex on the server side. Q: A tab with a Lightning Component only displays in the Salesforce1 UI. Can I make a Lightning Component that shows up in both the mobile and the desktop UIs? A: Currently you can only use Lightning Components in the Salesforce1 Mobile App or a standalone app.
- 8. Preguntas Q: Visualforce already has components. How are Lightning Component different and why would I want to use them? A: Visualforce components are page-centric and most of the work is done on the server. Lightning is designed from the component up, rather than having the concept of a page as its fundamental unit. Lightning Components are client-side centric, which makes them more dynamic and mobile friendly. Q: Does Lightning work with Visualforce? A: Not at this time. Q: Will Lightning Components be replacing Visualforce? A: No
- 9. Crear una org Creación entorno desarrollo – gratuita https://developer.salesforce.com/signup Accesso a Salesforce https://login.salesforce.com Material de hoy: http://developerforce.github.io/lightning-components-tutorial/setup- environment.html
- 11. Abrir la consola de desarrollador Si, de momento solo se pueden crear componentes desde la consola de desarrollador
- 12. Creamos el componente File > New > Lightning Component Nombre del componente -> QuickContacts
- 13. Creamos la ficha Create > Tabs
- 14. Añadimos la ficha al menú Movil Administer > Mobile Administration > Mobile Navigation
- 16. Creamos un nuevo componente “ContactList” File > New > Lightning Component
- 18. Añadimos el componente dentro del comp. anterior
- 19. Añadimos estilo
- 20. Creamos el evento SearchKeyChange File > New > Lightning Event. Este evento servirá para comunicar los 2 componentes
- 21. Creamos el componente SearchBar File > New > Lightning Component
- 23. Creamos el estilo para SearchBar
- 24. Escuchamos el evento en el componenete SearchList
- 26. Añadimos SearchBar al componenete inicial
- 29. Crear una org e instalción paquete Creación entorno desarrollo – gratuita https://developer.salesforce.com/signup Accesso a Salesforce https://login.salesforce.com Material de hoy: http://leeanndroid.github.io/LightningProcessBuilder/index.html Intalación paquete: http://bit.ly/TripApprovalPackage
- 30. Modificación Quick Action Setup | Create | Global Actions | Publisher Layouts Seleccionamos New Trip y guardamos
- 31. Creación campo Fórmula Setup | App Setup | Create | Objects | Trip Request
- 32. Nuevo Usuario Setup | Administration Setup | Manage Users | Users Usuario que aprobará los gastos
- 33. Creación Approval Process Setup | Create | Workflow & Approval | Approval Process Manage approval process for: Trip Request Create New Appoval Process | Use Jump Start Wizard
- 34. Approval Process
- 35. Approval Process No olvides activarla!!
- 36. Process Builder - New Setup | Build | Workflow and Approvals | Process Builder
- 37. Process Builder – Añadir objeto
- 38. Process Builder – Añadir objeto
- 39. Process Builder – Definir norma
- 40. Process Builder – Nueva Acción Crear entrada en Chatter
- 41. Process Builder – Nueva Acción
- 42. Process Builder – Nueva Acción Crear registro Evento
- 43. Process Builder – Nueva Acción Enviar aprobación
- 44. Process Builder – Activación Para activarlo es necesario: Al menos una norma definida Al menos una acción (inmediata ó programada) No se puede editar después de activar!!!
- 45. Process Builder – Prueba ¿Dónde? Simular Salesforce1 app en el navegardor https://<instancia>.salesforce.com/one/one.app Salesforce1 app En el entorno
- 46. Process Builder – Prueba 1. Selecciona la Quick Action 2. Introducimos la información
- 47. Process Builder – Prueba ¿Qué ha pasado? Tenemos una entrada en chatter
- 48. Process Builder – Prueba ¿Qué ha pasado? En el calendario tenemos un Evento
- 49. Process Builder – Prueba ¿Qué ha pasado? Proceso de Aprobación
- 52. Crear una org Creación entorno desarrollo – gratuita https://developer.salesforce.com/signup Accesso a Salesforce https://login.salesforce.com Material de hoy: http://developerforce.github.io/lightning-app-builder-tutorial/
Editor's Notes
- #12: public with sharing class ContactListController { @AuraEnabled public static List<Contact> findAll() { return [SELECT id, name, phone FROM Contact LIMIT 50]; } @AuraEnabled public static List<Contact> findByName(String searchKey) { String name = '%' + searchKey + '%'; return [SELECT id, name, phone FROM Contact WHERE name LIKE :name LIMIT 50]; } @AuraEnabled public static Contact findById(String contactId) { return [SELECT id, name, title, phone, mobilephone, Account.Name FROM Contact WHERE Id = :contactId]; } }
- #13: <aura:component implements="force:appHostable"> <p>ContactList goes here</p> </aura:component>
- #17: <aura:component implements="force:appHostable"> <p>ContactList goes here</p> </aura:component>
- #18: ({ doInit : function(component, event) { var action = component.get("c.findAll"); action.setCallback(this, function(a) { component.set("v.contacts", a.getReturnValue()); }); $A.enqueueAction(action); } })
- #21: What you will learn Create custom Lightning Events Communicate between components using events <aura:event type="APPLICATION"> <aura:attribute name="searchKey" type="String"/> </aura:event>
- #22: <aura:component> <div> <input type="text" class="form-control" placeholder="Search" onkeyup="{!c.searchKeyChange}"/> </div> </aura:component>
- #23: ({ searchKeyChange: function(component, event, helper) { var myEvent = $A.get("e.c:SearchKeyChange"); myEvent.setParams({"searchKey": event.target.value}); myEvent.fire(); } })
- #24: .THIS { width: 100%; padding: 8px; } .THIS input { width: 100%; padding: 8px; -webkit-appearance: none; border: solid 1px #dddddd; }
- #25: <aura:handler event="c:SearchKeyChange" action="{!c.searchKeyChange}"/>
- #26: searchKeyChange: function(component, event) { var searchKey = event.getParam("searchKey"); var action = component.get("c.findByName"); action.setParams({ "searchKey": searchKey }); action.setCallback(this, function(a) { component.set("v.contacts", a.getReturnValue()); }); $A.enqueueAction(action); }
- #27: <aura:component implements="force:appHostable"> <c:SearchBar/> <c:ContactList/> </aura:component>