William Baeyens (baeyw)
Sr. System Architect - Pega Consulting
Pegasystems Inc.
baeyw Member since 2019 8 posts
Posted: April 26, 2021
Last activity: April 26, 2021
Posted: 26 Apr 2021 3:51 EDT
Last activity: 26 Apr 2021 8:53 EDT

On using cases types to manage a "data object"


I was wondering about experiences or best practices in regards to using long-lived Case types instead of Data- classes to manage data objects. 

For example, using a "Customer" Case type that would represent a Customer record, allowing you to use some case processing on your customers (an email each year for his Birthday? A subcase to renew a recurring payment? Usage of case Audit functionality ?  etc ). 

Are there clear cons against this kind of practice?  Apart from making In-flight case handling potentially harder (but you can design around that) I personally can't see anything. 

What should we pay attention to when deciding on implementing this kind of design? 

Kind regards


***Edited by Moderator: Pooja Gadige to move from Pega Academy to Product, add platform capability tag***
Pega Platform 8.5.3 Case Management Senior System Architect