Table of Contents | ||||
---|---|---|---|---|
|
...
All GET requests for retrieving data will be done via the SQL endpoint. Please see the SQL for more information on how to create a request. Please see the Data Dictionary for comprehensive detail of available Tables and Data.
In an effort to make the PCR-360 API more flexible, PCR has made the decision to no longer create individual endpoints for all the different data types. Instead, PCR is encouraging Users to use the SQL endpoint with a structured SELECT statement to retrieve exactly the data you want. Please see the SQL endpoint documentation for more information.
...
Field | Required for INSERT | Required for UPDATE | Required for Action Type | Data Type | Options | Notes | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
type | Yes | Yes | String | ACTION | Required for ALL Service Desk Action Requests | |||||||||||||
RECID / sda_number | No | Yes* | Integer | *Either “RECID” or “sda_number” are "Conditionally Required" when attempting to UPDATE, but not both. RECID column from SERVICE_DESK_ACTIONS table. | ||||||||||||||
sd_recid / sd_number | Yes* | No | Integer / String | *Either “sd_recid” or “sd_number” are "Conditionally Required" when attempting to INSERT, but not both. RECID column from SERVICE_DESK table. | ||||||||||||||
sd_action | Yes | No | String | ADD, CHG_MOVE, CHG_UPDOWN, CHG_MISC, REMOVE, CHG_SERVICE_ID, CHG_MULTI_LOCATION, CHG_OWNER, TASK | The type of Service Desk Action to be created | |||||||||||||
location | No* | No* | CHG_MULTI_LOCATION | Integer | RECID of Location. | |||||||||||||
moveto_location | No | No | Integer | RECID of Location *Not allowed, and will throw an Error if used on a TASK Action | ||||||||||||||
catalog | Yes | No | ADD, CHG_UPDOWN, TASK | Integer | RECID of Service Catalog | |||||||||||||
service / service_id | Yes* | No | CHG_UPDOWN, CHG_MOVE, CHG_MISC, REMOVE, CHG_SERVICE_ID, CHG_MULTI_LOCATION, CHG_OWNER | Integer | *Either RECID of Service or SERVICE_ID of Service needs to be provided | |||||||||||||
rating_group | No* | No | String | The LIST CODE for the Rating Group for the Phone Service being used by the Service Desk Action. Conditionally Required creating Service Desk Actions when using a Serice Catalog of type "Phone". | ||||||||||||||
sla | No | No | Integer | RECID of SLA | ||||||||||||||
due_date | No | No | String | Format “YYYY/MM/DD” | ||||||||||||||
service_host / service_host_name | No* | No* | Integer / String | RECID of Service Host / Name of Service Host / Either RECID or Name should be provided / Conditionally Required when adding an Action to a Phone Service Catalog. | ||||||||||||||
reference | No | No | String | |||||||||||||||
owner_contact | No | No | Integer | RECID of Contact. Only a Contact or Department can be Owner, not both. | ||||||||||||||
owner_department | No | No | Integer | RECID of Department. Only a Contact or Department can be Owner, not both. | ||||||||||||||
urgency | No | No | Integer / String | Can be RECID or VALUE | ||||||||||||||
start_date | No | No | String | Format: “YYYY/MM/DD” | ||||||||||||||
gla | No | No | Integer | Multiple are sent comma delimited. Example: gla1,gla2,gla3 | ||||||||||||||
gla_type | Only if gla is sent | Only if gla is sent | String | Options: Default, Usage, Equipment and Labor | Multiple are sent comma delimited. Example: type1,type2,type3. | |||||||||||||
gla_percent | Only if gla is sent | Only if gla is sent | Integer | The total of all percentages for a single type must be 100 | Mutliple are sent comma delimited. Example: percent1,percent2,percent3. | |||||||||||||
sdc_recid | No | No | Integer | Passing an SDC will allow an Action to be created with default Workflows, Equipment and Charges. RECID column from SERVICE_DESK_ACTIONS SDC table. | ||||||||||||||
new_service | No | No | CHG_SERVICE_ID | Integer | The new Service ID for the Service being changed. One of the following must be true for the new Service ID:
| |||||||||||||
auth_code_type | Yes* | No | ADD | Integer | Lists
| RECID of Auth Code Type for an authcode service. *Required when attempting to INSERT an authcode Service. | ||||||||||||
classes_of_service | Yes* | No | ADD | Integer | Example | RECID of Class of Service for an authcode service. *Required when attempting to INSERT a new auth_code_type record. | ||||||||||||
bandwidth | No | No | Integer | Lists
| RECID of Bandwidth for a data/backbone service. | |||||||||||||
owner_type | No | No | CHG_OWNER | String | 'contact', 'department' | The type of the Owner, either a Contact or a Department. | ||||||||||||
owner | No | No | CHG_OWNER | Integer | RECID of the Owner. Must be Active. | |||||||||||||
udf_IDENTIFIER | No | No | Mixed | IDENTIFIER is the unique identifier string given to each UDF |
...
For full documentation on SDCs, see the Service Desk Classification wiki page.
...
Ordering from Service Pools
To request a Service from a pool:
Excerpt | ||
---|---|---|
| ||
Services can be used from Service Pools from the Order screen at Main > Service Desk > Orders. When requesting a new Service a User will specify a Service Catalog Type on the Service Order Action and then must select from a list of Available services. The list is drawn from all these criteria:
|
- The requested Service must have Status “Available“
- The requested Service must be in the requested catalog or an ancestor
- The requested Service must be in a pool only if the requested catalog is specified on that pool
- If the requested catalog is not listed on any pools then any Available Service not specified on a pool that also matches the catalog can be requested
Headers:
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
...
Cloak | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CHG_MOVE Action Example
Toggle cloak |
---|
Cloak | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CHG_UPDOWN Action Example
Toggle cloak |
---|
Cloak | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CHG_MISC Action Example
Toggle cloak |
---|
Cloak | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
REMOVE Action Example
Toggle cloak |
---|
Cloak | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CHG_SERVICE_ID Action Example
Toggle cloak |
---|
Cloak | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CHG_MULTI_LOCATION Action Example
Toggle cloak |
---|
Cloak | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CHG_OWNER Action Example
Toggle cloak |
---|
Cloak | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
TASK Action Example
Toggle cloak |
---|
Cloak | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Results
Toggle cloak |
---|
Cloak | |||||
---|---|---|---|---|---|
If the request is successful, the RECID of the Action will be returned as follows:
|
Adding Attachments to Service Desk Actions
...
Field | Required | Data Type | Options | Default | Notes |
---|---|---|---|---|---|
type | Yes | String | UDFS | type=UDFS is required | |
sd_recid | Yes* | Integer | *Conditionally Required, see NOTE below. RECID column from SERVICE_DESK table. | ||
sda_recid | Yes* | Integer | *Conditionally Required, see NOTE below. RECID column from SERVICE_DESK_ACTIONS table. | ||
sd_number | Yes* | String | The Number of the Service Desk item that the UDF is for. *Conditionally Required, see NOTE below | ||
sda_number | Yes* | Integer | The Number of the Action that the UDF is for. *Conditionally Required, see NOTE below | ||
udf_IDENTIFIER | Yes | Mixed | IDENTIFIER is the unique Identifier of the UDF to assign the value to. Example: udf_LEGACYNUM=value | ||
udf_UDF-RECID | Yes* | Integer | UDF-RECID is the RECID of the UDF to assign the value to. Example: udf_684=value. RECID column from USER_DEFINED_FIELDS_VALS table.
| ||
udf_UDF-IDENTIFIER | Yes* | Mixed | IDENTIFIER is the unique Identifier of the UDF to assign the value to. Example: udf_LEGACYNUM=value
|
NOTES
- "udf_UDF-RECID" and "udf_UDF-IDENTIFIER" are "udf_UDF-IDENTIFIER" are Conditionally Required. The use of one is Required, but not both.
- "sd_recid" or "sd_number" are Conditionally Required. The use of one is Required, but not both.
"sda_number" or "sda_recid" are Conditionally Required. The use of one is Required, but not both
..
"sd_recid", "sd_number" and "sda_number" can be omitted if "sda_recid" is provided
Correct Examples
"sd_recid=123&sda_number=001"
"sd_number=SO12345&sda_number=002"
"sda_recid=345"
Incorrect Examples:
"sd_recid
" or "sd_number" are Conditionally Required. The use of one is Required, but not both.=123"
"sda_number" or "sda_recid" are Conditionally Required. The use of one is Required, but not both.
"sd_recid", "sd_number" and "sda_number" can be omitted if "sda_recid" is provided
Correct Examples
"sd_recid=123&sda_number=001"
"sd_number=SO12345&sda_number=002"
"sda_recid=345"
Incorrect Examples:
"sd_recid=123"
"sda_number=001"
...
If the request is successful, the RECID(s) of the new Service Desk Action UDF records will be returned in the same order as provided:
...
language | xml |
---|
...
=001"
Results
Toggle cloak |
---|
Cloak | |||||
---|---|---|---|---|---|
If the request is successful, the RECID(s) of the new Service Desk Action UDF records will be returned in the same order as provided:
|
Service Desk Action GLAs
GLAs can be easily set for a Service Desk Action.
...
Either "sd_recid" or "sd_number" need to be provided, but not both
Either "sda_number" or "sda_recid" is required, but not both
"sd_recid", "sd_number" and "sda_number" can be omitted if "sda_recid" is provided
Correct Examples
"sd_recid=123&sda_number=001"
"sd_number=SO12345&sda_number=002" or
"sda_recid" is required, but not both=345"
Incorrect Examples:
"sd_recid=123"
"sda_number=001", "sd_number" and "sda_number" can be omitted if "sda_recid" is provided
Correct Examples
"sd_recid=123&sda_number=001"
"sd_number=SO12345&sda_number=002"
"sda_recid=345"
Incorrect Examples:
"sd_recid=123"
"sda_number=001"
...
If the request is successful, the RECID(s) of the new Service Desk Action GLA records will be returned in the same order as provided:
...
language | xml |
---|
...
Results
Toggle cloak |
---|
Cloak | |||||
---|---|---|---|---|---|
If the request is successful, the RECID(s) of the new Service Desk Action GLA records will be returned in the same order as provided:
|
Locating Service Desk Action Data
Please see the wiki entry for Service Desk Actions for detailed information about where this data can be found.
...