Abstract: Disclosed herein is an integration of automatic search functionality into a business application. The application is monitored for an instance wherein the user is initiating an activity that involves an expenditure. Upon detection of such an activity, a query is automatically generated based on information related to the expenditure. The query is communicated to a search component, from which corresponding search results are eventually received. Finally, at least some information related to the search results is displayed to the user. In one embodiment, assuming the user's express or implicit approval, auto-generation of data and/or modification of business process flow are facilitated based on the search results.

Abstract: This document describes tools that enable merchants to sell items through multiple sales channels without requiring the merchants to interact directly with those sales channels. These tools also permit merchants to learn and interact with as little as one user interface. A merchant may, for example, sell items through the merchant's own physical, brick-and-mortar store, an auction website, a fixed-price website, and the merchant's own website using a single user interface. Embodiments of these tools also enable customers to tracks purchases made through multiple sales channels with a single user interface. If a customer buys one of a merchant's items from an independent website and another from the merchant's own website, for example, the tools may permit the customer to view both of these purchases through a single user interface.

Abstract: Embodiments provide for extending the architecture of a legacy messaging system that otherwise communicates message rules to a client as rows in a rule table. Due to architectural limitations of some messaging systems, rules larger than a specified size are prevented from being streamed between a server and a client. Example embodiments provides for extended rules that represent a combination of conditions, actions or exceptions to be performed on messages and are created by a client as message objects. Because they are created by a client as message objects, rather than rows on a table, the extended rules are allowed to be streamed between the client and server, thus extending the architecture of a legacy messaging system. The client also sets a property value on the message object created, thereby allowing the server to identify the message object as including the extended rule. The system, however, still supports legacy clients.

Abstract: Embodiments provide for storing message rules in a serialized global form on a server for transfer of the data between different servers. Message rules include condition and action data structures, wherein at least the action data structures include global identifiers. A client creates a message object that includes an extended rule with the global identifiers, sets a property on the message object used to identify the object as an extended rule, serializes the message object using a code library, and stores the message object on a message server. Upon execution of a message rule, the rule is deserialized using a copy of the code library and translated into server specific for executing the extended rule on received messages.

Abstract: Embodiments provide for decoupling a module that assigns a SPAM confidence level from a module that executes actions within a message rule, and allowing a user the flexibility in assigning those actions. The confidence level indicates the likelihood that a received message includes unsolicited or unwanted content and is assigned to a received message by a calculation module. A rule execution module accesses an Anti-SPAM rule, which includes conditions and actions defined by a user. The rule execution module then scans the message to determine if the conditions are met and what actions should be executed. For example, a condition of the Anti-SPAM rule may be a threshold value, which is compared to the SPAM confidence level. If the SPAM confidence level exceeds the threshold the actions within the Anti-SPAM rule are executed.