IT Process Automation

Andy_Thompson wrote:

The Soap call to Service Desk of "createRequest" is more a function of Service Desk itself than of the ITPAM operator.

You can read about the "createRequest" web service in the Service Desk Technical Reference Guide that comes with the Service Desk install media. Here is an excerpt from that doc that may help:

propertyValues is a list of values for each Property object that will be attached to the new Request. The Properties that are attached are determined by the new Request‘s ‗category‘ attribute value. All properties created from the CA Service Desk Manager Web Services interface will have a default value (for more information, see Categories and Properties), which is important because a Request will not save until all of its Properties marked ―required‖ have a value.
You may override the default by supplying values for any properties that will be attached when the Request is created. You must supply this information before the Request is created, since createRequest() attempts to back-store the object you most recently create. Use getPropertyInfoForCategory() to get a list of properties for a specific Category. This function returns the properties in order of their ‗sequence‘ attribute, which is the expected order of the propertyValues array. For example, if the sequences and symbols of the properties are as follows:
100 – Hard Drive Size
200 – CPU
300 – Memory
The propertyValues array, depending on the programming language, may appear as follows:
[“40 GB”, “Pentium 4 1.7 Ghz”, “256”]

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.ca.com/UnicenterServicePlus/ServiceDesk">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:createRequest>
         <sid>1558738301</sid>
         <creatorHandle>cnt:F65CA47558A73E41BBFF34D0E65F6404</creatorHandle>
         <attrVals>
            <string>description</string>
            <string>Test Description</string>
            <string>category</string>
            <string>pcat:66443334</string>
            <string>log_agent</string>
            <string>cnt:F65CA47558A73E41BBFF34D0E65F6404</string>
            <string>summary</string>
            <string>Test Summary Here</string>
            <string>status</string>
            <string>OP</string>
            <string>customer</string>
            <string>cnt:F65CA47558A73E41BBFF34D0E65F6404</string>
            <string>type</string>
            <string>R</string>
            <string>priority</string>
            <string>0</string>
         </attrVals>
         <propertyValues>
         <!-- The value Yes below is the value of the first (and only) property dropdown -->
            <string>Yes</string>
            </propertyValues>
         <template></template>
         <attributes>
            <string>ref_num</string>
         </attributes>
         <newRequestHandle></newRequestHandle>
         <newRequestNumber></newRequestNumber>
      </ser:createRequest>
   </soapenv:Body>
</soapenv:Envelope>

Brent_Verkler wrote:

From: Verkler, Brenton
Sent: Wednesday, December 12, 2012 1:46 PM
To: mb.11871426.99849557@myca-email.ca.com
Subject: RE: [PAM - General Discussion] RE: Service Desk - Create Request with Properties

Good afternoon.

This may be helpful (This is from soapUI 4.5.1 opening a Request with one required property in Service Desk R12.6):

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.ca.com/UnicenterServicePlus/ServiceDesk">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:createRequest>
         <sid>1558738301</sid>
         <creatorHandle>cnt:F65CA47558A73E41BBFF34D0E65F6404</creatorHandle>
         <attrVals>
            <string>description</string>
            <string>Test Description</string>
            <string>category</string>
            <string>pcat:66443334</string>
            <string>log_agent</string>
            <string>cnt:F65CA47558A73E41BBFF34D0E65F6404</string>
            <string>summary</string>
            <string>Test Summary Here</string>
            <string>status</string>
            <string>OP</string>
            <string>customer</string>
            <string>cnt:F65CA47558A73E41BBFF34D0E65F6404</string>
            <string>type</string>
            <string>R</string>
            <string>priority</string>
            <string>0</string>
         </attrVals>
         <propertyValues>
         <!-- The value Yes below is the value of the first (and only) property dropdown -->
            <string>Yes</string>
            </propertyValues>
         <template></template>
         <attributes>
            <string>ref_num</string>
         </attributes>
         <newRequestHandle></newRequestHandle>
         <newRequestNumber></newRequestNumber>
      </ser:createRequest>
   </soapenv:Body>
</soapenv:Envelope>

--Thank You,
Brent

Using SDM 17.1.01 ..  benefited and found this thread to be yet relevant.

I was able to pass sid form login method to createrequest

Followings are CreateRequest operator config.

I see in the discussion you had several samples about to create the request,...

you may execute this at the command line to get the attributes of cr (the Request)

bop_sinfo -d cr

It will show a list like this

C:\Users\Administrator>bop_sinfo -d cr

Factory cr
Attributes:
id INTEGER
producer_id LOCAL STRING(20)
persistent_id STRING(30)
new_delay_log LOCAL STRING(0)
ref_num STRING(30) REQUIRED
summary STRING(255)
description STRING(4000)
status SREL -> crs.code REQUIRED
active SREL -> bool.enum REQUIRED
open_date DATE

.
.

In the activity from Brent, you see

            <string>log_agent</string>             <string>cnt:F65CA47558A73E41BBFF34D0E65F6404</string>

log_agent is in the list of "bop_sinfo -d cr"