Skip to main content
LinkedIn
Copied!

Table of Contents

Creating a case type rule form in Dev Studio

Version:

Only available versions of this content are shown in the dropdown

Provide advanced options for your business processes by creating case types through a case type rule form. For example, you can select an application layer in which to store your case type, or define multiple options at once, for example, for the people that your case type involves, processes that can support your case type, or dependencies with other case types.

Creating case types through a rule form is suitable for advanced developers. If your use case does not require advanced configurations, create a case type by using the Case Designer tool, which helps you visualize your business process in a low-code way. For more information, see Creating a top-level case type.

  1. In the header of Dev Studio, click Create Process Case Type .

  2. In the Case Type Record Configuration section, in the Label field, briefly describe the purpose of your case type.

    Enter Loan requests review.
  3. In the Context section, define how your application stores the case type:

    1. If you use branches to work on your application, in the Development branch list, select a branch that you want to use to store the case type.

    2. In the list of application layers, select a layer in which you want to store the case type.

    3. In the Applies to field, press the Down arrow key, and then select the class to store the case type.

    4. In the Add to ruleset list, select a ruleset and a ruleset version to store the case type.

  4. Optional:

    To override the default work item that your application associates with this development change, press the Down arrow key in the Work item to associate field, and then select a work item.

    For more information about your default work item, see Setting your current work item.
  5. Click Create and open.

  6. Optional:

    To customize how the case appears at run time, change the icon that the system displays to users when processing the case:

    1. In the Appearance section, click Edit.

    2. In the Appearance dialog box, select a new icon.

    3. Click Submit.

  7. Optional:

    To define people involved in a case by reusing an existing rule, in the Work parties rule field, provide a relevant rule name.

    You can also define work parties manually. For more information, see Defining case participants.
  8. In the Starting process section, click Add a row, in the text field press the Down arrow key, and then select a process that runs when the case starts at run time.

    You only provide a starting process for case types without the Create stage. For more information, see The Create stage.
  9. Optional:

    To enable users to supplement the case with additional processing, in the Case wide supporting processes section, in the text field press the Down arrow key, and then select a supporting process that users can add to this case.

    1. Optional:

      To add more supporting processes, click the Add a row icon, and then provide another process.

  10. Optional:

    To create dependencies between case types, in the Child case types section, enter a case type that users need to resolve before the current case reaches its resolution.

    For more information about configuring child case types on a rule form, see Creating case hierarchy on a case type rule form.
  11. In the Case wide actions section, define how users interact with a case by providing a flow action:

    1. In the Flow Action column, enter a flow action.

    2. In the Visibility column, define when a flow actions starts by selecting a When rule, an expression, or an option to always start the flow action.

  12. Optional:

    To look for similar cases in the database so that you avoid creating duplicate cases, in the Case match section, in the text field, enter a rule name that evaluates conditions used for finding duplicate cases.

  13. Click Save.

  • Creating case hierarchy on a case type rule form

    Organize hierarchically your business processes by adding child case types to your main, parent case type. Consequently, you define which additional actions users need to resolve before your main process is complete. For greater flexibility and efficiency, you can define conditions under which a child case type starts. When you use a case type rule form to create case hierarchy, you can select advanced options and perform additional configuration.

  • Calculating properties in a case type

    Save time and manage your case type resources efficiently by automatically calculating aggregated properties. You can calculate a property by sourcing values from other case types instead of asking users to provide values manually.

  • Configuring stages on a case type rule form

    Provide advanced configurations for sets of actions in your business processes by adding stages on a case type rule form. As a result, you can configure multiple settings from a single screen. For example, you can define which optional processes you want to enable for the case type, or what attachments users need to provide in order for the case to enter a specific stage.

  • Categorizing attachments on a case type rule form

    Organize the information and materials in your case types by creating categories for attachments. When you use a case type rule form to create attachment categories, you can access additional data about a category, such as a property that you can later use to reference attachments by category.

  • Defining purpose of a case type by creating specifications

    Engage with your stakeholders and communicate goals that you want your case type to achieve by creating specifications. Specifications represent actions that users can perform by using your application so that all parties involved in the development process have a common understanding of the purpose of your application.

Did you find this content helpful?

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 Community 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
Contact us