I’m building a feature in constellation that allows users to link cases across different case types. Initially, the feature will be launched from case-wide actions, and I plan to use a “search and select” pattern. However, the existing Case Reference Data pattern only supports searching within a single case type. Since users need to link cases across multiple case types, I need a way to search cases from the entire work pool instead of being limited to one type. How can I design or implement a search that works across multiple case types?
I don’t think there is an OOTB way of selecting multiple case types’ instances by using case reference field from App Studio as of now. But there is a work around for this. After creating your case reference property, Go to Dev Studio, Convert the property into advanced configuration. You can see that its simply a page list property configured with selected case class. Now, in dev studio create a new property similar to this and give page definition as your class group in which all your case types are present. Also create two data pages in your class group level(one list, one lookup). Configure the newly created look up data page in this property. Now, mark this property as relevant record and you can immediately see in the data model of the case type that this property also shows as case reference.
One limitation I see here is that this approach only works for case types under one class group.
I tried using Data Reference first. But the issue with data reference is, when I try to use Search and Select pattern, the list data page needs to have “Enable querying” option selected. But if it is selected, it directly passes SQL query to the data class table with this property which returns no results ultimately as that data class does not have our cases in it. If we don’t use a query enabled data page, then search and select filters do not work.
Thanks @VVNagaSaiN for the advice — we were able to meet our requirement using your approach. However, we’ve run into a challenge. We have multiple filters to support search, and some of these are based on fields from other tables, such as Address and Reference Number. When we apply filters using associations, the search does not return results as expected. It seems like this might be a limitation of the feature. The same works in list views using promoted filters but not using Advanced Search feature. We’re exploring possible workarounds—any suggestions or ideas would be greatly appreciated.
