Abstract: Methods, apparatus, and articles of manufacture for enabling keyboard accelerators in software applications implemented via a browser application are disclosed herein. Keyboard accelerators are enabled by intercepting keyboard data before it can be utilized by the browser application for its own purposes, such as initiation of a keyboard accelerator native to the browser application. The intercepted keyboard data is evaluated to determine whether it corresponds to a defined remote application keyboard accelerator, and if so, then a remote application function module is called to implement the feature mapped to the particular identified keyboard accelerator. The keyboard data may then be removed from an event queue or otherwise deleted such that the browser application continues to be executed without reference thereto.

Abstract: According to one aspect of the present invention, a method is provided in which a search request containing search criteria is received from a first user. A search is performed based on the search criteria to retrieve records in one or more databases that match the search criteria. A list of search results based on the retrieved records is displayed to the first user. In response to the first user's selection of a particular search result in the list of search results, details of the particular search result are displayed to the first user.

Abstract: Updates made to a central database (3) or to another partially replicated database (23-1) are selectively propagated to a partially replicated database (23-2) if the owner of the partially replicated database (23-2) is deemed to have visibility to the data being updated. Visibility is determined by use of predetermined rules stored in a rules database. Stored rules are assessed against data content of various tables that make up a logical entity, known as a docking object that is being updated. The stored rules are assessed against data content of various tables that make up a docking object, not necessarily being the docking object that is being updated. The visibility rules of these related docking objects are recursively determined. Changes in visibility are determined to enable the central computer to direct the nodes to insert the docking object into its partially replicated database.

Abstract: System and method for preparing, using, and displaying a state model of a process, as an industrial or business process, as a sequence of discrete steps. The state model defines the behavior of the logical objects making up a process model of the process as (1) a set of permitted states and (2) a set of permitted transitions between the permitted states. The state model is created by selecting a template for the state model, and selecting industrial or business object components for the state model (for example, by using “OOP” methods or other programming paradigms). The user then selects or defines state transitions for the state model, for example, by defining permitted state transitions from a “from state” to a “to state”. The defined or selected state transition rules are identified to State Transition Rule names.

Abstract: Attaching files and other objects in a distributed computing environment. This includes adding file attachments and non-database objects, such as, text file data, web file data, image file data, and other file attachment objects to databases. These objects may be retrieved at the convenience of a node to which the objects are sent. Visibility rules can be set to determine which attachments and objects are seen by a node. Distribution rules for an object determine whether a node must request the object or whether the node is forced to receive the object.

Abstract: A method and system for passing information between a client, as a browser, and a server, as an application server, where the information is passed through a web server for processing between the application server and the browser. The webserver loads one or more template files. These template files contain standard markup language plus special tags. These tags are parsed, translated into commands for the application server, and sent to the application server. The application server returns the objects called to the web server, which passes the called objects to the client. The session is persistent.

Abstract: Client-server systems and methods for transferring data via a network, including a wireless network, between a server and one or more clients or browsers that are spatially distributed (i.e., situated at different locations). At least one local client computer provides a user interface to interact with at least one remote server computer which implements data processing in response to the local client computer. The user interface may be a browser or a thin client.

Abstract: A method of maintaining a database. The database is a partially replicated database having a central database and a plurality of individual partially replicated databases. Updates made to the central database or to one of the individual, partially replicated databases are selectively propagated to one or more recipient partially replicated databases if the owner of the recipient partially replicated database has visibility to the data being selectively transmitted. This is accomplished by first replicating a group or records as a single logical docking object. A single set of visibility rules is applied to the data content of the entire logical docking unit. The docking object is then applied to the recipient individual partially replicated database if the owner thereof has visibility to the data being transmitted in the single logical docking object. Also disclosed are methods of controlling and logging the propagation of docking objects.

Abstract: A method and system for passing information between a client, as a browser, and a server, as an application server, where the information is passed through a web server for processing between the application server and the browser. The webserver loads one or more template files. These template files contain standard markup language plus special tags. These tags are parsed, translated into commands for the application server, and sent to the application server. The application server returns the objects called to the web server, which passes the called objects to the client. The session is persistent.

Abstract: Instantiation of tiered software applications running on an Internet or Intranet computer system, including a method of instantiation and a program product for instantiation. The method, and program product are particularly useful in instantiation of multi-tiered applications having a user interface tier on the client, browser, or remote computer, from a meta data repository containing attributes and values of the attributes.

Abstract: A method and system for enabling a CTI user to log in at any work station in a network and utilize the system with the correct teleset, and also to transfer a CTI transaction or interaction to another CTI user.

Abstract: Instantiation of tiered software applications running on an Internet or Intranet computer system, including a method of instantiation and a program product for instantiation. The method, and program product are particularly useful in instantiation of multi-tiered applications having a user interface tier on the client, browser, or remote computer, from a meta data repository containing attributes and values of the attributes.

Abstract: A software development method and system having a suite of graphical customization tools that enables developers to rapidly configure all aspects of the underlying application software, including the look-and-feel, behavior, and workflow. This is accomplished without modifying application source code, base objects, or SQL. The sophisticated repository management capabilities of the method and system of our invention allows teams of developers to work efficiently on configuring applications. The application upgrader provides an automated process to upgrade the customizations to future product releases thus protecting the investment in customization. The ease, comprehensiveness, scalability, and upgradeability of the customization process help reduce the total lifecycle cost of customizing enterprise applications.

Abstract: Methods and apparatus for distributing a first relation amongst a set of orthogonal sub-relations are disclosed. As a method, an orthogonal sub-relation of the set of orthogonal sub-relations is identified and then removed from the first relation. The removed sub-relation is then replaced with an associated reference that points to the removed sub-relation to form a distributed relation. A reduced first relation that is substantially reduced in size as compared to the first relation, such that the distributed relation is formed of the reduced first relation and all the referenced orthogonal sub-relations.

Abstract: Techniques to support various operations (e.g., drag-and-drop, stretch) and data manipulation in a browser environment, e.g., to allow data for an object located in one part of a document (e.g., a webpage) to be associated with another object located in another part of the document. In one design, a document includes at least one applet for at least one display window. Each applet includes at least one browser object representative of an entity for an end application. Each browser object is associated with a respective set of one or more scripts used to facilitate a set of one or more operations (e.g., drag-and-drop, stretch) permitted for the browser object. A data transfer object is generated upon initiation of a selected operation and includes data associated with a source (browser) object. The data transfer object may thereafter be operated on by various target (browser) object to effectuate the selected operation.

Abstract: Techniques to support user interaction in a browser environment, “capture” certain user actions, and perform appropriate defined actions. In a first scheme, “setup” pages are used to detect user actions. Each setup page is associated with a respective script that is executed when the page is activated (e.g., via a Back or Forward button). The script performs the defined actions to obtain the proper behavior for dependent pages. The scripts for the setup pages keep track of the state of these pages, and further maintain a local history stack for the URLs of the dependent pages. In a second scheme, each dependent page includes a hidden history frame having a script that performs a set of defined actions for the page. The script further keeps track of whether or not the dependent page has been loaded previously.

Abstract: Updates made to a central database (3) or to another partially replicated database (23-1) are selectively propagated to a partially replicated database (23-2) if the owner of the partially replicated database (23-2) is deemed to have visibility to the data being updated. Visibility is determined by use of predetermined rules stored in a rules database. Stored rules are assessed against data content of various tables that make up a logical entity, known as a docking object that is being updated. The stored rules are assessed against data content of various tables that make up a docking object, not necessarily being the docking object that is being updated. The visibility rules of these related docking objects are recursively determined. Changes in visibility are determined to enable the central computer to direct the nodes to insert the docking object into its partially replicated database.

Abstract: A method of and system for collecting, storing, and retrieving data in a data base management system. The database management system includes a master database server (4), at least one workgroup server (315), and a plurality of workgroup user clients (310). The workgroup server (315) is interposed between the master database server (4) and said workgroup user clients (310). The method creating a transaction in a local database resident on one of the workgroup user clients (310), entering the transaction into a transaction log resident on the workgroup user client (310), and creating a transaction file corresponding to the transaction in an outbox of said workgroup user client (310). Next, the transaction file is copied to an inbox identified to the workgroup user client (310) and updating the transaction file into a workgroup database (305) resident on the workgroup server (315). The workgroup database (305) includes a transaction log.

Abstract: Methods and apparatus for deploying a generic application engine in a browser program executing on a client platform are described. As a method, an application engine kernel is formed in the browser program that is independent of the client platform and the browser program concurrently with loading user interface (UI) components and corresponding data components associated with the application engine. A minimum required subset of application engine components are then loaded by the kernel in order to process any initial user requests.

Abstract: A method for upgrading (31-b of FIG. 1) a software application (35-b) from a prior version to a subsequent version while preserving user modifications to the prior application. The method includes comparing differences between the two versions of the software applications. This is followed by enumerating the differences between the two versions of the software applications; and determining which differences between the two versions of the software are conflicting and which are compatible. The compatible changes are made (7). Also disclosed is an article of manufacture containing computer readable program code for carrying out the above process, and a program storage device carrying the code.