Problem

get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200

No response body

No content

get
/ux/sd/problem/conversation/
200

No response body

No content

post

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
post
/ux/sd/problem/conversation/
201

No response body

No content

get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200

No response body

No content

get
/ux/sd/problem/conversation/{id}/
200

No response body

No content

put

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200

No response body

No content

put
/ux/sd/problem/conversation/{id}/
200

No response body

No content

delete

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
delete
/ux/sd/problem/conversation/{id}/
204

No response body

No content

Gets a list of Problems

get

This endpoint is used to fetch all the Problems in the current organization

Authorizations
AuthorizationstringRequired
Query parameters
items_per_pageintegerRequired

Items Per Page

pageintegerRequired

Page Number

reversebooleanOptional

Sorting Order

sortstringOptional

Sorting Key

Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/
200Success

Creates a new problem

post

This endpoint is used to save a new problem for the current organization

Authorizations
AuthorizationstringRequired
Body
Other propertiesanyOptional
Responses
post
/ux/sd/problem/problem/
201

No response body

No content

Gets a problem with the given id

get

This endpoint is used to fetch a problem details in the current organization

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/{id}/
200Success

Edits the problem with given id

put

This endpoint is used to edit an existing problem for the current organization

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
put
/ux/sd/problem/problem/{id}/
200Success

Deletes the problem with given id

delete

This endpoint is used to delete an existing problem for the current organization

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
delete
/ux/sd/problem/problem/{id}/
204

No response body

No content

Add attachments for the selected problem.

post

This endpoint is used to add new attachments.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
post
/ux/sd/problem/problem/add-attachment/
200Success

Gets attachments for the selected problem.

get

This endpoint is used to fetch the attachments.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/attachment/
200Success
post

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
post
/ux/sd/problem/problem/delete-problem-task/{id}/
200Success
post

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
post
/ux/sd/problem/problem/delete_problem/
200Success

Gets history for the selected problem.

get

This endpoint is used to fetch the history.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/history/
200Success
get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/options/
200Success
get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/problem-data/{id}/
200Success
get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/problem-task-list/{id}/
200Success
get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/problem-task/{id}/
200Success

Get rich text data

get

This endpoint is used to get the rich text data.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/process-rich-text/
200Success
post

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
post
/ux/sd/problem/problem/relation/
200Success

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/requester_search/
200Success
get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/root_cause_draft/{id}/
200Success
post

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
post
/ux/sd/problem/problem/save-problem-task/
200Success

Save rich text data

post

This endpoint is used to save the rich text data.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
post
/ux/sd/problem/problem/save-rich-text/
200Success
post

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
post
/ux/sd/problem/problem/save_problem_cause/
200Success
get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/top_filter/
200Success
post

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

problem_idstring · max: 25Required
display_idstring · max: 50Optional
is_merge_problembooleanOptional
is_archivebooleanOptional
unread_mailbooleanOptional
creation_timestring · date-timeOptional
created_by_idstring · max: 225Optional
last_update_timestring · date-timeOptional
updated_by_idstring · max: 225Optional
due_datestring · date | nullableOptional
Responses
chevron-right
200Success
application/json
post
/ux/sd/problem/problem/workflow_options_map/
200Success
get

API endpoint that allows Problem to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/sd/problem/problem/workflow_status/
200Success

Last updated