Update User Preference
This API is used for updating the existing user-preference configuration. Update API expects all parameters retrived via get API. Fields "id", "is_predefined" and "created_by" are read-only and can't be updated. Any missing non mandatory field in udpate request, will be set to default values.
Unique id, to indentify the user-preference
Show optional properties
{
"name": "Default notification console",
"type": "NOTIFICATION_CONSOLE",
"sequence_number": 349,
"primary_term": 1
}{
"id": "1jldkjdfjrr",
"name": "Default notification console",
"type": "NOTIFICATION_CONSOLE",
"assign_to": [
"Operator"
],
"is_default": true,
"parent_id": "string",
"data": {},
"sequence_number": 349,
"primary_term": 1,
"create_timestamp": 1660635421552
}unique id for the user preference.
Display name for the user preference.
The type user-preference. There are 4 types supported.
- "NOTIFICATION_CONSOLE"
- "NOTIFICATION_SUMMARY_CONSOLE"
- "TOPOLOGY_CONSOLE"
- "COLORS_PREF"
The console is assigned to which ROLE. For logged in user , this field value will be populated automatically, but if Admin user wants to assign, the console to any ROLE then it needs to be sent in the request payload. Non admin user won't be able to assign any ROLE.
This defines wheather the "user-preference" is default.
Parent id of the console. In case of the root, value would be null.
This will contain all UI specific user-preference details. This is free object and can contain any thing UI wants to store.
The seq_no and primary_term together, helps to achieve optimized concurrency control. This two field value, must be sent along with update request, if user want to avoid accidental concurrent changes.
The seq_no and primary_term together, helps to achieve optimized concurrency control. This two field value, must be sent along with update request, if user want to avoid accidental concurrent changes.
Timestamp in epoch milliseconds, notifies the value when user preference is created
Created
"UserPreference Object"The id, uniquely identified the user-preference.
The seq_no and primary_term together, helps to achieve optimized concurrency control. This two field value, must be sent along with update request, if user want to avoid accidental concurrent changes.
The seq_no and primary_term together, helps to achieve optimized concurrency control. This two field value, must be sent along with update request, if user want to avoid accidental concurrent changes.
The type user-preference. The below types are supported.
- "NOTIFICATION_CONSOLE"
- "NOTIFICATION_SUMMARY_CONSOLE"
- "TOPOLOGY_CONSOLE"
- "COLORS_PREF"
- "LOG_VIEWS"
- "BAR_CHARTS"
The console is assigned to which ROLE. For logged in user , this field value will be populated automatically, but if Admin user wants to assign the console to any ROLE then it needs to be sent in the request payload. Non admin user won't be able assign any ROLE.
Display name for the console.
This is notification console preference, created for admin.
system created user preferences.
used to show default user prefereces for user
Parent id of the console. In case of the root, value would be null.
This will contain all UI specific user-preference details. This is free object and can contain any thing UI wants to store.
The user responsible for creation of object.
Timestamp in epoch milliseconds, notifies the value when user preference is created
Timestamp in epoch milliseconds, notifies the value when user preference is updated
Response Headers
Provide information about the location of a cloned resource.
Unauthorized
Resource not found
Conflicting
Internal server error
curl -X PUT -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{"type:"string","name:"string","sequence_number:"integer","primary_term:"integer"}' https://{api_host}/tcsa/api/configuration-management/v1/user-preferences/{id}