Has anyone used the "SourceID" field within the Create XML Document Step? If so what is it's purpose? I have read the Step Reference and help but it is very vague. Typically, I take URL document and "convert" into the XML document. I was curious if this field will allow you to filter information in the XML Document. If someone has an example of it's use I would like to see how it is used.
Any help is appreciated.
Looks like you have experience in creating XML scripts. I am trying to integrate with a web service and retreive some information from MS CRM to make call routing decisions. The web service is working on one of the CRM Servers and I need to call the service from IPCC script. I am looking at the following steps to create this , can you tell me if I am on the right track or missing something entirely??
Create URL Documsnt
Create XML Document
Get XML Document Data
You are on the right track.
Create document variable.
Use the "Create URL Document" step with the URL of the web service you would like to get info from.
Then use the "Create XML Document" step to retrieve the information into the document variable.
If you have to iterate through the xml to collect a bunch of data you will to build the xpath for information that you need.
Then use the "Get XML Document Data" step with the respective xpath to retrieve the data into your output string variable.
Here is an OLD example of an xpath statement:
If you need more information let me know and I will post an example.
Thanks! I have the script almost there...
I am receiving an error during reactive debugging on the Extract XML data step. Below is an example of the output from the web service and the XML path I have set in my script. Any help would be great!!
The xml path in my get xml document data step
"/descendant: :CiscoRoutingInfo/child: :OwnerTelephone"
Maybe this is a web or copy and paste thing but do you actually have a space in between the colons in your xpath? In all of my scripts I do not have any spaces.
Thanks, I had added these spaces after reveiwing the doc you sent, it looked like there might be spaces in the xml path in the sample. I have removed the spaces. I might be getting the error on the create XML document step. The return data is already xml before I execute this step, will this cause problems? In the reactive debug screen the document name during the create xml document step changes from the http:// name to something looking like this:
Then on the get xml document data step I am receiving the following error.
null; nested exception is: java.io.IOExeption
This is your problem. It is not pulling the xml from the web service correctly. The corect output should be the entire xml document in one long string with line feeds and carriage returns replaced with /n and /r. Are you using GET or POST? The Microsoft web services I was interfacing with would not work with POST. IPCC passes a null character at the end of the post and the web services couldn't handle it.
I am using a get right now. The web service has a attribute named TelephoneNumber that I am trying to pass the Caller Id in a create URL Document step. I have the url set as follows;
The method is set to get and I have the parameter name "TelephoneNumber" mapped to the value ANI which is the variable containing the string with the caller ID passed from the script. Maybe this is returning an error on the page???
Another issue could be authentication to the web service which is located on a server on the local W2K3 domain. IPCC is not on the domain so if i open a browser to the web service I am forced to authenticate with a username, password, and domain. This may cause the get url document step to fail.
Hey, Thanks for all your advise! Do you know what step would actually submit the url created in the get url document step. Reading the step guide this only creates the url it does not submit it for processing... I tried adding an http send response but am getting an error which says the triggering contact is not http???
It is the "Create XML Document" step makes the request. The HTTP steps are used if the trigger is an HTTP trigger not a JTAPI trigger. That is a whole other conversation. Here is what I would try. I would enable security auditting on the web server and find out what username is trying to access the web service then add that username with the correct password to web server. I don't know of another way to find out which user is trying to access the information. Another idea would be to disable the authentication for the web service and make sure the ipcc application is working. OR maybe just allow anonymous access to the particular web service you need to access for your script.
BTW What version of IPCC are you using?
I am using IPCC Express Premium 4.0(4). The web server is part of a Windows 2003 Domain which my IPCC server is obviously not a member. I think it could be domain authentication that might be messing me up. I changes the local admin password in windows on the IPCC server to match the local admin password on web server. this allows IE to use service without authentication. I created a local admin in the webserver with the same user/password as the ipcc admin... I will see if I can gather some information from the security logs....
Does anything special need to be configured for the variable used to store the URL document created? This is the same variable referenced by the create xml document step as both the source and output docs....
Thanks for all your time on this! It was the server authentication!! So, now I am getting the XML doc in my variable as below.
However my variables do not populate with the expected values. They are all null following the get xml document data steps. I am using the following as my xml path.
If you can find away to get it out of the xml it will work.
I don't know why this is happening but it is definitely your problem.
Looking to your topic because I've had the same issue on a customer site, I have searched a little.
I've seen on the UCCX admin web page that the site is trusted by IE. So I've trusted my web server in IE. And it seems to work ...
In the other hand, dev team of the web server seem to have problems with past certificates ...
Moreover, it works fine in HTTPS but not in HTTP. I think that it could be a difference behavior of the web server between http and https.
A way to workaround this issue is to use the "Set Xml_Doc = URL[URL_var]" in place of Get URL Document.
For information, I use UCCX 5.0.2 on a Win2K3 SP1.
Hop this help ...