Salesforce Org lifecycle management : empowering admins
•Als PPTX, PDF herunterladen•
0 gefällt mir•735 views
Recap of TrailheaDX in CT. Slide of Group meet conducted on 26-Jul. Blog - http://www.jitendrazaa.com/blog More information available at - https://www.meetup.com/Connecticut-Salesforce-Developer-User-Group/events/241570452/?comment_table_id=482174126&comment_table_name=event_comment#
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Salesforce Org lifecycle management : empowering admins
Ähnlich wie Salesforce Org lifecycle management : empowering admins (20)
Mehr von Jitendra Zaa
Mehr von Jitendra Zaa (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Salesforce Org lifecycle management : empowering admins
- 1. Org Lifecycle Management Connecticut WIT & Developer Group Meet Empowering Admins
- 2. #TDX17 Co-Host • Susan DeFazio • Maria Belli • Howard Friedman • Jitendra Zaa
- 3. #TDX17 Speaker Jitendra Zaa Technical Architect & MVP @JitendraZaa
- 4. Agenda • Introduction • Change Management • Salesforce Sandboxes • SFDC • Resources • Q&A
- 5. THINGS to do • Learn Standard features • Don’t reinvent the wheel • Deliver excellence • Focus on HOW • Keep business focused on underlying WHY
- 6. General To-Do : Create a Process Set yourself up for success
- 7. Set up a Center of Excellence (COE) Transparency is key
- 8. Know your Enterprise Ecosystem Coordinate across platforms • Learn about Salesforce identity features • Utilize SSO • Know all data integration points and flows • Be ready to identify possible impacts when outside system changes • Maintain your own list of integrated fields with all attributes
- 10. Principles of Change Management
- 13. Sandbox is a key part of cloud building • Copy of production on similar infrastructure • Template for faster creation • Change sets for easier deployment • IDEs for faster deployment
- 14. Bundled Sandboxes by Edition
- 16. Scratch Orgs vs Sandboxes
- 17. Sandbox Access considerations Post-refresh scripts and tasks • Write Apex, load data, mask some fields, Users need FULL org access • Change all username except few
- 18. Sandbox Deployment Methodology Example
- 19. Sandbox strategy
- 20. Tying it all together for beginners Recommendations for linking all the things • Developer edition • Sandboxes • Change sets & ANT • New packaging options • Scratch Org & Environment hub & VCS • Be aware of the new source-driven paradigm
- 21. #TDX17 Salesforce Admin : Existing Process Effects ? Few to none • Partner with your developers • Learn their processes • Maintain existing promotion policies • What happens in early sandboxes does not affect you • Be an appropriate gatekeeper
- 22. Key Takeaways You can do it ! 1. Secure management / executive support 2. Familiarize yourself with your IT ecosystem, Systems. People 3. Identify workstreams / projects and draw planned flow to present to stakeholders 4. Scale down appropriately
- 23. Where do I get to learn more ? Have you even been paying attention, people ?
- 25. More about Trust and Availability https://www.trust.salesforce.com https://www.trust.salesforce.com/en/security
- 27. Please don’t ask any Questions
Hinweis der Redaktion
- Everyone knows what Org is ? What Lifecycle is ? What management is ? Who went to TrailheaDX, experience ?
- Why admin need empowering ? Admins are unsung heros who take charge of org and enforces best practices.
- Things admin needs to do. Who has sabdboxes ? How many ? Build it, break it, learn in Sandboxes. Don’t reinvent wheel , - There was Appexchange project to support business hours and people using it, c’mon, we have built in business hours from salesforce. Most of time customers say, What they want to do. Question should be why ? Example , checkbox on opportuniyty asking its type. In future, cant they have multiple LOB ? Learn to say NO. Let them know implications.
- Secure safety. Make them think, they are your mentor. Fine, even if they don’t know salesforce Make your boss Rockstar Either go, on and on for hour or make a process Internal idea exchange, suggestion box Brain stoirming is encouraged but there are som ebad idea and learn to say NO.
- Mostly small companies say – I don’t need center of excellence. Ok ok But what about those account people who decides which features goes ? We need that. Example – there is group only for Opp object. SO , any meeting you would be invited however at the same time if meeting is for case, you will not invited. Transparency Is key.
- What is first thing customer would buy for ? Sales cloud And second - ? Service ? No. Its platform feature.
- Your job is not finished when feature deployed but its done when adoption is done.
- Separation of responsibility Chances are very low that admins will use scratch org
- Healthcare, finance, education.. There are rules People don’t supposed to know things Developers needs to write a code but not see the data Your lawyers would not enjoy if devs gets access If CEO knows sandbox exists, they will try to login and mess. Don’t tell username, scramble it. CEO needs to see data, not supposed to change it.
- All you pay, comes free of cost in Sandbox Let dev have fun in dev en and dev sandbox. Left like is dev But right is for admin, THE admin How many have more than 1 admin ? You get hug, you get hug.
- Please don’t use Appexchange packages to move between orgs. They install there stuff into salesforce, you loose control. Atleast I don’t like it.