PAM 4.3.1 integrated with SDM 14.1.03 with SDM Custom Operators and ITIL Process Definitions loaded.
I have copied the working out-of-the-box "Request Fulfillment" process to use as a template for a new hire process.
After the existing "Get_Object_Values" operator, I am inserting the "Get_Related_List_Values" operator to get the properties associated with the request ticket.
I have set the Object Handle to Process.persid (inherited from the initialize operator) and the ListName to "<string>properties</string>".
When I try to run this I am getting this error:
<Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>soapenv:Server.userException</faultcode><faultstring>org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.</faultstring><detail><hostname xmlns="http://xml.apache.org/axis/" xmlns:ns1="http://xml.apache.org/axis/">MY-HOSTNAME</hostname></detail></Fault>
Looking at the SOAPCallData, it shows this generated for the inline text:
<getRelatedListValues xmlns="http://www.ca.com/UnicenterServicePlus/ServiceDesk"> <sid>1734301844</sid> <objectHandle>cr:403814</objectHandle> <listName><string>properties</string></listName> <numToFetch>-1</numToFetch> <attributes> </attributes></getRelatedListValues>
Using SoapUI, I get responses back using a SID and this ListName, but I also pass Attributes for Label and Value. There is not a field for attributes in the operator nor is it called out in the documentation as a required input.
If I understand the documentation right, it should return an array of all associated properties on the ticket which I would then need to parse. I'm not to that point since it's failing here.
Searching for the "SAXException: SimpleDeserializer" error didn't give me any leads to troubleshoot.
I would try using something like SoapUI outside of PAM to confirm that the soap call either works or does not work. If the same results occur outside of PAM, this may be a question for the Service Desk community. Keep us posted.
It does work in SoapUI. That is were I tested before setting the input values. It's resolved, see below.
I usually get that SAXException: SimpleDeserializer when I have extra xml tags in the SOAP envelope. Looking at the custom operator for "Get Related List Values" the inline text used is:
<getRelatedListValues xmlns="http://www.ca.com/UnicenterServicePlus/ServiceDesk"> <sid>M_SESSIONID__</sid> <objectHandle>M_OBJECTHANDLE__</objectHandle> <listName>M_LISTNAME__</listName> <numToFetch>-1</numToFetch> <attributes> </attributes></getRelatedListValues>
since listName is not a string you do not need to surround it with <string>...</string>. Try using ListName as just "properties".
That was it exactly. I copied the input from SoapUI without thinking the operator would already set the type to String.
(Note to anyone else following up from this: A weird thing happened after I changed this and saved it. Both values for Connection Parameters were blanked out and I had to reset them. I'll keep an eye on it. IE 11 is the browser.)
Using PAM in IE. I salute you brave soldier
Oh, I use whatever gets the job done. This customer is primary IE, so it's easier for me to see any issues in IRFs rendering that way and see what breaks. Chrome and Firefox are installed on all my DEV instances.
Of course, it seems that every release of PAM brings it own quirky behavior in each of the browsers. Much better now than the 2.x days!