From ca65c74ee0866f762dbe100ee0abb3fff4baa162 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9rome=20Perrin?= <jerome@nexedi.com>
Date: Wed, 27 Dec 2017 06:03:01 +0000
Subject: [PATCH] administration: workaround alarm.getLastActiveProcess not
during alarm execution
At this point, the alarm is active, but active process for this activity
was not created yet. By passing include_active, the latest active
process will be returned (not the previous one)
Honnestly, not sure if this falls into workaround or non documented
normal use case for include_active=True.
---
.../erp5_administration/Alarm_activateCheckConsistency.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bt5/erp5_administration/SkinTemplateItem/portal_skins/erp5_administration/Alarm_activateCheckConsistency.py b/bt5/erp5_administration/SkinTemplateItem/portal_skins/erp5_administration/Alarm_activateCheckConsistency.py
index 21609e7f4e..b693175e58 100644
--- a/bt5/erp5_administration/SkinTemplateItem/portal_skins/erp5_administration/Alarm_activateCheckConsistency.py
+++ b/bt5/erp5_administration/SkinTemplateItem/portal_skins/erp5_administration/Alarm_activateCheckConsistency.py
@@ -1,7 +1,7 @@
kw = {}
if context.getProperty('incremental_check'):
- last_active_process = context.getLastActiveProcess()
+ last_active_process = context.getLastActiveProcess(include_active=True)
if last_active_process is not None:
kw['indexation_timestamp'] = {
'query': last_active_process.getStartDate(),
--
2.30.9