IT Process Automation

  • 1.  Using changeStatus Soap Operator Fails

    Posted Dec 29, 2016 11:26 AM

    I'm using the Invoke Service Desk Web Service Operator to do the following:

    <impl:changeStatus xmlns:impl="http://www.ca.com/UnicenterServicePlus/ServiceDesk">
    <sid>sid__</sid>
    <creator>creator__</creator>
    <objectHandle>objectHandle__</objectHandle>
    <description>description__</description>
    <newStatusHandle>newStatusHandle__</newStatusHandle>
    </impl:changeStatus>

     

    I've verified that my new status exists and is allowed and I'm getting back the following.


    soapenv:Client
    Unknown value for status
    Unknown value for status
    1000

     

    Any ideas or help would be greatly appreciated.

     

    Thanks!



  • 2.  Re: Using changeStatus Soap Operator Fails

    Broadcom Employee
    Posted Dec 30, 2016 02:04 AM

    Hello Joel,

    SDM WS error messages are docuementated at this URL:
    https://docops.ca.com/ca-service-management/14-1/en/building/building-ca-service-desk-manager/web-services-management/tips-for-soap-web-services-clients

    ::

    UDS_BAD_PARAM1000

    A bad parameter was passed to a method. This error occurs if a required parameter is missing, the wrong type was passed, or an invalid value was used.

    There are some known patches for SDM 12.9 for problems qith the changeStatus function.

    The user trying to used this WebService function must have administrator permissions.

     

    I think it is best you active at the sdm server with pdm_log4j_Config the debug level and redo your test.

    The jrsvr.log file with show the data for your ws call.

    This will be the starting point to investig why the function is now working for you.

    You may open a CA Support case to get help from ITPAM and SDM team.

    Ferdinand



  • 3.  Re: Using changeStatus Soap Operator Fails
    Best Answer

    Posted Jan 02, 2017 08:52 AM

    What value are you substituting for newStatusHandle__ ?



  • 4.  Re: Using changeStatus Soap Operator Fails

    Posted Jan 03, 2017 08:30 AM

    Heh, Figured it out and Lindsay you're hot on the trail of my problem. Here I thought Sending the code string was what was being asked for. For instance "OP" would set it to open. I was wrong, Instead it was looking for the unique persid. I created my own operator that does a lookup of the persid based on the code and it's delete flag.

    Many Thanks!