4. Removed/Reviewed Features
4.1. Pictures in drop-down questions
Drop down questions cannot display colored icons next to the drop-down value.
This was the case for questions like “Risk Impact” which were displaying a colored squared icon, based on the answer.
4.2. Create HOPEX Object as answer to question
In HOPEX V5 it is not possible to create HOPEX objects when answering questions of “Object” type. The only option is to select an existing one.
4.3. Questionnaire Layout
With Questionnaire Builder, a lot of effort was put into designing a new layout proposed to questionnaire's respondents. This new layout replaces the old ones. Therefore, tabular entry is no longer provided as an option to answer questionnaires.
 
4.4. Questionnaire Template Presentation
It is no longer possible to define a Questionnaire Template Presentation on the Questionnaire Template.
The only option which is still available is accessible via the properties pane of the questionnaire. It is the property:
Creation Mode – To define how the questionnaires should be created in the context of a campaign (one per person, one per assessed object, one per context)
The following options are no longer available:
Presentation Mode
Matrix number per page
Introduction Page Displaying
Display an ending page
Checks Page Displaying
Question Comment Display
Display a page to add documents
Each Question in a group Displaying
Context in a group
Context group folded
Scoring Displaying
Historic Displaying
Trigger Transition At Close
Display explanatory documents
Display explanatory external references
4.5. Presentation Tools
These objects are no longer supported. Nevertheless, for questionnaires on processes, the new layout automatically allows access to the process diagram, when it exists.
4.6. Inherited Questions
HOPEX allowed to define questions at the metaclass level, so that they would be automatically fetched on questionnaires assessing the metaclass instances. A practical example of this mechanism is the “Inherited Control Steps”: questions defined at the Control metaclass level, that would be automatically fetched by questionnaires assessing controls.
This mechanism is no longer supported, and it has been replaced by another one.
Customers using inherited questions must re-create them in the questionnaire template used by their campaign (e.g., the “Control Execution Questionnaire” questionnaire template for the “Control Execution” assessment template).
The following screenshot shows an example of the “Control Execution Questionnaire” questionnaire template used by Control Execution assessment campaigns, where a generic question has been created, followed by a block which is dynamically populated by the control steps.
4.6.1. Aggregation of Inherited Controls Steps
When creating generic questions, you might want to include the question answers in an aggregation schema. To do so, you must make sure to connect the question answer to the existing scoring rule.
Below is an example where a new question of “dropdown” type, with possible answers “OK”, “NO” and “NA”, called “New question OK/NO/NA” is defined in the questionnaire template used by control execution campaigns.
The question will be asked with respect to all controls in the scope of the campaign. To make sure it is included in the aggregation schema launched once the campaign's session has been closed, the user must connect its answer to the existing “OK/KO Scoring Rule” scoring rule.
 
 
 
4.6.2. Inherited Test Steps
It is no longer possible to define inherited test steps to be used within Test Sheets.
4.7. Meta Tests
In older versions, HOPEX allowed to define meta tests of two types on each question:
1. Those defining whether a question should be visible/mandatory or not based on the answer to previous question(s)
2. Those whose logic depends on actual HOPEX data
The former type of meta-tests will have to be rewritten in the new Questionnaire Builder.
The latter are still supported, and can be defined, accessing the question property page from HOPEX.
4.7.1. Write Logical Expressions in the new Builder
To write logical expressions affecting whether a question is visible, or mandatory based on pre-defined conditions, the user must use the dedicated Logic section, available in the new Questionnaire Builder, accessing the question property pane.
4.8. Delegation
Delegation must now be defined at the question level. By default, every question can be delegated, otherwise the option must be disabled in the question properties pane.
This means that it is no longer possible to define delegation either at the questionnaire template level or question group level.
4.9. Questions Group Populated by Query
HOPEX allowed to define question groups which were dynamically populated by a query. This mechanism is no longer available.
4.10. Questions with Link Answered Objects
HOPEX allowed to define questions whose answer would be automatically linked to the assessed object. This mechanism was used, for instance, when answering a question via a Business Document which was then connected to the assessed object.
This feature is no longer available.
4.11. Computed Questions
HOPEX allowed to create questions whose answer was automatically computed.
This feature is no longer available.