Zum Ende der Metadaten springen
Zum Anfang der Metadaten

Sie zeigen eine alte Version dieser Seite an. Zeigen Sie die aktuelle Version an.

Unterschiede anzeigen Seitenhistorie anzeigen

« Vorherige Version anzeigen Version 4 Nächste Version anzeigen »

Universal Messenger deals with different types of data:

Entries

The actual business data; for example:

  • Customers

  • Backoffice Users

  • Subscribers

  • Contacts

  • “Persons”

  • Service Desk Tickets

  • Events

  • etc.

Properties of Entries:

  • are stored in one (actually two) data base tables

  • have a customizable set of attributes

  • can be selected via elaborate query language / UI query generator

  • are receipients of emails / newsletters

  • can “subscribe” to Lists

  • can be understood as documents in a document store

Newsletters

Historically the main purpose was sending email newsletters to subscribers.

  • Newsletters can be created from the GUI, from external systems (CMS) or programmatically

  • Newsletters are queued until they are actually sent

  • Newsletters can be organized in Newsletter Groups

  • Newsletters are archived after sending

  • viewing a Newsletter (in an email client) or clicking links within a Newsletter can be tracked

Other management and auxiliary data objects

  • Mailing templates

  • Cron Jobs

  • Lists

  • Segments

  • Plugin Instances

  • Keine Stichwörter