Skip to main content

Troubleshooting tips for challenges and mission exercises

Pega Academy provides auto-grading of some challenges and mission exercises. The auto-grader is that stakeholder that expects the acceptance criteria specified in the challenge or mission exercise to be met, including naming conventions and spelling.

Spelling mistakes are the most common cause of validation errors. If a task or user story fails validation after you submit your solution build for verification, click the failed task or user story to reveal the actual error message. Then, review your solution build carefully, and fix any naming conventions or spelling errors noted in the validation results. If the validation error is not related to a naming convention of spelling error, review our list of the most common causes of error messages.

Most Common Errors

Open Accordion Close Accordion

You must use the login credentials provided in every challenge and mission exercise.

Note: Pega Robot Manager challenges must be completed in order. If you cannot login using the credentials provided in the challenge or mission exercise, it is because you did not complete the preceding challenges.

Common errors in case life cycle design

Open Accordion Close Accordion

This error indicates you did not name the case type as specified in the acceptance criteria of the challenge or mission exercise. In most cases, it is best to reset the Pega instance and start over.

It is possible to edit the underlying class name from Dev Studio.

  1. Switch to Dev Studio.
  2. Click the App explorer, and identify the Work class name (red box), and the case type name (blue box).
    Identify class names
  3. In the header, click Configure > System > Refactor > Classes.
  4. Click Rename a Class.
  5. In the Old Class Name field, enter the first few characters of the Work class name you identified in step 2, and then press the down arrow on your keyboard to display a list of class names.
  6. Select the complete class name that matches the Work class name and the case type name. In this example, you select UPlus-AcctMgmn-Work-BalanceTransferCaseType.
    Enter old class name and new class name
  7. In the New Class Name field, enter the name of the Work class (do not change) and the case type name as specified in the acceptance criteria of the challenge or mission exercise.
  8. Click Next on the next three pages - do not make any changes.
  9. On the next page, click Finish.
  10. On the next page, click Done.
  11. Right-click on the Work class name, and select Refresh all to view the updated class names.

Return to the challenge or mission exercise page and verify your solution.

Open Accordion Close Accordion

This error indicates the names of the stages do not match the acceptance criteria specified in the challenge or mission exercise. Spelling errors are the most common cause of this error. Review the acceptance criteria in the challenge or mission exercise and ensure you named the stages as specified in the acceptance criteria.

Open Accordion Close Accordion

This error indicates you did not configure the transition of one or more stages in the case life cycle as specified in the acceptance criteria of the challenge or mission exercise.

To resolve this error, review the acceptance criteria for stage transitions in the challenge or mission exercise, and confirm your solution build meets the acceptance criteria.

For remedial learning on how to configure stage transitions, see the Pega Academy topic Case life cycle design: Stage transitions (link opens in a new tab/window.)

Open Accordion Close Accordion

This error indicates you did not name a persona according to the acceptance criteria in the challenge or mission exercise. This error can also indicate you did not spell the name of the persona correctly when you first created the persona.

To resolve this error, review the names of the persona in the stage indicated in the task or user story.

If you made an initial mistake when creating the persona:

  1. Remove the persona from the stage(s) in the case type, and then save the changes to the case type.
  2. From the App Studio explorer panel, click Users > User management.
  3. On the Personas tab, delete the persona(s) that are causing the error.
  4. Click Add to add a new persona.
  5. Enter the name of the persona as specified in the acceptance criteria. Ensure you do not make any mistakes.
  6. Enter a description, and then click Submit.
  7. Return to the case type.
  8. In the appropriate stage - as specified in the acceptance criteria - click + Persona and select the persona from the list.
  9. Save your changes to the case type.

More tips for resolving case life cycle design errors

Common errors with Fields and Views

Open Accordion Close Accordion

This error indicates you did not configure the field with the correct filed type as specified in the acceptance criteria for the challenge or mission exercise.

To resolve this error:

  1. From App Studio, click the Data explorer
  2. Open the Transfer offers data object.
  3. Delete the field you want to change (click the trash can icon on the right.
  4. Click Add field to add a new field with the correct Type.
  5. Confirm the field is updated in the View
Open Accordion Close Accordion

This error indicates the View is not configured correctly. To resolve this error, remove the step from the process and save the change to the case type. Then, add a new step and configure the view as specified in the challenge or mission exercise.

NOTE: If you added fields, data objects, or data references to the view do not try to create these artifacts again. Simply select them from the Fields menu (on the left of the Configure view modal).

Open Accordion Close Accordion

You cannot change the type of a field (property). To change a field type, you must delete the field with the incorrect type, then create a new field with the correct type.

  1. In App Studio, click the Data Designer, then open the data object that contains the field you want to change.
  2. Delete the field you want to change (click the trash can icon on the right).
  3. Click Add field to add a new field with the correct type.
  4. Edit the view(s) that contain the field to ensure the new field is referenced correctly.

Common errors with data objects

Open Accordion Close Accordion

This error indicates you did not name the data object as specified in the acceptance criteria.

Note: You must spell the name of the data object correctly when you first create the data object. If you misspelled the name of the data object when you first created it, editing the name later only changes the descriptive label, but the auto-grader is checking for the rule ID.

To resolve this error, review the acceptance criteria for the data objects in the challenge or mission exercise. Then, follow the steps below to resolve the error:

  1. Access your Pega instance and open App Studio.
  2. Click the Data explorer.
  3. Identify the data object that you want to delete
  4. Click the vertical menu on the far right of the data object row, and click Delete.
  5. Follow the procedure in the challenge or mission exercise to create a new data object.

If you are still having trouble completing the challenge or mission exercise, we recommend resetting the Pega instance and working through the challenge or mission exercise again. If you are having technical issues with a Pega instance, please contact the Pega Academy support team.

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice