I've put together a diagrammatic storyboard with accompanying text to describe all of the possible combinations / permutations when a Chandler User sends out stamped items. Caveat: This assumes that we can implement the IDEAL solution. The storyboard diagrams can be found at: ---+++Stamping and Ecosystem: What happens when a Chandler User sends out an invitation to other Chandler Users, Scooby Users and People outside of the Ecosystem ---++++Edit and Update Scenario A creates an invitation to send to BCDE * B is a Chandler user sharing the invitation with A * C is a Chandler user, not sharing * D is a Scooby user * E is an email user ---+++B the Chandler User, Sharing with A * B receives the invitation in their email client; AND * B receives the invitation in their Chandler / Dashboard NOW section * B can reply to the email in their email client; OR * B edits the item in Chandler * (A and D can see B's edits in Chandler and Scooby respectively, even before B has hit the Update button to Send out his edits.) * B updates the item * A receives the update in their email client as a separate email in the same thread; AND * A receives the update to the original invitation item in their Chandler / Dashboard NOW section * B receives the update in their email client as a separate email in the same thread * C receives the update in their email client as a separate email in the same thread; AND * C receives the update to the original invitation item in their Chandler / Dashboard NOW section * D receives the update in their email client as a separate email in the same thread; D can click on a URL ticket to view / edit the item on Scooby * E receives the update in their email client as a separate email in the same thread ---+++C the Chandler User, Not-sharing * C can see the invitation in their Chandler, in the collection they share with A as soon as A has created the item and a sync happens. The invitation is auto-triaged in C's Dashboard to Later, because it is an invitation for an event scheduled in the future. * When A sends the invitation, C receives the invitation in their email client; AND * C receives the invitation item pops into the NOW section of C's Dashboard * C can reply to the email in their email client; OR * C edits the item * C updates the item * A receives the update in their email client as a separate email in the same thread; AND * A receives the update to the original invitation item in their Chandler / Dashboard NOW section * B receives the update in their email client as a separate email in the same thread; AND * B receives the update to the original invitation item in their Chandler / Dashboard NOW section * C receives the update in their email client as a separate email in the same thread * D receives the update in their email client as a separate email in the same thread; D can click on a URL ticket to view / edit the item on Scooby * E receives the update in their email client as a separate email in the same thread ---+++D the Scooby User * D receives the invitation in their email client * D can reply to the email in their email client; OR * D clicks on a URL ticket to view/edit the invitation on Scooby * D edits the invitation * (A and B can see D's edits as D is making them (assuming background sync) * D updates the invitation * A receives the update in their email client as a separate email in the same thread; AND * A receives the update to the original invitation item in their Chandler / Dashboard NOW section * B receives the update in their email client as a separate email in the same thread; AND * B receives the update to the original invitation item in their Chandler / Dashboard NOW section * C receives the update in their email client as a separate email in the same thread; AND * C receives the update to the original invitation item in their Chandler / Dashboard NOW section * D receives the update in their email client as a separate email in the same thread; D can click on a URL ticket to view / edit the item on Scooby again. * E receives the update in their email client as a separate email in the same thread ---+++E the Email client User * E receives the invitation in their email client * E can reply to the email in their client * A receives the reply in their email client as a separate email in the same thread; AND * A receives the reply to the original invitation item in their Chandler / Dashboard NOW section as a separate email in the same thread * B receives the reply in their email client as a separate email in the same thread; AND * B receives the reply to the original invitation item in their Chandler / Dashboard NOW section as a separate email in the same thread * C receives the reply in their email client as a separate email in the same thread; AND * C receives the reply to the original invitation item in their Chandler / Dashboard NOW section as a separate email in the same thread * D receives the reply in their email client as a separate email in the same thread |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
