Skip to main content
Topics#Data ManagementSam Mundle's Question
Sam Mundle asked in #Data Management
Feb 11, 2019, 6:45 PM

Best Development Strategy for Brand New Org in Upgrade to Lightning

My team is currently upgrading our SF platform to Lightning and like many saw an opportunity to rework much of our business logic and updates in the process. We have decided to scrap almost all of the system as it is quite old and was very poorly maintained. We would like to begin develpment using the Source Driven model to take advantage of version control and local development. However, this model uses the smaller scratch orgs that focus on incremental improvements to an already workable org. I'm looking for a way to only transfer over user/customer data and develop the new Lightning platform independently of the Classic prod org running now. Any suggestions? Any good way of doing this scratch org-based development within a partial sandbox?
5 answers
  1. Amnon Kruvi (The Architech Club)
    Feb 11, 2019, 7:48 PM
    Hi Sam, 

     

    You can certainly use the sandbox approach with source control. For example:

     

    1. Create 1 developer sandbox per developer

     

    2. Create 1 partial {integration) and 1 full (release) sandbox

     

    3. Each developer works in their own sandbox

     

    4. Developers commit their code to source control once a task is finished

     

    5. Source control is deployed daily to the partial sandbox, where it can undergo sanity testing

     

    6. A stable build is promoted to the release sandbox to undergo full testing

     

    7. A successful build is deployed to production
Write an answer...
0/9000