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
3 replies
Subscribers
5 subscribers
Views
1646 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
Plugin deployment - Is Appian keeping a reference to the plugin key's in the
padmanabhanv
over 9 years ago
Plugin deployment - Is Appian keeping a reference to the plugin key's in the kdb database or another location. I had a plugin with key "CreateX". I changed something in the plugin, renamed the key to "CreateY" and deployed without issues(
forum.appian.com/.../Custom_Smart_Service_Plug-ins
However I had to make another change in the plugin and now renamed it back to "CreateX" - but it throws an error saying input counts don't match which is true if Appian is referring to the older version of the key. Is this a known issue? Do we have to keep a log of the changes the plugin underwent in its life cycle and use that for putting a unique constraint on the plugin key?...
OriginalPostID-118928
OriginalPostID-118928
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 9 years ago
This is documented here
forum.appian.com/.../Custom_Smart_Service_Plug-ins.html
and is a constrain to make sure existing process won't break by the removed/added node inputs, that's why you need to use a different key.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 9 years ago
This is documented here
forum.appian.com/.../Custom_Smart_Service_Plug-ins.html
and is a constrain to make sure existing process won't break by the removed/added node inputs, that's why you need to use a different key.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data