I appreciate sending a message afterwards forces the cache to be reset but this does not meet the requirements – I would like messages to be hidden and then made visible based on a business logic status change and not when a message happens to be sent. Desired behaviour:
1. General message exchange, some messages read and some unread.
2. business process reaches a particular status and message are all hidden and the unread message count has unread hidden messages removed.
3. business process reaches another status and message are unhidden and the unread message count now includes the count of those previously hidden messages.
Currently, If I move the business process to a state where they are supposed to be hidden, the messages are hidden and the unread count seems to be correct. However, when I move the process to the state where messages are visible again, they don’t get shown until I send another message to that user again.