Join the conversation. Connect with RAZOR
Case Study 0215
Migration of Salesforce Classic to Lightning Web Components
PROBLEM
Our client, a commercial healthcare company, had been on the Salesforce Classic platform for several years. Their member base had been steadily increasing, and with that growth, came new challenges. They started noticing system performance degradation, gaps in security, antiquated interface design, and an overall less than ideal user experience. The client also had concerns regarding ambiguity over how long Salesforce Classic customers would be able to use the interface.
SOLUTION
Provide their user base with a better UI experience, their developers with a more modern architecture, and avoid being forced to migrate to Lightning at an inconvenient time. The client decided to be proactive and undertook a well-planned migration to the Lightning framework, and more recently to Lightning Web Components.
FOR DEVELOPERS
- LWC is aligned with modern web standards (CSS, HTML, and JavaScript), so developers don’t need to be as familiar with Salesforce architecture and can build components for pages faster
- Code reuse is supported for quicker deployments
- Support unit testing for quality assurance
- Access to more developer talent who can quickly use Lightning Web Components to create desired solutions
FOR ADMINS
- Standard-based architecture of Lightning Web Components make the process of building a Lightning page much easier
- Implementing Lightning Web Components is much simpler and more intuitive
- Layered security between the components with stronger authentication standards
FOR USERS
- Enhance user experience – easier to navigate pages, information is more targeted and better aligned on the screen
- LWC components run more fluidly without browser interferences, enhancing performance
- Mobile friendly
- Chat option
- Users are more productive
Published:
December 01, 2019
Category:
Healthcare / Salesforce
Client:
Major Health Insurance Provider
