System and methods for implementing custom transactions within a multi-tenant platform
US-2017236084-A1 · Aug 17, 2017 · US
US2018158030A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2018158030-A1 |
| Application number | US-201715496745-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 25, 2017 |
| Priority date | Dec 2, 2016 |
| Publication date | Jun 7, 2018 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Examples of the present disclosure describe systems and methods relating to an automatic meeting invite processor. When processing a meeting invite, the automatic meeting invite processor may enforce a calendar booking rule, which may be comprised by a predicate and an action. The predicate may specify characteristics relating to the meeting invite, such as a sender, scheduled date/time, scheduled location, etc. The predicate may also relate to context associated with a recipient of the meeting invite (e.g., the recipient's calendar or mailbox content). When a predicate is satisfied, the automatic meeting invite processor may perform one or more actions, wherein an action may relate to the meeting specified by the meeting invite or to the meeting invite object itself. Thus, when the predicate is satisfied, the meeting invite may be automatically processed by the automatic meeting invite processor using the action specified by the calendar booking rule.
Opening claim text (preview).
What is claimed is: 1 . A system comprising: at least one processor; and a memory storing instructions that when executed by the at least one processor perform a set of operations comprising: receiving a meeting invite; accessing a transport rule associated with the meeting invite, wherein the transport rule is comprised of a transport predicate, a transport action, and a calendar booking rule; determining, based on the content of the meeting invite, whether the transport predicate is satisfied; and when the transport predicate is satisfied, modifying the meeting invite based on the transport action, wherein modifying the meeting invite comprises associating the calendar booking rule with the meeting invite. 2 . The system of claim 1 , wherein the transport action comprises updating a header associated with the meeting invite to contain information associated with the calendar booking rule. 3 . The system of claim 1 , wherein the transport predicate specifies a sender associated with the meeting invite. 4 . The system of claim 1 , wherein the calendar booking rule comprises a calendar booking predicate and a calendar booking action. 5 . The system of claim 4 , wherein the calendar booking predicate comprises a predicate associated with the transport predicate. 6 . The system of claim 4 , wherein the calendar booking action comprises an action selected from the group consisting of: accepting the meeting invitation; tentatively accepting the meeting invitation; rejecting the meeting invitation; marking the meeting invitation as read; and deleting the meeting invitation. 7 . The system of claim 1 , wherein associating the calendar booking rule with the meeting invite comprises storing the calendar booking rule in a header of the meeting invite. 8 . A system comprising: at least one processor; and a memory storing instructions that when executed by the at least one processor perform a set of operations comprising: receiving the meeting invite; extracting one or more properties from the meeting invite; determining, based on the one or more properties, that a calendar booking rule applies to the meeting invite, wherein the calendar booking rule comprises a calendar booking predicate and a calendar booking action; evaluating the calendar booking predicate to determine whether the calendar booking predicate is satisfied; and when the calendar booking predicate is satisfied, performing the action specified by the calendar booking action. 9 . The system of claim 8 , wherein evaluating the calendar booking predicate comprises evaluating a mailbox context associated with a mailbox for a recipient of the meeting invite. 10 . The system of claim 8 , wherein evaluating the calendar booking predicate comprises evaluating a scheduling availability associated with a recipient of the meeting invite. 11 . The system of claim 8 , wherein the calendar booking predicate specifies a sender associated with the meeting invite. 12 . The system of claim 8 , wherein the calendar booking action comprises an action selected from the group consisting of: accepting the meeting invitation; tentatively accepting the meeting invitation; rejecting the meeting invitation; marking the meeting invitation as read; and deleting the meeting invitation. 13 . The system of claim 8 , wherein the one or more properties are headers within the meeting invite. 14 . The system of claim 8 , wherein the calendar booking rule is stored in the meeting invite as one or more headers. 15 . A computer-implemented method for processing a meeting invite, the method comprising: receiving a meeting invite; accessing a transport rule associated with the meeting invite, wherein the transport rule is comprised of a transport predicate, a transport action, and a calendar booking rule; determining, based on the content of the meeting invite, whether the transport predicate is satisfied; and when the transport predicate is satisfied, modifying the meeting invite based on the transport action, wherein modifying the meeting invite comprises associating the calendar booking rule with the meeting invite. 16 . The computer-implemented method of claim 15 , wherein the transport action comprises updating a header associated with the meeting invite to contain information associated with the calendar booking rule. 17 . The computer-implemented method of claim 15 , wherein the transport predicate specifies a sender associated with the meeting invite. 18 . The computer-implemented method of claim 15 , wherein the calendar booking rule comprises a calendar booking predicate and a calendar booking action. 19 . The computer-implemented method of claim 15 , wherein the calendar booking action comprises an action selected from the group consisting of: accepting the meeting invitation; tentatively accepting the meeting invitation; rejecting the meeting invitation; marking the meeting invitation as read; and deleting the meeting invitation. 20 . The computer-implemented method of claim 15 , wherein associating the calendar booking rule with the meeting invite comprises storing the calendar booking rule in a header of the meeting invite.
Computer-aided management of electronic mailing [e-mailing] · CPC title
Protecting data · CPC title
Physics · mapped topic
Calendar-based scheduling for persons or groups · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.