Questionnaire - Manage Questions Wizard


This wizard enables you to define the contents for standard and multi-section questionnaires by selecting the questions from those available in the reference table and by specifying their properties based on their context of use.

  • Define constraints that require users to comply with a rule before the answer to a question can be validated.
  • Define conditions that determine whether or not certain questions are displayed.
  • Define the answers to be saved in the SD_REQUEST table for future use.
  • Define the display order of questions.

Notes

  • In a multi-section questionnaire, you can access the wizard in each section.
  • A given question can be used in several questionnaires but it cannot be included two or more times in the same questionnaire.
  • If a question is being used in another question via a constraint or condition, its description, type and rank cannot be modified.
  • If a question is being used in another question via a constraint or condition, it cannot be deleted.
  • Constraints cannot be defined for questions whose type is Radio Button, Checkbox, Comment, Table Header, Grid, List, Signature or URL.

Best Practice big icon.pngBest practice

  • Arrange the layout of the questionnaire to make it easy to read.
    • Use Comment questions to add recommendations or details. Open url.png See Types of questions.
    • Add System questions to enhance the layout of the questionnaire, e.g. horizontal line separators. 
    • Use HTML to display values.

Screen description

       Manage the questions wizard.png

Add icon.png: Used to add a question selected from those in the reference table to the questionnaire. 

  • Click [ CREATE A NEW QUESTION ] to define a new one. It will automatically be added to the reference table and associated with this questionnaire.
  • You can add questions from another questionnaire.
  • You cannot include the same question more than once.
     

Delete icon.png (Note: Only if the question is not being used in another question via a constraint or condition): Used to remove the question from the current questionnaire.

  • The question will remain in the reference table, only the link with the questionnaire will be deleted.
  • If the question is being used in another questionnaire, it remains associated with it.
     

Edit icon.png (Note: Only if the question is not being used in another question via a constraint or condition): Used to modify the code, description or type of the question, as well as default answers. Open url.png  See Question Editor.

Question: Name of the question.

Type: Type of question used to format the answer field. Open url.png  See Types of questions.

Code: Question ID.

Mandatory (Note: Non-modifiable for certain types of questions such as Comment): Used to indicate whether users are required to provide an answer (box is checked) or if it is an optional question (box is not checked).

Constraint (Note: Except for questions whose type is Radio Button, Checkbox, Comment, Table Header, Grid, List, Signature or URL): Used to indicate whether a constraint is defined for the question (Constraint icon.png) or not (No constraint icon.png). Open url.png See Manage data entry constraints.

Alone on line: Used to indicate whether the next question should be displayed on the next line of the questionnaire (box is checked). This is mandatory for certain types of questions such as Radio Button, Grid and Memo because of their length, and for conditional questions. To display the next question on the same line, do not check the box.

Condition: Used to indicate whether the question will be conditionally displayed (Condition icon.png) or not (No condition icon.png). Open url.png See Manage display conditions.

Targets: Used to indicate whether the answer to the question should be stored in Target fields in the SD_REQUEST table (Target icon.png) or not (No target icon.png). Open url.png See Manage targets.

Apps Only: Used to indicate if the question is displayed only when the questionnaire is opened in an Product name - ev sas.png app (box is checked), or if it is permanently displayed regardless of whether the questionnaire is accessed from an Product name - ev sas.png app or from an Product name - ev itsm.png screen (box is not checked).

Up arrow.png and Down arrow.png: Used to modify the order in which questions are displayed when the questionnaire is run. Note: In the Questions tab, the display order is indicated in the Rank column.

  • Questions with a condition or constraint cannot be positioned after the questions on which they depend.
  • A question used in a condition cannot be positioned after the conditionally displayed question.
     

[ PREVIEW ]: Used to display the questionnaire as shown to users.

  • Questions with conditions are displayed in red.
  • The * symbol appears in front of mandatory questions.
     

[ CREATE A NEW QUESTION ]: Used to create a question directly in the questionnaire without returning to the reference table.

  • The Question Editor will automatically appear.
  • The new question will be available for all questionnaires.
     

[ ASSIGN THE DYNAMIC VALUES ]: Used to select the dynamic values used in constraints and conditions in the current questionnaire.
         Dynamic value association.png

  • [ CREATE A NEW DYNAMIC VALUE ]: Used to create a dynamic value directly in the questionnaire without returning to the reference table.
    • The editor will automatically appear.
    • The new dynamic value will automatically be associated with the current questionnaire and will be available for all questionnaires.

Manage data entry constraints

Constraints enable you to check that answers to questions comply with specific rules before they can be validated. 

  • Rules that compare static values, dynamic values or regular expressions, or rules that compare the answers to previous questions.
  • They can be combined using logical operators such as AND or OR.
  • The constraint is evaluated once the answer is entered. A blocking error message will appear if the constraint is not met. Users cannot proceed further in the questionnaire.
     
Data entry error in the questionnaire Error message displayed
Constraint - Error example.png Constraint - Error message example.png

Examples

    Open url.png See the other examples.

  • Check that the answer to the Departure question is greater than or equal to the answer to the Arrival question AND greater than or equal to the current date (@today dynamic value).
  • Check that the answer to the Appointment time question falls between 8 am and 8 pm.
    See the configuration.

    1. Create an Appointment time question whose type is Date and Time.

    2. Define the data entry constraint for this question using two rules:

    • Rule 1: Compared to a user static value option - Appointment time question - Value: >= 8 am
    • AND operator
    • Rule 2: Compared to a user static value - Appointment time question - Value: <= 20h
  • Check that the attachment is in the correct format, i.e. constraint on authorized file extensions (.png, .gif) AND that it does not exceed the maximum file size (1 MB).
  • Check that the answer to the Description question does not contain a script value.

Notes

  • Icons in the Constraint column:
    • Constraint icon.png indicates a question where a constraint is defined.
    • No constraint icon.png indicates a question where no constraint is defined.
    • No icon is displayed for questions where constraints cannot be defined. These are questions whose type is Radio Button, Checkbox, Comment, Table Header, Grid, List, Signature or URL.
  • A constraint can contain a maximum of 10 rules combined using the AND; OR logical operators.
  • The list of options available for each rule in the constraint depends on the type of question and is defined by Logo - EasyVista.png. You cannot add to them.

How to define a constraint for a question

1. Open the questionnaire you want and select Manage Questions to display the questions.

2. Click No constraint icon.png next to the question where you want to define a constraint.
        Constraint editor.png

3. In the editor, click Plus icon.png and define each rule in the constraint. You can refer to the examples (1) specific to each type of question.

  • Select the method of comparison you want from the Option column (Note: The options proposed are specific to the type of question). Specify the condition or value applicable.
  • Select the logical operator to be applied to the rules from the Separator drop-down list.
    • AND: The answer to the question with the constraint is validated only if both rules are satisfied.
    • OR: The answer to the question with the constraint is validated if at least one of the rules is satisfied.
  • Enter the error message (2) to be displayed when the constraint is not met.

4. Click [ SAVE ]. The icon for the question with the constraint will automatically be replaced by Constraint icon.png.

Manage display conditions

Conditions enable you to display a question based on certain rules.

  • Rules can apply to the answers to previous questions and/or they can be based on the result of an SQL query. 
  • They can be combined using logical operators such as AND or OR.

Examples

  • Display the question, New name only if the answer to the previous question, Type of request, was Change name.
  • Display the question, Next order date only if the result of the SQL query, Number of printers in stock < 3 returns a positive answer.

Notes

  • Icons in the Condition column:
    • Condition icon.png indicates a question where a condition is defined.
    • No condition icon.png indicates a question where no condition is defined.
    • No icon is displayed for questions where conditions cannot be defined.
  • A condition can contain a maximum of 10 rules combined using the AND; OR logical operators.
  • The list of options available for each rule in the condition depends on the type of question and is defined by Logo - EasyVista.png. You cannot add to them.
  • An SQL query is considered to be successful if the value returned is greater than 0 (at least one record is returned by the query: SELECT COUNT(*) > 0.
  • A question used in another question with a condition:
    • Cannot be deleted.
    • Cannot have its type or values modified.
  • In preview mode, questions with conditions are displayed in red.

How to define a condition for a question

1. Open the questionnaire you want and select Manage Questions to display the questions.

2. Click No condition icon.png next to the question where you want to define a condition.
        Condition editor.png

3. In the editor, click Plus icon.png and define each rule in the condition.

  • If the rule depends on a previous question:
    • Select it from the Question drop-down list. 
    • In the Condition drop-down list, select the operator you want to apply to this question. Note: For certain types of questions such as Radio Button, Grid and List, the operators proposed are possible answers for the question.
    • Depending on the selected operator, specify the comparison value in the field displayed next to the operator.

Example documentation icon EN.png

  • Question Name  ==> Operator = Starts with, comparison value = SMIT
  • Question: Type of keyboard requested  ==> Operators = Two radio button values azerty and qwerty
  • If the rule depends on the result of an SQL query:
    • Select SQL Condition from the Question drop-down list and click Edit icon.png
    • Enter the query in the wizard. Note: You can use the @ID@ variable which represents the REQUEST_ID field identifying the incident or request associated with the questionnaire.
    • Click [ SAVE ]. The value in the Condition column will be SELECT > 0.
  • Select the logical operator to be applied to the rules from the Separator drop-down list.
    • AND: The answer to the question with the condition is validated only if both rules are satisfied.
    • OR: The answer to the question with the condition is validated if at least one of the rules is satisfied.

4. Click [ SAVE ]. The icon for the question with the condition will automatically be replaced by Condition icon.png.

5. Check your questionnaire by clicking [ PREVIEW ]. Questions with conditions are displayed in red.

Manage targets

A target identifies a field from the SD_REQUEST table in which answers to questions are saved. Each answer can be stored:

  • In a Text or Memo field: Target gross result or non-typed. These are generally free fields and external fields.
  • In a field whose type is identical to the question: Target typed result.

    Open url.png See the examples.

Notes

  • Icons in the Targets column:
    • Target icon.png indicates a question whose answer is stored in the SD_REQUEST table.
    • No target icon.png indicates a question whose answer is not stored in the SD_REQUEST table.
    • No icon is displayed for questions whose answers cannot be stored in the SD_REQUEST table. These are questions whose type is Comment, Table Header, Signature, File Upload or URL.
  • The fields that can be selected as targets depend on the type of question.
  • Answers to questions whose type is Date or Date and Time can only be stored in a Date field without the _UT suffix.
  • System fields are not proposed as target fields.
        Example documentation icon EN.png  RFC_NUMBER, SLA_ID, REQUEST_ID
  • Certain fields are used by wizards in specific contexts and as such, cannot be used as target fields in these contexts.

    Example documentation icon EN.png  The REQUESTOR_PHONE field is used by the Transfer wizard for change requests. It can be used as a target field for a questionnaire in an Incident process but not for a questionnaire in a change request.

    List of fields concerned:
    • Incident context: EXPECTED_START_DATE_UT, EXPECTED_END_DATE_UT, DESCRIPTION
    • Change request context: REQUESTOR_PHONE
    • Multi-cart change request context: CI_ID
  • The answers saved in the SD_REQUEST table:
    • Can be displayed in Incident/Request/Action/Problem forms if the Target fields are visible.
    • Can be used in reports.

Best Practice big icon.pngBest practice

  • To store answers to questions in fields in the SD_REQUEST table:
    • Check that the Target field is not being used by the wizard displaying the question, otherwise data entered in the answer will be lost.
    • Ensure consistency of use when the Target field is modified by the internal update steps of business rules.

Target fields for storing answers

        Target editor.png

Target gross result:: List of all Text or Memo fields regardless of the type of question. Select the field based on the processing to be performed on the answer.

Target typed result: List of all fields whose type is identical to the question. Note: The selected field can be different from the one selected in Target gross result.

Best Practice icon.png We recommend you specify the Target typed result.

 

Action (Note: Only for Memo questions): Used to indicate how the new data is stored if the Target field in the SD_REQUEST table is not empty.

  • The new data will overwrite existing data.
  • The new data will be inserted before or after existing data.

 

Examples of targets

Type of question Answer Target
Radio Button Yes   (radio button value 1)
  • Target gross result: 1
  • Target typed result: Index 1
Date and Time 03/02/2017   Calendar icon.png 10:00:00
  • Target gross result: 03/02/2017 10:00:00
  • Target typed result: 03/02/2017 10:00:00
Decimal 1000.99
  • Target gross result: 1000.99
  • Target typed result: 1000.99
Duration 1:25
  • Target gross result: 85
  • Target typed result: 85
Grid Laboratory   (list value 2)
  • Target gross result: 2
  • Target typed result: Index 2
Tags:
Last modified by Unknown User on 2017/03/31 19:54
Created by Administrator XWiki on 2017/03/31 19:54

Shortcuts

Recent Updates

Haven't been here in a while? Here's what changed recently:

-   Product name - ev itsm.png
-   Product name - ev sas.png

Interesting Content

How to Automate Integration
Add a Shortcut to an App
History
Quick Dashboard
Full text search - Stop Words

Powered by XWiki ©, EasyVista 2018