we have 4 different inactivity scheduler for different people (20 minutes, 30 minutes, 180 minutes, 360 minutes). Before we upgraded from 9.20 to 9.32 everything worked fine.
Since 9.32 we're only able to define one inactivity scheduler by menu (RAD kill.inactive.setup). So we decided to implement our own inactivity schedulers (like in 9.20) by adding 4 schedule entries like described in different other forum posts (application: kill.inactive, strings1: users which won't get by inactivity timer, 1 in number1=20 - for 20 minutes, 1 in times=00:20:00, 2 in times=00:10:00, repeat interval 00:05:00, class or scheduled class inactive2 - own defined process -- we also did a test with 2 in number1=10).
But the 4 inactivity schedulers won't be thrown. The process is still polling the 4 schedulers but no user will be thrown by the system.
Only the inactivity by the RAD kill.inactive.setup is working. In this case the timer will give a message every 5 minutes to the 30 minutes inactivity. If we change the 5 minutes to 20 minutes, the users will get a message "20 minutes to inactivity" every 5 minutes.
Now we tested about our problem that only the kill.inactive.setup-scheduler is working and found this:
- If this inactivity is stopped, no inactivity will work, also the own schedulers aren't working
-If we are deleting our own 4 schedulers, only the message will disappear one time
-Starting the inactivity timer by RAD kill.inactive.setup no scheduler is started, but the only 1 set inactivity will work.
Could anybody explain, what's going on here, and how to implement 4 different schedulers whithout an alert every 5 minutes?
this is the problem. If we start the inactivity timer (Menu: System Administration->Ongoing Maintenance->System->Start Inactivity Timer) then no scheduler entry is set. Also if we delete our existing schedulers and restart the Inactivity timer, no scheduler will be set, but inactivity timer works for the entries in System Inactivity Timer.
In the 9.32 release notes, it specifically mentions that the legacy inactive process is obsolete and has been replaced in 9.32 applications by the new process. (while it mentions backwards compatiblity, that applies only when using the 9.32 RTE with older application versions).
The custom inactivity timers probably all worked by starting additional instances of the legacy inactive processor, but that is deprecated in 9.32.
Operator Level Settings
Administrators can now configure the inactivity timer settings for a specific operator, by specifying
the Warning Time and Allowed Inactive Time fields on the Security tab of the operator record.
Operator level settings take precedence over system level settings specified in the Start Inactivity
From SM9.32 onwards you do not requires background process named ‘inactive’ and attached scheduler record. You just need to start the inactivity record in system which can be set from,
Menu navigator - > System Administration - > Ongoing Maintenance -> System -> Start Inactivity Timer
Also from SM9.32, in each operator record you can explicitly mention the Inactive and Warning time which precede over inactive record. These fields are placed at bottom of left column in Security tab of operator record.
Form name is same in all version of sm till now, that is, operator.g
If you have performed full application upgrade then you have to promote these fields or whole form in your system.
____________________________________ Assign Kudo, if found post useful and mark it accepted if solves the issue.