Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
8 subscribers
Views
1375 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
We are refactoring table and column names, thought of confirming if there could
senthilar
over 9 years ago
We are refactoring table and column names, thought of confirming if there could be any side-effects:
We have our CDTs created using XSD file. There are lots of CDTs and the XSD file itself has about 2000 lines. This application has crossed UAT. Now we are taking up the exercise of standardizing the DB table and column names by updating the XSD with @Table and @Column attributes.
We are not using SQL queries anywhere. Is it safe to do this exercise now? Can it result in any side-effects? What should we lookout for?
Many Thanks!...
OriginalPostID-123819
OriginalPostID-123819
Discussion posts and replies are publicly visible
Parents
0
bharathwajanr587
over 9 years ago
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 :)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
bharathwajanr587
over 9 years ago
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 :)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data