The following table describes the parameter in the request:
Parameter
Type
Description
key
String
Internal ID or alias of the hierarchy.
GET response
The response contains the relationships and the code lists in each relationship. The child.codeListDetails attribute contains the top-level node relationship.
The following table describes the attributes in the response body:
Field
Type
Definition
relations
Array
Lists the code list in the relationship.
child
Object
Contains information about the child in the hierarchy model.
codeListDetails
Object
Includes details for the child code list.
id
String
ID of the child code list.
internalId
String
Unique identifier of the child code list.
alias
String
Alternative identifier of the child code list.
name
String
Name of the child code list.
rdsDetails
Object
Includes details for the child reference data set.
id
String
ID of the child reference data set. For more information, see Asset IDs.
internalID
String
Unique identifier of the child reference data set.
alias
String
Alternative identifier of the child reference data set.
name
String
Name of the child reference data set.
parent
Object
Contains information about the parent in the hierarchy model.
codeListDetails
Object
Includes details for the parent code list.
id
String
ID of the parent code list.
internalId
String
Unique identifier of the parent code list.
alias
String
Alternative identifier of the parent code list.
name
String
Name of the parent code list.
rdsDetails
Object
Includes details for the parent reference data set.
id
String
ID of the parent reference data set. For more information, see Asset IDs.
internalID
String
Unique identifier of the parent reference data set.
alias
String
Alternative identifier of the parent reference data set.
name
String
Name of the parent reference data set.
GET example
To retrieve the relationships in a hierarchy model based on the internal ID or alias, you might use the following request:
GET https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v2/hierarchies/parent_codelist/relations HTTP/1.1 Accept: application/json IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
The child.codeListDetails attribute contains the top-level node relationship. For example, the first relationship in the example is the top-level node relationship.
Get history of a hierarchy by time range (v2)
Retrieves all the change events of a hierarchy for a specific time range based on an internal ID or alias.
GET request
To retrieve all the change events of a hierarchy for a specific time range based on an internal ID or alias, submit a GET request with the following URI:
The following table describes the parameter in the request body:
Parameter
Description
assetKey
Internal ID or alias of the hierarchy.
from
Start date and time of the time range, which is inclusive. Time range must be in the following ISO-8601 format: yyyy-MM-dd'T'HH:mm:ss'Z'. For example, you might use 2019-12-12T14:04:04Z.
to
End date and time of the time range, which is exclusive. Time range must be in the following ISO-8601 format: yyyy-MM-dd’T’HH:mm:ss’Z'. For example, you might use 2019-12-15T14:04:04Z.
page
Optional. Page number to display. Default is 0.
pageSize
Optional. Number of records to display per page. Default value is 100. Maximum value is 10000.
modificationType
Optional. Type of modification. Value can be CREATE, UPDATE, or DELETE.
GET response
The response contains the change events of a hierarchy for a specific time range.
The following table describes the attributes in the response body:
Attribute
Type
Description
pageSize
Number
Number of records displayed per page.
page
Number
Page from which the response was retrieved.
numberOfElements
Number
Number of records returned in the current page.
lastPage
Boolean
Indicates whether the current page is the last page in the total result.
firstPage
Boolean
Indicates whether the current page is the first page in the total result.
content
Array
Includes the list of modification events.
asset
Object
Includes details about the asset.
id
String
ID of the hierarchy. For more information, see Asset IDs.
name
String
Name of the hierarchy.
internalId
String
Unique identifier of the hierarchy.
alias
String
Alternative identifier of the hierarchy.
assetType
String
Type of the asset. The value is hierarchy.
modificationType
String
Type of change made to the hierarchy. Value can be CREATE, UPDATE, or DELETE.
fieldChanges
Object
Includes details of the previous and new values of the fields with changes.
confidentiality
String
Optional. Confidentiality of the hierarchy.
description
String
Optional. Description of the hierarchy.
domain
String
Optional. Domain of the hierarchy.
priority
String
Optional. Priority of the hierarchy.
status
String
Optional. Status of the hierarchy.
version
String
Optional. Version of the hierarchy.
eventTime
String
Date and time when the hierarchy was last updated.
userName
String
User name of the user who initiated the modification.
GET example
To retrieve all the change events of a hierarchy for a specific time range based on the internal ID or alias, you might use the following request:
GET https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v2/hierarchies/country_iso/summary/audit?from=2023-01-01T00:00:00Z&to=2024-01-01T00:00:00Z HTTP/1.1 Accept: application/json IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
The following sample response shows the change events of the hierarchy from 2023-01-01T00:00:00Z to 2024-01-01T00:00:00Z:
HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Content-Length: 2552
Get history of hierarchy relationships by time range (v2)
Retrieves all the change events of hierarchy relationships for a specific time range based on an internal ID or alias.
GET request
To retrieve all the change events of hierarchy relationships for a specific time range based on an internal ID or alias, submit a GET request with the following URI:
You can append query parameters to the URI to specify the time range, page number, page size, and modification type.
The following table describes the query parameters:
Parameter
Description
assetKey
Internal ID or alias of the hierarchy.
from
Start date and time of the time range, which is inclusive. Time range must be in the following ISO-8601 format: yyyy-MM-dd'T'HH:mm:ss'Z'. For example, you might use 2019-12-12T14:04:04Z.
to
End date and time of the time range, which is exclusive. Time range must be in the following ISO-8601 format: yyyy-MM-dd’T’HH:mm:ss’Z'. For example, you might use 2019-12-15T14:04:04Z.
page
Optional. Page number to display. Default is 0.
pageSize
Optional. Number of records to display per page. Default value is 100. Maximum value is 10000.
modificationType
Optional. Type of modification. Value can be CREATE, UPDATE, or DELETE.
GET response
The response contains the change events of hierarchy relationships for a specific time range.
The following table describes the attributes in the response body:
Attribute
Type
Description
pageSize
Number
Number of records displayed per page.
page
Number
Page from which the response was retrieved.
numberOfElements
Number
Number of records returned in the current page.
lastPage
Boolean
Indicates whether the current page is the last page in the total result.
content
Array
Includes the list of modification events.
asset
Object
Includes details about the hierarchy.
id
String
ID of the hierarchy. For more information, see Asset IDs.
internalId
String
Unique identifier of the hierarchy.
alias
String
Alternative identifier of the hierarchy.
assetType
String
Type of the asset. The value is hierarchy.
modificationType
String
Type of change made to the hierarchy. Value can be CREATE, UPDATE, or DELETE.
from
Object
Includes details of the previous and new values of the child node in the relationship.
to
Object
Displays the previous and new values of the parent node in the relationship.
eventTime
String
Date and time when the hierarchy was last updated.
userName
String
User name of the user who initiated the modification.
GET example
To retrieve all the change events of a hierarchy for a specific time range based on the internal ID or alias, you might use the following request:
GET https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v2/hierarchies/hr_hierarchy/mappings/audit?from=2023-01-01T00:00:00Z&to=2024-01-01T00:00:00Z HTTP/1.1 Accept: application/json IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
The following sample response shows the change events of the hierarchy from 2023-01-01T00:00:00Z to 2024-01-01T00:00:00Z:
HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Content-Length: 1929