Skip to main content

Community

Genesys Connector Missing Evaluation Answer Values

Answered

Please sign in to leave a comment.

Comments

2 comments

  • Official comment

    Hi Johnathan,

    Thank you for the detailed analysis and for sharing the query and API reference.

    We will review how the Genesys connector handles multipleSelectQuestion questions, including their answer options and scores, to assess whether the nested data is being captured correctly. We will get back to you once our review is complete.

    Could you share a bit more about how you use this data downstream? That will help us scope the fix correctly. We will keep you updated on this thread as we make progress.

    Best,
    Syead Mujtaba Imam Rizwi

    Additional technical evidence supporting this request

    We independently investigated this same issue and can confirm and extend the original reporter's findings with concrete data:

    1. The gap is quantified: In our environment, 26% of answer rows (48 out of 185 in EVALUATION_ANSWER_QUESTION_GROUP_QUESTION_SCORE) reference sub-option question IDs and answer IDs that do not exist in any relational table. These are the multipleSelectOptionQuestions children.

    2. The problem spans three tables, not just answer options: The connector correctly inserts the parent multipleSelectQuestion into EVALUATION_FORM_QUESTION_GROUP_QUESTION, but the child sub-options (nested under multipleSelectOptionQuestions in the API response) are missing from both:

    • EVALUATION_FORM_QUESTION_GROUP_QUESTION — the sub-option question IDs, text labels, and types are not inserted
    • EVALUATION_FORM_QUESTION_GROUP_QUESTION_ANSWER_OPTION — the Selected/Unselected answer options for each sub-option are not inserted

    Meanwhile, EVALUATION_ANSWER_QUESTION_GROUP_QUESTION_SCORE does contain individual answer rows for each sub-option (with QUESTION_ID and ANSWER_ID populated), making these orphaned foreign keys that cannot be resolved through the relational model.

    3. The parent question's ANSWER_ID is always empty: For multipleSelectQuestion rows in the answer scores table, the ANSWER_ID is consistently an empty string, which aligns with the original reporter's observation. The actual Selected/Unselected state is only recorded on the child sub-option rows — which are themselves unresolvable.

    4. Published version vs. master form matters: Each published version of a form generates new unique IDs for all questions and answer options. Even if a workaround involves loading form JSON manually, it must come from the published form endpoint (GET /api/v2/quality/publishedforms/evaluations/{id}), not the master form endpoint, because the IDs differ between versions.

    Suggested implementation: The connector should flatten the multipleSelectOptionQuestions array into EVALUATION_FORM_QUESTION_GROUP_QUESTION (as child rows with a reference to the parent question) and their answerOptions into EVALUATION_FORM_QUESTION_GROUP_QUESTION_ANSWER_OPTION, similar to how it already handles multipleChoiceQuestion types. This would make the existing answer score rows resolvable without any external API calls.