Skip to main content

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

Specializing a case type

Updated on November 15, 2021

Specialize a case type to support variations in the way that cases are processed in your application. Each version that you create is uniquely identified by a circumstance.

Tip: Specialized versions are not automatically added to the parent case types of your base case type. Open the Case Type form for each parent case type to add your specialized version as a child.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. On the Settings tab, click Specialization.
  3. Press the Down Arrow key in the autocomplete field and select the name of a single-value property.

    Note: Case types support specialization by a single-value property. The property that you specify is used for this version and all future, specialized versions that you create. This means that the autocomplete field is hidden the next time that you follow this procedure.

  4. Click + Add specialization.
  5. Define a property value for the circumstance by using one of the following fields:
    • Text input — Enter a string value without quotes that is consistent with the property type.

      For example, enter 100 for a property that stores integer error codes.

    • Drop-down list — Select a value that maps to an entry from the property's configured table type.

      For example, select XL when the property is configured as a local list of clothing sizes.

  6. Click Save.

The values that you provide are used to create a specialized version of the base case type. To view your specialized case types in the Case Type Explorer, expand the name of a base case type.

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