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
+1
person also asked this
people also asked this
Replies
32 replies
Subscribers
6 subscribers
Views
45502 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Using Exchange Web Services for email
alanl
over 7 years ago
My exchange administrators are saying that I need Appian to use Exchange Web Services. How can I get Appian to talk using this protocol?
Thanks in advance. I did a search and I didn't see anything after 2015...
OriginalPostID-258508
Discussion posts and replies are publicly visible
0
Vinod Bongoni
Certified Lead Developer
over 7 years ago
That's great. You’re welcome Prasad. I’m happy to help
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
alexis gutierrez
over 6 years ago
in reply to
Vinod Bongoni
Hi,
We are migrating our mailbox to office365.
The customer requirement are to :
- use the Exchange Web Service soap (so no IMAP/POP3) to access the mailbox,
- read mails and attachement,
- and use a proxy to access the office365 mailbox.
So we tried several solutions with, each time, the proxy configured in the Appian administration console :
- First, we used the Advanced Call Web Service (SOAP) plugin but the call to the web service ended with a "TimeOut" error.
We think that this plugin is not use the proxy configured in the administration console,isn´tit?
- Then we tried the getEWSEmails () function of the Exchange Web Service plugin but we also got a "TimeOut" error. We think that this plugin is not use the proxy configured in the administration console,isn´tit?
-Then we tried the smart service Call Web Service as according to the Proxy section of the Administration Console this smart node used the configured proxy.
However, after filling in the URL of the WSDL and the authentication informations, we are unable to get the services with the associated button.
The error message received is: "The WSDL can not be processed because the client and server failed to negotiate SSL security. (APNX-1-4045-004) »
- Finally, we created a REST integration object with a POST method in which we send a SOAP request to the body.
This last solution works but does not allow us to handle attachment without to use pv on a process like the Advanced Call Webservice plugin can do.
So could you answer us regarding these questions:
- What are your recommendations regarding our requirements ?
- how to make working your plugin with proxy?
- Is your plugin working for attachment?
- Why the smart node Call Web Service does not work with the proxy configured ?
- Do you know a solution to directly convert a Base64 encoded text field (mail attachments) to a document in Appian ?
Thank you in advance for your answer.
Alexis
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<