Skip to main content

 –

Updating cases and followers

Suggest edit Updated on September 29, 2021

You can run a utility in your application to update the cases that users were following in previous releases so that the cases are no longer locked when they are followed. By using this utility, other users can follow cases, because they are no longer locked.

If you have cases that no users were following, you can update the cases by adding the latest UI kit but do not have to run the utility. If users subsequently follow these cases, the cases are no longer locked.

Any custom logic that relies on of the work party type of follower continues to work. However, it is recommended that you run this utility or replace your logic with APIs to retrieve a list of followers for a case. You can access APIs and API documentation by clicking Resources > Pega API.

To update your cases:

  1. Add the latest UI kit to your application stack.
    If you have cases in previous versions that no users were following, you must add the UI kit if you want to update cases so that they are no longer locked when users subsequently follow them.
    1. In the header of Dev Studio, click the name of the application, and then click Definition.
    2. In the Built on application section, click Add application.
    3. In the Name field, enter UIkit.
    4. In the Version field, press the Down Arrow key and select the latest version.
    5. Click Save.
  2. Optional: If you are updating cases that users were following, run the update utility.
    1. In the header of Dev Studio, click ConfigureSystemReleaseUpgradeUpgrade Tools.
    2. Click Update case followers.
    3. In the dialog box that is displayed, click Run utility.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us