Infraon API Guide
Product DocsSchemaAuthentication
  • Welcome
    • Base URL
    • Authorization
    • Responses
  • Modules
    • Schema
    • Authentication
    • Announcement
    • API Registration
    • Async Tasks
    • BusinessRule
    • BusinessServiceConfiguration
    • Service Catalogue
    • CMDBBlacklistWhitelist
    • CMDBCategory
    • CMDBConsumables
    • Ux
    • CMDBSoftwareLicense
    • Cmdb
    • CMDBRelation
    • CMDBSoftware
    • ContractManagement
    • Department
    • Events
    • Field Configuration
    • IMACD
    • Knowledge Base
    • Leaves
    • Chat
    • Marketplace
    • APIViewSet
    • BeepViewSet
    • SMSviewset
    • Suppressedviewset
    • Organization Location
    • Partner
    • Predicted Events
    • Requester
    • Service Feasibility Requests
    • Role Profile
    • Tag
    • Service_outage
    • Teams
    • Telecom Settings
    • Trap Configurations
    • User Profile
    • Vendor Managemment
    • Association Events
    • Device Template
    • Discovery Configuration
    • Jobs
    • MIB Explorer
    • Seasonal Events
    • IPAM
    • Log Grok Pattern Configuration
    • Log Pipeline Configuration
    • Log Integraion
    • Log Search
    • CLI Download Jobs
    • Configuration Profiles
    • Configuration Policies
    • Configuration Rules
    • Configuration Search
    • Configuration Template
    • Configuration Trigger
    • Jobs Account Audit
    • Manage Vulnerabilities
    • OS Image Download
    • Rule Group
    • Configuration Upload Jobs
    • Work Flow Jobs
    • Change
    • Checklist
    • Incident
    • Problem
    • Release
    • Request Process
    • Task
    • Models
Powered by GitBook
On this page
  1. Modules

Field Configuration

PreviousEventsNextIMACD

Gets a field_config with the given id

get

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

Authorizations
Path parameters
idstringRequired
Responses
200Success
application/json
get
GET /ux/common/fieldconfig/field-config/{id}/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Accept: */*
200Success
{
  "workflow_name": "text",
  "workflow_id": "text",
  "module": "text",
  "role_name": "text",
  "status": "text",
  "field_config_id": "text"
}

Deletes the field_config with given id

delete

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

Authorizations
Path parameters
idstringRequired
Responses
204
No response body
delete
DELETE /ux/common/fieldconfig/field-config/{id}/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Accept: */*
204

No response body

No content

Get the options for the Field configuration

get

This endpoint is used to get the default options for field_config

Authorizations
Responses
200Success
application/json
get
GET /ux/common/fieldconfig/field-config/options/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Accept: */*
200Success
{
  "workflow_name": "text",
  "workflow_id": "text",
  "module": "text",
  "role_name": "text",
  "status": "text",
  "field_config_id": "text"
}
  • GETGets a list of field configs
  • POSTCreates a new field_config
  • GETGets a field_config with the given id
  • PUTEdits the field_config with given id
  • DELETEDeletes the field_config with given id
  • POSTGet the configured field for the workflow
  • GETGet the options for the Field configuration

Gets a list of field configs

get

This endpoint is used to fetch all the field configs from the current organization

Authorizations
Query parameters
items_per_pageintegerRequired

Items Per Page

pageintegerRequired

Page Number

reversebooleanOptional

Sorting Order

sortstringOptional

Sorting Key

Responses
200Success
application/json
get
GET /ux/common/fieldconfig/field-config/?items_per_page=1&page=1 HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Accept: */*
200Success
[
  {
    "workflow_name": "text",
    "workflow_id": "text",
    "module": "text",
    "role_name": "text",
    "status": "text",
    "field_config_id": "text"
  }
]

Creates a new field_config

post

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

Authorizations
Body
Other propertiesanyOptional
Responses
201
No response body
post
POST /ux/common/fieldconfig/field-config/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 32

{
  "field_config": "field_config1"
}
201

No response body

No content

Edits the field_config with given id

put

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

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

workflow_namestringOptional
workflow_idstringOptional
modulestringRead-onlyRequired
role_namestringRead-onlyRequired
statusstringRead-onlyRequired
field_config_idstringOptional
Responses
200Success
application/json
put
PUT /ux/common/fieldconfig/field-config/{id}/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 70

{
  "workflow_name": "text",
  "workflow_id": "text",
  "field_config_id": "text"
}
200Success
{
  "workflow_name": "text",
  "workflow_id": "text",
  "module": "text",
  "role_name": "text",
  "status": "text",
  "field_config_id": "text"
}

Get the configured field for the workflow

post

This endpoint is used to get the configureed fields for the status

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

workflow_namestringOptional
workflow_idstringOptional
modulestringRead-onlyRequired
role_namestringRead-onlyRequired
statusstringRead-onlyRequired
field_config_idstringOptional
Responses
200Success
application/json
post
POST /ux/common/fieldconfig/field-config/field_permission/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 70

{
  "workflow_name": "text",
  "workflow_id": "text",
  "field_config_id": "text"
}
200Success
{
  "workflow_name": "text",
  "workflow_id": "text",
  "module": "text",
  "role_name": "text",
  "status": "text",
  "field_config_id": "text"
}