- fix condition for alarm not being configured in alarm table

Alarm can be recognised as replaceable in catalog in two cases:

 * if alarm_date from catalog is empty (existing case)
 * if alarm is not existing in catalog yet (case added by changing indentation)

Second case happens during first indexation.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31573 20353a03-c40f-0410-a6d1-a30d3c3de9de

product/ERP5/Document/Alarm.py

@@ -597,6 +597,7 @@ Alarm Tool Node: %s
         # convert the date to the user provided timezone
         alarm_zone = periodicity_start_date.timezone()
         alarm_date = alarm_date.toZone(alarm_zone)
+
     return alarm_date
 
   # XXX there seem to be something which wants to call setters against