Frequently Asked Questions (FAQs)

Get quick answers to your questions about our services and policies. For more assistance, contact our support team.

As a statistical analysis viewer, can I quickly create a new questionnaire through this API?

No. Statistical analysis viewers do not have permission to use the template creation API. Only system administrators and questionnaire administrators have permission to use this API.

What are the main differences between creating a questionnaire from a template and creating one from scratch?

The main differences when creating a questionnaire from a template are: - There is no need to redesign the questionnaire structure and questions - Template settings are inherited automatically (such as response limit and total response control) - The request parameters are simpler; you only need to provide survey_id and title - You can quickly create multiple questionnaires with the same structure but different titles - It ensures consistency in questionnaire structure, making subsequent data analysis and comparison easier

What evaluation relationship types does the 360 survey evaluation relationship entry API support?

The 360 survey evaluation relationship entry API supports the following evaluation relationship types: superior, subordinate, colleague, other, and self-evaluation. These are the standard 360-degree assessment relationship types, covering the various hierarchy levels and role relationships within an organization.

What are the configuration rules for evaluation relationship level names?

The configuration rules for evaluation relationship level names are as follows: 1. The page supports 10 levels, while the API supports 99 levels; 2. It supports adding and modifying level names; 3. The name length of each level is limited to 60 characters. This means the system displays 10 levels in the user interface, but the backend API can handle up to 99 levels.

What are the validation rules for email addresses and mobile phone numbers in evaluation relationship entry?

The validation rules for email addresses and mobile phone numbers in evaluation relationship entry are as follows: 1. Email addresses and mobile phone numbers can be entered; 2. They must correspond one-to-one, and duplicates are not allowed; 3. The system will verify the uniqueness of the email addresses and mobile phone numbers to ensure that each evaluator has a unique contact method.

What are the length limits for the name and level name in evaluation relationship entry?

The length limit rules for evaluation relationship entry are as follows: 1. The name length limit for the name is 64 characters; 2. The name length limit for the level is 60 characters. These limits ensure data consistency and system stability.

What is the many-to-many relationship rule for evaluation relationships?

The many-to-many relationship rules for evaluation relationships are as follows: 1. The same person being evaluated can have multiple evaluators; 2. The same evaluator can evaluate multiple people; 3. This design supports complex organizational assessment structures, allowing one person to be evaluated by multiple people while also enabling one person to evaluate multiple people.

What are the validation rules for self-evaluator entry?

The validation rules for self-evaluator entry are as follows: 1. The name entered for the self-evaluator must be the same as the name of the person being evaluated; 2. If they do not match, the entry will fail; 3. This rule ensures the accuracy of the self-evaluation relationship and prevents incorrect self-evaluation relationship entries.

How do the add and append modes of the add evaluation relationship API differ?

The add and append modes of the add evaluation relationship API are distinguished by the is_delete_for_prev_eval_rel field: 1. If it is true, it is the add mode, which will delete the previous evaluation relationship; 2. If it is false, it is the append mode, which will add new evaluation relationships based on the existing ones.

What are the restriction rules for re-importing evaluation relationships when response sheets already exist?

The restriction rules for re-importing evaluation relationships when response sheets already exist are as follows: 1. The frontend page does not support re-importing evaluation relationships; 2. In the API, when is_delete_for_prev_eval_rel is true, re-importing is restricted; 3. This restriction prevents accidental operations that could lead to data loss when response data already exists.