dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Ant,

What SQL command did you use to "set" the email notification? I am just
curious, as I have never actually done it, but just guessing that this
might work.

Note that the data looks like this

userinfoid |            name             |
             value
------------+-----------------------------+--------------------------------------------------------------------------------------------------
    2125003 | keyMessageEmailNotification |
\xaced0005737200116a6176612e6c616e672e426f6f6c65616ecd207280d59cfaee0200015a000576616c7565787001
    1979887 | keyMessageEmailNotification |
\xaced0005737200116a6176612e6c616e672e426f6f6c65616ecd207280d59cfaee0200015a000576616c7565787000

The first one should be when a user wishes to receive email, the second for
when they do not.  ( I think)

Is this what your table looks like?

Regards,
Jason


On Tue, Oct 27, 2015 at 8:19 AM, Knut Staring <knutst@xxxxxxxxx> wrote:

> Did you also clear the server cache? Alternatively restart Tomcat
> On Oct 27, 2015 8:16 AM, "Ant Snyman" <ant@xxxxxxxx> wrote:
>
>> Hi All,
>> We want to enable all the users to receive email notifications and is
>> looking for a way to do it in the backend via a SQL script (without having
>> each user go into Profile-- > Settings).
>>
>> We have seen the table "usersetting" which is populated when the email
>> notification is ticked on the UI. I played around by creating a user (with
>> email address) and populating this table with a SQL insert but then I do
>> not see the tick on the UI (after doing all the usual stuff like clearing
>> cache). The system then also do not pick up that this user must receive
>> email notifications.
>>
>> Where else in the database is the user flagged to receive email
>> notifications?
>>
>> Regards
>>
>> *Ant Snyman*
>>
>> *Cell: 0824910449 <0824910449>*
>>
>> *Landline: 028 2713242*
>>
>>
>> Health Information Systems Program - SA
>>
>> *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-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> 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
>
>


-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+46764147049