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
5 replies
Subscribers
9 subscribers
Views
4040 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hi, What is the best approach to change the CDT names in an applicati
Rahul Gundu
over 9 years ago
Hi,
What is the best approach to change the CDT names in an application?
The same prefix, used by some other applications, The application is at initial stage, and only one workflow is implemented. So,we feel that, it's a right time to do this activity.
Example: APP1_Employee to APP2_Employee
Thanks,
Rahul Gundu
OriginalPostID-183162
OriginalPostID-183162
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 9 years ago
@rahulg That's true, if I am not wrong what @harshav meant to say is, to create a new cdt and use it from now on as you have said that the application is at early stages. And re your understanding that a new data type is created and impact analysis is not done - To the best of my knowledge, it is an expected behavior because Appian forms UUID of a data type by using the attributes namely 'Name' and 'Namespace' which means that if you change either of them Appian assumes that you are working on a different object. The same can be studied at https://forum.appian.com/suite/help/7.11/Custom_Data_Types.html#Properties by going through the 'Namespace' and 'Name' properties and also in the 'Note' part at https://forum.appian.com/suite/help/7.11/Custom_Data_Types.html#Edit.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 9 years ago
@rahulg That's true, if I am not wrong what @harshav meant to say is, to create a new cdt and use it from now on as you have said that the application is at early stages. And re your understanding that a new data type is created and impact analysis is not done - To the best of my knowledge, it is an expected behavior because Appian forms UUID of a data type by using the attributes namely 'Name' and 'Namespace' which means that if you change either of them Appian assumes that you are working on a different object. The same can be studied at https://forum.appian.com/suite/help/7.11/Custom_Data_Types.html#Properties by going through the 'Namespace' and 'Name' properties and also in the 'Note' part at https://forum.appian.com/suite/help/7.11/Custom_Data_Types.html#Edit.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data