Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/5f8c4b07446e8ad1#

Hi everyone,

Not too long ago we have started the discussion for adding new
functionality called "Email Event Subcriptions". We have discussed
quite a few options there and come up some basic plan which I'd like
to finalize in this discussion and finally create a new Feature
Request for this.===

Goal

...

...

  1. We need flexible way of subscribing users (and/or Emails) to

...

  1. different types of actions.

...

  1.  For example I wish to subscribe to receive an email when:

      ...

        1. New TOPIC is added to the Forum Category (now TOPIC.ADD event

      ...

        1. triggered) so it's CATEGORY level subscription.

      ...

        1. New POST is added to the TOPIC (now POST.ADD event triggered) so

      ...

        1. it's TOPIC level subscription.

      ...

        1. New CATEGORY is added

      ...

        1. Category is modified

      ...

        1. ANY type of resource that we have Event changed

      ...

      1. It can be managed in Admin (grid) or Front (separate forms/events

      ...

      1. needs to be programmed)

      ...

      1. Emails should be send out to all Users (BCC) once that particular

      ...

      1. Event / Action is triggered.

      NOTE: Recently we have refactored and improved Email Events interfaces
      and functionality which allows adding CC, BCC of all kinds, BUT it's
      missing ability to associate the Events with Items. This is something
      we are looking to have here.

      Additionally we can allow subscribe Users which didn't Register, but
      just entered their email address. On the Front-end there might be
      additional logic added to verify your subscription so there is NO
      spamming to 3rd party emails.===

      Proposed table structure

      ...

      Table: EmailEventSubscriptions -

      • SubscriptionId (auto-increment)

      ...

      • PortalUserId (from PortalUser table, default NULL)

      ...

      • UserEmail (string default NULL, used in case if user subscribed

      ...

      • without Registration - quite useful)

      ...

      • EventId (from Events table)

      ...

      • CategoryId (from Categories table, default NULL)

      ...

      • ItemPrefix (default NULL)

      ...

      • ItemId (default NULL)

      ...

      • Status (int - Active, Disabled, Pending)

      ...

      • ModifiedOn (int with DateTime Formatter)

      ...

      Admin Interfaces

      ...

      I think we should have a separate section for this OR since all this
      is related to current Email Events we can create a new tab called
      Subscriptions. There we can show the grid of subscribers to that Event
      + ItemId and Prefix with opens to Add / Remove new ones.

      One other thing is that we need to create a new Agent that will Clean
      things up when Items are removed (deleted) so we don't end up with
      gazillion unknown records.

      Original discussion can be found here (currently closed):

      http://groups.google.com/group/in-portal-dev/browse_thread/thread/edb7fe2518e798fb

      DAEmail Event Subcriptions

      Related Tasks

      Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId513b375f-8291-3313-9d9f-704c39b1f915
      keyINP-982

      Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId513b375f-8291-3313-9d9f-704c39b1f915
      keyINP-1017