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
4 replies
Subscribers
5 subscribers
Views
1770 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Deploying a rule calling a new Web Service operation
mikej117
over 7 years ago
Hi,
Our Appian instances call a web service to retrieve personnel data. We have recently (today) added a new web service operation to retrieve some new data and have integrated this with our Appian dev instance. We want to call the operation using an expression rule (using the webservicequery function). In order to get the operation list to update in Dev, we had to create a temporary process model with a Call Web Service node, that allowed the operation list to be refreshed. That worked and now the expression rule works fine in Dev.
Now here's the problem: When the expression rule and related newly-generated CDTs are imported into the Test environment, the expression rule is complaining that the operation is not available. But the web service was updated for the Test environment, so it should be available.
What is the best way to get the operation list updated ...
OriginalPostID-247832
Discussion posts and replies are publicly visible
Parents
0
mikej117
over 7 years ago
Thanks Abhinav. I tried deploying the generated data types with the new expression rule and got the same result: Operation not available.
Last time this error occurred, the fix was to restart the App Server (JBoss) to force the WSDL to be refreshed. While that would avoid the need to manually call a process model in Production, it's not really a timely or easy solution for deployment.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
mikej117
over 7 years ago
Thanks Abhinav. I tried deploying the generated data types with the new expression rule and got the same result: Operation not available.
Last time this error occurred, the fix was to restart the App Server (JBoss) to force the WSDL to be refreshed. While that would avoid the need to manually call a process model in Production, it's not really a timely or easy solution for deployment.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data