Several standard rules are available for your use in the @baseclass, Work- class, or other classes. Your custom harnesses typically override these by using the same Purpose key part.
Harness |
Description |
More |
| @baseclass. ActivityStatusSuccess |
Presents a form when a top-level activity completes with presenting an HTML display. ("The operation completed successfully, but returned no content." with green checkmark.) | How to customize the activity success and exception windows |
| @baseclass. ActivityStatus ExceptionHandler |
Presents a form when an activity fails or an uncaught Java exception occurs. ("Please contact your System Administrator ." with red X.) | How to customize the activity success and exception windows |
| AutoClose | Closes the work object form automatically; an alternative to Confirm when there is no new information to display. | |
| Confirm | Presents a read-only confirmation display of the work item, acknowledging user completion of an assignment. It contains the Next Assignment option., which by default is linked to the standard activity Work-.GetNextWork. Your application can override that activity. | Maximizing User Productivity with GetNextWork |
| DisplayInput | Special purpose, not for use in BPM applications that use flows. | business rules engine |
| DisplayOutput | Special purpose, not for use in BPM applications that use flows. | business rules engine |
Purpose |
Description |
More |
| LockInfo | For diagnostic or debugging purposes, displays the requestor session holding a lock on the work object. | Understanding object locking |
| Work-.New | Supports entry of a new work item and the start of a flow rule execution for that work item. | Working with user forms |
| NewCovered | Allows a user to create both a cover work item and in the same form create one or more covered work items. | cover |
| NewSample | For work item creation. Incorporates styles from the standard User skin rule, introduced in Version 5.3. | |
| Work-.Perform | Allows a user to select a flow action from a drop-down list in the Take Action section, and complete an assignment based on the selection. | |
| Perform_Buttons | Allows a user to select a flow action by clicking a button, rather than choosing from a selection list. | Used primarily in PRPC Version 5 applications. |
| Perform_Step | Allows a user to complete the flow action marked as most likely immediately, rather than choosing this action from a selection list. | Used primarily in PRPC Version 5 applications. |
| PerformExternal | Supports directed Web access. | External assignments through directed Web access |
| PerformSample | Simple harness with Take Action area. | |
| PerformScreenFlow | Supports execution of screen flows with breadcrumbs. | screen flow |
| PortletHarness | A template rule for building application harnesses, configured to generate portlet-compliant HTML. | |
| PrintOptions | Allows a user to select which top-level sections are to be printed. | |
| PrintView | Provides a presentation of a work object suitable for printing. | |
| pyCMConfirm | Deprecated. Use Work-.Confirm. | |
| pyCMPerform | Deprecated. Use Work.-Perform | |
| pyCMReview | Deprecated. Use Work.-Review. |
Purpose |
Description |
More |
| Reopen | Allows a user to reopen a resolved work item. | Reopening a resolved case |
| Review | Presents the work item and assignment in read-only mode, not allowing data entry. | |
| ReviewSample | Presents the work item and assignment in read-only mode, not allowing data entry. | |
| RuleForm | Second key part of multiple standard harnesses that define the structure of rule forms. Reserved. | |
| SimpleConfirm | Similar to the Confirm harness, but with portlet-compliant HTML. Use this version when your flow application is a JSR 168 portlet that will be displayed by a portal server. | |
| SimplePerform | Similar to the Perform harness, but with portlet-compliant HTML. Use this version of the Perform harness when your flow application is a JSR 168 portlet that will be displayed by a portal server. | |
| TabbedScreenFlow | Supports execution of screen flows with a tabbed layout. If the primary screen flow calls a subflow screen flow, a second level of nested tabs appears. | screen flow |
| TreeNavigation | Alternative for screen flows, where a left tree structure presents flow navigation details. | screen flow |