To bypass a task within a generic case

Parent Previous Next

The procedure to bypass a task within a generic case is as follows:

  1. Using the Advanced search spy-glass (), select Generic Case as the Search for and Search by category, and enter the Case ID as the search criteria 1.
  2. With the Results tab in current focus, double-click on the row containing the exact record match, or return to the Criteria tab and refine the search filters. The Generic Case Details window is displayed.
  3. Click on Tasks. The Tasks tab is activated, revealing all ad hoc tasks assigned to the generic case together with those included in the underlying workflow structure, as displayed in the Tasks summary table.
  4. Highlight the specific row matching the task to be skipped within the overall workflow path.
  5. Click on Task Actions. The Task Actions window is displayed.
  6. Using the Select action drop-down field, select the specific status progression value of Bypass Task 2.
  7. Click on Next. The Bypass Task window is displayed.
  8. Using the Bypass reason drop-down field, select a parameter value to qualify the circumstances surrounding the generic task being skipped within the overall workflow path 3.
  9. Use the Notes field to add contextual data in support of the generic task being skipped.
  10. Click on Save. On returning to the Tasks tab, the status of the generic task is set to Bypassed and the End date is stamped with the current system date and time; all dependent tasks within the overall workflow structure will be preserved, awaiting onward progression.


Note

1 Additional search criteria may need to be employed (e.g. start and end date ranges, company, status, category) to ensure that the correct generic case is returned; an alternative Search by category of Contact or Contact Group may be selected to extend the available search fields.

2 This option is active only for non-mandatory generic tasks included within a workflow path that are currently in progress i.e. with a status of Live.

3 These custom values can be populated by the end user via the general lookup parameter entitled Task Bypass Reasons.


See related topics...

Generic task progression management overview

To cancel a task within a generic case

To place a task on hold within a generic case

To define a general lookup parameter value

Using the search facility