Skip to content

Implement a forms microservice #14

@GabrielMajeri

Description

@GabrielMajeri

Many business process flows start with the end user/beneficiary filling in and submitting a form. The data associated with that form must be collected and stored in our databases.

API routes

  • POST /forms/submit:

    Parameters (in the body):

    • flow_id: unique object identifier of the flow (the same one as in MongoDB)
    • flow_instance_id: unique identifier of the flow instance (used for tracking individual flow runs within the admin dashboard, useful for statistics and such)
    • form_id: unique identifier of this form within the flow (string)
    • data: dictionary consisting of field names and values. E.g.:
      {
         "name": "Exemplu Student",
         "reason": "eliberare adeverință student pentru muncă"
      }
      This data is a JSON object, it changes depending on the form in question.

    Returns: a status code indicating if the form data was saved/submitted successfully, or an error message if something failed.

Metadata

Metadata

Assignees

Labels

back-endIssues related to the app's back end

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions