About Specialization

The Specialization setting, on the Details tab of the Case Designer landing page, displays the number of circumstance-qualified (by property) case type instances for this base case type. Circumstanced case types can:

• Cover or be covered by other base or specialized case types.
• Be auto-instantiated (the system copies the circumstanced property onto the subcase).
• Use attachment categories and auto-attach functionality.
• Use the Stages display.
• Be used in Add Work submenus.
• Employ data propagation.

Select to create specialized case type rules. In the Specialization pop-up dialog, do the following:

1. Select a single value property in the Define new specialization for <case type name> on field (listed by the Description label on the Property rule form).
2. Beneath the property value area, click the Add Row icon ( ).
3. Enter a value that is consistent with the property type, or select one of the property's Table Type values.
4. Optional. Select the Create a Starting Process? check box so that the system creates a non-circumstanced copy of the starter flow Work-.pyStandardCMAssignment for this specialized case type. The name is a concatenation of the word "Start" and the property value. The flow does not appear in the Starting Process list on the specialized Case Type rule form or on the case types tree.
   
   You can test these flows use the Run option on the Flow rule form.
   Add the flows to the Starting Processes list on the circumstanced Case Type rule form's Processes tab so that users can add specialized cases from the Other Actions > Add Work submenu on user forms. Add the flows to the Supporting Processes list so that they can be started on the submenu.
   
   
5. Add another row to specify another value.
6. When finished, click OK to close the dialog and create the specialized copies. They appear on the Case Explorer, indented beneath the base rule node.
   
   The system copies the base rule's Starting Processes list to the specialized case type. If you add the specialized starter flow to the list on the base Case Type rule form, the flow appears in the Create menu (if the base case type is configured to appear).
   

If the base rule has a parent, the system does not automatically update the Coverable Work Types list on the parent Case Type rule form's Processes tab. You must manually add the specialized versions as described in Case Type rules — Completing the Processes tab.

To configure a specialized version as a parent, open its Case Type rule form (use the Open menu on the Explorer tree) and add the child case types to the Coverable Work Types list.

As a best practice, to take advantage of case management specialization features, use the Specialization option to circumstance the case type. You can circumstance the base rule by template or date property using the Save As form. However, the copy must also use a property value in order to work with the automated case management features described above. Copies that are circumstanced by date, date range, or template values are displayed on the tree in bold typeface beneath the base case type.

For an example, see PDN article When and how to use case specialization.

	case management, landing page, subcase,top-level case type, ad hoc work, cover, folder, case, instantiate, case type, Federated Case Management
	About Case Type rules About the Case Manager and Case Worker portals Process and Rules category — Case Management Gallery

Tools — Process and Rules
Designer Studio — About Landing Pages

Help Home