Question2Replies43Views anand3846 Member since 2009 9 posts EY Posted: 9 months agoLast activity: 9 months ago Data Driven behavior in case life cycleHello,Can anyone explain to me the data driven behavior of weather case based in the data model exercise of the LSA 8 course, How it is configured for the weather case to close (without any when condition check depending on the Venue type? Pega Academy ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Posted: 9 months agoVicio.Pi Accenture replied to anand3846Hi, i am following this thread as the solution proposed is not downloadable and i am not sure to have understood the proposed solution steps. Are we talking about a boolean property within the Venue "intelligent" data model, used to skip stages within Weather case type? Thanks, V Posted: 9 months agopedel PEGA replied to anand3846It was originally planned to have this exercise but later was pulled. Unfortunately it made its way into the 8.3 LSA course by mistake. Pls ignore. It will be removed. Once upon a time it was thought it might be worthwhile to “flip the tables” between Work- and Data- using the Visitor Pattern. As opposed each case making every decision, at special extension points, a case could potentially “delegate” or "defer" what-happens-next decision-making to a Data instance. But each data instance type worth specializing still needs somewhere to store its process rules. The end result would be applying pattern-inheritance against the case, e.g., Work-CaseType-DataType. The difference is so minimal it was not worth the effort to use the Visitor pattern. Instead, simply change the pxObjClass of the case type when needed, e.g., .pxObjClass = D_CaseTypeDCR[DataType:].pxObjCass.