Working with Request Offerings and Service Requests
2 min
about request offering and service request web methods docid 2cb7yylom2hau6l9l0nmousing the getcategories web method docid\ zaajkho blm b1o86pl8dusing the getcategorytemplates web method docid\ vjtnrz0u1 ukuhteq q0tusing the getalltemplates web method docid\ euawqwgn9sxnvw8qddnxvusing the getsubscriptionid web method docid\ kvanfbbunuyfoamwh9so9using the getpackagedata web method docid\ cfp8zzfb6tekdccxun0krusing the usercanaccessrequestoffering web method docid\ zmvsintsjm16cmayucanhusing the submitrequest web method docid 7z5e9uobmcdsyecptwa qusing the getrequestdata web method docid\ gmje3kkccb78ubaiiiubdusing the fetchservicereqvalidationlistdata web method docid\ lwn6owthirbh8pcyr8ymv about request offering and service request web methods there are several web methods that provide access to the request offerings available in the service catalog, provide the ability to submit service requests, and provide access to retrieve them once they are submitted the following table summarizes the available web methods for this \<font color="#ffffff">web method\</font>\<font color="#ffffff">description\</font> getcategories returns a list of categories in the service catalog getcategorytemplates returns a list of the request offerings in the service catalog that belong to the specified category getalltemplates returns a list of all of the request offerings in the service catalog getsubscriptionid returns the subscription id that corresponds to the request offering for the current user getpackagedata returns the details of the specified request offering usercanaccessrequestoffering checks if the current user can access the specified request offering submitrequest creates and submits the service request on behalf of a specified user getrequestdata returns the data for the specified service request fetchservicereqvalidationlistdata returns the allowable validation list data for the specified service request parameter when accessing the various service catalog web methods via the api, most of the web methods are invoked based on the id of the service request subscription record, and not with the id of the request offering itself when you define the request offering, you must specify whether it is configured as "publish and subscribe" or "publish" publish action when configured as "publish and subscribe", users belonging to the indicated organizational unit have access to the request offering when configured as "publish", users have access to the request offering based on the service level agreement for the organizational unit to which the user belongs the servicereqsubscription record (used internally by the service catalog) contains information about the organizational unit to which the request offering is associated, along with the service level agreement information if it is configured relative to the service level agreement in the following sections, several of the web methods use the id value of the servicereqsubscription record you can use a helper web method called getsubscriptionid to obtain the subscription id, which can then be used in any subsequent operations, such as submitrequest
