Questionnaire master data

The questionnaire master form can be opened from the menu Extras/Questionnaire.

Note: When you are working on creating and specifying a questionnaire, you can quickly make any changes visible by executing the Generate questionnaire function. As a result, the questionnaire is opened immediately so that you can test it. This function shows the procedure without generating the questionnaire again.

You can define the properties and administrative data of a questionnaire, such as the responsible agent, the sta­tus, type, language, etc., in the form heading and on the Master data tab.

Properties

Description

Keyword

The keyword can be maintained in multiple languages, meaning that you can use one and the same questionnaire in several languages. This makes the selection of a possible questionnaire, e.g., for an appointment, unique.

Status

Controls the release. Status can be defined in the PSA_QST_STA_QUE variable. In selections, only released questionnaires are offered.

Anonym

Personalized or anonymous storage of the answers.

Anonymous questionnaires are for surveys that must not contain contact data, e.g., for data security reasons.

In case the flag is set, all answer records are saved to the answer table without any reference to the contact. This also makes it possible to capture anonymous training evaluations, for example.

The answer records are then given an identical sequence number to identify their coherence. This makes it possible to determine which answers came from the same contact during the evaluation, but without being able to identify this contact.

Modal

Controls whether the questionnaire opens as a modal or non-modal dialog.

Input type

Once: The questionnaire can no longer be invoked after it has been completed. To capture it again, all existing answer sets must be deleted.

Once, but updatable: The questionnaire can be opened several times for adjustments, e.g., to modify the answer sentences. When opened again, the last page is displayed, "Cancel" or "Ready" dismisses the information about the last page.

Repeatedly: For recurring customer surveys directly at the person, for example. Every survey creates new answer sets. The sets can be distinguished in the answer table by their automatically created "number" and "modified on".

Start-, End-, Fallback dia­log

The start and end dialogs are for welcoming and, respectively, finally thanking the respondents. It is recom­mended to always provide these dialogs if external contacts are questioned via the web client. The dialogs are usually not required for questionnaires that are filled in by internal staff members.

Visit reports for an appointment or question catalogs for a phone call usually don’t contain such dialogs.

The fallback dialog is for providing information in case the questionnaire has already been filled out (Input type = Once).

The content and layout of the dialogs can be specified as follows:

  1. Dynamically: Variable content (title, text and image) in a static layout corresponding to the dia­log template. The image must have a size of W=235 pixels * H=100 pixels.
  2. Fixed: static content and layout according to dialog template
  3. Dynamic with a captcha: The questionnaire can be preceded by a security procedure (captcha), e.g. to block bots.

See below for implementation notes!

Header, Footer

Selection of the dialog templates that should be used (e.g., standard navigation buttons, "Next" … "Ready").

Navigation

Selection of the method (decision table) for answer-related navigation in the question­naire.

Loader

Selection of a questionnaire loader. It is required if fields from default or client-specific objects (e.g., contact data) should be displayed, modified and updated (writ­ten back) in the questionnaire.

Implementa­tion

Extension of the questionnaire by a superclass through customizing. Can be implemented per questionnaire.

Admin: An administrator list is available for adding implementations to questionnaires. In the admin list, either a static Java class or a Cubes dialog implementation can be specified. The name of the Cubes implementation must be prefixed with a "$" sign. The implemen­tation must extend the de.pisa.psa.frm.psa_qst.PsaQstFrmApp class.

Follow-up URL

Forwarding to a URL after completion of a web questionnaire (call via a link, display in portal mode of the web client). If you enter a follow-up URL, the page is set to be opened in por­tal mode after closing the questionnaire using "Finish". If the field of the URL is blank, the global setting of the Web client is used.

Captcha template and implementation

The questionnaire can be preceded by a security procedure (Captcha) to fend off bots. For this, the Dynamic with Captcha start dialog template is available.

Info

Admin: Variables and settings

  • The PSA_CAP_IPL variable sets the implementation for generating the Captcha. Currently, there are de.pisa.psa.cap.PsaSimplecaptcha and de.pisa.psa.cap.PsaKaptcha.
  • PSA_QST_CAP_CLI_GEN defines the client types the Captcha is to be generated for.
  • PSA_QST_CAP_AUT_LGO specifies which client type auto­matically logs off after how many incorrect entries.
  • There is a new external Jar, PsaCap_1.0.0.jar.