Portals in applications
Case Manager portal — Using My Cases |
The My Cases page in the Case Manager portal initially displays, in the top-level nodes of a tree grid, all cases where the following are true:
Expanding a node shows the child cases.
Cases on this page refer to work instances belonging to case types defined on the Case Type Explorer, and use the same case-type icons. You can change the default icons using the Appearance option on the Detailstab in the Case Designer landing page.
To ensure that an operator's cases appear in this tab, name the operator in a work party rule referenced in the Work Parties Rule field on the top-level case type rule's Processes tab. Use the Details tab for a case type in the Case Designer landing page to edit this work party rule.
The case information, collected in the new case work harness, is displayed under the following fields:
Heading |
Description |
| Name |
Name of the case type as it appears in the Case Type 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 child cases of the same type with the same parent are nested beneath the child case name. |
| Item ID |
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. |
| My Roles |
The work item owner. See Ownership. |
| Creation Date |
The date and time the case was created by the user or by the system. |
| Urgency |
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. |
| Deadline |
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 agreement (.pyCaseTypeDefault), used by the .OverallSLA flow. You can set goals and deadlines on the Service-level agreement form or in the Case Designer. 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. |
| Status |
This item's work status (property Work-.pyStatusWork). |
The case-level and expanded child case lists use the Work-pyMyCasesReport and the Work-.pyLoadMyCasesNested report definitions, respectively. By default, the lists show a maximum of 500 items. You can modify this value by copying the rules and updating the Maximum Number of Rows To Retrieve field in the Data Access tab.
The user can do the following in the grid:
The Quick Create feature lets users create ad hoc cases to track work that is not instantiated from the current application's case type structure. See Working with ad hoc cases.
The user can perform the following actions by right-clicking an item and opening a context menu.
| Selection | Description |
| Open |
Open review user form . |
| Complete Item |
Resolve this case. Status becomes Resolved-Completed. The user cannot manually add a child case to a completed case. If this case has child cases, the field appears. The user selects the Yes radio button (default) to resolve them (includes direct and nested child cases). To resolve only the selected case, the user selects No. If one or more of the child cases must be resolved before the parent, and the user selects Yes, the system displays an error message indicating which child case(s) must be resolved. The system does not resolve any of the child cases. |
| Withdraw Item |
Reject and withdraw this case. Status becomes Resolved-Withdrawn. The user cannot manually add a child case to a withdrawn case. The user can resolve all child cases as described in the Complete Item above. |
| Configure for reuse |
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. |
| Actions |
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 child cases to the current case , or start processes that support this case. |
| Create Ad Hoc Case |
Create an ad hoc child case under the parent case or another ad hoc case. See |
After performing an action on this tab, the user can click Refresh to refresh the current page.
The sections in the My Cases tab can be localized to suit your requirements.
|
portals, case, assignment, flow |
|
About the Case Manager portal
About Portal rules Portals for application users Using the Case Type Explorer |