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
2 replies
Subscribers
5 subscribers
Views
1243 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
Hi, After a recent server restart we are facing problems with our sma
senthilar
over 10 years ago
Hi,
After a recent server restart we are facing problems with our smart service. It used to work fine. But after a restart it fails to deploy itself. The error message from logs is
ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to enable Plug-in 'Docusign Plugin' (com.hcl.docusign) version 1.0.0: 'The Smart Service Module was invalid: Illegal attempt to change the data type for smart service com.hcl.docusign.DocusignPlugin, input or output named recipients (APNX-1-4104-005)'...
OriginalPostID-112680
OriginalPostID-112680
Discussion posts and replies are publicly visible
Parents
0
sujithak
over 10 years ago
we created a duplicate version of the plugin with a new name and deployed that again and made it work. But facing this issue again. The following steps result in the error:
1) We have 1 single xsd file which contains all the CDTs (around 20) used by the application. We are in early development phase, so we regularly update the XSD and import that into Appian (and do Impact Analysis to make sure everything is mapped correctly). The CDT associated with the smart service has not been modified in the updated XSD and the updated XSD is imported successfully into Appian.
2) The smart service continues to work after this import.
3) Server is restarted for some maintenance activity. Now, the smart service fails to deploy itself with the error described above.
How to avoid this? Should we not import the cdt again if it is associated with the smart service (though in our case there was no modification to the smart service associated CDT)? What would be a quick and easy solution than to recreate and deploy the plugin again?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sujithak
over 10 years ago
we created a duplicate version of the plugin with a new name and deployed that again and made it work. But facing this issue again. The following steps result in the error:
1) We have 1 single xsd file which contains all the CDTs (around 20) used by the application. We are in early development phase, so we regularly update the XSD and import that into Appian (and do Impact Analysis to make sure everything is mapped correctly). The CDT associated with the smart service has not been modified in the updated XSD and the updated XSD is imported successfully into Appian.
2) The smart service continues to work after this import.
3) Server is restarted for some maintenance activity. Now, the smart service fails to deploy itself with the error described above.
How to avoid this? Should we not import the cdt again if it is associated with the smart service (though in our case there was no modification to the smart service associated CDT)? What would be a quick and easy solution than to recreate and deploy the plugin again?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data