PVXS QSRV2 complains on LoadedModules Group PV

Hello guys! The new group PV that shows the modules and versions as a NTTable is GREAT! This is from a simple test:

pvget TEST:iocuser-12099:LoadedModules
TEST:iocuser-12099:LoadedModules 
     Module  Version
    require    5.1.0
  adsupport 1.10.0+4
       asyn 4.44.2+0
     adcore 3.13.0+0
     admisc 30d2f726
   autosave 5.11.0+0
       busy  1.7.3+2
  sequencer  2.2.9+4
       calc  3.7.5+0
   caputlog  4.0.0+8
    devlib2 2.12.0+0
   iocstats  3.2.0+1
    recsync  1.5.0+1
     essioc  2.1.2+0
       nds3  3.0.0+3
  nds3epics  1.0.2+1
     fimioc  2.3.0+0
        tsc  4.0.9+3
  ifcdaqdrv  develop
iocmetadata  0.1.0+2
 iocshutils 2.10.0+2
       loki  1.0.0+3
 mcoreutils  1.2.2+1
    mrfioc2  2.3.1+9
       pcre 8.44.0+3
      s7plc  1.5.2+1
      sscan 2.11.5+4
        std  3.6.4+0
     stream 2.8.24+2
       xdma  1.0.0+3
       pvxs  1.3.1+0

This is actually not a real issue, but when testing with PVXS and QSRV2, I get the following warning:

2024-04-19T15:53:43.064337295 WARN pvxs.ioc.group.processor
     Group TEST:iocuser-12099:LoadedModules defines no +trigger mappings.  Default to individual/split monitor updates.

I did struggle with this +trigger mapping in the past, so one possible way to overcome that is to have a sequential process on all the records from the moduleversion.template (with FLNK fields) and set the +trigger mapping to the last record of the chain. This makes more sense when the records are actually updating and processing (not the case of these ones), but at least we get rid of this message. I will try to do this next week and see how it goes.