Skip to main content

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

Creating child case types in Dev Studio

Updated on May 11, 2022

Define a more structured work processing in your organization by creating child case types. When you create a child case type, you define a set of actions that are dependent on the main business process, and that users need to complete before the parent case type reaches a resolution. As a result, you avoid creating long and complex case types and you deliver more granular and flexible applications that are easier to maintain

For example, a process of hiring an employee for a managerial position might require more complex and longer background check. By defining the background check as a child case type, you have the possibility to reuse this business scenario in only the relevant circumstances. A case of hiring a manager can reach a resolution only after the child case of running a background check completes.
Before you begin: Create a parent case type. For more information, see Creating a top-level case type.
Note: Creating case type hierarchy in Dev Studio is suitable for advanced developers. To take advantage of low-code tools, create child case types in App Studio. For more information, see Creating a child case type.
  1. In the navigation pane of Dev Studio, click Case types.
  2. Hover over the name of a case type, and then click MoreAdd a child case type.
  3. In the Add case type dialog box, define the case type that you want to use:
    • To create a new case type, select New case type, and then, in the Name field, enter a label for your case type.
    • To reuse an existing case type, select Existing case type, and then, in the Select an existing case type to add as a child list, select a case type that you want to use.
  4. Optional: If you create a new case type, to define resources that your case type can access by using class inheritance, expand the Advanced Settings section:
    • To change the parent class from which your case type directly inherits resources, in the Derives from (Directed) field, enter a new class.
    • To change the class from which your case type inherits resources by using the class name structure, in the Derives from (Pattern) list, select a new class.
    • To change the ruleset or the ruleset version to store your new case type, in the Ruleset and Ruleset version lists, select the new values.
  5. Click Submit.
What to do next: Populate your case types with actions that advance your business processes closer towards a resolution. For more information, see Case life cycle elements.

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