An ad hoc case is a case that you can create to handle a business exception or track a related task in the case that you are currently processing. Because ad hoc cases are not instances of a case type, they are not part of your case-type hierarchy.
Operators employ ad hoc cases to efficiently handle exceptions that may arise in the course of expected business processing without having to wait for modification of the application's case type structure. For example, a human resource hiring specialist, after completing a phone interview, may want to perform a background check in order to continue with the hiring process. Since there is no background-check case type in the organization, the specialist creates an ad hoc case to track this work.
An ad hoc cases is an instance (called Simple Case) of class Work-Cover-SimpleCase, which is created by the standard Simple Case flow (pySimpleCaseWorkFlow). The case contains one assignment named Ad Hoc Case Dashboard in which operators create tasks that are processed as assignments in the standard Complete Task flow (Data-AdHocTask.WorkTask).
Note: Standard ad hoc starting flows Standard Ad-Hoc Task (pyManualTaskStandardAssignment) and Ad-Hoc Task Needing Manager Approval (pyManualTaskStandardApproval) are supported in existing configurations but are deprecated. Use pySimpleCaseWorkFlow instead.
At run time, an operator can create ad hoc cases in the Case Manager portal, user forms, and Pega Pulse.