Case Manager portal — Using My Cases

Heading

Description

Name of the case type as it appears in the Case Explorer. If available, appends the customer name (.pyCustomerName) to the case name. If the item is ad hoc work, the name is New ad hoc work for: <case type name>.

Two or more subcases of the same type with the same parent are nested beneath the subcase name.

The unique identifier assigned by the application to this case. A prefix or suffix portion of this identifier can help users remember the application or work type. By default, ad hoc instances use the prefix "C-". See Understanding work item IDs.

The work item owner. See Ownership.

The date and time the case was created by the user or by the system.

Indicates the case's urgency value. By default, a value of 10 is considered of normal priority. A red urgency clock in the row header indicates that the item has an urgency value equal to or greater than 60. A yellow urgency clock indicates an urgency value from 30 to 60. The rest are indicated by a green urgency clock .

For this case, the time remaining from the current time to the overall deadline time, or the time elapsed from the deadline to the current time. The deadline time is specified this case type's service level rule (.pyCaseTypeDefault), used by the .OverallSLA flow.

You can set goals and deadlines in the service level rule, or using the Goals and Deadlines option on the Details tab in the Case Designer landing page. The time appears in yellow if the case has exceeded its goal but not its deadline; in red if the deadline is exceeded. A blank value in this field indicates that the Goals and Deadlines option has not been initialized, or that the service level rule is not present in this case type class.

See Using the Cases Explorer.

This item's work status (property Work-.pyStatusWork).

Open review user form .

Resolve this case. Status becomes Resolved-Completed. The user cannot manually add a subcase to a completed case.

If this case has subcases, the Would you like to mark all the subcases as Complete? field appears. The user selects the Yes radio button (default) to resolve them (includes direct and nested subcases). To resolve only the selected case, the user selects No.

If one or more of the subcases must be resolved before the parent, and the user selects Yes, the system displays an error message indicating which subcase(s) must be resolved. The system does not resolve any of the subcases.

Reject and withdraw this case. Status becomes Resolved-Withdrawn. The user cannot manually add a subcase to a withdrawn case.

The user can resolve all subcases as described in the Complete Item above.

This option is available only for ad hoc cases, and appears only if the operator's access group references the standard pyPega-ProcessEngine:CaseDesigner role, which contains the privilege .pyCaseInstitutionalize. The option enables an operator to convert ad hoc case to a case types in the current application's case type structure.

See Working with ad hoc cases.

Enables the user to start local or connector flow actions defined in the flow. The menu also provides an Add Work submenu, so that user can add subcases to the current case , or start processes that support this case.

See Working with ad hoc cases.

Create an ad hoc subcase under the parent case or another ad hoc case. See