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
6 replies
Subscribers
5 subscribers
Views
3145 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
We are having an issue with CDT reference. We got to change the namespace of CDT
janakik
over 10 years ago
We are having an issue with CDT reference. We got to change the namespace of CDT, so we just changed the namespace and imported the new CDT before that we deleted the old CDT.
Now when we do the impact analysis on this new CDT it was not listing out any Appian Process Models/Rules referencing to this new CDT. But we could see ^ symbol in the process models which mean it is referencing to the old CDT.
Any help would be great!...
OriginalPostID-110988
OriginalPostID-110988
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Just to complement what has been already said:
Impact Analysis inspects every single item in your applications under the Applications tab to determine what objects make reference to the selected CDT. Once CDTs are registered/created in Appian Impact Analysis will identify them as unique through their name + namespace combination; that said when you change the namespace this CDT is no longer a version of the deleted one, it's a completely new one since the identifier name + namespace is no longer the same, that makes Impact Analysis unable to think that object A referencing {old_namespace}myCDT is now supposed to make reference to {new_namespace}myCDT.
This behavior is expected since Appian cannot guess that {old_namespace}myCDT is supposed to be now a new version of {new_namespace}myCDT; there's nothing that could link those CDTs specially since the way you created the new one was by deleting the old and uploading the new one; notice how at no point there's an association when you upload a CDT with a deleted one other than the one that gets created if you keep the original name and namespace.
In summary, when updating a namespace you need to:
1. Upload the CDT with the new namespace
2. Manually update your models/objects to point to the new CDT
3. Only at this point you can delete the CDT with the old namespace.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Just to complement what has been already said:
Impact Analysis inspects every single item in your applications under the Applications tab to determine what objects make reference to the selected CDT. Once CDTs are registered/created in Appian Impact Analysis will identify them as unique through their name + namespace combination; that said when you change the namespace this CDT is no longer a version of the deleted one, it's a completely new one since the identifier name + namespace is no longer the same, that makes Impact Analysis unable to think that object A referencing {old_namespace}myCDT is now supposed to make reference to {new_namespace}myCDT.
This behavior is expected since Appian cannot guess that {old_namespace}myCDT is supposed to be now a new version of {new_namespace}myCDT; there's nothing that could link those CDTs specially since the way you created the new one was by deleting the old and uploading the new one; notice how at no point there's an association when you upload a CDT with a deleted one other than the one that gets created if you keep the original name and namespace.
In summary, when updating a namespace you need to:
1. Upload the CDT with the new namespace
2. Manually update your models/objects to point to the new CDT
3. Only at this point you can delete the CDT with the old namespace.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data