Skip to main content

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

Creating case hierarchy on a case type rule form

Updated on November 22, 2021

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.

For example, you can supplement your parent case type Review a job candidate with a child case type Run a background check to provide more information about a candidate who applies for a position in your organization. To make the process more flexible, you can run a background check on some of the candidates, for example, when you want to hire a manager.
Before you begin: Create a parent case type by using a rule form. For more information, see Creating a case type rule form in Dev Studio.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Process category, and then click Case Type.
  3. In the list of case types instances, open the case type that you want to edit.
  4. On the Process tab, in the Child case types section, in the text field, press the Down arrow key, and then select a case type that you want to use in the case type hierarchy.
    For example: Enter Run background check.
  5. Optional: To define how case types in the hierarchy exchange data, click Data propagation, and then define the sharing options for the data:
    1. In the Data Propagation dialog box, click Add property values.
    2. In the Propagate property value column, enter a source property from the parent case type.
      For example: Enter PhoneNumber.
    3. In the To property value column, enter a destination property in the child case type.
      For example: Enter ContactNumber.
      Result: At run time, your application populates the contact number in a Run background check child case type usinga value that a user provided for a phone number in a Review job candidate parent case type.
    4. Optional: To propagate values for more properties, repeat steps 5.a through 5.c.
    5. Optional: To use a data transform to pass the values, select the Apply data transform check box, and then, in the text field, enter a data transform.
    6. Click Submit.
  6. Optional: To define when the child case starts, click the Disclose icon, and then define case instantiation options:
    Allow users to start a child case manually at run time
    1. Select the Manual instantiation check box.
    2. Optional: To allow users to start the case only under certain circumstances, in the Permitted When field, enter a When rule that defines when a user can start a child case.
      For example: Select a When rule that allow users to start a Run a background check child case type only if a job candidate applies for a manager position.
    Start a child case automatically
    1. Select the Automatic instantiation check box.
    2. Select whether a child case starts together with a parent case or if a child case starts when a case fulfills the dependencies.
    3. Optional: If you configure a case type to start during a parent case creation, to allow case instantiation only under certain circumstances, in the Permitted When field, enter a When rule that defines when the child case starts.
      For example: Select a When rule that starts a Run a background check child case type only when a job candidate has less than five years of work experience.
    Tip: You can select both manual and automatic start of a case type. If the system cannot start a case type automatically, a user can start the case manually. If you skip defining case instantiation options, the system always starts the child case.
  7. Optional: To define additional child case type settings, click the Disclose icon, and then provide relevant values:
    1. Optional: To define how many instances of a child case the application can start at run time, in the Max Instances field, enter an integer.
    2. Optional: To indicate that the parent case type cannot reach resolution before the child case type is complete, select the Required check box.
  8. Optional: To add more child case types, click Add a row, and then repeat steps 4 through 7.
  9. Click Save.

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