Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.
The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.
💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.
🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.
Start by sharing what could be better - the community and our teams will help take it from there.
I am not an intersystems dev, so just sharing thoughts out loud I guess.
My first thought was a workflow where you would add a criteria that would look something like "SourceConfigName.Category" = "XYZCategory", which is not something that exists today. I thought maybe a custom criterion type could be created, but the dropdown options are hardcoded unfortunately. Adding one is probably a bad idea?
My next thought was a search index that somehow associates the message to a category, but that would be a new search table entry for every message and every category for each operation with that set, which sounds like a storage nightmare.
My last thought was maybe you could generate saved searches based on your categories then use those to pre-populate the list of SourceConfigs that are applicable. There is a table for saved searches (EnsPortal_MsgFilter.SavedSearch) although I haven't figured out how those are formatted, or how to generate one.