Question
de Volksbank
NL
Last activity: 8 Jul 2019 3:25 EDT
Code Refactoring approach
Hello All,
Need suggestion - We went to production recently with MVP, but realized that we need to refactor the code, where we have to below changes
1. Rename application , access groups
2. Change class names
3. Change table names etc.,
Changing all this is fine in Development, but what about the code which is in production already?
If i do changes in dev and deploy , there will be 2 classes (old and new) same goes with application and access group etc.,
Can we clean up the code in prod and deploy the new changes? is it right approach.
Regards
Gouri Shankar K
Pegasystems Inc.
FR
Hello,
That sounds very risky. Because with the migration you will still have existing cases and assignments working with the old versions.
Could you be working with both applications and move the users from the old one to the new day after day to finally forget about the old one
de Volksbank
NL
Hello MarcLasserre, Thanks for your response.
You have right question, we do have discussed about old cases and we thought we will delete the cases if there are less.
else we have to find a way how we can migrate the cases as per new design (Not found any concrete approach as of now)
Yes all users will have access to new application (Redesigned application, access group etc) once we go live with new design.
My questions:
1. If i start renaming class (Using wizard), it renames classes and rules with new names, then i will not have old rules in development, But if i deploy to next environment (Test, Prod) it will have 2 rules each (old and new) this causes in-sych b/w dev and production.
2. What i know with my exp, is deleting / refactoring code in production directly is not a good idea.
I will post new questions, if any.
Regards
Gouri Shankar K