dhis2-devs team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 1156
committer: Lars Helge Overland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Wed 2014-07-23 14:39:27 +0200
message:
  Maintenance mode docs
modified:
  src/docbkx/en/dhis2_user_man_settings.xml


--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs

Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription

=== modified file 'src/docbkx/en/dhis2_user_man_settings.xml'
--- src/docbkx/en/dhis2_user_man_settings.xml	2014-07-12 11:09:00 +0000
+++ src/docbkx/en/dhis2_user_man_settings.xml	2014-07-23 12:39:27 +0000
@@ -62,16 +62,27 @@
               .</para>
         </listitem>
         <listitem>
-          <para>Omit indicator values with zero numerator value in data mart: Defines whether aggregated indicator values with zero as the
-            numerator value should be written to the indicator data mart table. Having such values written is required for instance when
-            connecting Excel pivot tables to the data mart as Excel will need the numerator data to correctly aggregate up in the
-            organisation unit hierarchy. If third-party tools like Excel are not used with the application this will reduce the total number
-            of values written to the data mart (which again will improve performance) and could safely be set to omit.</para>
-        </listitem>
-        <listitem>
-          <para>Enable multi-organisation unit forms: Enable support for entering data forms for multiple organisation units at the same
-            time, in data entry, click on the parent organisation unit for the children that you want to enter data for, and the dataset
-            list will include datasets that are assigned to the children of that parent.</para>
+          <para>Enable multi-organisation unit forms: Enable support for entering data forms for
+            multiple organisation units at the same time, in data entry, click on the parent
+            organisation unit for the children that you want to enter data for, and the dataset list
+            will include datasets that are assigned to the children of that parent.</para>
+        </listitem>
+        <listitem>
+          <para>Omit indicator values with zero numerator value in data mart: Defines whether
+            aggregated indicator values with zero as the numerator value should be written to the
+            indicator data mart table. Having such values written is required for instance when
+            connecting Excel pivot tables to the data mart as Excel will need the numerator data to
+            correctly aggregate up in the organisation unit hierarchy. If third-party tools like
+            Excel are not used with the application this will reduce the total number of values
+            written to the data mart (which again will improve performance) and could safely be set
+            to omit.</para>
+        </listitem>
+        <listitem>
+          <para>Put analytics in maintenance mode: Puts the analytics engine / Web API resource in
+            maintenance mode, implying that 503 Service Unavailable will be returned for all
+            requests. This is useful when you need to perform maintenance on the server like
+            rebuilding indexes while the server is running in production, in order to reduce load
+            and more efficiently carry out the maintenanec.</para>
         </listitem>
       </itemizedlist>
     </section>
@@ -153,9 +164,9 @@
             grant the user roles they are granted themselves to others.</para>
         </listitem>
         <listitem>
-          <para>Users must belong to a group controlled by the user manager: This allows user groups
-            to play a role in user management. When checked, user A can manage user B only if user
-            B belongs to a user group to which user A has read/write access. When user A creates a
+          <para>Users must belong to a group controlled by the user manager: This allows user groups
+            to play a role in user management. When checked, user A can manage user B only if user
+            B belongs to a user group to which user A has read/write access. When user A creates a
             new user, she or he must assign the new user to such a user group.</para>
         </listitem>
         <listitem>