This documentation supports the 20.08 version of Remedy Action Request System, which is available only to BMC Helix subscribers (SaaS).
To view an earlier version, select the version from the Product version menu.


Example of using the REST API to retrieve an association

Association is an object that defines relationships in Remedy AR System metadata objects. The associations enable you to manage relationships between forms for various Remedy AR System functions.

GET associations for single entry

You can use the GET operation to get associations for a particular entry on a form. The following table lists details about this GET operation.

URL qualifier

/entry/{formName/{entryId}/assoc/{AssociationName}

formName - The form for which an entry is to be read. 
entryId - The entry ID.

MethodGET
Header
HeaderValue
Authorizationtoken
(Optional) X-AR-Client-Type Client Type ID
(Optional) X-AR-RPC-QueueRPC queue to which the client calls are routed
(Optional) X-AR-Timeout

Timeout (in seconds) for REST request

Default value —120 seconds

(Optional) X-AR-TR-Core-IdThe core ID in a trace ID
(Optional) X-AR-TR-CounterThe counter in a trace ID
(Optional) X-AR-Trace-IdThe complete trace ID
(Optional) X-AR-TR-Is-Counter-LockedThe lock counter
ReturnsReturns links for all associated entries.
All possible error codes

If the request is not successful, one of the following error codes are returned:

  • 400 - Request body is incorrect
  • 403 - Forbidden
  • 404 - Form does not exist
  • 500 - Internal Server Error

For more information, see HTTP status codes.

Example 1

The following example returns all associations on a form as links that show the related entries.

Request URL

/entry/PurchaseOrder/000000000000001?fields=assoc

Response Body

// entry plus links to search for related entries
{
    "values" : {
        ...
    },
    "_links" : {
        "assoc-PurchaseOrderLineItems" : {
            "href" : "/entry/PurchaseOrder/000000000000001/assoc/PurchaseOrderLineItems"
        }
    }
}

Example 2

The following example returns a list of entries for a specific association.

Request URL

/entry/PurchaseOrder/000000000000001?fields=assoc(PurchaseOrderLineItems)

Response Body

// entry plus links to related entries
{
    "values" : {
        ...
    },
    "_links" : {
        "assoc-PurchaseOrderLineItems" : [{
            "href" : "/entry/LineItem/000000000000006"
        }, {
            "href" : "/entry/LineItem/000000000000008"
        }]
    }
}

Example 3

The following example expands the entries returned for an association.

Request URL

/entry/PurchaseOrder/000000000000001?expand=assoc(PurchaseOrderLineItems)

Response Body

// entry plus embedded related entries
{
    "values" : {
        ...
    },
    "_embedded" : {
        "assoc-PurchaseOrderLineItems" : [{
            "values" : {...},
            "_links" : { "self" : { "href" : "/entry/LineItem/000000000000006" } }
        }, {
            "values" : {...},
            "_links" : { "self" : { "href" : "/entry/LineItem/000000000000008" } }
        }]
    }
}

GET associations for multiple entries

You can use the GET operation to get associations for multiple entries on a form. The following table lists details about this GET operation.

URL qualifier

/entry/{formName}?fields=assoc(AssociationName)

formName - The form for which an entry is to be read.

MethodGET
Header
HeaderValue
Authorizationtoken
(Optional) X-AR-Client-Type Client Type ID
(Optional) X-AR-RPC-QueueRPC queue to which the client calls are routed
(Optional) X-AR-Timeout

Timeout (in seconds) for REST request

Default value —120 seconds

(Optional) X-AR-TR-Core-IdThe core ID in a trace ID
(Optional) X-AR-TR-CounterThe counter in a trace ID
(Optional) X-AR-Trace-IdThe complete trace ID
(Optional) X-AR-TR-Is-Counter-LockedThe lock counter
Parameters

Name

Description

fieldsSelects what parts of the JSON document to return (for example, ?fields=entryId1,entryId2)
qSearch qualification
offsetOffset for the entries to return
limitNumber of entries to limit the result to
sortOrder to sort the results in (for example, ?sort=submitDate.desc)
expandExpands the related entries (associations).

For more information, see Common parameters.

ReturnsReturns all associations for all the entries on a form.
Errors

If the request is not successful, the following error code is returned:

400 - Request body is incorrect.

For more information, see HTTP status codes.

Related topic

Learning about the REST API

Was this page helpful? Yes No Submitting... Thank you

Comments