<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Call Web Service global element does not exist (APNX-1-4050-001)</title><link>https://community.appian.com/discussions/f/process/12729/call-web-service-global-element-does-not-exist-apnx-1-4050-001</link><description>I am trying to use Call Web Service in my process model, but I am receiving the following error for the WSDL: 
 This Operation is unavailable. The following error occurred during the creation of the message schemas: The global element { clones.telcordia</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Call Web Service global element does not exist (APNX-1-4050-001)</title><link>https://community.appian.com/thread/57340?ContentTypeID=1</link><pubDate>Thu, 28 Jun 2018 12:12:49 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:09777a5f-5ea5-4e88-83aa-a23ed82df02d</guid><dc:creator>christiang</dc:creator><description>&lt;p&gt;SoapUI was able to consume the WSDL without any problem.&amp;nbsp; I discovered the issue. Appian does not handle &amp;lt;xsd:include&amp;gt; properly. It seems to overwrite all other elements defined in the namespace. I had to use the workaround of pasting the contents of all included xsd files into the WSDL.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Call Web Service global element does not exist (APNX-1-4050-001)</title><link>https://community.appian.com/thread/57328?ContentTypeID=1</link><pubDate>Thu, 28 Jun 2018 10:38:23 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:21f3bf17-3857-40ab-8437-a79f4c8dd1a3</guid><dc:creator>Pitla Mahesh</dc:creator><description>Hi,&lt;br /&gt;
&lt;br /&gt;
Please try to consume the same WSDL using SOAP UI. If you are able to consume in SOAP UI, then compare the request and response of the SAOP UI with the Appian&amp;#39;s request and response or sample request and response. Based on that ask the vendor to make changes.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>