Print this Page
1.1 Portfolio
50. Business Message Service
Close this Page

1.1.50 Business Message Service:
1. Virtually every application service is provided with Business Message Services (BMS) that may also be called email.
2. A key factor of BMS is that messages are shared with all approved people.   Private email may be person-to-person, but business messages are person-to-company and company-to-company.
3. Out of office messages are eliminated as any approved person can handle a persons electronic message and may reply.   To build on the experience that people already have, File-Explorer is like the Eliza spread sheet used to show message lists - click on any row to show the message detail.
4. When the mail server inserts the message records, it assigns the expiry date and time as seven years into the future.   Eliza will periodically purge data that has expired - in compliance with GDPR.
  * BMS Catalogue  
  * BMS Portfolio  
  * Portfolio Email Policy  

2. Data: (84xx)
1. ZUMH is the message header as auto-key, to, from, date, time, subject. Created by mail-server only if both To and From email addresses are known. Read only by Eliza with "Z" prefix and no secondary table.
2. *ZUMB is the message body in text or HTML as auto-key, header-key. Created by mail-server. Read only by Eliza with "Z" prefix and no secondary table.
3. ZUMF is the message file or attachment as auto-key, header-key. Created by mail-server. Read only by Eliza with "Z" prefix and no secondary table.
4. UMA is address book (CRM) of approved business contacts and people (staff). Table-pair managed by Eliza spread sheet and forms. Any email to or from address not in this table is private and not recorded in UMH.
5. UMS is the send subscription as auto-key, header-key, subject, person-key, sent date+time, opt-in-date+time, opt-out-date+time, reply-date+time, expired-date+time, show-page+record+key. Table-pair by Eliza.
+
6. UMM is the send Message hand crafted as one or more text areas.
7. UMP is the send Attachment as page or uploaded file.
8. UMC is the send Copy CC or BCC list.
9. UMD is the send Diary event.

2b. Review:
1. All messages, business, private and junk are archived to ZUMH.
2. ZUMB text or html will be stored as a file using ZUMH primary key as the message number and file name.
3. Post-processing will decide what is business, private or junk.
4. Address book includes both a white list and black list, black listed email addresses are junk.

3. Functions:
1. Eliza spread sheet: filter UMH "BACKUP" as backed up documents sorted in date-time order. Click on any row to show UMT with UMA for download.
2. Eliza spread sheet: filter UMH "contact" as to-from contact name. Click on any row to show UMT with optional UMA for download.
3. Eliza spread sheet: filter UMH "email-domain" as to-from company. Click on any row to show UMT with optional UMA for download.
4. Eliza spread sheet: filter UMH "Me-Today" as to-from me-today. Click on any row to show UMT with optional UMA for download.
* Normal 4GL spread sheets and forms will be able to provide all the functionality that is likely to be needed in a consistent way.
* Navigate from Address book to contact, show all from-to messages for that contact.
* Navigate from Message to from-to contact, show address book, show all from-to messages for that contact.

3b. Function Send:
1. From addrrss book, select one contact. Click "Send" to show message send menu bar and sub-pages.
2. Menu bar has buttons to show stacked pages as Messages, Attachments, References, Copy Distribution List, Blind Distribution List, Diary Events.
3. Message (UMM) is large text area. JS enabled HTML editing. Extra topics can be added.
4. Page or Attachment (UMP) list of uploaded files.
5. Copy (UMC) or blind Distribution List of selected contacts from address book.
6. Diary (UMD) event.

4. Fields:
* Person (to, from) is encrypted as: auto-key, person-key, person-first-name, person-family-name, email-prefix, email-domain. CC, reply-to and sender may be overlooked or hidden or encrypted.
* Date and time are when the message arrived at email server stored as INT. "Z" type tables are write-once read-only primary table without secondary table.
* Some simplistic encryption method may change plain text subject and HTML to a set of numbers - must be quick to reverse.
PHASE TWO: Dates have an offset added such as -1234567. Time has an offset added as 55331122. Drop down Lists have numeric codes.
* Standard field layouts must be used so normal 4GL functions can be reused. Dates must be YYYYMMDD.

5. ZUMH Header:
01 INT key auto-incremented as message-key and message file name.
02 INT state with 123 as the only active state.
03 INT office with 123 as the only office key.
04 INT symbolic key as c01 key = updated after insert.
05 INT to-person-key as 8 digit key to CRM-UMC.
06 INT from-person-key as 8 digit key to CRM-UMC.
07 INT mail-status.
08 INT mail-type.
09 INT mail-del.
10 INT mail-kind.
11 INT number-of-attachment-files.
12 INT Expired date as 8 digit YYYYMMDD (+seven years).
13 INT Expired time as 8 digit HHMMSS00.
14 INT YYDDD day number created as 5 digits.
15 INT YYWW week created as 4 digits.
16 INT YYMM month created as 4 digits.
17 INT Created date as 8 digit YYYYMMDD (email into server).
18 INT Created time as 8 digit HHMMSS00.
19 INT message-size.
20 V128 Subject.
+++ to a criminal, the above will look like a worthless list of subjects out of context.
99 V128 unused FromA.
99 V64 unused FromP.
99 V128 unused ToA.
99 V64 unused ToP.
99 V128 unused ReplyToA.
99 V64 unused ReplyToP.
99 V128 unused ReplyFromA.
99 V64 unused ReplyFromP.
99 V128 unused SenderA.
99 V64 unused SenderP.
99 V128 unused CcA.
99 V64 unused CcP.
Text and/or HTML moved to message table ZUMT.

6. ZUMB Message Text or HTML:
This table may be a file in a subfolder by created YYMM.
Much of the data is copied from ZUMH so the text/HTML is stored in a different place to the header.
01 INT key auto-incremented as unique text-key.
02 INT state with 123 as the only active state.
03 INT office with 123 as the only office key.
04 INT message-key copied from ZUMH.c01.
05 INT to-person-key as 8 digit key to CRM-UMC.
06 INT from-person-key as 8 digit key to CRM-UMC.
07 INT mail-status.
08 INT mail-type.
09 INT mail-del.
10 INT mail-kind.
11 INT number-of-attachment-files or spare.
12 INT Expiry date as 8 digit YYYYMMDD (+seven years).
13 INT Expiry time as 8 digit HHMMSS00.
14 INT YYDDD day number created as 5 digits.
15 INT YYWW week created as 4 digits.
16 INT YYMM month created as 4 digits.
17 INT Created date as 8 digit YYYYMMDD (email into server).
18 INT Created time as 8 digit HHMMSS00.
19 INT message-size.
20 TEXT escaped HTML or message.
+++ to a criminal, the above will look like a worthless list of html text out of context.

7. ZUMF Attachment File:
Virtually the same as ZUMB with the text replace with the assigned file name and 21 as the original document name.
One record per file is recommended so the data is easy to index, search and filter.
01 INT key auto-incremented as unique file-key.
02 INT state with 123 as the only active state.
03 INT office with 123 as the only office key.
04 INT message-key copied from ZUMH.c01.
05 INT to-person-key as 8 digit key to CRM-UMC.
06 INT from-person-key as 8 digit key to CRM-UMC.
07 INT mail-status.
08 INT mail-type.
09 INT mail-del.
10 INT mail-kind.
11 INT number-of-attachment-files or kind of file.
12 INT Expiry date as 8 digit YYYYMMDD (+seven years).
13 INT Expiry time as 8 digit HHMMSS00.
14 INT YYDDD day number created as 5 digits.
15 INT YYWW week created as 4 digits.
16 INT YYMM month created as 4 digits.
17 INT Created date as 8 digit YYYYMMDD (email into server).
18 INT Created time as 8 digit HHMMSS00.
19 INT size of file.
20 TEXT assigned file name is message key and this file key.
21 TEXT original attachment name.
+++ to a criminal, the above will look like a worthless list of file names out of context.

8. UMC Address Book:
Created from ZUMH for every email address, certain messages marked as Junk have the email address blacklisted.
01 INT key auto-incremented from 10000001 as unique person key CRM-UMC.
02 INT state with 123 as the only active state.
03 INT office with 123 as the only office key.
04 INT person-key as 8 digit key as c01 = updated after insert.
05 INT spare with 123 as the default value.
06 INT spare with 123 as the default value.
07 INT spare with 123 as the default value.
08 INT spare with 123 as the default value.
09 INT Kind of Person or blacklist (list).
10 INT Preferred Contact Method (list).
11 INT number-of-changes.
12 INT Expiry date as 8 digit YYYYMMDD (+seven years).
13 INT Expiry time as 8 digit HHMMSS00.
14 INT YYDDD day created as 5 digits.
15 INT YYWW week created as 4 digits.
16 INT YYMM month created as 4 digits.
17 INT Last change person key as 8 digit key to CRM-UMC (never changed)).
18 INT last change date as 8 digit YYYYMMDD.
19 INT last change time as 8 digit HHMMSS00.
20 INT Created person key as 8 digit key to CRM-UMC.
21 INT Created date as 8 digit YYYYMMDD (email into server).
22 INT Created time as 8 digit HHMMSS00.
++ Eliza encrypted data follows as long numbers...
23 V32 Comment.
24 V64 Person First Name or salutation.
25 V32 Person Family Name.
26 V64 Email Prefix.
27 V32 Email Domain.
28 V32 Building or Flat Name.
29 V32 House and Street Name.
30 V32 District or Village.
31 V32 Town or City.
32 INT County Name (list).
33 INT Country Code (list).
34 V8 Postcode.
35 V16 Mobile.
36 V16 Home Phone.
37 V16 Work Phone.
38 INT spare to 40 INT spare.
This data can be copied by agencies without causing a data breach because it is meaningless.

9. UMS Subscription:
Every envelope created for a send-message is represented by a unique subscription record - the imbedded link points to this record.
01 INT sent message key auto-incremented from 10000001.
02 INT state with 123 as the only active state.
03 INT office with 123 as the only office key.
04 INT symbolic key as c01 key = updated after insert.
05 INT to-person-key as 8 digit key to CRM-UMC (contact).
06 INT from-person-key as 8 digit key to CRM-UMC (staff).
07 INT spare with 123 as the default value.
08 INT spare with 123 as the default value.
09 INT spare with 123 as the default value.
10 INT Kind of Person (list).
11 INT number-of-changes.
12 INT Expiry date as 8 digit YYYYMMDD (3 days to 3 weeks).
13 INT Expiry time as 8 digit HHMMSS00.
14 INT YYDDD day created as 5 digits.
15 INT YYWW week created as 4 digits.
16 INT YYMM month created as 4 digits.
17 INT Last change person key as 8 digit key to CRM-UMC.
18 INT last change date as 8 digit YYYYMMDD (message sent).
19 INT last change time as 8 digit HHMMSS00.
20 INT Created person key as 8 digit key to CRM-UMC.
21 INT Created date as 8 digit YYYYMMDD (email into server).
22 INT Created time as 8 digit HHMMSS00.
23 V32 Comment (internal).
24 V32 Subject (of subscription choice).
25 INT Opt-In date as 8 digit YYYYMMDD (when viewed).
26 INT Opt-In time as 8 digit HHMMSS00.
27 INT Opt-Out date as 8 digit YYYYMMDD (rejected).
28 INT Opt-Out time as 8 digit HHMMSS00.
29 V16 IP address (internal).
30 V64 Browser (internal).
This data does not contain any Personally Identifiable Information (PII).
When created, the opt-in and opt-out dates are 10 years into the future, well past the expiry date.

10. UMM Message:
For each subscription record, a message record will exist. More than one message (minutes) record can be supported.

11. UMP Page or Attachment:
For each subscription record, any number of reference pages or attachments are supported.

12. UMC Copy:
For each subscription record, any number of CC or BCC people from the address book are supported.

13. UMD Diary:
For each subscription record, any number diary entries are supported.