Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Scoring answers in a questionnaire

Updated on May 11, 2022

Calculate a cumulative score based on your questionnaire results, to generate metrics and trends for a specific focus group. For example, in a questionnaire about satisfaction with customer service, you can assign high scores to better ratings and low scores to poorer ratings to quickly calculate the general satisfaction level of customers.

Note: Only standard Pega Platform applications support scoring answers. You cannot configure scoring values in applications based on Cosmos React.
You can configure scoring only for questions that you add to a question page in a questionnaire. Individual questions that you ask by using the Question shape in a case life cycle do not support scores.
  1. Navigate to the questionnaire:
    Open the questionnaire in App Studio
    1. In the navigation pane of App Studio, click Case types.
    2. In the list of case types, open a case type of the Questionnaire type that you want to edit.
    Open the questionnaire in Dev Studio
    1. In the header of Dev Studio, click ConfigureCase ManagementQuestionnaire.
    2. Click the questionnaire that you want to edit.
  2. Click a question with one of the following answer formats:
    • Picklist
    • Check box
    • Radio button matrix
  3. In the Question settings pane, in the Scoring section, click the Properties icon.
  4. In the Binary window, assign numeric values to the choices.
    For example:
    Configuring scores for answers
    Binary window with a numeric value assigned for each answer
  5. Click Submit.
  6. Click Save.
Result: When users provide answers, your application calculates the cumulative score for the questionnaire, and saves the score in the pxCumulativeQuestionScore property.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us