Skip to main content

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

Selecting a license category for a case type

Updated on May 11, 2022

Communicate the applicable business use case for your case type by selecting a relevant license category. The system uses license categories to report usage of your case types, and to help you ensure that you comply with your software requirements.

For example, you can select a license category that indicates that most of the case processing occurs in an internal system.
Before you begin: To avoid licensing implications and inconsistencies, ensure that you select licensing for your case types before you move your application to a production environment.
  1. In the navigation pane of App Studio, click Case types.
  2. In the case work area, click the Settings tab.
  3. In the navigation pane, click General.
  4. In the License category list, assign a license to your case type:
    • To communicate that an application routes or tracks work in an internal system, select Work Execution.
    • To communicate that an application routes, tracks, and completes work by updating information in external systems, select Work Management.
    • To communicate that work processing occurs outside of an application, select Work Dispatch.
    • To communicate that work execution requires a custom extension for complex scenarios, select Complex Work Execution.
  5. Click Save.
Result: The case type has a license category but the default audit reports do not evaluate the classification. For more information about how these classifications affect your license agreement, contact your Pega Account Executive.

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