We are refactoring table and column names, thought of confirming if there could

On the high-level, there will not be major issues as you are changing only CDTs, which are getting normalized. But, as a best practice, this should have been conceived during the development phase. Having said that, the main concern is to keep the modifications synched across all the environments(Dev, test, UAT and Prod).

Please make sure to do the following
1 Do the impact analysis properly for all the modified CDTs.
2.Don't change the namespace used in the CDT
3. In anywhere in the process model, if you would have used the 'ac!cdt.fieldname' mapping in the output values, please go and update those things.
4. Make sure, you update the rule which use the "anytype" datatype, which uses the CDT(modified) to map to the modified field name.
5. Need to analyse and update the query rules that uses the updated CDT.
6. On the portal reports, mapping of the definition need to be verified for the modified field name in the CDT.

I hope, this would help in moving forward in your activity of re-factoring. But, Finally, please do a thorough testing of the entire functionality once you do the modification :)

Thank you Bharath! Just to be clear, we are not modifying any field names in CDT, we are only adding the @Table and @Column attributes so that we get the DB Table and Column names as per project standards. By default, appian generates these names based on the CDT and member element values.