International Business Machines Corporation

Isaac Kam-Chak Cheng

Vikas Krishna

Donald Lee Clare

Louis S W Mau

Dilip Kumar Biswal

Jian J Xu

Josephine Miu Cheng

Jyh-Herng Chow

Michael Leon Pauser

Suet Mui Chiu

Hoang K Chau

Timothy Joel Bethea

Neil Harold Arthur Boyette

Cecilia O Chu

Cecilia Oi-Lin Chu

Dawn Marie Fritz

Savitha Srinivasan

Scott Holmes

Neil Boyette

Yongshin Yu

Yolanda A Rankin

Systems and methods for adapting an existing call flow wherein the call flow further comprises an associated data set, comprising: activating the existing call flow, the existing call flow generating a series of questions designed to obtain information from a caller; determining if an exception condition has occurred; allowing a user to activate an exception call flow in response to the exception condition; retaining the data set associated with the call flow when the exception condition occurred; adapting the data set such that the call flow addresses the exception condition; analyzing the adapted data set to determine if it is unique; and, modifying the existing call flow to incorporate the adapted data set if the adapted data set is unique.

System and method for call flow generation via real-time tracking of guided problem resolution

A system for efficient snapshot querying include: providing a first version value for each data in a history table, where the first version value indicates a beginning of a period in which the data is valid; providing at least a second version value for each data in the history table, where the second version value indicates an end of the period in which the data is valid; receiving a request for a version of a database; and retrieving the data with the first version value less than or equal to the requested version and the second version value greater than or equal to the requested version. By maintaining a history table with redundant version information, the system is able to provide efficient snapshot querying while also avoiding the overhead burden of conventional approaches. No aggregates, joins, or sub-queries are required to retrieve a snapshot.

Redundant version information in history table that enables efficient snapshot querying

A system for synchronizing data on a first device with data at a second device, includes: determining a pre-image of the data on the first device according to a filter after a previous synchronization with the data at the second device; determining a current image of the data at the second device according to the filter; determining a delta of the current image, where the delta comprises data that exists in the current image and has changed since the previous synchronization; instructing the first device to delete data that exists in the pre-image but not in the current image; and instructing the first device to UPSERT a union of the data that exists in the delta and the data that exists in the current image but not the pre-image. This is efficient in time and bandwidth resources while also providing consistent data integrity.

Incrementally sychronizing occasionally-connected mobile databases, preserving horizontal filter scope consistency by using client pre-image

A computer-implemented method for validating updated business rules. A first set of documents utilized to validate a first set of business rules is provided. A second set of business rules generated from an update of the first set of business rules is received. Each business rule includes input parameters. A second set of documents is received. A template file includes the input parameters and corresponding path expressions. An augmented set of documents includes the first and second sets of documents. The second set of business rules is automatically semantically validated against the augmented set of documents. The semantic validation includes executing the second set of business rules with each document of the augmented set. The executing includes binding, via the path expressions, the input parameters to values included in a document of the augmented set.

Validating updated business rules

A system and method for defining and dynamically invoking polymorphic call flows in a call flow system. Call flows are defined that include a publisher call flow and subscriber call flows. A first trigger point in a publisher call flow is defined. Triggers specifying late-binding references to trigger points are defined in the subscriber call flows. Subsequent to the call flows being published in a repository, the publisher call flow is executed, the first trigger point is located, and the publisher call flow is executed. Without changing any other call flow and without terminating and restarting the publisher call flow, a call flow is added to the call flow system and invoked or a call flow is removed.

System and method for defining and dynamically invoking polymorphic call flows

A method for specifying, deploying and updating work flows. A work flow comprising manual and automatic steps is created in a computing system A first XML schema set represents the automatic steps. The XML schemas in the first XML schema set identify software routines for performing the automatic steps. A second XML schema set represents the manual steps. The XML schemas in the second XML schema set include instructions directing human representatives to perform the manual steps. A runtime component executes the first and second XML schema sets. Without terminating the runtime component, a manual step is represented in an XML schema to be added to the first set. Representing the manual step includes transforming the manual step into an automatic step represented in the XML schema and adding to the XML schema a class name and method name identifying a software routine that performs the automatic step.

Method for specifying, deploying and dynamically updating work flows

A method for defining and dynamically invoking polymorphic call flows in a call flow system. A publisher call flow and subscriber call flows are defined. A first trigger point in the publisher call flow is defined. Triggers specifying late-binding references to trigger points are defined in the subscriber call flows. A second trigger point in a first subscriber call flow is defined. A trigger specifying a late-binding reference to the second trigger point is defined. Publishing the call flows includes storing a second subscriber call flow's representation that includes a first trigger's representation. To execute the publisher call flow, identifiers of the publisher call flow and the first trigger point are located in the first trigger's representation. Without changing any other call flow and without terminating and restarting the publisher call flow, a call flow is added to the call flow system and invoked.

Method for defining and dynamically invoking polymorphic call flows

A method and system for efficient snapshot querying include: providing a first version value for each data in a history table, where the first version value indicates a beginning of a period in which the data is valid; providing at least a second version value for each data in the history table, where the second version value indicates an end of the period in which the data is valid; receiving a request for a version of a database; and retrieving the data with the first version value less than or equal to the requested version and the second version value greater than or equal to the requested version. By maintaining a history table with redundant version information, the method and system are able to provide efficient snapshot querying while also avoiding the overhead burden of conventional approaches. No aggregates, joins, or sub-queries are required to retrieve a snapshot.

A method and system for synchronization-replication concurrency maintain a history table for a data table in a mirror, where the history table can include redundant version values that indicate a period in which data values corresponding to the version values are valid. Replication can thus be performed between a source and a mirror for a current version of the data table, while synchronization is simultaneously performed between the mirror and a client for an earlier version of the data table using the history table.

Synchronization-replication concurrency using non-shared snapshot query on a history table at read-uncommitted isolation level

A method for synchronizing data on a first device with data at a second device, includes: determining a pre-image of the data on the first device according to a filter after a previous synchronization with the data at the second device; determining a current image of the data at the second device according to the filter; determining a delta of the current image, where the delta comprises data that exists in the current image and has changed since the previous synchronization; instructing the first device to delete data that exists in the pre-image but not in the current image; and instructing the first device to UPSERT a union of the data that exists in the delta and the data that exists in the current image but not the pre-image. This is efficient in time and bandwidth resources while also providing consistent data integrity.

A technique is provided for generating one or more XML documents from a relational database using the XPath data model. Data stored on a data storage device that is connected to a computer is transformed. Initially, a document object model tee is generated using a document access definition, which defines the mapping between an XML tree structure and relational tables. The document object model tree is traversed to obtain information to retrieve relational data. The relational data is mapped to one or more XML documents.

Generating one or more XML documents from a relational database using XPath data model

A technique is provided for creating metadata for fast search of XML documents stored as column data. Data is stored in a data store connected to a computer. A main table is created in a relational database management system, wherein the main table has a column for storing an extensible markup language (XML) document in a native XML format One or more side tables are created in the relational database management system, wherein each side table has one or more columns that store one or more attributes extracted from die XML document for fast searching of the XML document. Thereafter, the side tables are used to locate data in the main table.

XML document stored as column data

A technique is provided to store fragmented XML data into a relational database by decomposing XML documents with application specific mappings. Data stored on a data store that is connected to a computer is transformed. Initially, an XML document containing XML data is received. A document access definition that identifies one or more relational tables and columns is received. The XML data is mapped from the application DTD to the relational tables and columns using the document access definition by generating a first document object model tree using the XML document, generating a second document object model tree using the document access definition, and mapping the data from the first document object model tree into columns in one or more relational rabies using the second document object model tree.

Storing fragmented XML data into a relational database by decomposing XML documents with application specific mappings

A technique is provided for generating one or more XML documents from a single SQL query. Data stored on a data storage device that is connected to a computer is transformed. A query is received that selects data stored in a relational database management system on the data storage device, wherein a data access definition defines: (1) a collection of one or more tables in the relational database management system for storing attributes from an XML document, (2) how data stored in the tables maps to the XML document, (3) a query for mapping the data stored in the tables to the XML document, and (4) a table that will contain the XML document after the XML document is generated. Then, one or more XML documents are generated from the selected data using the data access definition.

Growing community of inventors

San Jose, CA, United States of America

Isaac Kam-Chak Cheng