Sometimes when developing a custom smart service plug-in, you change your mind ahttps://community.appian.com/discussions/f/plug-ins/1278/sometimes-when-developing-a-custom-smart-service-plug-in-you-change-your-mind-aSometimes when developing a custom smart service plug-in, you change your mind about whether an input is required or what you are going to name one of the activity class parameters. Is there any way to do this and avoid the errors like the ones shownen-USTelligent Community 12RE: Sometimes when developing a custom smart service plug-in, you change your mind ahttps://community.appian.com/thread/4413?ContentTypeID=1Mon, 30 Sep 2013 04:28:11 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:8f203830-ad9a-48f3-9b76-f44d314d3b67prestonbThat did it! Thanks!<div style="clear:both;"></div>RE: Sometimes when developing a custom smart service plug-in, you change your mind ahttps://community.appian.com/thread/4412?ContentTypeID=1Mon, 30 Sep 2013 04:02:13 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:922723cc-5213-4cd9-81e6-63807564e715Eduardo FuentesPer the Best Practices section in the Appian Developer Guide, when changing the name or number of inputs/outputs you have to change the smart service key. More information at <a href="https://forum.appian.com/suite/wiki/72/Custom_Smart_Service_Plug-ins#Upgrading">forum.appian.com/.../Custom_Smart_Service_Plug-ins</a><div style="clear:both;"></div>