Skip to main content

PEGA ACADEMY

Troubleshooting Tips for Case life cycle design

Find quick and easy solutions to the most common errors with case life cycle design

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 error messages for case life cycle design - and how to fix them.

Common errors with 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.

Open Accordion Close Accordion

This error indicates you did not configure the status of one or more stages in the case life cycle as specified in the acceptance criteria. For additional guidance on how to set case status see the article Changing case statuses (link opens in a new tab/window).

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. For additional guidance on how to set case status see the article Creating a primary stage (link opens in a new tab/window).

Open Accordion Close Accordion

This error indicates that you may have copy and pasted the email message, and did not use the Insert property button to reference the properties correctly.

You must use the Insert property button to insert property references.

Open Accordion Close Accordion

This error indicates you did name one or more of the steps in the process according to the acceptance criteria, or you misspelled one of more of the step names.

Return to your Pega instance and carefully review your work.

Open Accordion Close Accordion

This error indicates you did not change the template of a multi-step process to Vertical navigation.

To resolve this error, return to your Pega instance and select the multi-step form process. Confirm the template (in the configuration panel on the right) is set to the template specified in the acceptance criteria of the challenge of mission exercise.

Open Accordion Close Accordion

This error indicates you either did not add the portal channel interface to the application, or you did not match the naming convention as specified in the acceptance criteria.

To resolve this error, add the portal channel interface to the application, or replace the portal channel interface with a new one that matches the naming convention as specified in the acceptance criteria.

To replace a channel interface:

  1. In App Studio, ensure you remove the channel interface from all case types.
  2. Open the Channels explorer.
  3. On the Current channel interfaces page, click the channel interface you want to replace.
  4. In the upper-right corner, click Actions > Delete channel interface.
  5. In the Delete channel interface modal, click Delete.
  6. On the Current channel interfaces page, click the type of channel interface you want to add to the applicaiton.
  7. In the Name field, enter the name of the channel interface as specified in the acceptance criteria in the challenge or mission exercise.
  8. In the Description field, enter the description as specified in the acceptance criteria in the challenge or mission exercise.
  9. Click Submit.
  10. Open the case type for which you want to add the channel interface, and follow the acceptance criteria in the challenge or mission exercise.

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