When we introduced the Risk to Children alerts and badges in Mosaic 20.1, we carefully considered the implementation of this. As the Risk to Children register was likely to already exist for many, if not all, customers, there would be records that were recorded as being on the Risk to Children register long before this functionality was introduced. The fact that they were on the register would show on their own person record already, but would not have triggered any badges on related people or co-habitees - or triggered alerts to relevant workers.
β
We decided that if we were to trigger this functionality on historic register entries immediately, there was a risk of suddenly showing badges and alerts for someone who should have been removed from the register previously, may have been a person of concern but proved not to be a risk, etc. The conclusion was that it would be better to ask that this list was reviewed after the functionality was available/switched on by yourselves - and anyone who was correctly on the register should have their registration deleted and re-added manually from the front end, which would allow the badges and alerts to be triggered at that point.
β
We did amend the alerts guidance in the Mosaic guides to highlight this. However, we now recognise that not all customers would have consulted this prior to taking the upgrade/enabling the functionality, as the key information needed for configuration was in the release notes.
β
A knowledge article is available here advising of these requirements. We recommend that customers using this functionality review the Risk to Children register entrants and re-add any relevant person records to the register to trigger the relevant alerts and badges.
Risk to Children alerts and badges
In this article, we explain why alerts or badges may not appear for individuals linked to someone on the Risk to Children Register.
Y
Written by Yusef Abulaynain
Updated over 5 months ago