Posted: 25 May 2018 5:03 EDT Last activity: 25 Jun 2018 15:17 EDT
Create case types in existing application
We are upgrading an application to 7.3.1 from a prior version. We have been requested to check feasibility of creating case types in existing application. I understand that technically we can create case type and we can reuse some flow rules in stages. However I think this change may have severe impact on the in-flight work objects if assignments or flow hierarchy is changed by any chance. I would like to know -
1. Has anyone done case type conversation in existing application post Pega7 upgrade? If yes, what is the suggested approach?
2. Was there any impact on the in-flight workobjects in production?
Thanks in advance.
***Edited by Moderator Marissa to update platform capability tags***
Thanks Asif for your response but my questions are little different. I want know whether or not anyone attempted to create case types after Pega7 upgrade and was there any impact on the in-flight workobjects.
I am not sure but I think creating case types may cause serious problems for inflight workobjects as casetypes may crate conflict with the pxFlow structure. Again I am not sure on this part, I will try to do some poc. Hence I looking for suggestion in this area.
While I have no direct experience with this I assume you are not the first person to attempt it. It shouldn't impact your in-flight items, so long as your flows and the specific assignment shapes the items are assigned to continue to exist (i.e. the assignment object agrees with pxFlow on the work object and they both agree with the current flow found by rule resolution). Depending on how involved you go, there may be challenges if you want to add functionality that puts data on the work object up front that is referred to downstream, since your in-flight items won't have that. I can't actually think of a scenario where that's how things work OOTB, but it is a real possibility. But for a simple case type, I believe you should be okay. I'd still want to test those cases, to be sure there aren't any surprises as part of your development/QA process.