|
Select a case type in the Cases Explorer to open its Case Designer landing page in the Designer Studio work area. The case type name appears at the top of the page, which contains three tabs, Stages & Processes, Details, and Specifications.
Use this tab to design your application by describing the stages within a case type, and then define the steps or processes that happen in each stage. This approach provides an easy way to capture objectives in a single view that allows all team members get a clear understanding of how each case type works and progresses in the context of the overall application. See Using the Stages & Processes tab for more information.
Stages represent show where a case is at any time during its process lifecycle — from creation to resolution. For example, a purchase request case can have these stages in this sequence.
Within each stage, a case progresses through required processes and some optional processes. For instance, during the Procurement stage, steps include sending email, entering accounting information, creating the order, and waiting for fulfillment.
By designing with stages, you do not need one primary flow using sub flows and alternate paths with decision shapes. Building stages and the processes inside them provides a realistic and intuitive representation of business scenarios as users would experience them. Because stages orchestrate processes, each can be designed independently, which promotes reuse.
Click the Configure process detail link to view a stage's in Process Outline. Here you can create, view, and configure the properties or processes as they will be implemented in each application stage. See Flows - Process Modeler basics.
Use this tab to configure processing behavior for each of the case types.
Most of the settings on this tab update the case type rule. Make sure that there is an unlocked RuleSet version in the current application that enables the system to update or copy the case type rule.
The table describes the items. Select the link next to each item to update its settings.
Item |
Description |
| Case-wide Supporting Processes | The number of supporting processes for this case type. Like spinoff flows, supporting processes are used for out-of-sequence assignments that can run concurrently with the main process. See About Supporting Processes for details. |
| Case-wide local actions | Specify local actions that are available to this case type only. Enter the local action and optionally a when rule to define a condition that must be met before the local action becomes available. |
| Attachments |
The number of attachment categories associated with this case. Select the link to add, remove, or update categories. Click OK to apply your updates. For a description of this feature and how to use the dialog, see Case Type rules — Completing the Attachment Categories tab. |
| Appearance |
The image that visually identifies the case type on the Case Manager portal My Cases list, and on the tabs of case items on Designer Studio. Select to open the Appearance pop-up dialog. Click the radio button next to the image you want, and click OK to close the dialog and save your edits.
|
| Calculations |
The number of target numeric properties for this subcase type that will be summed when specified subcase type property values are updated. Appears only if this case type is a parent to other subcase types. Select to specify one or more target numeric property values and the input property values in one or more of its subcases. These settings also appear on the Case Type rule form's Calculations tab. See Completing the Calculations tab. |
| Email instantiation | Only available for top-level cases. Configure email instantiation for a top-level case. See About Email Instantiation for details about setting up email instantiation. |
| Data Propagation | Only available for case type that is a parent to one or more case types. The number of properties configured for data propagation among the subcases covered by this parent case. See About Propagation for details. |
| Instantiation | Only available for subcase types. Configure manual or automatic instantiation for a subcase. When you select this option, the Instantiation pop-up dialog appears. See About Instantiation for details about setting up manual or automatic instantiation. |
| Locking |
Configure locking behavior for this case type. The Default Locking and Optimistic Locking options are available only on top-level case types. The setting automatically propagates to all of its subcase types and cannot be overridden. Default Locking — Sets to standard locking behavior; the system locks a case when it is opened by a user for a period of 30 minutes. No other user can open and work on it. You can change the standard time period in the Custom timeout field. This conservative approach helps ensure that data can be updated in both parent and subcases with transaction integrity. For example, the parent case may contain properties that count or total values in the subcase. Locking both at once helps keep these counts or totals in synch. Optimistic Locking — Enables multiple users to open and review or work on a single case at the same time. When the first user submits the updates, other users are notified that the case has been updated when they attempt to commit their updates. Those users can either:
Do not lock the parent case when the child case is being performed — Available only on subcase types when Default Locking option is set at the top-level case type. By default, when a user opens a subcase, its parent case is also locked. Select to prevent locking the parent. Use this setting if the conservative approach is considered unnecessary and hinders worker throughput. |
| Goals and Deadlines | Goal and deadline times from the start of this case, its parent, or the top-level case to the case's resolution. See About Goals and Deadlines for details. |
| Parties |
Appears if the Case Type rule's Details tab has a work parties rule specified in the Work Parties Rule field. Displays the number of roles configured defined in the rule. When you create a case type either in Application Express or the Cases Explorer, the system creates an instance of pyCaseManagementDefault work party rule in your case type. Select to edit the rule. Click OK to close the dialog, update the work parties rule, and save it. See Work Parties form - Completing the Valid Parties tab
|
| Specialization | For this base case type, the number of circumstance-qualified (by property) case type instances. Circumstanced case types can:
See About Specialization for details. |
| Status Stages |
The number of status stages defined for this case type. Status stages are work-status based "Where-am-I" graphical display on user forms. A horizontal array of read-only chevron images ( |
| Validation | Links to OnAdd and Validate validate rules used by this case type. By default, the system uses Work-Cover-.OnAdd and Work-Cover-.Validate rules whenever a case is created or updated.
You can customize these standard rules by copying them into the case type's Applies To class. Retain the names |
| Duplicate search | Click Edit to launch a modal that allows you edit the Case Match rule to specify potential duplicate cases and assign weighted match conditions. See Case Match rule for details. Specify conditions that must match, or evaluate to True, and create weighted match conditions. When a case meets all of the Must Match conditions, AND the threshold for the sum of weighted conditions, it meets the criteria for being a potentially duplicate case, and is displayed to the end user at run-time. |
| Geolocation tracking |
Indicates whether the geolocation tracking feature is Enabled or Disabled. To alternate the settings, click Edit to open the Geolocation tracking dialog. When you change the default geolocation tracking setting for the first time, the system copies the standard when rule pyGeolocationTrackingIsEnabled to the case type. You can customize the when to suit your requirements. If you edit it, the label Custom appears. Click Edit to open the rule. |
Use this tab to view, modify, or add specifications to the selected case type. You can perform the following actions:
. For information about using these options, see Application Profile page — Requirements, Specifications, and Analysis tabs.
> Copy in the right hand column of the row containing the specification that you want to copy. The edit form opens, so that you can update the information for the copy and save it. See Add/Edit Specification dialog . > Delete in the right hand column of the row containing the specification that you want to delete. The specification is deleted from the system.> Document in the right hand column of the row containing the specification that you want to document or print. The system generates a Microsoft Word document with the information from the specification, opens Microsoft Word on your local system, and loads the generated document. In the Microsoft Word window, you can save a copy of the generated document to your local system, or print it. Use the buttons and menus on the landing page header as follows:
Item |
Description |
| Save |
Save updates on all tabs. If you do not want to save your edits, click Close to exit the landing page.
|
| Edit stages |
Open the Edit Primary Stages dialog and add, edit, or delete the stages in the Stages & Processes tab. |
| Run |
Create a case for this case type. |
| Actions |
This menu provides the following items:
|
| Close |
Exit and close the landing page. Edits will be lost when you close the page without clicking Save first. |
About Case Designer landing pages
An image specified in the Icon field for this case type on the Application rule form's 
A work parties rule specified in the Case Type rule is the default for any starting flows in that work type, overriding a work parties rule referenced on the Flow Rule form's 
) presents the user with a high-level view of the individual tasks that must be performed in order to resolve the case. The array provides a breadcrumb trail; highlighted chevrons indicate stages that have been completed. See 
Tools — Process and Rules
Help Home