topic Default emailFeedDisabled to true for new users in Alfresco Forum

Default emailFeedDisabled to true for new users

dshookowsky — Wed, 11 Jul 2018 14:57:00 GMT

I know that I can post to /alfresco/service/slingshot/profile/userprofile with a json payload { "username": "user@example.org", "properties":{"cm:emailFeedDisabled": true } } to disable the setting for individual users.Unfortunately, that only works for existing users and I'd have to repeat the proc

Re: Default emailFeedDisabled to true for new users

cesarista — Wed, 11 Jul 2018 15:28:30 GMT

A possibility is to define a quartz job that is run daily after LDAP users sync.

The job would run a query for obtaining those users whose emailFeedDisabled parameter is true, and then you may iterate over them and change the corresponding parameter to false.

Regards.

--C.

Re: Default emailFeedDisabled to true for new users

dshookowsky — Wed, 11 Jul 2018 20:58:07 GMT

We're not doing a full directory sync at the moment. Users are added as they authenticate. It looks like we have to somehow override the user model to provide the property value, but I was hoping for something simpler, like a configuration flag in a property file or database field.

Re: Default emailFeedDisabled to true for new users

afaust — Wed, 11 Jul 2018 21:26:44 GMT

Alternatively, a regular onCreateNode policy on cmerson should do the trick, and you can set the preferences JSON to a default value including disabling the feed.

Re: Default emailFeedDisabled to true for new users

cesarista — Wed, 11 Jul 2018 21:54:33 GMT

Yes, Axel's option is the most suitable in fact. I remember an old example of policy (by Jared Ottey) for setting quota on created users that should be very similar to this case. But Daniel, you will have to program a little bit (in both cases).

GitHub - Redpill-Linpro/alfresco-defaultquota-policy: This module adds a policy allowing you to set the Default Quota wh…

Regards.

--C.

Re: Default emailFeedDisabled to true for new users

dshookowsky — Wed, 11 Jul 2018 23:53:59 GMT

Thanks to both of you for the quick responses. This looks like a good approach.