BusinessRule

Gets a list of business_rule

get

This endpoint is used to fetch all the business_rule 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/common/business_rule/business_rule/
200Success

Creates a new business_rule

post

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

Authorizations
AuthorizationstringRequired
Body
Other propertiesanyOptional
Responses
post
/ux/common/business_rule/business_rule/
201

No response body

No content

Gets a business_rule with the given id

get

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

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

Edits the business_rule with given id

put

This endpoint is used to edit an existing business_rule 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.

idstringRead-onlyRequired
module_namestringRead-onlyRequired
rule_idstringOptional
namestring · max: 255Optional
is_enablebooleanOptionalDefault: true
is_overridebooleanOptional
module_idintegerOptional
depthintegerOptionalDefault: 1
descriptionstring | nullableOptional
is_deletedbooleanOptional
is_pre_configuredbooleanOptional
Responses
chevron-right
200Success
application/json
put
/ux/common/business_rule/business_rule/{id}/
200Success

Deletes the business_rule with given id

delete

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

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
delete
/ux/common/business_rule/business_rule/{id}/
204

No response body

No content

post

API endpoint that allows users 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.

idstringRead-onlyRequired
module_namestringRead-onlyRequired
rule_idstringOptional
namestring · max: 255Optional
is_enablebooleanOptionalDefault: true
is_overridebooleanOptional
module_idintegerOptional
depthintegerOptionalDefault: 1
descriptionstring | nullableOptional
is_deletedbooleanOptional
is_pre_configuredbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/common/business_rule/business_rule/create-csv/
200Success
post

API endpoint that allows users 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.

idstringRead-onlyRequired
module_namestringRead-onlyRequired
rule_idstringOptional
namestring · max: 255Optional
is_enablebooleanOptionalDefault: true
is_overridebooleanOptional
module_idintegerOptional
depthintegerOptionalDefault: 1
descriptionstring | nullableOptional
is_deletedbooleanOptional
is_pre_configuredbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/common/business_rule/business_rule/csv_cols/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/business_rule/business_rule/download_rule_csv/
200Success
post

API endpoint that allows users 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.

idstringRead-onlyRequired
module_namestringRead-onlyRequired
rule_idstringOptional
namestring · max: 255Optional
is_enablebooleanOptionalDefault: true
is_overridebooleanOptional
module_idintegerOptional
depthintegerOptionalDefault: 1
descriptionstring | nullableOptional
is_deletedbooleanOptional
is_pre_configuredbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/common/business_rule/business_rule/multidelete/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/business_rule/business_rule/options/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/business_rule/business_rule/rule_count/
200Success
post

API endpoint that allows users 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.

idstringRead-onlyRequired
module_namestringRead-onlyRequired
rule_idstringOptional
namestring · max: 255Optional
is_enablebooleanOptionalDefault: true
is_overridebooleanOptional
module_idintegerOptional
depthintegerOptionalDefault: 1
descriptionstring | nullableOptional
is_deletedbooleanOptional
is_pre_configuredbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/common/business_rule/business_rule/upload-csv/
200Success

Last updated