This documentation applies to the 8.1 version of Service Request Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Request_Submit_Service

Use the Request_Submit_Service function to create and submit service requests. The following tables list the values required to submit a service request through the SRM:RequestInterface_Create form.

Note

Service requests generated from the Request_Submit_Service function are validated against On Behalf Of (OBO) rules. To use this function, an OBO rule must be configured so that the Requested By user can submit a service request on behalf of the Requested For user.

For information about configuring OBO rules, see Creating on-behalf-of definition rules.

The following table lists the required fields if you are using web services or an interface form. A record is not created if the required field values are NULL.

Note

Service request definitions (SRDs) that have questions associated with them are not currently supported because no mechanism exists to gather the responses to questions through the web service interface.

Required input field values

Web service field

Database field on interface form

Notes

Company

Company

TitleInstanceID

TitleInstanceID

Instance ID of the service to be requested. An interface must be built for users to easily obtain this value from the SRD.

Source_Keyword

Source Keyword

Enter Interface Form or something similar to describe the creation origin.

Login_ID

Login ID

Add_Request_For

Add Request For:

The interface form has the following attributes for the Requested For field on the interface form:

  • Individual (the default)
  • Organization
  • Department
  • Company

    One of these attributes must be passed through the web service.

Impact

Impact

The interface form has the following attributes for the Impact field on the interface form.

  • 1-Extensive/Widespread
  • 2-Significant/Large
  • 3-Moderate/Limited (the default)
  • 4-Minor/Localized

    One of these attributes must be passed through the web service.

Urgency

Urgency

The interface form has the following attributes for the Urgency field on the interface form.

  • 1-Critical
  • 2-High
  • 3-Medium (the default)
  • 4-Low

    One of these attributes must be passed through the web service.

Status

Status

The interface form has the following attributes for the Status field on the interface form.

  • Draft
  • In Cart
  • In Review
  • Submitted(Default)
  • Pending
  • Waiting Approval
  • Initiated
  • In Progress
  • Completed
  • Rejected
  • Cancelled
  • Closed

AppRequestSummary

AppRequestSummary

The Title of the SRD must be passed through the AppRequestSummary field of the web service. The Summary field on the service request stores this value.

The following table lists optional input field values. These fields are not required to create an entry.

Optional input field values

Web service field

Database field on interface form

Details

Details

Status_Reason

Status Reason

Middle_Name

Middle Name

Phone_Number

Phone Number

Internet_E-Mail

Internet E-Mail

Organization

Organization

Department

Department

z1D_WorkInfoDate

z1D_WorkInfoDate

z1D_WorkInfoCommunicationSource

z1D_WorkInfoCommunicationSource

z1D_WorkInfoSummary

z1D_WorkInfoSummary

z1D_WorkInfoDetails

z1D_WorkInfoDetails

The following table lists the fields set by workflow. Input fields (required and optional) trigger the workflow to generate the values in the fields. When you use web services, these fields are not exposed.

Fields set by workflow

Web service field

Database field on interface form

Field value

Notes

Short_Description

Short Description

"."

Source Keyword

Web Service

Submitter

$USER$

Submitter

login_ID

z1D_Action

z1D Action

CREATE

Summary

OfferingTitle

Filled in with "SRD Title"

Impact

Impact

3-Moderate/Limited

Urgency

Urgency

3-Medium

Status

Status

Draft

Requested For

Add Request For:

Individual

Login ID

$USER$

Categorization_Tier_1

Categorization Tier 1

Filled in from Navigation Categories - Category 1 field on SRD

Categorization_Tier_2Categorization Tier 2 Filled in from Navigation Categories - Category 2 field on SRD
Categorization_Tier_3Categorization Tier 3 Filled in from Navigation Categories - Category 3 field on SRD

Submitter

$USER$

Request Type

Standard

First_Name

First Name

Filled in from Login ID

Last_Name

Last Name

Filled in from Login ID

Location_Company

Location Company

Filled in from Company

z1D_WorkInfoType

z1D_WorkInfoType

General Information

z1D_WorkInfoSecureLog

z1D_WorkInfoSecureLog

Yes

z1D_WorkInfoViewAccess

z1D_WorkInfoViewAccess

Public

When a record is created successfully, the newly created record ID is returned.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Jan Sierens

    According the WSDL: Status, Short_Description, OfferingTitle, TitleInstanceID, Source_Keyword, Add_Request_For_, Urgency and Impact are mandatory. 

    The attribute Customer_Login which apparently is used for setting the Requested For is not mentioned.

    Apr 24, 2013 09:39
    1. Catherine Siderine

      Hi Jan,

      Thank you for your feedback on the documentation, and sorry for the delay in responding. We have created an internal tracking ID for this issue and will address it as soon as possible. If you want to contact Customer Support to log a formal ticket on this issue, click here

      Cathy

      May 01, 2013 11:57
  2. Jan Sierens

    Was OBO rules check for the submit service released in 8.1?

    Apr 24, 2013 10:30
    1. Catherine Siderine

      Hi Jan, 

      Yes, the OBO rules check was introduced in version 8.1.

      Regards,

      Cathy

      May 01, 2013 11:58