Custom event fields

The platform supports adding custom event fields to individual operators. These fields will appear at the end of the emission form and can have validation based on other fields (custom or not).

The available field types are:

• Open text
• Boolean

When validating fields, we support the following attributes:

• required: boolean field, if true, then the field is required.
• required_condition: comparison operator, with the following structure:
  • {"if": "field_name", "equals": "value"}}: if field_name is equal to value, then the field is required. Used to make nested conditions based on other custom fields or the event status field (event_status)

Note: validation only applies when moving the event to complete or needs review step.

Interactive Configuration Builder

Use this interactive tool to build your custom field configuration visually or by editing JSON directly:

Field Configuration

No fields configured yet.

Click "Add Field" to get started.

Live Preview

No fields to preview yet.

Add fields to see how they'll appear in the emission form.

Tips:

• Start in Visual Builder mode to create fields without worrying about JSON syntax
• Switch to JSON Editor mode to paste existing configurations or make bulk edits
• Use the preview panel to test conditional logic by interacting with the fields
• Click "Copy JSON" to get the formatted configuration for Django admin

Configuring custom fields

Configuring custom fields is an operation done per company, through Django admin. Here are the steps to set it up:

1. Log in Django Admin (follow the steps here)
2. Navigate to Accounts -> Companies and find the company you want to set up custom fields.
3. Click on the company name and edit the Extra field settings field with the desired values. The following example creates 4 fields, with the text ones only beinf required when the answer to the boolean fields is false:

[
    {
        "type": "boolean",
        "label": "The detection is being considered “additive under Appendix A”?",
        "required": true,
        "field_name": "additive_under_appendix_a"
    },
    {
        "type": "text",
        "label": "Justification (if selected no):",
        "field_name": "additive_under_appendix_a_justification",
        "required_condition": {
            "if": "additive_under_appendix_a",
            "equals": false
        }
    },
    {
        "type": "boolean",
        "label": "Confirmation that the event has been accounted for in corporate emissions SOR",
        "required": true,
        "field_name": "account_for_in_emissions_sor"
    },
    {
        "type": "text",
        "label": "Justification (if selected no):",
        "field_name": "account_for_in_emissions_sor_justification",
        "required_condition": {
            "if": "account_for_in_emissions_sor",
            "equals": false
        }
    }
]

4. Save the changes.