View source for Resolving work with ad hoc cases

Resolving work with ad hoc cases / ← When to use a dynamic case

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in one of the groups: Users, editor, pegaemployee.
• The action you have requested is limited to users in one of the groups: pegaemployee, editor, Administrators.

---

You can view and copy the source of this page.

{{Design pattern |Title=When to use a dynamic case |Description= Deciding when to use a dynamic case |Version= 8.4 |Applications= Pega Platform |Capability Area= Case Management |Owner=Potluri, krishna}} Ad hoc cases are similar to child cases but rather than being executed automatically, they are executed optionally, or on an as needed basis. The determination to use a dynamic case is a manual and an a dynamic process. For example, when opening a bank account, the banker learns that the customer opening the account has a high net worth and represents a lot of future business potential. The banker makes an ad hoc decision that they should do the following: * Send a hand-signed welcome letter from a branch president. * Schedule a follow-up phone call in one week with the client to welcome them to the bank. * Review results. Pega Platform™ enables knowledge workers to create ad hoc cases to manage these unexpected and dynamic tasks. The ad hoc cases are tracked in Pega Platform. If the bank finds that this is a common pattern for high net-worth clients, they should convert the ad hoc case into a child case that becomes a standard part of opening an account. == Related information == [https://community.pega.com/knowledgebase/articles/case-management/84/creating-ad-hoc-cases Creating ad hoc cases] [https://community.pega.com/knowledgebase/articles/case-management/84/empowering-knowledge-workers Empowering knowledge workers]

Return to When to use a dynamic case.