I have 2 different case types in the same class group.
1 separate group of users work on one case type and another on the other case type but they want to be able to see each others cases in readonly/review mode. Wouldn't that mean I need to have one application with all rulesets for both case types in the application/ruleset stack so that if users of one case type open cases from the other case type the rules for that other case type could be resolved to? The downside of having just 1 application is that there would be more potential for accidently breaking each other. One application and case type are already being worked on in production and I am developing the other case type now.
***Edited by Moderator Marissa to update platform capability tags****
Yeah that's the path I was going down but I saw something peculiar where I am able to open a case in review mode through "Recents" gadget that was created from a different application than the one I was currently logged into and it came up fine in Review harness. It looks like when I trace it it does an application switch for that thread when you click on it. So that's when I was not sure if I really needed a single application or not even though I would have my own custom gadget for users to search for cases for each case type. So because of how recents gadget is working I was unsure whether I would still need one single application.