Abstract: Data is shared between multiple enterprise data sources and mobile clients in a distributed system such that requests from a mobile client for enterprise data are received, the appropriate enterprise data sources that contain the requested data are determined, and the enterprise data is retrieved from the determined enterprise data sources. When the enterprise data is retrieved, it is converted into a relational format that can relate the retrieved data, even if the data comes from multiple enterprise data sources. The converted enterprise data is stored in a relational data store in the mobile client. In this way, mobile applications can be fully integrated with data from multiple enterprise data sources and data updates and configuration changes can be distributed to and from the mobile clients in real-time, without using interim data storage, and thereby avoiding complicated synchronization and data conflict issues between the enterprise data sources and the mobile clients.

Abstract: Data is shared between multiple enterprise data sources and mobile clients in a distributed system such that requests from a mobile client for enterprise data are received, the appropriate enterprise data sources that contain the requested data are determined, and the enterprise data is retrieved from the determined enterprise data sources. When the enterprise data is retrieved, it is converted into a relational format that can relate the retrieved data, even if the data comes from multiple enterprise data sources. The converted enterprise data is stored in a relational data store in the mobile client. In this way, mobile applications can be fully integrated with data from multiple enterprise data sources and data updates and configuration changes can be distributed to and from the mobile clients in real-time, without using interim data storage, and thereby avoiding complicated synchronization and data conflict issues between the enterprise data sources and the mobile clients.

Abstract: A travel management system. In one implementation, a state-based desktop client provides a travel planning and management workspace for the user. The user may perform travel planning activities, and log out of the travel workspace without having to repeat travel planning tasks. In another implementation, travel planning tasks may be stored as data feeds that keep up-to-date fare and availability data even when the user is not logged into the travel workspace.

Abstract: A method for generating an expense report, comprising: receiving an itinerary for travel, generating a description and a cost for one or more travel elements of the itinerary; and generating projected expenses that are expected to be incurred based on historical data associated with the itinerary

Abstract: Data is shared between multiple enterprise data sources and mobile clients in a distributed system such that requests from a mobile client for enterprise data are received, the appropriate enterprise data sources that contain the requested data are determined, and the enterprise data is retrieved from the determined enterprise data sources. Data maintained at a mobile client is shared with multiple enterprise data sources. The mobile clients send requests to an application server for synchronization of data records maintained at the mobile client with corresponding data records at the enterprise data sources. The client request includes metadata that identifies enterprise data sources for the requested data records and that specifies a relational correspondence between the requested data. The mobile client data records and the corresponding data records of the enterprise data sources are compared to identify any data conflicts between the two sets of data records. Any identified data conflicts are resolved.

Abstract: Data is shared between multiple enterprise data sources and mobile clients in a distributed system such that requests from a mobile client for enterprise data are received, the appropriate enterprise data sources that contain the requested data are determined, and the enterprise data is retrieved from the determined enterprise data sources. When the enterprise data is retrieved, it is converted into a relational format that can relate the retrieved data, even if the data comes from multiple enterprise data sources. The converted enterprise data is stored in a relational data store in the mobile client. In this way, mobile applications can be fully integrated with data from multiple enterprise data sources and data updates and configuration changes can be distributed to and from the mobile clients in real-time, without using interim data storage, and thereby avoiding complicated synchronization and data conflict issues between the enterprise data sources and the mobile clients.

Abstract: Data is shared between multiple enterprise data sources and mobile clients in a distributed system such that requests from a mobile client for enterprise data are received, the appropriate enterprise data sources that contain the requested data are determined, and the enterprise data is retrieved from the determined enterprise data sources. Data maintained at a mobile client is shared with multiple enterprise data sources. The mobile clients send requests to an application server for synchronization of data records maintained at the mobile client with corresponding data records at the enterprise data sources. The client request includes metadata that identifies enterprise data sources for the requested data records and that specifies a relational correspondence between the requested data. The mobile client data records and the corresponding data records of the enterprise data sources are compared to identify any data conflicts between the two sets of data records. Any identified data conflicts are resolved.

Abstract: A method and apparatus for prioritizing a plurality of incoming electronic mail messages for a user uses a user created and modified rules-control (12) which is stored in a rules-store (12). Incoming messages are stored in a message store (11) and are screened individually by a rules test unit (13). The rules-test unit has a comparator (52) which matches keywords which are chosen by the user while creating the rules, add supplies signals to an action list unit (54). By applying the user created rules for deciding which messages constitute the priority messages for the user, a priority assigning unit (45) within an action portion (35B) of the rules-store (12) assigns a priority number (say from 1 to 5, 1 being the highest priority for example) to each screened message. Responsive to the assigned priority number of the screened message, the message is sent to a main folder store or forwarded or put away as appropriate. The user created rules can be modified by the user using a conventional keyboard.