Idea ID: 2804918

User Options JSON structure for REST

Status : Waiting for Votes
over 1 year ago

Hi,

In our customer environment, we are transfering created Request in SMAX to the Service Manager for resolving (the project for replacing SM is in the first phase).

We have found out that that selected values of User Options are in the request details in the additional JSON format, which is very hard to transfer into SM for resolver's easy usage. for User options ENTITY_LINK attribute type are visible only ID's of records and for ENUM attribute type only technical name of the list value:

{
"entities": [
{
"entity_type": "Request",
"properties": {
"UserOptions": "{\"complexTypeProperties\":[{\"properties\":{\"DynamicComplexTypeRefName_c\":\"UserOption558fe9213ba016345da1d69d43027f79dcc4_c\",\"LaptopModel_c\":\"11132\",\"OSType_c\":\"Mainframe\",\"OrderLaptop_c\":true}}]}",
"Description": "<p>dfsgy</p>",
"LastUpdateTime": 1591982216001,
"Id": "87561"
}

Would be great, if Admin can get additional information for User Options, especially ENTITY_LINK type (Display Label, SubType, etc) and to get User Options in the JSON format of Request as details of linked attributes (e.g. Requested for Person):

{
"entities": [
{
"entity_type": "Request",
"properties": {
"Description": "<p>dfsgy</p>",
"LastUpdateTime": 1591982216001,
"Id": "87561"
},
"related_properties": {
"RequestedForPerson": {
"Email": "**PERSONAL INFORMATION REMOVED**",
"FirstName": "User",
"Id": "16345",
"LastName": "User"
}
}
}

Tags: