Abstract: Methods, devices, and systems for creating a call abstraction to enable an application to monitor and control various types of User Agents (UAs) are provided. The application may be adapted to monitor and control simple UAs that do not recognize out of dialog (OOD)-REFER signals as well as advanced UAs that do recognize and can respond to OOD-REFER signals.

Abstract: A data reporting framework that works across on-premise and hosted Customer Relationship Management (CRM) platforms enabling definition and execution of secure custom reports is provided. A fetch query language of a CRM platform is used along with reporting service tools and constructs to enable users to upload and execute custom fetch based reports with support for expressions, code, formatting, and drill through. Users are also enabled to build simple reports from within CRM and, if needed, enhance those reports using reporting service tools and re-upload in CRM. Furthermore, custom reports may be executed in a sandboxed environment to provide full security in a multi-tenant, hosted CRM system.

Abstract: Architecture that facilitates support for similar user interface (UI) models and user experience of independent applications. A data mapping component is provided that maps a user record of a business-centric application to a business object of the business-centric application. When employed in combination with another independent application, such as a personal information manager (PIM), a PIM component exposes the business object via a PIM user interface in a personalized way that enables user interaction with the business object to apply PIM actions to the business object. The mapping component can be a join table between the user record and the business object that enables the setting of PIM settings and user interface actions into the business product. Additionally, a communications infrastructure is provided where the PIM client UI communicates to the data-based server system in the business environment and persists PIM-specific settings to the business object.

Abstract: A data reporting framework that works across on-premise and hosted Customer Relationship Management (CRM) platforms enabling definition and execution of secure custom reports is provided. A fetch query language of a CRM platform is used along with reporting service tools and constructs to enable users to upload and execute custom fetch based reports with support for expressions, code, formatting, and drill through. Users are also enabled to build simple reports from within CRM and, if needed, enhance those reports using reporting service tools and re-upload in CRM. Furthermore, custom reports may be executed in a sandboxed environment to provide full security in a multi-tenant, hosted CRM system.

Abstract: A Customer Relationship Management (CRM) system enables tracking of multiple types of goals within the system employing the same construct, whose look-and-feel and behavior may be dynamically modified based on different user defined metrics. Actuals against the goals are computed by the system based on source entity definitions in metrics and user defined dimensions with filters.

Abstract: Methods, devices, and systems are provided for enhancing the functionality of a communication device, such as a communication endpoint. This provides the ability to enhance less intelligent SIP endpoints with required features to support a richer user experience. Furthermore, the endpoint enhancer may be dynamically pluggable onto an existing network device. This provided pluggability allows a network administrator to add a new SEE template to the network without disrupting the network operation or the operation of previously existing SEEs.

Abstract: Methods, devices, and systems are provided for enhancing the functionality of a communication device, such as a communication endpoint. This provides the ability to enhance less intelligent SIP endpoints with required features to support a richer user experience. Furthermore, the endpoint enhancer may be dynamically pluggable onto an existing network device. This provided pluggability allows a network administrator to add a new SEE template to the network without disrupting the network operation or the operation of previously existing SEEs.

Abstract: Systems and methods for associating multiple credentials with a single user account in a distributed authentication system. A user can be authenticated to a service by providing any one of the multiple credentials to the authentication system. Thus, a user can provide credentials that are more easily entered or supplied on a given device. All of the credentials are associated with a single user account. The credentials can be associated symmetrically, where the user account is independent of each credential, or asymmetrically, where the user account is stored with a primary credential and the other credentials are secondary credentials that reference the primary credential.

Abstract: A client programming model with abstraction hides from an underlying client application or application program interface (API) the details of where each element of data is located, and which copy of the data is resident on an available server and associated databases. The model wraps a database, such as a virtual database, and provides data-dependent and application-dependent routing, failover, and operational administration.

Abstract: Various embodiments of the present invention are directed toward extending a federation of servers and balancing the data load of said federation of servers, in order to improve accessibility and scope of the system by moving the first backup data structure on the second server to the new server, creating a second data structure on the new server, and creating a second backup data structure for the second data structure on the second server. To balance the load, certain embodiments employ a method comprising suspending writes to the selected logical partitions, copying selected logical partitions to the new physical partition, redirecting reads and writes to the logical partitions in the new physical partition, and removing the original selected logical partitions.

Abstract: Maintaining versions and workspaces in an object repository is disclosed. The system provides an efficient way to manage versions of objects by only copying objects when absolutely necessary, i.e. when a property value in a particular object has changed. In addition, the system provides a mechanism to control whether or not relationships are propagated to successor versions of an object. A further aspect of the system is that resolution of objects during a relationship traversal can be customized depending on whether or not an application accessing the objects is version-aware. If the application is not version aware, a means for resolving the relationship to a particular object is provided. A still further aspect of the system is that merge behavior is parameterized. When two versions of an object are merged, flags control how conflicts in property values and relationship contents are managed.

Abstract: Various embodiments of the present invention are directed toward extending a federation of servers and balancing the data load of said federation of servers, in order to improve accessibility and scope of the system by moving the first backup data structure on the second server to the new server, creating a second data structure on the new server, and creating a second backup data structure for the second data structure on the second server. To balance the load, certain embodiments employ a method comprising suspending writes to the selected logical partitions, copying selected logical partitions to the new physical partition, redirecting reads and writes to the logical partitions in the new physical partition, and removing the original selected logical partitions.

Abstract: Maintaining versions and workspaces in an object repository is disclosed. The system provides an efficient way to manage versions of objects by only copying objects when absolutely necessary, i.e. when a property value in a particular object has changed. In addition, the system provides a mechanism to control whether or not relationships are propagated to successor versions of an object. A further aspect of the system is that resolution of objects during a relationship traversal can be customized depending on whether or not an application accessing the objects is version-aware. If the application is not version aware, a means for resolving the relationship to a particular object is provided. A still further aspect of the system is that merge behavior is parameterized. When two versions of an object are merged, flags control how conflicts in property values and relationship contents are managed.