Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Verified Answer
+1
person also asked this
people also asked this
Replies
7 replies
Subscribers
8 subscribers
Views
2694 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
I am having an issue where calling a web service via web service smart ser
foussenik
over 10 years ago
I am having an issue where calling a web service via web service smart service is returning partial data. Calling same web service via soapUI returns full data.
Any idea?...
OriginalPostID-104498
OriginalPostID-104498
Discussion posts and replies are publicly visible
0
Aleksi White
Appian Employee
over 10 years ago
Have you looked over the documentation to ensure the call web service node is configured correctly?
forum.appian.com/.../Call_Web_Service_Smart_Service
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Aleksi White
Appian Employee
over 10 years ago
Could you also provide some more information on what web service you are calling, and on how your call web service node is configured?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
foussenik
over 10 years ago
This issue started occurring when process model was deployed in test environment. In dev environment it works fine.
I added web service node an configured it. It works fine on dev environment fine.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Aleksi White
Appian Employee
over 10 years ago
Did the application import without any issues into the test env? What sort of partial data is returned, and what full data is expected to return?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Rully
over 10 years ago
Hi Foussenik,
Is your web service response data object class contains more than 1 level inherited classes? My experience was when you contruct your data class to inherit more than 1 parent class, the data wouldn't be passed correctly to the web service layer eventhough it works in SoapUI. Try to remove the inheritance or keep it at one level and then see how it goes.
Hope this helps.
Regards,
Rully
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
+1
Eduardo Fuentes
Appian Employee
over 10 years ago
Another thing to check is that the relevant CDTs are re-created to point to the most recent definition of the WSDL. If the model was imported but the CDTs were not deleted (or if a least was 1 skipped) then the CDTs may still be pointing to a previous WSDL definition which had less fields.
To prove this theory:
0. Identify all the CDTs related to this web service. Sort by namespace if that makes it easier. Remember you need to identify ALL of them, if you miss at least one then the issue will not be resolved.
1. Delete those CDTs. Once again, I'll have to emphasize that you need to delete ALL of the related ones, if you miss at least one then the issue will not be resolved.
2. Open up the process model, right click on the Call Web Service Smart Service - Properties - Setup
3. Temporarily check Authentication Required and typed something in username and password and click Refresh
4. Uncheck the authentication required option.
5. Finish configuring the smart service.
6. Save and publish the model
7. To quickly update the references in the process model simply export your application from the SAME ENVIRONMENT (TEST) and import it again. This mimics Impact Analysis but only for this application which should be faster.
8. Start the process and see if the data is now returned correctly.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Reject Answer
Cancel
0
foussenik
over 10 years ago
Eduardo,
Appian Admin follow your steps and it is working now.
Thanks
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel