Project

General

Profile

Actions

Feature proposal #6982

closed

Improve notification actions with optional field value check

Added by krileon over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
Start date:
15 January 2018
Due date:
% Done:

100%

Estimated time:

Description

It'd be useful for notifications to be able to be toggled on/off from a standardized field format. If the field exists it'd check if the field has a value of 1 (checkbox field). If it doesn't exist then pretend it's a value of 1. This would allow admins to create fields to toggle notifications on/off on a per recipient basis.

Actions #1

Updated by krileon over 6 years ago

Probably something like cb_notification_systemaction. Examples as follows.

cb_notification_comment
cb_notification_comment_reply

Actions #2

Updated by krileon over 6 years ago

The following will now be checked. If the field doesn't exist it's simply ignored. If it does then its value can not be 0.

cb_notif_request_conn
cb_notif_accepted_conn
cb_notif_rejected_conn
cb_notif_comment
cb_notif_comment_reply
cb_notif_tag
cb_notif_like
cb_notif_gallery_conn
cb_notif_gallery_comment
cb_notif_gallery_tag
cb_notif_gallery_like
cb_notif_blog_conn
cb_notif_group_create_conn
cb_notif_group_join_conn

The GJ notifications that override normal GJ notification behavior do not support this since it has its own means for toggling off notifications. Where the above are supported is noted in their system action descriptions. Descriptions also suggest using a checkbox field.

Actions #3

Updated by krileon over 6 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100
Actions #4

Updated by krileon about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF