Abstract: CRM application controls and functionality for multiple CRM applications/instances are integrated with an ECS application user interface by designating a single CRM application/instance as primary and providing synchronization and rich client control capabilities. Other CRM applications/instances are set up as secondary within the ECS user interface employing a single CRM connection module and a single state manager. Accessing a secondary CRM application/instance activates relevant controls applicable to that CRM application/instance without a user having to logout and login to the ECS client.

Abstract: Synchronization between Communications and Scheduling (CS) service and customer relationship management (CRM) applications is facilitated through a synchronization module on the CS service side using Extensible Markup Language (XML) formatted storage for keeping track of synchronization states. The CRM server version of an item is compared with the XML formatted storage to detect changes and the same performed for the CS service item. The updates are stored in a CS service item or transmitted to the CRM application for application to a corresponding CRM item. Last updated item is selected in case of a conflict.

Abstract: A display is generated for displaying entities that are related to a selected entity. The display includes one or more tiles, each tile displaying a representation of a selected entity and associated entities, within that single tile.

Abstract: A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input to manipulate the business data record to perform an operation, a task or a workflow within the business data system. The business data system performs the operation, task or workflow based on the touch gesture user input.

Abstract: A layout transformation system accesses application metadata that defines a plurality of different structures for displaying components of the application, based upon the particular modality of the display device. The layout transformation system then transforms a user interface display based on the application metadata and based upon the particular modality, and provides the user interface display to the display device for rendering and user interaction.

Abstract: A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input to manipulate the business data record to perform an operation, a task or a workflow within the business data system. The business data system performs the operation, task or workflow based on the touch gesture user input.

Abstract: A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input to manipulate the business data record to perform an operation, a task or a workflow within the business data system. The business data system performs the operation, task or workflow based on the touch gesture user input.

Abstract: A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input manipulating a contact within the business data system. The business data system manipulates the contact based on the touch gesture user input.

Abstract: A database startup service is launched at the boot time of a computer that is configured to receive requests to start the execution of a database server. A business application plug-in is then started in a minimal functionality mode of operation. The plug-in determines whether an action has been performed that requires access to a database. If access to the database is needed, the plug-in transmits a request to the database startup service to start the database service. Once the database server has been started, the plug-in transitions to a full functionality mode of operation where all of the functionality provided by the plug-in is enabled. The plug-in might also determine that access to the database is no longer needed. In response thereto, the plug-in may transmit a request to the database startup service to terminate the execution of the database server.

Abstract: CRM application controls and functionality for multiple CRM applications/instances are integrated with an ECS application user interface by designating a single CRM application/instance as primary and providing synchronization and rich client control capabilities. Other CRM applications/instances are set up as secondary within the ECS user interface employing a single CRM connection module and a single state manager. Accessing a secondary CRM application/instance activates relevant controls applicable to that CRM application/instance without a user having to logout and login to the ECS client.

Abstract: Concepts and technologies are described herein for collecting and displaying information. A client device executes one or more application programs for providing operations with respect to entity-related data that relates to one or more entities. The application programs analyze the entity-related data to identify one or more entities associated with the entity-related data and transmit entity information relating to the entities to a server or database. Information relating to the entity is retrieved from the server or database and is presented to a user of the client device.

Abstract: A database startup service is launched at the boot time of a computer that is configured to receive requests to start the execution of a database server. A business application plug-in is then started in a minimal functionality mode of operation. The plug-in determines whether an action has been performed that requires access to a database. If access to the database is needed, the plug-in transmits a request to the database startup service to start the database service. Once the database server has been started, the plug-in transitions to a full functionality mode of operation where all of the functionality provided by the plug-in is enabled. The plug-in might also determine that access to the database is no longer needed. In response thereto, the plug-in may transmit a request to the database startup service to terminate the execution of the database server.

Abstract: Embodiments provide aspects of a workspace interface that includes a number of customizable business role workspaces, but are not so limited. In an embodiment, a computer-implemented method provides a number of role-specific workspaces as part of an integrated business development application, each role-specific workspace including role-specific ribbon tools, gadgets, and/or tabs tailored to address particular aspects of a business or business role. In one embodiment, a number of customizable role-specific workspaces are combined with personal information management features as part of providing an integrated business management solution. Other embodiments are included and available.

Abstract: A technique for establishing inspected secure communication includes establishing a first secure connection between a client device and a client-side device and a second secure connection between the client-side device and a server device. The client-side device establishes the first secure communication channel by providing a certificate impersonating the server device to the client device. The first and second communication channels enable client-side inspection of communications.

Abstract: Lightweight directory access protocol (LDAP) management is described. In an implementation, a method includes exposing a user interface suitable for receiving inputs from a user that specify whether execution of a particular lightweight directory access protocol (LDAP) action is permitted. A policy is configured based on the inputs, for managing lightweight directory access protocol (LDAP) traffic on a network.

Abstract: A single passcode can be used for validation by a user of several entities in a system without compromising security. The source of the entity providing validation credentials, along with the passcode, is considered when determining validity. A one-time password system validates credentials if a validation credentials, such as a user's valid passcode and the source of the credentials, have not been used previously. In a one-time passcode system, a validation processor receives validation credentials from a client processor. If the client processor has not previously sent the validation credentials to the validation processor, and the credentials are valid, the validation processor will validate the credentials. Otherwise, the credentials are invalid. Other client processors can utilize the same passcode and their respective source identifiers, and as long as the other client processors have not previously utilized the credentials, the credentials are declared valid.

Abstract: A network access protection method includes creating an access policy as a function of statement-of-health information. The network access protection method also includes selectively allowing, denying or redirecting communications based upon the access policy and the current statement-of-health of one or more computing devices associated with the communications.

Abstract: Lightweight directory access protocol (LDAP) management is described. In an implementation, a method includes exposing a user interface suitable for receiving inputs from a user that specify whether execution of a particular lightweight directory access protocol (LDAP) action is permitted. A policy is configured based on the inputs, for managing lightweight directory access protocol (LDAP) traffic on a network.

Abstract: Lightweight directory access protocol (LDAP) management is described. In an implementation, a method includes intercepting data, configured according to a lightweight directory access protocol (LDAP), for communication between a client and a server. One or more polices are applied to the data to determine whether performance of an LDAP action specified in the data is permitted. When the performance is not authorized, the LDAP action is modified such that performance of the modified LDAP action is permitted.

Abstract: A technique for establishing inspected secure communication includes establishing a first secure connection between a client device and a client-side device and a second secure connection between the client-side device and a server device. The client-side device establishes the first secure communication channel by providing a certificate impersonating the server device to the client device. The first and second communication channels enable client-side inspection of communications.