str(id)).

\n

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

\n

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

\n

Not well supported or untested:

\n

``FileField``\n``ImageField``\n``BinaryField``\n

\n

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

"}b3:Tf9e,{"type":"object","description":"Serializer for Documents.\n\nRecognized primitve fields:\n\n * ``StringField``\n * ``URLField``\n * ``EmailField``\n * ``IntField``\n * ``LongField``\n * ``FloatField``\n * ``DecimalField``\n * ``BooleanField``\n * ``DateTimeField``\n * ``ComplexDateTimeField``\n * ``ObjectIdField``\n * ``SequenceField`` (assumes it has integer counter)\n * ``UUIDField``\n * ``GeoPointField``\n * ``GeoJsonBaseField`` (all those fields)\n * ``DateField``\n\nCompound fields: ``ListField`` and ``DictField`` are mapped to corresponding DRF fields, with respect to nested field specification.\n\nThe ``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)``).\n\nFor ``EmbeddedDocumentField`` also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.\n\nGeneric fields ``GenericReferenceField`` and ``GenericEmbeddedDocumentField`` are handled by their own with corresponding serializer fields.\n\nNot well supported or untested:\n\n ``FileField``\n ``ImageField``\n ``BinaryField``\n\nAll other fields are mapped to ``DocumentField`` and probably will work wrong.","properties":{"id":{"type":"string","readOnly":true},"creationtime":{"type":"string","readOnly":true},"agent_id":{"type":"string","readOnly":true},"connection_status":{"type":"string","readOnly":true},"failure_message":{"type":"string","readOnly":true},"organization":{"type":"string","maxLength":25},"job_id":{"type":"string"},"ci_id":{"type":"string"},"job_iteration_id":{"type":"string"},"ipaddress":{"type":"string","maxLength":225},"device_account":{"type":"string","maxLength":225},"dpassword":{"type":"string","maxLength":225},"denable_password":{"type":"string","maxLength":225},"connection_protocol":{"type":"string","maxLength":25},"error":{"type":"string","maxLength":2000},"task_owner":{"type":"string","maxLength":225},"client_ip":{"type":"string","maxLength":225},"job_type":{"type":"string","maxLength":225},"job_name":{"type":"string","maxLength":225},"process_name":{"type":"string","maxLength":225},"connection_for":{"type":"string","maxLength":225},"last_update_time":{"type":"string","format":"date-time"},"config_type":{"type":"string","maxLength":225},"uofw":{"type":"string","maxLength":225}},"required":["agent_id","connection_status","creationtime","failure_message","id","organization"],"x-gitbook-description-html":"

Serializer for Documents.

\n

Recognized primitve fields:

\n

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

\n

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

\n

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)).

\n

For EmbeddedDocumentField also nested seriali