We are looking to rebuild out Field Service Mobile implementation as it was developed 6 years ago and is heavily customised and inconsistently built. Our plan is to completely reinstall it fresh out of the box and introduce only minimum customisation needed for our business requirements.
For capturing development, we are considering:
- Update Sets - We use them for all work currently
- My Company Applications - Capturing customisations to Field Service Mobile in a scoped app and storing them in the My Company Applications repository
- Git - We don't currently use this, but I'm interested to know if it's the approach we should consider
For the rebuild, we want to:
- Link changes to the relevant story so we know why specific changes were made
- Move changes reliably between instances
- Clearly identify what is included in each release
- Be able to return to a previously working version if something goes wrong
- Minimise issues with future Field Service upgrades
I'm interested to hear your thoughts on which approach, or combination of them, on how your teams approach this or what you'd recommend.
Please don't just give a response from the post popped into AI for a generic result, people's lived experience is more useful 🙂
