Changes between Version 52 and Version 53 of BluePrint/Messaging

Timestamp:

06/16/10 21:18:39 (15 years ago)

Author:

Fran Boon

Comment:

--

BluePrint/Messaging

@@ -48 +48 @@
 [[Image(Message Flows.png)]]
 ==== How do we achieve this? ====
+ * Table {{{msg_log}}} is used as a replacement for the current {{{msg_inbox}}}, {{{msg_outbox}}} & {{{ticket_log}}}.
+  * Fields: sender, subject, body, verified, actionable, assignee (multiple?), actioned, priority
+   * Q: Do we move some of these 'ticketing' fields to a separate {{{ticket_msg}}} table?
  * Table {{{pe_subscription}}} is used to maintain subscriptions for a {{{pe_pentity}}}.
   * Fields: ''tbc''
@@ -56 +59 @@
   * Q: Do we mark as read if pe_contact_id status suggests person has received message?
   * Good to have UI to 'Mark Unread'
+ * shn_rest_controller() is modified to check msg_log for messages tagged to the resource (list) or record (display/update)
+ * 'Ticketing Module' UI
+  * default view is all un-actioned messages (assigned to this user &/or unassigned?)
+  * If a message is routed to a resource, this results in a 'create' form popup with as many fields auto-populated as possible (subject into 'name' field & body into 'comments' field, if nowhere better)
+   * Q: If a message is routed to a resource, does this automatically mark ticket as 'actioned'? Provide a popup to ask this?
 === User Interface ===
 The home page should be a common Inbox view which, by default, shows all new unread Items (the 'Ticketing Module').