Integrate SurveyJS Libraries with Backend

SurveyJS includes several client-side libraries that work in a web browser. Use these libraries as building blocks for your frontend:

• SurveyJS Form Library embeds a survey onto a web page.
• SurveyJS Creator allows users to create/modify survey structure.
• SurveyJS Dashboard displays survey results.
• SurveyJS PDF Generator allows users to save your survey as a PDF document.

SurveyJS can work with any server-side framework and database. This help topic describes the main aspects that you should take into account when you integrate SurveyJS with your backend.

To communicate with the server, SurveyJS libraries use JSON objects. The following diagram illustrates the communication process:

SurveyJS libraries send and receive two types of JSON objects:

• Survey schema
  Describes the survey structure—pages, panels, and questions.

• Survey result
  Contains a respondent's answers to survey questions.

Your backend development team should implement server-side code that stores these JSON objects in a database and delivers them to and from the client side.

Backend implementation is a custom development task that lies beyond the scope of SurveyJS libraries. However, we can highlight implementation aspects that facilitate successful SurveyJS integration.

Design a REST API endpoint that accepts JSON data in requests and sends JSON data in responses.

To authenticate a user that sends a request, determine their identity. To authorize the user, determine the resources they can access. Prevent users from accessing API operations outside their predefined roles.

Validate API calls and sanitize user input to prevent cross-site request forgery (CSRF), cross-site scripting (XSS), and SQL injection (SQLi) attacks.

A survey management application should include a database to store survey schemas and results. Depending on your business needs, you can build an on-premises data storage or host data in a cloud service.

In the simplest case, the database can include two tables: one for survey schemas and one for survey results. The tables should establish a one-to-many relationship (one schema to many survey results) and can contain the fields described below.

SurveySchemas

• id - A unique identifier of a survey schema.
• content - A JSON object or text string that contains the survey schema.

SurveyResults

• id - A unique identifier of a survey result.
• survey_schema_id - A required field that refers to SurveySchemas.id.
• content - A JSON object or text string that contains the survey result.

Each database can also include additional fields as required. For example, if you need to track who and when created or changed a survey schema, you can add the following fields to the SurveySchemas table: createdDate, createdByUser, changedDate, and changedByUser.

The following table illustrates permissions that each SurveyJS component needs for correct operation:

Note that SurveyJS Dashboard needs to read one record from SurveySchemas and all records with the same survey_schema_id from SurveyResults. SurveyJS PDF Generator needs to read one record from SurveySchemas and, optionally, one record with a desired result from SurveyResults.

Although SurveyJS does not offer production-ready backend solutions, you can refer to the following page for free examples that can be used as a starting point to implement a full-cycle survey management system on your premises: Backend Integration Examples.