dhis2-users team mailing list archive

[Elmarie Claasen <elmarie@xxxxxxxx>]

Thanks all for the input, yes I don't think the base URL is set for the
server.
The rest mentioned are all correct.

For those doing manuals it would really be useful to add these dependencies
onto that part of the manuals.

Elmarie

On 03 Oct 2017 12:34, "Dan Cocos" <dcocos@xxxxxxxxx> wrote:

> Check in the logs for “ERROR” if the base URL for the server is not set it
> will fail and the error will only be present in the logs.
>
> *Dan Cocos*
> Principal, BAO Systems
> dcocos@xxxxxxxxxxxxxx <nhobby@xxxxxxxxxxxxxx> | http://www.baosystems.com
> |  2900 K Street, Suite 406, Washington D.C. 20007
> <https://maps.google.com/?q=2900+K+Street,+Suite+406,+Washington+D.C.+20007&entry=gmail&source=g>
>
>
>
> On Oct 3, 2017, at 5:14 AM, Adebusoye Anifalaje <busoye@xxxxxxxxxxxxxx>
> wrote:
>
> Hi Elmarie,
> The documentations states that  "They are sent via the internal DHIS2
> messaging system.”
>
> Have you checked if the notification is coming though on the dashboard
> messages?
>
> Best,
>
> - -
>
>
>
>
>
> *<Screen Shot 2017-09-07 at 09.01.09.png>Busoye Anifalaje (PhD)Director of
> Services (Principal), BAO SystemsUK: +44 7901-740-757 | US: +1 682
> <https://maps.google.com/?q=US:+%2B1+682&entry=gmail&source=g>-307-0986| busoye@xxxxxxxxxxxxxx
> <busoye@xxxxxxxxxxxxxx> | http://www.baosystems.com
> <http://www.baosystems.com/> |Skype: busoye | 2900 K Street, Suite 406,
> Washington D.C. 20007
> <https://maps.google.com/?q=2900+K+Street,+Suite+406,+Washington+D.C.+20007&entry=gmail&source=g>*
>
> On 3 Oct 2017, at 10:12, Elmarie Claasen <elmarie@xxxxxxxx> wrote:
>
> Hi Prosper,
>
>
> Analytics ran last night and monitoring was turned on then but did not
> receive any validation notifications.
>
>
> Regards,
>
>
> *Elmarie Claasen*
> <image001.png>
> Project Manager
> Health Information Systems Program
> Tel:      041-367 1027
> Cell:     082 374 2209
> E-mail: elmarie@xxxxxxxx
> Skype:  elmarie.claasen52
>
>
> *From:* Prosper BT [mailto:ptb3000@xxxxxxxxx]
> *Sent:* Tuesday, October 3, 2017 11:02 AM
> *To:* Elmarie Claasen <elmarie@xxxxxxxx>
> *Cc:* dhis1-users <dhis2-users@xxxxxxxxxxxxxxxxxxx>; dhis2-devs <
> dhis2-devs@xxxxxxxxxxxxxxxxxxx>
> *Subject:* Re: [Dhis2-users] Problem with setting up validation
> notifications
>
>
> Dear Elmarie,
>
>
> How are you testing this? because notifications will be sent out when
> analytics run and monitoring turned on
>
>
> Regards
>
>
>
>
>
> Prosper Behumbiize, MPH
> DHIS2 Implementation| HISP Uganda
> prosper@xxxxxxxxxxxxxx <ptb3000@xxxxxxxxx> | prosper@xxxxxxxxx | Skype:
> prospertb
>
>
> On Tue, Oct 3, 2017 at 11:39 AM, Elmarie Claasen <elmarie@xxxxxxxx> wrote:
>
> Hi Prosper,
>
>
> Thanks so going through this I now understand what the “Notify users in
> hierarchy only” is for. I have set it up in this manner described in the
> manual.
> However I still don’t understand why the system is not sending out
> notifications. Have I left anything out or is there a known bug?
>
>
> Regards,
>
>
> *Elmarie Claasen*
> <image001.png>
> Project Manager
> Health Information Systems Program
> Tel:      041-367 1027
> Cell:     082 374 2209
> E-mail: elmarie@xxxxxxxx
> Skype:  elmarie.claasen52
>
>
> *From:* Prosper BT [mailto:ptb3000@xxxxxxxxx]
> *Sent:* Tuesday, October 3, 2017 10:33 AM
> *To:* Elmarie Claasen <elmarie@xxxxxxxx>
> *Cc:* dhis1-users <dhis2-users@xxxxxxxxxxxxxxxxxxx>; dhis2-devs <
> dhis2-devs@xxxxxxxxxxxxxxxxxxx>
> *Subject:* Re: [Dhis2-users] Problem with setting up validation
> notifications
>
>
> Dear Elmarie,
>
>
> There is some guidance here on validation rules
> https://docs.dhis2.org/master/en/user/html/dhis2_user_
> manual_en_full.html#manage_validation_rule
>
>
> Regards
>
> Prosper Behumbiize, MPH
> DHIS2 Implementation| HISP Uganda
> prosper@xxxxxxxxxxxxxx <ptb3000@xxxxxxxxx> | prosper@xxxxxxxxx | Skype:
> prospertb
>
>
> On Tue, Oct 3, 2017 at 11:23 AM, Elmarie Claasen <elmarie@xxxxxxxx> wrote:
>
> Hi all,
>
>
> I am struggling to set up validation notifications on an aggregated
> instance with validation rules defined.
> I could not find guidance in the DHIS2 manuals specifically how to set
> this up.
> I followed the following:
>
> 1)      Validation rules are defined
>
> 2)      Added a validation notification template where I selected
> collective summary and left the “notify users in hierarchy unticked” since
> I don’t quite understand what that option would mean. Selected a user group
> to which this notification template should send notifications
>
> 3)      Under scheduling activated Data Monitoring to “All daily”
>
> 4)      We do have an email configured on the instance which is
> successfully sending out other mails e.g. forgot password notifications,
> password expiry notifications etc.
>
>
> What am I missing in the configuration as the particular user group do not
> receive notifications?
>
>
> Regards,
>
>
> *Elmarie Claasen*
> <image001.png>
> Project Manager
> Health Information Systems Program
> Tel:      041-367 1027
> Cell:     082 374 2209
> E-mail: elmarie@xxxxxxxx
> Skype:  elmarie.claasen52
>
>
>
>
>
> *This message and any attachments are subject to a disclaimer published
> at http://www.hisp.org/policies.html#comms_disclaimer
> <http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.  If you cannot access the
> disclaimer, kindly send an email to disclaimer@xxxxxxxx
> <disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.*
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
>
> *This message and any attachments are subject to a disclaimer published
> at http://www.hisp.org/policies.html#comms_disclaimer
> <http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.  If you cannot access the
> disclaimer, kindly send an email to disclaimer@xxxxxxxx
> <disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.*
>
>
>
> *This message and any attachments are subject to a disclaimer published
> at http://www.hisp.org/policies.html#comms_disclaimer
> <http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.  If you cannot access the
> disclaimer, kindly send an email to disclaimer@xxxxxxxx
> <disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.*
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>
>

-- 


*This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer 
<http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the 
disclaimer before opening any attachment or taking any other action in 
terms of this electronic transmission.  If you cannot access the 
disclaimer, kindly send an email to disclaimer@xxxxxxxx 
<disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to 
this e-mail or opening any attachment you agree to be bound by the 
provisions of the disclaimer.*