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
9 replies
Subscribers
4 subscribers
Views
2993 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
Within one of our Appian instances we are getting the 'Illegal attempt to ch
dons
over 9 years ago
Within one of our Appian instances we are getting the 'Illegal attempt to change an input to an output' errors during deployment of the plugins. This is happening for plugins we have developed and other plugins that we didn't develop. None of the CDT or the parameters to the plugins have changed in quite some time. In order to figure out / resolve the issue, I have two questions regarding this problem.
First, can anyone tell me entries I can add to appian_log4j.properties file that will help me determine exactly what differences Appian thinks there are between the currently deployed plugin and the plugin attempting to deploy? The message tells me the parameter/CDT name, but what I need to know more specific details about what is different.
Second, is there some utility or option that can be used to completely remove a plugin from Appian so the latest plugin can be deployed successfully without having to change the plugin's key?
Thanks
OriginalPostID-145909
OriginalPostID-145909
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 7 years ago
No changes in the product on this feature. The solution is still to use the annotations and to instruct developers not to delete the CDTs that plug-in use.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 7 years ago
No changes in the product on this feature. The solution is still to use the annotations and to instruct developers not to delete the CDTs that plug-in use.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data