From d49f53af0ecd3982ea27f2b95201ec91b1fb4b03 Mon Sep 17 00:00:00 2001 From: Remington Steed Date: Mon, 2 Mar 2015 16:54:56 -0500 Subject: [PATCH] LP#1205072: Correct and clarify the upgrade notes Signed-off-by: Remington Steed Signed-off-by: Dan Wells --- .../Administration/action-trigger-granularity.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/RELEASE_NOTES_NEXT/Administration/action-trigger-granularity.txt b/docs/RELEASE_NOTES_NEXT/Administration/action-trigger-granularity.txt index 215e6c6cdf..51f315c1ef 100644 --- a/docs/RELEASE_NOTES_NEXT/Administration/action-trigger-granularity.txt +++ b/docs/RELEASE_NOTES_NEXT/Administration/action-trigger-granularity.txt @@ -4,8 +4,10 @@ The 'granularity' field in the staff client Action Trigger Event Definition configuration interface (Admin -> Local Administration -> Notifications / Action Triggers) is now case sensitive. Previously, entering, for example, 'hourly' would be automatically modified to -'Hourly'. Now, 'hourly' and 'Hourly' are each valid, distinct values. +'Hourly'. Now, 'hourly' and 'Hourly' are each valid, distinct values, +and the form field now always provides the lowercase value. -This is important because the granularitiy values configured on the +This is important because the granularity values configured on the server for processing action/trigger events are case sensitive as -well. +well. When upgrading, please check that your saved values match the +values used in your crontab. -- 2.11.0