Use a separate Xelence Studio database for each branch of work
Also listed as: Multiple Xelence Studio databases per branch
What is it?
Developers can keep multiple Xelence Studio databases, one per Git branch, so parallel lines of work don't overwrite each other's data.
Why does it matter?
Safer parallel development and fewer conflicts when switching between pieces of work.
Start thinking about
- How do changes move from development to production today, and where are the delays?
- Who approves a release, and which checks must pass first?
- How much of your testing is automated, and which areas would you automate next?
- How will you keep personal information out of development and test environments?
- How will you manage your customizations so that taking a new base version stays manageable?
- What skills or training will your developers need as Studio adds AI assistance?
Terms used on this card
- Git
- A widely used version-control system. It tracks every change to your solution's files, so work can be shared, merged or rolled back.
- Xelence Studio
- The web-based design tool your developers use to configure Xelence solutions, such as forms, rules, workflows and reports. It has Git version control built in.