Defining Questions on Controls in Hopex version 4.0

[cnisparnorddk]

Before Hopex Versions 4.0 when creating controls, the default question control steps (control has been run "Ok?") normally was assigned from inherited control steps to new controls according to the documentation:

---------------------------

Question/answer types

The type of question proposed by default at creation of a control step is "OK/NO".

Possible answers to this question are:

- OK

- NO

- N/A: Not Applicable

https://doc.mega.com/hopex-v4-en/#page/IRM/Internal_Control/GRC_Execution.Defining_Questions_on_Cont...

---------------------------

This behaviour has changed in version 4.0, even though the documentation says something else. 

Now all new controls need to have individual questions. The default question is not inherited and generated by default anymore on all controls.

Will this mean that you have to update question controlsteps on all controls, and there is no inherited control step used in all controls anymore?

Best regards 

[mimperiali · Accepted solution]

Good morning Claus,
Thanks for reaching out. Since HOPEX V4 allows to use the old questionnaires, the doc still contains content which is not relevant for the new questionnaire builder. To have a practical understanding of the impacts of the new Questionnaire Builder, please refer to this section: https://doc.mega.com/hopex-v4-en/#page/Deploy/New_Questionnaire_Builder_-_Migration_of_Existing_Clie...

As for your question, the link above shows how you should define inherited control steps with the new builder (see chapter "Inherited Question"): you will want to open the questionnaire template used by your assessment template, and add your inherited questions here. This way they will be automatically added to each questionnaire of your assessment campaigns.

Hope this helps. Please do not hesitate to come back to me if you have further questions.

Best,

Mike

[AHassan]

"Inherited control steps" is no longer supported and it has been replaced by another one.

Please see the below screenshot: