Skip to main content

Application Form

Organizations in Axvero can create custom application forms and multi-step workflows for each application type. These forms are used to collect all required and optional information from applicants, tailored to the organization's industry and specific needs.

Application Types & Industry Context​

  • Each industry (e.g., tax consultancy, legal firm, banking) may have different application types, each with its own form requirements.
  • Example: In tax consultancy, application types include Yearly Tax Filing, Tax Audit Request, and Salary Certificate Request. Each type has its own set of fields and steps.

Dynamic Form Creation from JSON​

Organizations can define application forms and steps using a JSON configuration. This allows technical users to quickly design, update, and manage forms without code changes.

Example JSON Structure​

{
  "applicationType": "Yearly Tax Filing",
  "steps": [
    {
      "title": "Personal Information",
      "fields": [
        { "id": "applicantName", "label": "Applicant Name", "type": "text", "required": true },
        { "id": "dateOfBirth", "label": "Date of Birth", "type": "date", "required": true }
      ]
    },
    {
      "title": "Financial Details",
      "fields": [
        { "id": "incomeStatement", "label": "Income Statement", "type": "file", "required": true },
        { "id": "supportingDocs", "label": "Supporting Documents", "type": "file", "required": false }
      ]
    }
  ]
}

Key Features​

  • Step-based forms: Organize fields into logical steps for better user experience.
  • Field types: Support for text, number, date, select, file upload, etc.
  • Required/optional fields: Easily specify which fields are mandatory.
  • Validation: Define validation rules for each field.
  • Industry-specific customization: Forms can be tailored for each application type and industry.

How It Works​

  1. Organization admin defines the form structure in JSON.
  2. Axvero dynamically renders the form and steps for applicants.
  3. Users complete the form, step by step, with validation and guidance.
  4. Submitted data is stored and processed according to the organization's workflow.

Document Templates & Master Document List​

Organizations in Axvero can create and maintain a master list of document templates for each application type and workflow. This enables:

  • Defining required and optional documents for each application type (e.g., tax filing, audit request)
  • Grouping documents by category, relevance, or application type
  • Customizing document requirements per organization

DocumentTemplate Model​

  • Each template has a name, description, default required/optional status, and can be linked to an application type or category.
  • Example: "Income Statement" (required for tax applications), "Foreign Asset Declaration" (optional for most, required for some)

Admin Workflow​

  1. Organization admin creates and manages document templates via the API.
  2. Templates are linked to application types and workflows as needed.
  3. When an applicant starts an application, Axvero uses the relevant templates to determine which documents are required or optional.

API Endpoints​

  • GET /document-templates?organizationId=...&applicationType=... — List templates for an org and app type
  • POST /document-templates — Create a new template
  • PUT /document-templates/{templateId} — Update a template
  • DELETE /document-templates/{templateId} — Remove a template

Example​

  • "Income Statement" (required for yearly tax filing)
  • "Foreign Asset Declaration" (optional for most, required for some application types)

This approach ensures each organization can fully customize its document requirements and workflows in Axvero.

For more details on configuring forms and steps, see the documentation for your specific industry and application type.