US20020133509A1 - Automatic data update - Google Patents
Automatic data update Download PDFInfo
- Publication number
- US20020133509A1 US20020133509A1 US09/804,034 US80403401A US2002133509A1 US 20020133509 A1 US20020133509 A1 US 20020133509A1 US 80403401 A US80403401 A US 80403401A US 2002133509 A1 US2002133509 A1 US 2002133509A1
- Authority
- US
- United States
- Prior art keywords
- user
- accessed data
- database
- data
- accessed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/174—Form filling; Merging
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99953—Recoverability
Definitions
- the present invention relates to automatically updating data elements used by software applications.
- the present invention relates to automatically updating data elements in form documents used by software applications.
- Existing systems can allow different or same applications accessing a common database to simultaneously use/access the database.
- applications using form documents that contain data elements allow users using the applications to simultaneously edit (update) the data elements in the forms.
- a data element may be, for example, a field, including entries (data) in the field.
- the system locks the common database or the applicable data elements when a first user begins working on a form, for example, to input or edit data elements, thereby precluding other users from accessing the common database, or working on the form or certain data elements of the form while the form is being accessed by the first user. Therefore, typical systems implement “a last in, last win” update procedure.
- data entered by a first user in a form can be overwritten by another user before the first user finalizes the form, such as by signing the form electronically, saving, printing or forwarding.
- the common database and the application-based database should be synchronized.
- a network environment such as a client-server network
- the common database is a network (server) database
- local application-based databases on client terminals advantageously allows users to perform application tasks without a network connection.
- a transaction log which is a database, can maintain a log of changes made to the application-based databases.
- the application-based databases can be synchronized with the common database at a later time, for example, when the user again connects to the network.
- Such synchronization gives rise to the problem of last in, last win when changes by users, respectively, are applied to the common database.
- changes made offline could become the latest changes in the main database irrespective of what other users had performed.
- the present invention can be attained by monitoring a database to detect changes to accessed data in the database, and updating the accessed data during use of the data in accordance with synchronization rules in response to the detected changes.
- the present invention can be attained by a device comprising a processor monitoring a database to detect changes to accessed data in the database, and updating the accessed data during use of the data in accordance with synchronization rules in response to the detected changes.
- the present invention can be attained by a process of accessing data stored in a database, inputting the accessed data to a form, using the form with the inputted accessed data by a first user, monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user, updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes, displaying update status of the accessed data in accordance with the updating, and storing the accessed data in the database by the first user.
- the rules are applied to synchronize simultaneous changes being made to data in a database.
- the update status of the accessed data can be a displayed message indicating if the accessed data has not been changed since the first user began using the accessed data; if the first user has changed the accessed data; and if the second user has changed the accessed data while the first user is using the accessed data.
- the present invention can be attained by implementing the process of the present invention in a standalone computer or a standalone processing device, in a network environment, such as a client-server system or the Internet.
- the present invention can be attained by a device comprising means for accessing data stored in a database; means for inputting the accessed data to a form; means for using the form with the inputted accessed data by a first user; means for monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user; and means for updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes.
- the present invention can be attained by a system to automatically update forms, the system comprising a server storing data in a database; and clients connected to the server via a network and accessing the data stored in the database, wherein the accessed data is input to a form used by a first user, the database being monitored to detect changes to the accessed data by a second user while the form is being used by the first user, and the accessed data in the form being updated while being used by the first user in accordance with rules corresponding to the detected changes.
- the present invention can be attained by a computer readable media encoded with processing instructions for implementing a method of automatically updating forms to be performed by a computer, the method comprising accessing data stored in a database; inputting the accessed data to a form; using the form with the inputted accessed data by a first user; monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user; and updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes.
- FIG. 1 is a functional block diagram of software according to the present invention in an embodiment of a computer system in which the present invention can be implemented.
- FIG. 2 is a functional block diagram of software according to the present invention in another embodiment of a computer system in which the present invention can be implemented.
- FIG. 3 is a flow chart of operations in the present invention.
- FIGS. 4 - 6 are flow charts of a software process according to the present invention.
- FIG. 1 is a functional block diagram of software according to the present invention as implemented in a network 10 .
- the network 10 may, for example, have a conventional topology and a conventional architecture, such as a client-server architecture, using conventional communication protocols.
- the network 10 can, for example, be a local area network or a wide area network, such as the Internet.
- at least one server 11 is in communication with network 12 and the server 11 stores data in a database 13 .
- the database 13 (also referred to as the common/network/central/main/primary database) can, for example, be a conventional (commercial) database management system (DBMS) supporting conventional or standard query languages, such as structured query language (SQL).
- DBMS database management system
- SQL structured query language
- Client terminals 14 a - 14 n are in communication with the network 12 and execute software that use/access the data in database 13 via the network 12 using the DBMS functions.
- the at least one server 11 and the client terminals 14 a - 14 n may, for example, be conventional computers, such as personal, portable and hand-held computers, or other computing devices, capable of storing, displaying and processing information, and communicating with remote computers and computing devices by receiving and transmitting information via a network using conventional techniques.
- Each client terminal 14 a can execute applications (software) 16 a - 16 n , which access the network database 13 to retrieve and store data in the database 13 for use, for example, by users. Use of the data may involve viewing, editing, input of new data (creation) in the database 13 or processing of the data. Further, application programs 16 a - 16 n may maintain local databases 18 a - n , respectively. Although, in one embodiment, an application program does not maintain a separate local database.
- the present invention can take the form of a program segment included in each application program 16 .
- the present invention takes the form of software processes (update process) 20 a - 20 n executing in a multi-tasking operating system environment in a computer and communicating using conventional programming techniques with the respective application programs 16 .
- each software process 20 may be implemented as a thread executing in the client terminals 14 . Operation of software processes 20 a - 20 n corresponding respectively to application programs 16 a - 16 n will be described in more detail below.
- FIG. 2 is a functional block diagram of software according to the present invention as implemented in a standalone computing device 30 .
- the computing device 30 may, for example, be a conventional computer, such as a personal, portable and hand-held computer, or other computing device, capable of storing, displaying and processing information.
- Storage devices to store information such as memory, hard drives, or drives for removable media (e.g., CD-R, CD-ROM, CD-RW, DVD-ROM, DVD-R and DVD-RAM) may be connected to the device 30 by conventional techniques to provide local storage for the device 30 .
- the computing device 30 may have the capability to communicate with other computers and computing devices by receiving and transmitting information via a network using conventional techniques.
- the Device 30 also executes applications (software) 16 a - 16 n .
- the application programs 16 a - 16 n access the common database 32 stored locally in the device 30 , to retrieve and store data in the database 32 for use, for example, by users.
- the database 32 can be a conventional DBMS supporting conventional or standard query languages, such as SQL. Use of the data may involve viewing, editing, input of new data (creation) in the database 32 or processing of the data.
- the application programs 16 a - 16 n may maintain corresponding application databases 18 a - 18 n , respectively.
- the present invention can take the form of a program segment included in each application program 16 , respectively.
- the present invention takes the form of software processes 20 a - 20 n executing in a multi-tasking operating system environment on the device 30 and communicating using conventional programming techniques with the respective application programs 16 .
- each software process 20 may be implemented as a thread executing in the device 30 .
- Operation of software processes 20 a - 20 n corresponding respectively to application programs 16 a - 16 n will be described in more detail below.
- the present invention is not limited or tied to any particular hardware architecture and FIGS. 1 and 2 as described above provide only examples.
- FIG. 3 Operation of the present invention will be described with reference to FIG. 3.
- the operation of the present invention is the same for the standalone or the network configuration. Therefore, operation of the network configuration (FIG. 1) will be described as an exemplary embodiment.
- an embodiment of the present invention takes the form of a software process in a system in which applications 16 use form documents.
- a health/clinical information system includes various applications that use and share forms to input, for example, patient data.
- the system of the present invention using conventional techniques maintains a history of the revisions by users of forms to the data in the database 13 .
- a transaction log database can maintain a log of changes made to the database 13 .
- an application 16 a opens a form at 40 , for example, based upon a user command, the application 16 accesses data corresponding to the form opened from the network database 13 and inputs the data in the form for processing (use) by the user.
- Each application 16 can use one or more forms and the forms can have overlapping data elements.
- an update status information or log of updates to the data elements in the opened form may be provided to the user at 42 , providing the user an opportunity to review the updates.
- the software process 20 a corresponding to the application 16 a periodically (as determined according to system requirements) checks the network database 13 at 44 for any available updates to data elements of the opened form. Further, the software process 20 a can maintain a history the revisions to the opened form, such that software process 20 a can determine a time the form or the local application-database 18 a was last synchronized with the network database 13 .
- rules corresponding to the changes in the database 13 are applied at 46 to update the data elements of the opened form. While the form is open, a user is notified of any updates to the opened form at 48 . Further, an update status information or log of the updates may be provided to the user at 48 , providing the user with the opportunity to review the updates and to change the updates if necessary before saving the form at 50 .
- the present invention provides an efficient last in, last win update procedure (i.e., synchronization) when simultaneous changes are being made to a database by substantially reducing or eliminating the undesirable effect of inadvertently (unintentionally) overwriting other users' data.
- providing update status information at 42 and 48 accommodates differentiating data (fields) that have been changed by the user who opened the form, fields that have not changed since the form was opened and fields that have been updated from the network database 13 while the form has remained opened.
- the user can review all current and past changes to the data (changes by the user and other users) in the form for validation before saving the data to the network database 13 , which in some circumstances may have legal ramifications, such as approval of the data by the user.
- automatic update of the form opened by a first user using data input by a second user eliminates unnecessary data entry by the first user. For example, one user can open a mostly blank form and complete (fill in) majority of the fields. Before the first user saves the form, a second user can open the same form at a different location to find that the form is mostly empty. If the first user saves the completed form, which saves data input in the form to the network database 13 , thereafter the second user's form would automatically by updated (filled) by the software process 20 of the present invention. The second user only has to complete remaining empty fields of the form, which saves time.
- FIGS. 4 - 6 are flow charts of an exemplary synchronization rule set applied in response to changes to a primary database to update the data elements of a form while the form is open.
- a form can be a collection of data elements/data points.
- a data element for example, may represent a “last name” and a “telephone number” field, including a last name and telephone number entry (data) in the field.
- software process 20 at 60 and 62 , periodically checks the database (e.g., network database 13 , local primary database 32 ) for available new data (updates) to accessed data in a form opened.
- the network database 13 is checked for an update. If updates are available, at 64 the new records (changed data elements and information related thereto) are retrieved from the network database 13 and loaded for processing as an array (list) of new records.
- the software process 20 checks records existing as of the last time the form was updated or as of the time the form was opened (old records) against new records (e.g., records from databases 13 , 32 ). For example, old records are records being used or worked on and can, for example, contain data stored in the application-based database 18 , or data stored in the client terminal 14 memory.
- old records with entries (data) or as edited (completed or filled data elements), for example by a user in the opened form are checked against the new records. If there is an old record to be processed in the opened form at 66 , the old record and the new record are compared at 68 for a data element match (i.e., is the old record the same data element as the new record, such as both are “last name”). A match, for example, can be determined if the records have the same type and index.
- Combination data elements in a form can contain one or more entries or selections, such as patient medications and allergies in a health information system. If the new record is a combination, a combination identification can also be used as a match criteria.
- the comparing is repeated for other old records in the opened form at 66 . If there is a match at 68 , the old record is checked at 70 to determine if the old record was updated by the user of the opened form. If the old record was updated by the user at 70 , the new record is checked at 72 to determine if the new record was electronically signed (esig). A data element may be electronically signed using conventional techniques, such as by requiring a password to edit the data element. If the new record was electronically signed, the electronic signature of the old record and the new record are compared for a match at 74 . If the electronic signature of the old and the new record do not match, the old record is replaced with the new electronically record at 76 .
- a status flag at 78 can be set to indicate occurrence of an update.
- the status flag can be used to provide a user with update status information, which will be described in more detail below.
- the new record is removed from the list of new records at 80 . Further, if there is no electronic signature on the new record at 72 , the new record is removed from the list of new records at 80 . Therefore, as a rule, an existing field (old record) completed by a user of an opened form is replaced or updated with new data from the database 13 only if the new data is electronically signed by another user (i.e., another user has higher priority, disallowing edits to the signed data element by other users).
- the user's current changes to the opened form (but not yet saved to the database 13 ), which may or may not be electronically signed, will be retained over changes from the network database 13 , unless the changes (e.g., by another user) from the network database 13 are electronically signed by the other users.
- the changes e.g., by another user
- the form opened by the second user will be updated with data from the signed data element by the first user.
- the new record is checked at 82 to determine if the new record is a delete record. If the new record is a delete record at 82 , the old record is marked as deleted at 84 and the new record is removed at 80 from the list of available new records. The marking indicates occurrence of an update.
- the example synchronization rule set in FIG. 4 provides: if there is a record in a form opened (old record), for example, by a user to use, and the old record was entered or modified by the user and there is a matching new record (e.g., from the network database 13 ) with no electronic signature, the new record will be removed from the array of new records without an update to the opened form ( 66 to 68 to 70 to 72 to 80 ). If there is an old record that was entered or modified by the user and there is a matching new record with a matching electronic signature (e.g., signed by the same user), the new record will be removed from the array of new records without an update to the opened form ( 66 to 68 to 70 to 74 to 80 ).
- the old record will be replaced (update will occur) by the new record ( 66 to 68 to 72 to 74 to 76 to 78 ). If there is an old record that was not entered or modified by the user and there is a matching new record marked as deleted, the old record will be marked as deleted (update will occur) and the new record will be removed from the array of new record ( 66 to 68 to 82 to 84 to 80 ).
- a non-matching electronic signature e.g., signed by a different user
- the old records and the new records are compared at 102 for a data element and content match (i.e., is the old record the same data element as the new record, such as both are “last name,” and does the entry in the old record, which may be blank or completed in a combo field, match the entry of the new record).
- a match for example, can be determined if the records have the same type, index and data. If the new record is a combination, a combination identification can also be used as a match criteria. If there is a match at 102 , the new record is removed at 104 from the array of new records and the comparing is repeated for other old records in the opened form at 100 .
- an update does not need to occur if entries (data) of a combination old record are the same as the entries of the new record. If there is not a match at 102 , the old record is checked at 106 to confirm if the old record and the new record match by being the same data element. A match, for example, can be determined if the records have the same type and index. If the new record is a combination data element, a combination identification can also be used as a match criteria.
- the old record is checked at 108 to determine if the old record is electronically signed and the new record is not electronically signed. If at 108 , the old record is signed and the new record is not signed, the update will not occur by removing at 104 the new record from the array of new records. Therefore, at 108 , because the old record is signed, under a rule to be applied, another user cannot overwrite or edit a signed data element of the user working on the opened form (i.e., the user of the opened form can save the form so that the signed data element will overwrite the other user's data).
- This rule is also consistent with the general rule (as described above) that a completed field and not signed by a user in an opened form will be retained over available update data from the network database 13 , unless the update data is signed having higher priority. Therefore, at 108 , if the old record is signed and the new record is also signed, update of the opened form can occur and the new record is checked for the type of update at 110 . Further, at 108 , if the old record is not signed and the new record is signed, update of the opened form can occur and the new record is checked for the type of update at 110 . Further, at 108 , if the old record is not signed and the new record is also not signed, update of the opened form can occur and the new record is checked for the type of update at 110 .
- the new record is a delete record
- the old record in the form is removed (i.e., the data entry of the field in the form is removed) at 112 and a status flag at 114 can be set to indicate occurrence of an update.
- the new record is not a delete record
- the old record in the form is replaced at 116 with the new record (i.e., the data entry of the field in the form is updated). Thereafter, a status flag at 114 can be set to indicate occurrence of an update.
- the new record is checked at 118 to determine if the new record is a delete record. If at 118 , the new record is a delete record, the new record is removed at 104 from the array of new records to stop processing of the new record. If at 118 , the new record is not a delete record, the new user record is added at 120 to the old user record array. Therefore, at 120 , the data entry of a combination field in the form is updated, for example, by adding data entries, such as another medication to the “medication” field. Thereafter, a status flag at 114 can be set to indicate occurrence of an update.
- the example synchronization rule set in FIG. 5 provides: if there is a new record that exactly (i.e., same data element and entry) matches an old record, the new record will be removed ( 100 to 102 to 104 ). If there is a new record that is electronically signed and there is a matching old record, the old record will be replaced (update will occur) with the new record ( 100 to 106 to 108 to 110 to 116 to 114 to 104 ). If there is a new record that is marked as deleted that matches an old record that is not electronically signed, the old record will be removed (update will occur) ( 100 to 106 to 108 to 110 to 112 to 114 to 104 ).
- the old record will be replaced (update will occur) with the new record ( 100 to 106 to 108 to 110 to 116 to 114 to 104 ). If there is a new record that is not electronically signed that matches an old record that is electronically signed, the new record will be removed without an update to opened form ( 100 to 106 to 108 to 104 ). If there is a new record that does not match any old record, the new record will be added to the array of old records (i.e., update will occur by completing a data element in the opened form or adding an entry to a combination data element in the opened form) ( 100 to 106 to 118 to 120 to 114 to 104 ). If there is a new record that is marked as deleted and does not match any old record, the new record will be removed from the array of new records without updating the opened form ( 100 to 106 to 118 to 104 ).
- synchronization rule sets can be applied and the present invention is not limited to the exemplary synchronization rule set described with reference to FIG. 5 .
- a new record can be presented to the user for consideration/approval before automatically updating the user's form. Therefore a selective automatic data refresh can be provided.
- the software process 20 of the present invention can extend to n-users and n-forms. For example, if four users are editing forms, and one of the users saves data, the other three users can get updates if their forms contain data elements the overlap with the user who saved the data.
- the system determines at 130 if the updated data elements were viewable on a display screen of the client terminal 14 . If the updated data elements are not viewable at 130 , processing of the new records from the database 13 is complete. If the updated data elements are viewable, a message can be displayed at 132 to indicate or notify the user working on the opened form of updates. For all viewable records (data elements), at 134 - 144 , update history/log information can be displayed on a display screen of client terminal 14 .
- the update log information can be displayed using different colors, icons, or commentary bubbles, to provide the user the opportunity to review the updates, types of updates and to accommodate efficient validation/confirmation or authorization of the updates.
- a specified “updated by user” color can be used at 146 to display entries (data) of the field.
- entries of a field can be displayed with a specified “updated from the network database” color.
- entries of a field can be displayed with a specified “deleted by user” color.
- entries of a field can be displayed with a specified “deleted from the network database” color.
- entries of a field can be displayed with a specified “no changes made” color.
- the icons and information bubbles can be any type of information or image associated with types of updates to a data element in a form opened and displayed on a computer.
- the present invention can, for example, advantageously provide a system allowing multiple users to work simultaneously using data from a database without locking the common database. Further, the present invention can, for example, provide a system allowing multiple users to work simultaneously using data from a database without inadvertently overwriting prior data input in the database by another user. Further, the present invention can, for example, provide a system informing users working simultaneously using data from a database of changes made by other users to the database while working on the data.
- the present invention can, for example, provide a system allowing users using applications, which may be different applications, that use form documents containing data from a database to access, edit and update the form data (data elements) without locking the database, to prevent inadvertently overwriting changes to the database by other users while a first user is editing (updating) the form data, and to inform the users of changes to the database by other users while the users are accessing the form data.
- the present invention can, for example, provide an efficient data refresh during use of an application, by applying synchronization rules to update data elements in the application during execution.
- the present invention can, for example, provide a system allowing users to efficiently and simultaneously edit form documents, which are a collection of data elements/points from a database. Further, the system of the present invention accommodates different forms used by different applications, the forms having overlapping (sharing) data elements.
Abstract
A process of accessing data in a database, inputting the accessed data to a form, using the form with the accessed data by a first user, monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user, updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes, and displaying update status of the accessed data in accordance with the updating. The update status can indicate if the accessed data has not been changed since the first user began using the accessed data; if the first user has changed the accessed data; and if the second user has changed the accessed data while the first user is using the accessed data. The process can be implemented in a standalone processing device or in a network.
Description
- 1. Field of the Invention
- The present invention relates to automatically updating data elements used by software applications. In particular, the present invention relates to automatically updating data elements in form documents used by software applications.
- 2. Description of the Related Art
- Existing systems can allow different or same applications accessing a common database to simultaneously use/access the database. In particular, applications using form documents that contain data elements allow users using the applications to simultaneously edit (update) the data elements in the forms. A data element may be, for example, a field, including entries (data) in the field. Typically, to achieve such simultaneous use the system locks the common database or the applicable data elements when a first user begins working on a form, for example, to input or edit data elements, thereby precluding other users from accessing the common database, or working on the form or certain data elements of the form while the form is being accessed by the first user. Therefore, typical systems implement “a last in, last win” update procedure. In particular, in a typical system data entered by a first user in a form can be overwritten by another user before the first user finalizes the form, such as by signing the form electronically, saving, printing or forwarding.
- Further, in existing systems maintaining a common (main/primary/central) database and a local (application-based) database, the common database and the application-based database should be synchronized. For example, in a network environment, such as a client-server network, where the common database is a network (server) database, local application-based databases on client terminals advantageously allows users to perform application tasks without a network connection. When maintaining two separate databases, either in a network environment or in a standalone environment where multiple applications execute, each with an application-based database and a local common database, a transaction log, which is a database, can maintain a log of changes made to the application-based databases. The application-based databases can be synchronized with the common database at a later time, for example, when the user again connects to the network. Such synchronization, however, gives rise to the problem of last in, last win when changes by users, respectively, are applied to the common database. For example, in the network environment, upon synchronization, changes made offline could become the latest changes in the main database irrespective of what other users had performed.
- More particularly, in the system maintaining two databases and using forms that share or use common data elements, when users simultaneously edit the common data elements in different forms, a user cannot be aware of changes made by other users, potentially overwriting (deleting) the other users' data. Further, in such a system the user can approve a form without knowledge of changes made by the other users. In addition, such a system provides inefficient data input by the users. For example, two users open the same empty form or different empty forms that share common data elements, when a first user completes the form and saves the form (storing data in the main database), the second user would not know that some of the fields in the form opened by the second user have already been completed by the first user. Therefore, when the second user also completes the fields and saves the form, the first user's data are overwritten or deleted. Further, the second user cannot take advantage of using fields already completed by the first user, requiring repetitious data entry.
- According to the embodiments of the present invention, the present invention can be attained by monitoring a database to detect changes to accessed data in the database, and updating the accessed data during use of the data in accordance with synchronization rules in response to the detected changes.
- Further, the present invention can be attained by a device comprising a processor monitoring a database to detect changes to accessed data in the database, and updating the accessed data during use of the data in accordance with synchronization rules in response to the detected changes.
- Further, the present invention can be attained by a process of accessing data stored in a database, inputting the accessed data to a form, using the form with the inputted accessed data by a first user, monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user, updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes, displaying update status of the accessed data in accordance with the updating, and storing the accessed data in the database by the first user. The rules are applied to synchronize simultaneous changes being made to data in a database. The update status of the accessed data can be a displayed message indicating if the accessed data has not been changed since the first user began using the accessed data; if the first user has changed the accessed data; and if the second user has changed the accessed data while the first user is using the accessed data. Further, the present invention can be attained by implementing the process of the present invention in a standalone computer or a standalone processing device, in a network environment, such as a client-server system or the Internet.
- Further, the present invention can be attained by a device comprising means for accessing data stored in a database; means for inputting the accessed data to a form; means for using the form with the inputted accessed data by a first user; means for monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user; and means for updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes.
- Further, the present invention can be attained by a system to automatically update forms, the system comprising a server storing data in a database; and clients connected to the server via a network and accessing the data stored in the database, wherein the accessed data is input to a form used by a first user, the database being monitored to detect changes to the accessed data by a second user while the form is being used by the first user, and the accessed data in the form being updated while being used by the first user in accordance with rules corresponding to the detected changes.
- Further the present invention can be attained by a computer readable media encoded with processing instructions for implementing a method of automatically updating forms to be performed by a computer, the method comprising accessing data stored in a database; inputting the accessed data to a form; using the form with the inputted accessed data by a first user; monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user; and updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes.
- The advantages of the invention will become apparent and more readily appreciated from the following description of the preferred embodiments, taken in conjunction with the accompanying drawings of which:
- FIG. 1 is a functional block diagram of software according to the present invention in an embodiment of a computer system in which the present invention can be implemented.
- FIG. 2 is a functional block diagram of software according to the present invention in another embodiment of a computer system in which the present invention can be implemented.
- FIG. 3 is a flow chart of operations in the present invention.
- FIGS.4-6 are flow charts of a software process according to the present invention.
- Reference will now be made in detail to the present preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below in order to explain the present invention by referring to the figures.
- FIG. 1 is a functional block diagram of software according to the present invention as implemented in a
network 10. Thenetwork 10 may, for example, have a conventional topology and a conventional architecture, such as a client-server architecture, using conventional communication protocols. Thenetwork 10 can, for example, be a local area network or a wide area network, such as the Internet. Referring to FIG. 1, at least one server 11 is in communication withnetwork 12 and the server 11 stores data in adatabase 13. The database 13 (also referred to as the common/network/central/main/primary database) can, for example, be a conventional (commercial) database management system (DBMS) supporting conventional or standard query languages, such as structured query language (SQL).Client terminals 14 a-14 n are in communication with thenetwork 12 and execute software that use/access the data indatabase 13 via thenetwork 12 using the DBMS functions. The at least one server 11 and theclient terminals 14 a-14 n may, for example, be conventional computers, such as personal, portable and hand-held computers, or other computing devices, capable of storing, displaying and processing information, and communicating with remote computers and computing devices by receiving and transmitting information via a network using conventional techniques. - Each client terminal14 a can execute applications (software) 16 a-16 n, which access the
network database 13 to retrieve and store data in thedatabase 13 for use, for example, by users. Use of the data may involve viewing, editing, input of new data (creation) in thedatabase 13 or processing of the data. Further, application programs 16 a-16 n may maintain local databases 18 a-n, respectively. Although, in one embodiment, an application program does not maintain a separate local database. The present invention can take the form of a program segment included in each application program 16. In a preferred embodiment, the present invention takes the form of software processes (update process) 20 a-20 n executing in a multi-tasking operating system environment in a computer and communicating using conventional programming techniques with the respective application programs 16. In particular, each software process 20 may be implemented as a thread executing in theclient terminals 14. Operation of software processes 20 a-20 n corresponding respectively to application programs 16 a-16 n will be described in more detail below. - FIG. 2 is a functional block diagram of software according to the present invention as implemented in a
standalone computing device 30. Thecomputing device 30 may, for example, be a conventional computer, such as a personal, portable and hand-held computer, or other computing device, capable of storing, displaying and processing information. Storage devices to store information, such as memory, hard drives, or drives for removable media (e.g., CD-R, CD-ROM, CD-RW, DVD-ROM, DVD-R and DVD-RAM) may be connected to thedevice 30 by conventional techniques to provide local storage for thedevice 30. Although not required for the present invention when implemented in a standalone system, thecomputing device 30 may have the capability to communicate with other computers and computing devices by receiving and transmitting information via a network using conventional techniques.Device 30 also executes applications (software) 16 a-16 n. The application programs 16 a-16 n access thecommon database 32 stored locally in thedevice 30, to retrieve and store data in thedatabase 32 for use, for example, by users. Similar to the embodiment shown in FIG. 1, thedatabase 32 can be a conventional DBMS supporting conventional or standard query languages, such as SQL. Use of the data may involve viewing, editing, input of new data (creation) in thedatabase 32 or processing of the data. Further, although not required, the application programs 16 a-16 n may maintain corresponding application databases 18 a-18 n, respectively. The present invention can take the form of a program segment included in each application program 16, respectively. In a preferred embodiment, the present invention takes the form of software processes 20 a-20 n executing in a multi-tasking operating system environment on thedevice 30 and communicating using conventional programming techniques with the respective application programs 16. In particular, each software process 20 may be implemented as a thread executing in thedevice 30. Operation of software processes 20 a-20 n corresponding respectively to application programs 16 a-16 n will be described in more detail below. Of course, the present invention is not limited or tied to any particular hardware architecture and FIGS. 1 and 2 as described above provide only examples. - Operation of the present invention will be described with reference to FIG. 3. The operation of the present invention is the same for the standalone or the network configuration. Therefore, operation of the network configuration (FIG. 1) will be described as an exemplary embodiment. While the present invention is directed to synchronization of simultaneous changes by users to a database, an embodiment of the present invention takes the form of a software process in a system in which applications16 use form documents. For example, a health/clinical information system includes various applications that use and share forms to input, for example, patient data. The system of the present invention using conventional techniques maintains a history of the revisions by users of forms to the data in the
database 13. For example, a transaction log database can maintain a log of changes made to thedatabase 13. When an application 16 a opens a form at 40, for example, based upon a user command, the application 16 accesses data corresponding to the form opened from thenetwork database 13 and inputs the data in the form for processing (use) by the user. Each application 16 can use one or more forms and the forms can have overlapping data elements. - Because the history of the changes to the data in the
network database 13 is maintained, an update status information or log of updates to the data elements in the opened form may be provided to the user at 42, providing the user an opportunity to review the updates. Thesoftware process 20 a corresponding to the application 16 a periodically (as determined according to system requirements) checks thenetwork database 13 at 44 for any available updates to data elements of the opened form. Further, thesoftware process 20 a can maintain a history the revisions to the opened form, such thatsoftware process 20 a can determine a time the form or the local application-database 18 a was last synchronized with thenetwork database 13. If changes to the data elements of the opened form are available, rules corresponding to the changes in thedatabase 13 are applied at 46 to update the data elements of the opened form. While the form is open, a user is notified of any updates to the opened form at 48. Further, an update status information or log of the updates may be provided to the user at 48, providing the user with the opportunity to review the updates and to change the updates if necessary before saving the form at 50. - Therefore, the present invention provides an efficient last in, last win update procedure (i.e., synchronization) when simultaneous changes are being made to a database by substantially reducing or eliminating the undesirable effect of inadvertently (unintentionally) overwriting other users' data. Further, providing update status information at42 and 48 accommodates differentiating data (fields) that have been changed by the user who opened the form, fields that have not changed since the form was opened and fields that have been updated from the
network database 13 while the form has remained opened. The user can review all current and past changes to the data (changes by the user and other users) in the form for validation before saving the data to thenetwork database 13, which in some circumstances may have legal ramifications, such as approval of the data by the user. Further, automatic update of the form opened by a first user using data input by a second user eliminates unnecessary data entry by the first user. For example, one user can open a mostly blank form and complete (fill in) majority of the fields. Before the first user saves the form, a second user can open the same form at a different location to find that the form is mostly empty. If the first user saves the completed form, which saves data input in the form to thenetwork database 13, thereafter the second user's form would automatically by updated (filled) by the software process 20 of the present invention. The second user only has to complete remaining empty fields of the form, which saves time. - The operation of software process20 will be described in more detail with reference to FIGS. 4-6. In particular, FIGS. 4-6 are flow charts of an exemplary synchronization rule set applied in response to changes to a primary database to update the data elements of a form while the form is open. A form can be a collection of data elements/data points. A data element, for example, may represent a “last name” and a “telephone number” field, including a last name and telephone number entry (data) in the field. In FIG. 4, software process 20, at 60 and 62, periodically checks the database (e.g.,
network database 13, local primary database 32) for available new data (updates) to accessed data in a form opened. In particular, for each data element in an opened form, at 62 thenetwork database 13 is checked for an update. If updates are available, at 64 the new records (changed data elements and information related thereto) are retrieved from thenetwork database 13 and loaded for processing as an array (list) of new records. The software process 20 checks records existing as of the last time the form was updated or as of the time the form was opened (old records) against new records (e.g., records fromdatabases 13, 32). For example, old records are records being used or worked on and can, for example, contain data stored in the application-based database 18, or data stored in theclient terminal 14 memory. Initially, at 66 old records with entries (data) or as edited (completed or filled data elements), for example by a user, in the opened form are checked against the new records. If there is an old record to be processed in the opened form at 66, the old record and the new record are compared at 68 for a data element match (i.e., is the old record the same data element as the new record, such as both are “last name”). A match, for example, can be determined if the records have the same type and index. Combination data elements in a form can contain one or more entries or selections, such as patient medications and allergies in a health information system. If the new record is a combination, a combination identification can also be used as a match criteria. If there is not a match at 68, the comparing is repeated for other old records in the opened form at 66. If there is a match at 68, the old record is checked at 70 to determine if the old record was updated by the user of the opened form. If the old record was updated by the user at 70, the new record is checked at 72 to determine if the new record was electronically signed (esig). A data element may be electronically signed using conventional techniques, such as by requiring a password to edit the data element. If the new record was electronically signed, the electronic signature of the old record and the new record are compared for a match at 74. If the electronic signature of the old and the new record do not match, the old record is replaced with the new electronically record at 76. Therefore, at 76 a data element of the opened form is updated with a changed data element from thedatabase 13. A status flag at 78 can be set to indicate occurrence of an update. The status flag can be used to provide a user with update status information, which will be described in more detail below. - If at74, the electronic signature of the new record matches the electronic signature of the old record, the new record is removed from the list of new records at 80. Further, if there is no electronic signature on the new record at 72, the new record is removed from the list of new records at 80. Therefore, as a rule, an existing field (old record) completed by a user of an opened form is replaced or updated with new data from the
database 13 only if the new data is electronically signed by another user (i.e., another user has higher priority, disallowing edits to the signed data element by other users). As a general rule, the user's current changes to the opened form (but not yet saved to the database 13), which may or may not be electronically signed, will be retained over changes from thenetwork database 13, unless the changes (e.g., by another user) from thenetwork database 13 are electronically signed by the other users. For example, if a first user signs a data element and saves the data element in thenetwork database 13, entry (data) in the signed data element cannot be modified or removed by a second user who has opened a form that includes the same signed data element and the second user has changed and signed the same data element but has not yet saved the data element to thedatabase 13. Under this circumstance, the form opened by the second user will be updated with data from the signed data element by the first user. - If at70, the old record has not been updated by the user, the new record is checked at 82 to determine if the new record is a delete record. If the new record is a delete record at 82, the old record is marked as deleted at 84 and the new record is removed at 80 from the list of available new records. The marking indicates occurrence of an update.
- In summary, the example synchronization rule set in FIG. 4 provides: if there is a record in a form opened (old record), for example, by a user to use, and the old record was entered or modified by the user and there is a matching new record (e.g., from the network database13) with no electronic signature, the new record will be removed from the array of new records without an update to the opened form (66 to 68 to 70 to 72 to 80). If there is an old record that was entered or modified by the user and there is a matching new record with a matching electronic signature (e.g., signed by the same user), the new record will be removed from the array of new records without an update to the opened form (66 to 68 to 70 to 74 to 80). If there is an old record that was entered or modified by the user and there is a matching new record with a non-matching electronic signature (e.g., signed by a different user), the old record will be replaced (update will occur) by the new record (66 to 68 to 72 to 74 to 76 to 78). If there is an old record that was not entered or modified by the user and there is a matching new record marked as deleted, the old record will be marked as deleted (update will occur) and the new record will be removed from the array of new record (66 to 68 to 82 to 84 to 80). Of course, other synchronization rule sets can be applied in the present invention and the present invention is not limited to the exemplary synchronization rule set in FIGS. 4-6.
- With reference to FIG. 5, if the condition at66 is not satisfied, remaining new records in the array of new records are processed starting at 100. In particular, at 100 any new records that were added to the array of old records (i.e., array of records in the opened form and being used or worked on) will be considered old records for processing at 100. Generally, at 100 remaining old records to be processed are empty/blank and combination records in which additional information may be input, such as the “medication” field containing one or more medication names. If there are old records at 100, the old records and the new records are compared at 102 for a data element and content match (i.e., is the old record the same data element as the new record, such as both are “last name,” and does the entry in the old record, which may be blank or completed in a combo field, match the entry of the new record). A match, for example, can be determined if the records have the same type, index and data. If the new record is a combination, a combination identification can also be used as a match criteria. If there is a match at 102, the new record is removed at 104 from the array of new records and the comparing is repeated for other old records in the opened form at 100. Therefore, an update does not need to occur if entries (data) of a combination old record are the same as the entries of the new record. If there is not a match at 102, the old record is checked at 106 to confirm if the old record and the new record match by being the same data element. A match, for example, can be determined if the records have the same type and index. If the new record is a combination data element, a combination identification can also be used as a match criteria.
- If there is a match at106, the old record is checked at 108 to determine if the old record is electronically signed and the new record is not electronically signed. If at 108, the old record is signed and the new record is not signed, the update will not occur by removing at 104 the new record from the array of new records. Therefore, at 108, because the old record is signed, under a rule to be applied, another user cannot overwrite or edit a signed data element of the user working on the opened form (i.e., the user of the opened form can save the form so that the signed data element will overwrite the other user's data). This rule is also consistent with the general rule (as described above) that a completed field and not signed by a user in an opened form will be retained over available update data from the
network database 13, unless the update data is signed having higher priority. Therefore, at 108, if the old record is signed and the new record is also signed, update of the opened form can occur and the new record is checked for the type of update at 110. Further, at 108, if the old record is not signed and the new record is signed, update of the opened form can occur and the new record is checked for the type of update at 110. Further, at 108, if the old record is not signed and the new record is also not signed, update of the opened form can occur and the new record is checked for the type of update at 110. - If at110, the new record is a delete record, the old record in the form is removed (i.e., the data entry of the field in the form is removed) at 112 and a status flag at 114 can be set to indicate occurrence of an update. If at 110, the new record is not a delete record, the old record in the form is replaced at 116 with the new record (i.e., the data entry of the field in the form is updated). Thereafter, a status flag at 114 can be set to indicate occurrence of an update.
- If at106 the old record and the new record do not match, the new record is checked at 118 to determine if the new record is a delete record. If at 118, the new record is a delete record, the new record is removed at 104 from the array of new records to stop processing of the new record. If at 118, the new record is not a delete record, the new user record is added at 120 to the old user record array. Therefore, at 120, the data entry of a combination field in the form is updated, for example, by adding data entries, such as another medication to the “medication” field. Thereafter, a status flag at 114 can be set to indicate occurrence of an update. At 104, after the status flag is set at 114, after a data element of the form has been updated, or after processing of a new update record, the new record is removed from the array of new records and the process to check old records of the form at 100 is repeated.
- In summary, the example synchronization rule set in FIG. 5 provides: if there is a new record that exactly (i.e., same data element and entry) matches an old record, the new record will be removed (100 to 102 to 104). If there is a new record that is electronically signed and there is a matching old record, the old record will be replaced (update will occur) with the new record (100 to 106 to 108 to 110 to 116 to 114 to 104). If there is a new record that is marked as deleted that matches an old record that is not electronically signed, the old record will be removed (update will occur) (100 to 106 to 108 to 110 to 112 to 114 to 104). If there is a new record that is not electronically signed that matches an old record that is not electronically signed, the old record will be replaced (update will occur) with the new record (100 to 106 to 108 to 110 to 116 to 114 to 104). If there is a new record that is not electronically signed that matches an old record that is electronically signed, the new record will be removed without an update to opened form (100 to 106 to 108 to 104). If there is a new record that does not match any old record, the new record will be added to the array of old records (i.e., update will occur by completing a data element in the opened form or adding an entry to a combination data element in the opened form) (100 to 106 to 118 to 120 to 114 to 104). If there is a new record that is marked as deleted and does not match any old record, the new record will be removed from the array of new records without updating the opened form (100 to 106 to 118 to 104).
- Of course, other synchronization rule sets can be applied and the present invention is not limited to the exemplary synchronization rule set described with reference to FIG.5. For example, a new record can be presented to the user for consideration/approval before automatically updating the user's form. Therefore a selective automatic data refresh can be provided. Further, the software process 20 of the present invention can extend to n-users and n-forms. For example, if four users are editing forms, and one of the users saves data, the other three users can get updates if their forms contain data elements the overlap with the user who saved the data.
- With reference to FIG. 6, if at100, there are not other old records to be processed, the system determines at 130 if the updated data elements were viewable on a display screen of the
client terminal 14. If the updated data elements are not viewable at 130, processing of the new records from thedatabase 13 is complete. If the updated data elements are viewable, a message can be displayed at 132 to indicate or notify the user working on the opened form of updates. For all viewable records (data elements), at 134-144, update history/log information can be displayed on a display screen ofclient terminal 14. In particular, the update log information can be displayed using different colors, icons, or commentary bubbles, to provide the user the opportunity to review the updates, types of updates and to accommodate efficient validation/confirmation or authorization of the updates. For example, if at 138 a form data element (field) has been updated by the user of the opened form, a specified “updated by user” color can be used at 146 to display entries (data) of the field. At 148, entries of a field can be displayed with a specified “updated from the network database” color. At 150, entries of a field can be displayed with a specified “deleted by user” color. At 152, entries of a field can be displayed with a specified “deleted from the network database” color. At 148, entries of a field can be displayed with a specified “no changes made” color. Of course, the icons and information bubbles can be any type of information or image associated with types of updates to a data element in a form opened and displayed on a computer. - Therefore, the present invention can, for example, advantageously provide a system allowing multiple users to work simultaneously using data from a database without locking the common database. Further, the present invention can, for example, provide a system allowing multiple users to work simultaneously using data from a database without inadvertently overwriting prior data input in the database by another user. Further, the present invention can, for example, provide a system informing users working simultaneously using data from a database of changes made by other users to the database while working on the data.
- More particularly, the present invention can, for example, provide a system allowing users using applications, which may be different applications, that use form documents containing data from a database to access, edit and update the form data (data elements) without locking the database, to prevent inadvertently overwriting changes to the database by other users while a first user is editing (updating) the form data, and to inform the users of changes to the database by other users while the users are accessing the form data. Further, the present invention can, for example, provide an efficient data refresh during use of an application, by applying synchronization rules to update data elements in the application during execution. In particular, the present invention can, for example, provide a system allowing users to efficiently and simultaneously edit form documents, which are a collection of data elements/points from a database. Further, the system of the present invention accommodates different forms used by different applications, the forms having overlapping (sharing) data elements.
- Although a few preferred embodiments of the present invention have been shown and described, it would be appreciated by those skilled in the art that changes may be made in this embodiment without departing from the principles and spirit of the invention, the scope of which is defined in the claims and their equivalents.
Claims (17)
1. A process comprising:
monitoring a database to detect changes to accessed data in the database; and
updating the accessed data during use of the data in accordance with synchronization rules in response to the detected changes.
2. A device comprising:
a processor monitoring a database to detect changes to accessed data in the database, and updating the accessed data during use of the data in accordance with synchronization rules in response to the detected changes.
3. A process comprising:
accessing data stored in a database;
inputting the accessed data to a form;
using the form with the inputted accessed data by a first user;
monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user; and
updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes.
4. The process according to claim 3 , further comprising:
displaying update status of the accessed data in accordance with the updating; and
storing the inputted accessed data used by the first user in the database.
5. A device comprising:
a processor to access data stored in a database, to input the accessed data to a form, to use the form with the input accessed data by a first user, to monitor the database to detect changes to the accessed data by a second user while the form is being used by the first user, and to update the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes.
6. The device according to claim 5 , wherein the rules synchronize simultaneous changes made by the first user and the second user to the accessed data.
7. The device according to claim 5 , wherein the rules are based upon characteristic of edits by a second user to the accessed data and characteristic of the accessed data.
8. The device according to claim 5 , wherein use of the accessed data by the first user includes editing the accessed data.
9. The device according to claim 5 , wherein the processor provides update notification to the first user while the form is being used by the first user.
10. The device according to claim 9 , wherein the update notification comprises displaying update history information corresponding to each accessed data in the form.
11. The device according to claim 10 , wherein the update notification includes displaying the accessed data in different colors in accordance with the updating.
12. The device according to claim 10 , wherein the update notification includes associating comment bubbles with the accessed data.
13. The device according to claim 5 , wherein the inputted accessed data is stored locally and the database is stored remotely.
14. The device according to claim 5 , wherein the processor further maintains a change log of the accessed data.
15. A device comprising:
means for accessing data stored in a database;
means for inputting the accessed data to a form;
means for using the form with the inputted accessed data by a first user;
means for monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user; and
means for updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes.
16. A system to automatically update forms, the system comprising:
a server storing data in a database; and
clients connected to the server via a network and accessing the data stored in the database, wherein the accessed data is input to a form used by a first user, the database being monitored to detect changes to the accessed data by a second user while the form is being used by the first user, and the accessed data in the form being updated while being used by the first user in accordance with rules corresponding to the detected changes.
17. A computer readable medium encoded with processing instructions for implementing a method of automatically updating forms to be performed by a computer, the method comprising:
accessing data stored in a database;
inputting the accessed data to a form;
using the form with the inputted accessed data by a first user;
monitoring the database to detect changes to the accessed data by a second user while the form is being used by the first user; and
updating the accessed data in the form while being used by the first user in accordance with rules corresponding to the detected changes.
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/804,034 US7058663B2 (en) | 2001-03-13 | 2001-03-13 | Automatic data update |
JP2002572023A JP2004528636A (en) | 2001-03-13 | 2002-02-25 | Automatic data update |
PCT/US2002/005665 WO2002073432A1 (en) | 2001-03-13 | 2002-02-25 | Automatic data update |
CN02800640A CN1459061A (en) | 2001-03-13 | 2002-02-25 | Automatic data update |
EP02707884A EP1370959A4 (en) | 2001-03-13 | 2002-02-25 | Automatic data update |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/804,034 US7058663B2 (en) | 2001-03-13 | 2001-03-13 | Automatic data update |
Publications (2)
Publication Number | Publication Date |
---|---|
US20020133509A1 true US20020133509A1 (en) | 2002-09-19 |
US7058663B2 US7058663B2 (en) | 2006-06-06 |
Family
ID=25188022
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/804,034 Expired - Fee Related US7058663B2 (en) | 2001-03-13 | 2001-03-13 | Automatic data update |
Country Status (5)
Country | Link |
---|---|
US (1) | US7058663B2 (en) |
EP (1) | EP1370959A4 (en) |
JP (1) | JP2004528636A (en) |
CN (1) | CN1459061A (en) |
WO (1) | WO2002073432A1 (en) |
Cited By (140)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020138315A1 (en) * | 2001-03-20 | 2002-09-26 | Mineo Nozaki | Technical support system |
US20030088590A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | Method, system and computer program product for providing backup data for use in studying claims |
US20030088451A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | Technical support system |
US20030088454A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | System, method and computer program product for complaint report issue |
US20030088330A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | Method, system and computer program product for coping with the changes in hardware |
US20030088641A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | Technical support system |
US20030088453A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | System, method and computer program product for rank assignment |
US20030110168A1 (en) * | 2001-12-07 | 2003-06-12 | Harold Kester | System and method for adapting an internet filter |
US20030115087A1 (en) * | 2001-11-02 | 2003-06-19 | Toshiba Tec Kabushiki Kaisha | Technical support system |
US20040015586A1 (en) * | 2000-01-28 | 2004-01-22 | Ronald Hegli | System and method for controlling access to internet sites |
US20040088245A1 (en) * | 2002-11-04 | 2004-05-06 | Manoj Narayan | Systems and methods for producing documentary credit and conforming shipping documents |
US20040181788A1 (en) * | 2003-03-14 | 2004-09-16 | Websense Inc | System and method of monitoring and controlling application files |
US20050210035A1 (en) * | 2003-03-14 | 2005-09-22 | Kester Harold M | System and method of monitoring and controlling application files |
US20050267902A1 (en) * | 2001-07-20 | 2005-12-01 | Surfcontrol Plc | Database and method of generating same |
US20060031504A1 (en) * | 2001-12-05 | 2006-02-09 | Hegli Ronald B | Filtering techniques for managing access to Internet sites or other software applications |
US20060095358A1 (en) * | 2004-02-11 | 2006-05-04 | Viarengo Steve M | Method and system for automatically detecting that international shipment movement has satisfied a threshold condition |
US20070005435A1 (en) * | 2003-08-11 | 2007-01-04 | Sony Corporation | Communication system and communication method |
US20070050777A1 (en) * | 2003-06-09 | 2007-03-01 | Hutchinson Thomas W | Duration of alerts and scanning of large data stores |
US20070150956A1 (en) * | 2005-12-28 | 2007-06-28 | Sharma Rajesh K | Real time lockdown |
US20070276877A1 (en) * | 2004-07-22 | 2007-11-29 | Locke Victoria A | Synchronization of application documentation across database instances |
US20070294316A1 (en) * | 2004-07-22 | 2007-12-20 | Hicks Scott D | Synchronization of application rules across database instances |
US7523391B1 (en) * | 2003-03-25 | 2009-04-21 | Microsoft Corporation | Indicating change to data form |
US20090210459A1 (en) * | 2008-02-19 | 2009-08-20 | International Business Machines Corporation | Document synchronization solution |
US20090254589A1 (en) * | 2008-04-07 | 2009-10-08 | International Business Machines Corporation | Client side caching of synchronized data |
US20090287750A1 (en) * | 2002-03-29 | 2009-11-19 | International Business Machines Corporation | Method and Apparatus for Content Pre-Fetching and Preparation |
US7890642B2 (en) | 2004-08-07 | 2011-02-15 | Websense Uk Limited | Device internet resource access filtering system and method |
US20110173947A1 (en) * | 2010-01-19 | 2011-07-21 | General Electric Company | System and method for gas turbine power augmentation |
US8015174B2 (en) | 2007-02-28 | 2011-09-06 | Websense, Inc. | System and method of controlling access to the internet |
US8020206B2 (en) | 2006-07-10 | 2011-09-13 | Websense, Inc. | System and method of analyzing web content |
US8024471B2 (en) | 2004-09-09 | 2011-09-20 | Websense Uk Limited | System, method and apparatus for use in monitoring or controlling internet access |
US20110289052A1 (en) * | 2010-05-22 | 2011-11-24 | Nokia Corporation | Method and apparatus for eventually consistent delete in a distributed data store |
US8141147B2 (en) | 2004-09-09 | 2012-03-20 | Websense Uk Limited | System, method and apparatus for use in monitoring or controlling internet access |
US20120078865A1 (en) * | 2010-09-29 | 2012-03-29 | International Business Machines Corporation | Dynamic configuration of a persistence provider |
US20120117458A1 (en) * | 2010-04-01 | 2012-05-10 | Lee Hahn Holloway | Internet-based proxy service to modify internet responses |
US8244817B2 (en) | 2007-05-18 | 2012-08-14 | Websense U.K. Limited | Method and apparatus for electronic mail filtering |
US8250081B2 (en) | 2007-01-22 | 2012-08-21 | Websense U.K. Limited | Resource access filtering system and database structure for use therewith |
US8326814B2 (en) | 2007-12-05 | 2012-12-04 | Box, Inc. | Web-based file management system and service |
US20130124458A1 (en) * | 2011-11-16 | 2013-05-16 | Tomas Barreto | Resource effective incremental updating of a remote client with events which occurred via a cloud-enabled platform |
US8515902B2 (en) | 2011-10-14 | 2013-08-20 | Box, Inc. | Automatic and semi-automatic tagging features of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution |
US20130227479A1 (en) * | 2011-08-26 | 2013-08-29 | Salesforce.Com, Inc. | Systems and methods for dynamic list views and detail pages |
US8615800B2 (en) | 2006-07-10 | 2013-12-24 | Websense, Inc. | System and method for analyzing web content |
US20140089150A1 (en) * | 2012-09-27 | 2014-03-27 | Oracle International Corporation | One click to update buyer in mass on purchaser orders and prepare changes to communicate to supplier |
US8719445B2 (en) | 2012-07-03 | 2014-05-06 | Box, Inc. | System and method for load balancing multiple file transfer protocol (FTP) servers to service FTP connections for a cloud-based service |
US8745267B2 (en) | 2012-08-19 | 2014-06-03 | Box, Inc. | Enhancement of upload and/or download performance based on client and/or server feedback information |
US20140195888A1 (en) * | 2013-01-04 | 2014-07-10 | International Business Machines Corporation | Tagging autofill field entries |
US8868574B2 (en) | 2012-07-30 | 2014-10-21 | Box, Inc. | System and method for advanced search and filtering mechanisms for enterprise administrators in a cloud-based environment |
US8892679B1 (en) | 2013-09-13 | 2014-11-18 | Box, Inc. | Mobile device, methods and user interfaces thereof in a mobile device platform featuring multifunctional access and engagement in a collaborative environment provided by a cloud-based platform |
US8914900B2 (en) | 2012-05-23 | 2014-12-16 | Box, Inc. | Methods, architectures and security mechanisms for a third-party application to access content in a cloud-based platform |
US9015601B2 (en) | 2011-06-21 | 2015-04-21 | Box, Inc. | Batch uploading of content to a web-based collaboration environment |
US9019123B2 (en) | 2011-12-22 | 2015-04-28 | Box, Inc. | Health check services for web-based collaboration environments |
US9027108B2 (en) | 2012-05-23 | 2015-05-05 | Box, Inc. | Systems and methods for secure file portability between mobile applications on a mobile device |
US9049247B2 (en) | 2010-04-01 | 2015-06-02 | Cloudfare, Inc. | Internet-based proxy service for responding to server offline errors |
US9054919B2 (en) | 2012-04-05 | 2015-06-09 | Box, Inc. | Device pinning capability for enterprise cloud service and storage accounts |
US9063912B2 (en) | 2011-06-22 | 2015-06-23 | Box, Inc. | Multimedia content preview rendering in a cloud content management system |
US9098474B2 (en) | 2011-10-26 | 2015-08-04 | Box, Inc. | Preview pre-generation based on heuristics and algorithmic prediction/assessment of predicted user behavior for enhancement of user experience |
US9117054B2 (en) | 2012-12-21 | 2015-08-25 | Websense, Inc. | Method and aparatus for presence based resource management |
US9117087B2 (en) | 2012-09-06 | 2015-08-25 | Box, Inc. | System and method for creating a secure channel for inter-application communication based on intents |
WO2015127069A1 (en) * | 2014-02-24 | 2015-08-27 | Entefy, Inc. | System and method of message threading for a multi-format, multi-protocol communication system |
US9130972B2 (en) | 2009-05-26 | 2015-09-08 | Websense, Inc. | Systems and methods for efficient detection of fingerprinted data and information |
US9135462B2 (en) | 2012-08-29 | 2015-09-15 | Box, Inc. | Upload and download streaming encryption to/from a cloud-based platform |
US9195519B2 (en) | 2012-09-06 | 2015-11-24 | Box, Inc. | Disabling the self-referential appearance of a mobile application in an intent via a background registration |
US9195636B2 (en) | 2012-03-07 | 2015-11-24 | Box, Inc. | Universal file type preview for mobile devices |
US9197718B2 (en) | 2011-09-23 | 2015-11-24 | Box, Inc. | Central management and control of user-contributed content in a web-based collaboration environment and management console thereof |
US9213684B2 (en) | 2013-09-13 | 2015-12-15 | Box, Inc. | System and method for rendering document in web browser or mobile device regardless of third-party plug-in software |
US20150370865A1 (en) * | 2014-06-23 | 2015-12-24 | Sang Il Song | Framework for Visualizing Re-Written Queries to Database |
US9223822B1 (en) * | 2011-06-24 | 2015-12-29 | Emc Corporation | Techniques for performing indication management |
US9237170B2 (en) | 2012-07-19 | 2016-01-12 | Box, Inc. | Data loss prevention (DLP) methods and architectures by a cloud service |
US9292833B2 (en) | 2012-09-14 | 2016-03-22 | Box, Inc. | Batching notifications of activities that occur in a web-based collaboration environment |
US9311071B2 (en) | 2012-09-06 | 2016-04-12 | Box, Inc. | Force upgrade of a mobile application via a server side configuration file |
US9342620B2 (en) | 2011-05-20 | 2016-05-17 | Cloudflare, Inc. | Loading of web resources |
US9369520B2 (en) | 2012-08-19 | 2016-06-14 | Box, Inc. | Enhancement of upload and/or download performance based on client and/or server feedback information |
US9378282B2 (en) | 2008-06-30 | 2016-06-28 | Raytheon Company | System and method for dynamic and real-time categorization of webpages |
US9396245B2 (en) | 2013-01-02 | 2016-07-19 | Box, Inc. | Race condition handling in a system which incrementally updates clients with events that occurred in a cloud-based collaboration platform |
US9413587B2 (en) | 2012-05-02 | 2016-08-09 | Box, Inc. | System and method for a third-party application to access content within a cloud-based platform |
US9483473B2 (en) | 2013-09-13 | 2016-11-01 | Box, Inc. | High availability architecture for a cloud-based concurrent-access collaboration platform |
US9495364B2 (en) | 2012-10-04 | 2016-11-15 | Box, Inc. | Enhanced quick search features, low-barrier commenting/interactive features in a collaboration platform |
US9507795B2 (en) | 2013-01-11 | 2016-11-29 | Box, Inc. | Functionalities, features, and user interface of a synchronization client to a cloud-based environment |
US9519886B2 (en) | 2013-09-13 | 2016-12-13 | Box, Inc. | Simultaneous editing/accessing of content by collaborator invitation through a web-based or mobile application to a cloud-based collaboration platform |
US9535909B2 (en) | 2013-09-13 | 2017-01-03 | Box, Inc. | Configurable event-based automation architecture for cloud-based collaboration platforms |
US9535924B2 (en) | 2013-07-30 | 2017-01-03 | Box, Inc. | Scalability improvement in a system which incrementally updates clients with events that occurred in a cloud-based collaboration platform |
US9553758B2 (en) | 2012-09-18 | 2017-01-24 | Box, Inc. | Sandboxing individual applications to specific user folders in a cloud-based service |
US9558202B2 (en) | 2012-08-27 | 2017-01-31 | Box, Inc. | Server side techniques for reducing database workload in implementing selective subfolder synchronization in a cloud-based environment |
US9575981B2 (en) | 2012-04-11 | 2017-02-21 | Box, Inc. | Cloud service enabled to handle a set of files depicted to a user as a single file in a native operating system |
US9602514B2 (en) | 2014-06-16 | 2017-03-21 | Box, Inc. | Enterprise mobility management and verification of a managed application by a content provider |
US9628268B2 (en) | 2012-10-17 | 2017-04-18 | Box, Inc. | Remote key management in a cloud-based environment |
US9633037B2 (en) | 2013-06-13 | 2017-04-25 | Box, Inc | Systems and methods for synchronization event building and/or collapsing by a synchronization component of a cloud-based platform |
US9633075B2 (en) | 2014-06-23 | 2017-04-25 | Sap Se | Framework for re-writing database queries |
US9652741B2 (en) | 2011-07-08 | 2017-05-16 | Box, Inc. | Desktop application for access and interaction with workspaces in a cloud-based content management system and synchronization mechanisms thereof |
US9654495B2 (en) | 2006-12-01 | 2017-05-16 | Websense, Llc | System and method of analyzing web addresses |
US9665349B2 (en) | 2012-10-05 | 2017-05-30 | Box, Inc. | System and method for generating embeddable widgets which enable access to a cloud-based collaboration platform |
US9691051B2 (en) | 2012-05-21 | 2017-06-27 | Box, Inc. | Security enhancement through application access control |
US9705967B2 (en) | 2012-10-04 | 2017-07-11 | Box, Inc. | Corporate user discovery and identification of recommended collaborators in a cloud platform |
US9712510B2 (en) | 2012-07-06 | 2017-07-18 | Box, Inc. | Systems and methods for securely submitting comments among users via external messaging applications in a cloud-based platform |
CN107038647A (en) * | 2017-03-15 | 2017-08-11 | 平安科技(深圳)有限公司 | Insurance application cancelling method and device |
US9756022B2 (en) | 2014-08-29 | 2017-09-05 | Box, Inc. | Enhanced remote key management for an enterprise in a cloud-based environment |
US9773051B2 (en) | 2011-11-29 | 2017-09-26 | Box, Inc. | Mobile platform file and folder selection functionalities for offline access and synchronization |
US9794256B2 (en) | 2012-07-30 | 2017-10-17 | Box, Inc. | System and method for advanced control tools for administrators in a cloud-based service |
US9792320B2 (en) | 2012-07-06 | 2017-10-17 | Box, Inc. | System and method for performing shard migration to support functions of a cloud-based service |
US9805050B2 (en) | 2013-06-21 | 2017-10-31 | Box, Inc. | Maintaining and updating file system shadows on a local device by a synchronization client of a cloud-based platform |
US9819621B2 (en) | 2013-12-27 | 2017-11-14 | Entefy Inc. | Apparatus and method for optimized multi-format communication delivery protocol prediction |
US9843543B2 (en) | 2013-12-27 | 2017-12-12 | Entefy Inc. | Apparatus and method for multi-format and multi-protocol group messaging |
US9894119B2 (en) | 2014-08-29 | 2018-02-13 | Box, Inc. | Configurable metadata-based automation and content classification architecture for cloud-based collaboration platforms |
US9904435B2 (en) | 2012-01-06 | 2018-02-27 | Box, Inc. | System and method for actionable event generation for task delegation and management via a discussion forum in a web-based collaboration environment |
US9930002B2 (en) | 2013-12-27 | 2018-03-27 | Entefy Inc. | Apparatus and method for intelligent delivery time determination for a multi-format and/or multi-protocol communication |
US9953036B2 (en) | 2013-01-09 | 2018-04-24 | Box, Inc. | File system monitoring in a system which incrementally updates clients with events that occurred in a cloud-based collaboration platform |
US9959420B2 (en) | 2012-10-02 | 2018-05-01 | Box, Inc. | System and method for enhanced security and management mechanisms for enterprise administrators in a cloud-based environment |
US9965745B2 (en) | 2012-02-24 | 2018-05-08 | Box, Inc. | System and method for promoting enterprise adoption of a web-based collaboration environment |
US9978040B2 (en) | 2011-07-08 | 2018-05-22 | Box, Inc. | Collaboration sessions in a workspace on a cloud-based content management system |
US10038731B2 (en) | 2014-08-29 | 2018-07-31 | Box, Inc. | Managing flow-based interactions with cloud-based shared content |
US10110656B2 (en) | 2013-06-25 | 2018-10-23 | Box, Inc. | Systems and methods for providing shell communication in a cloud-based platform |
US10127217B2 (en) | 2005-11-17 | 2018-11-13 | Ebay Inc. | Method and system to transmit data |
US10135764B2 (en) | 2015-12-31 | 2018-11-20 | Entefy Inc. | Universal interaction platform for people, services, and devices |
US10200256B2 (en) | 2012-09-17 | 2019-02-05 | Box, Inc. | System and method of a manipulative handle in an interactive mobile user interface |
US10229134B2 (en) | 2013-06-25 | 2019-03-12 | Box, Inc. | Systems and methods for managing upgrades, migration of user data and improving performance of a cloud-based platform |
US10235383B2 (en) | 2012-12-19 | 2019-03-19 | Box, Inc. | Method and apparatus for synchronization of items with read-only permissions in a cloud-based environment |
US10353754B2 (en) | 2015-12-31 | 2019-07-16 | Entefy Inc. | Application program interface analyzer for a universal interaction platform |
US10394966B2 (en) | 2014-02-24 | 2019-08-27 | Entefy Inc. | Systems and methods for multi-protocol, multi-format universal searching |
US10452667B2 (en) | 2012-07-06 | 2019-10-22 | Box Inc. | Identification of people as search results from key-word based searches of content in a cloud-based environment |
US10491690B2 (en) | 2016-12-31 | 2019-11-26 | Entefy Inc. | Distributed natural language message interpretation engine |
US10509527B2 (en) | 2013-09-13 | 2019-12-17 | Box, Inc. | Systems and methods for configuring event-based automation in cloud-based collaboration platforms |
US10530854B2 (en) | 2014-05-30 | 2020-01-07 | Box, Inc. | Synchronization of permissioned content in cloud-based environments |
US10554426B2 (en) | 2011-01-20 | 2020-02-04 | Box, Inc. | Real time notification of activities that occur in a web-based collaboration environment |
US10574442B2 (en) | 2014-08-29 | 2020-02-25 | Box, Inc. | Enhanced remote key management for an enterprise in a cloud-based environment |
US10587553B1 (en) | 2017-12-29 | 2020-03-10 | Entefy Inc. | Methods and systems to support adaptive multi-participant thread monitoring |
US10599671B2 (en) | 2013-01-17 | 2020-03-24 | Box, Inc. | Conflict resolution, retry condition management, and handling of problem files for the synchronization client to a cloud-based platform |
US20200117737A1 (en) * | 2018-10-16 | 2020-04-16 | LeapAnalysis Inc. | Fast heterogeneous multi-data source search and analytics |
US10725968B2 (en) | 2013-05-10 | 2020-07-28 | Box, Inc. | Top down delete or unsynchronization on delete of and depiction of item synchronization with a synchronization client to a cloud-based platform |
US10846074B2 (en) | 2013-05-10 | 2020-11-24 | Box, Inc. | Identification and handling of items to be ignored for synchronization with a cloud-based platform by a synchronization client |
US10866931B2 (en) | 2013-10-22 | 2020-12-15 | Box, Inc. | Desktop application for accessing a cloud collaboration platform |
US10915492B2 (en) | 2012-09-19 | 2021-02-09 | Box, Inc. | Cloud-based platform enabled with media content indexed for text-based searches and/or metadata extraction |
US11087083B1 (en) * | 2020-03-31 | 2021-08-10 | Coupa Software Incorporated | Managing bundles of digital objects in an e-procurement system |
US11210610B2 (en) | 2011-10-26 | 2021-12-28 | Box, Inc. | Enhanced multimedia content preview rendering in a cloud content management system |
US11232481B2 (en) | 2012-01-30 | 2022-01-25 | Box, Inc. | Extended applications of multimedia content previews in the cloud-based content management system |
US11475010B2 (en) | 2020-09-09 | 2022-10-18 | Self Financial, Inc. | Asynchronous database caching |
US11494204B2 (en) | 2016-12-31 | 2022-11-08 | Entefy Inc. | Mixed-grained detection and analysis of user life events for context understanding |
US11573990B2 (en) | 2017-12-29 | 2023-02-07 | Entefy Inc. | Search-based natural language intent determination |
US11630822B2 (en) | 2020-09-09 | 2023-04-18 | Self Financial, Inc. | Multiple devices for updating repositories |
US11641665B2 (en) | 2020-09-09 | 2023-05-02 | Self Financial, Inc. | Resource utilization retrieval and modification |
US11755629B1 (en) | 2014-02-24 | 2023-09-12 | Entefy Inc. | System and method of context-based predictive content tagging for encrypted data |
US11768871B2 (en) | 2015-12-31 | 2023-09-26 | Entefy Inc. | Systems and methods for contextualizing computer vision generated tags using natural language processing |
Families Citing this family (68)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6883168B1 (en) | 2000-06-21 | 2005-04-19 | Microsoft Corporation | Methods, systems, architectures and data structures for delivering software via a network |
US6948135B1 (en) | 2000-06-21 | 2005-09-20 | Microsoft Corporation | Method and systems of providing information to computer users |
US7000230B1 (en) | 2000-06-21 | 2006-02-14 | Microsoft Corporation | Network-based software extensions |
US7155667B1 (en) | 2000-06-21 | 2006-12-26 | Microsoft Corporation | User interface for integrated spreadsheets and word processing tables |
JP4522650B2 (en) * | 2000-06-21 | 2010-08-11 | マイクロソフト コーポレーション | System and method for integrating spreadsheet and word processing tables |
US7191394B1 (en) | 2000-06-21 | 2007-03-13 | Microsoft Corporation | Authoring arbitrary XML documents using DHTML and XSLT |
US7624356B1 (en) | 2000-06-21 | 2009-11-24 | Microsoft Corporation | Task-sensitive methods and systems for displaying command sets |
US7346848B1 (en) | 2000-06-21 | 2008-03-18 | Microsoft Corporation | Single window navigation methods and systems |
US20050160087A1 (en) * | 2002-08-29 | 2005-07-21 | Fujitsu Limited | Data extractor and method of data extraction |
US7415672B1 (en) | 2003-03-24 | 2008-08-19 | Microsoft Corporation | System and method for designing electronic forms |
US7370066B1 (en) | 2003-03-24 | 2008-05-06 | Microsoft Corporation | System and method for offline editing of data files |
US7913159B2 (en) | 2003-03-28 | 2011-03-22 | Microsoft Corporation | System and method for real-time validation of structured data files |
US7296017B2 (en) | 2003-03-28 | 2007-11-13 | Microsoft Corporation | Validation of XML data files |
US7451392B1 (en) | 2003-06-30 | 2008-11-11 | Microsoft Corporation | Rendering an HTML electronic form by applying XSLT to XML using a solution |
US7406660B1 (en) | 2003-08-01 | 2008-07-29 | Microsoft Corporation | Mapping between structured data and a visual surface |
US7334187B1 (en) | 2003-08-06 | 2008-02-19 | Microsoft Corporation | Electronic form aggregation |
US7930757B2 (en) * | 2003-10-31 | 2011-04-19 | Adobe Systems Incorporated | Offline access in a document control system |
US8108672B1 (en) | 2003-10-31 | 2012-01-31 | Adobe Systems Incorporated | Transparent authentication process integration |
US8627489B2 (en) * | 2003-10-31 | 2014-01-07 | Adobe Systems Incorporated | Distributed document version control |
IL159838A0 (en) | 2004-01-13 | 2004-06-20 | Yehuda Binder | Information device |
US8819072B1 (en) | 2004-02-02 | 2014-08-26 | Microsoft Corporation | Promoting data from structured data files |
US7496837B1 (en) | 2004-04-29 | 2009-02-24 | Microsoft Corporation | Structural editing with schema awareness |
US7984382B2 (en) * | 2004-05-26 | 2011-07-19 | Qualcomm Incorporated | User interface action processing using a freshness status |
US7774620B1 (en) | 2004-05-27 | 2010-08-10 | Microsoft Corporation | Executing applications at appropriate trust levels |
US7457832B2 (en) * | 2004-08-31 | 2008-11-25 | Microsoft Corporation | Verifying dynamically generated operations on a data store |
US7692636B2 (en) | 2004-09-30 | 2010-04-06 | Microsoft Corporation | Systems and methods for handwriting to a screen |
US7516399B2 (en) * | 2004-09-30 | 2009-04-07 | Microsoft Corporation | Structured-document path-language expression methods and systems |
US7712022B2 (en) | 2004-11-15 | 2010-05-04 | Microsoft Corporation | Mutually exclusive options in electronic forms |
US7721190B2 (en) | 2004-11-16 | 2010-05-18 | Microsoft Corporation | Methods and systems for server side form processing |
US7509353B2 (en) * | 2004-11-16 | 2009-03-24 | Microsoft Corporation | Methods and systems for exchanging and rendering forms |
US7995758B1 (en) | 2004-11-30 | 2011-08-09 | Adobe Systems Incorporated | Family of encryption keys |
US7904801B2 (en) | 2004-12-15 | 2011-03-08 | Microsoft Corporation | Recursive sections in electronic forms |
US7680805B2 (en) * | 2004-12-30 | 2010-03-16 | Sap Ag | Synchronization method for an object oriented information system (IS) model |
US7937651B2 (en) | 2005-01-14 | 2011-05-03 | Microsoft Corporation | Structural editing operations for network forms |
US7725834B2 (en) | 2005-03-04 | 2010-05-25 | Microsoft Corporation | Designer-created aspect for an electronic form template |
US7673228B2 (en) | 2005-03-30 | 2010-03-02 | Microsoft Corporation | Data-driven actions for network forms |
US8010515B2 (en) | 2005-04-15 | 2011-08-30 | Microsoft Corporation | Query to an electronic form |
US7836034B2 (en) * | 2005-05-16 | 2010-11-16 | International Business Machines Corporation | Method and apparatus for updating first data value before second data value |
US9330134B2 (en) * | 2005-05-31 | 2016-05-03 | Fairwarning Ip, Llc | User identity mapping system and method of use |
US8200975B2 (en) | 2005-06-29 | 2012-06-12 | Microsoft Corporation | Digital signatures for network forms |
US8832047B2 (en) | 2005-07-27 | 2014-09-09 | Adobe Systems Incorporated | Distributed document version control |
US7426524B2 (en) * | 2005-09-27 | 2008-09-16 | International Business Machines Corporation | Update processes in an enterprise planning system |
US8001459B2 (en) | 2005-12-05 | 2011-08-16 | Microsoft Corporation | Enabling electronic documents for limited-capability computing devices |
US9710508B2 (en) * | 2006-03-09 | 2017-07-18 | Quickbase, Inc. | Method and system for managing data in a workflow process |
US20090037337A1 (en) * | 2007-07-31 | 2009-02-05 | Ahmad Baitalmal | Software Licensing and Enforcement System |
US20090037287A1 (en) * | 2007-07-31 | 2009-02-05 | Ahmad Baitalmal | Software Marketplace and Distribution System |
EP2188740A2 (en) * | 2007-07-31 | 2010-05-26 | Etelos, Inc. | Software marketplace and distribution system |
US7941399B2 (en) | 2007-11-09 | 2011-05-10 | Microsoft Corporation | Collaborative authoring |
US8660860B2 (en) * | 2007-11-09 | 2014-02-25 | Hospira, Inc. | System and method for synchronizing medication configuration information among systems containing medication configuration information |
US8028229B2 (en) * | 2007-12-06 | 2011-09-27 | Microsoft Corporation | Document merge |
US8825758B2 (en) * | 2007-12-14 | 2014-09-02 | Microsoft Corporation | Collaborative authoring modes |
US8301588B2 (en) * | 2008-03-07 | 2012-10-30 | Microsoft Corporation | Data storage for file updates |
US8352870B2 (en) | 2008-04-28 | 2013-01-08 | Microsoft Corporation | Conflict resolution |
US8429753B2 (en) | 2008-05-08 | 2013-04-23 | Microsoft Corporation | Controlling access to documents using file locks |
US8825594B2 (en) | 2008-05-08 | 2014-09-02 | Microsoft Corporation | Caching infrastructure |
CN101261622B (en) * | 2008-05-12 | 2011-12-07 | 金蝶软件(中国)有限公司 | Data dividing method and apparatus |
US8417666B2 (en) | 2008-06-25 | 2013-04-09 | Microsoft Corporation | Structured coauthoring |
KR101508794B1 (en) | 2008-07-09 | 2015-04-06 | 삼성전자주식회사 | Method for selectively securing records in a ndef message |
JP2010086059A (en) * | 2008-09-29 | 2010-04-15 | 4Z Corporation:Kk | Form system to be input, program, and method of updating form data |
US8265606B2 (en) * | 2008-10-09 | 2012-09-11 | Microsoft Corporation | Targeted advertisements to social contacts |
US8346768B2 (en) | 2009-04-30 | 2013-01-01 | Microsoft Corporation | Fast merge support for legacy documents |
US8918380B2 (en) * | 2009-07-09 | 2014-12-23 | Norsync Technology As | Methods, systems and devices for performing incremental updates of partial databases |
US8407245B2 (en) * | 2010-11-24 | 2013-03-26 | Microsoft Corporation | Efficient string pattern matching for large pattern sets |
US9053117B2 (en) | 2012-04-11 | 2015-06-09 | 4Clicks Solutions, LLC | Storing application data with a unique ID |
US20140082470A1 (en) * | 2012-09-19 | 2014-03-20 | 4Clicks Solutions, LLC | Spreadtree hierarchy system for spreadsheets and related methods |
US9460073B2 (en) | 2013-02-27 | 2016-10-04 | Google Inc. | Systems and methods for mutations and operational transforms in a collaborative spreadsheet environment |
US8997249B1 (en) | 2014-06-18 | 2015-03-31 | Storagecraft Technology Corporation | Software activation and revalidation |
US11501014B2 (en) | 2020-05-07 | 2022-11-15 | International Business Machines Corporation | Secure data replication in distributed data storage environments |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5471629A (en) * | 1988-12-19 | 1995-11-28 | Hewlett-Packard Company | Method of monitoring changes in an object-oriented database with tuned monitors |
US5581750A (en) * | 1993-03-15 | 1996-12-03 | International Business Machines Corporation | System and method for improving data recovery performance |
US5706510A (en) * | 1996-03-15 | 1998-01-06 | Hewlett-Packard Company | Zymbolic history management system |
US6006239A (en) * | 1996-03-15 | 1999-12-21 | Microsoft Corporation | Method and system for allowing multiple users to simultaneously edit a spreadsheet |
US6078924A (en) * | 1998-01-30 | 2000-06-20 | Aeneid Corporation | Method and apparatus for performing data collection, interpretation and analysis, in an information platform |
US6205478B1 (en) * | 1998-07-08 | 2001-03-20 | Fujitsu Limited | System for exchanging user information among users |
US6240414B1 (en) * | 1997-09-28 | 2001-05-29 | Eisolutions, Inc. | Method of resolving data conflicts in a shared data environment |
US6341291B1 (en) * | 1998-09-28 | 2002-01-22 | Bentley Systems, Inc. | System for collaborative engineering using component and file-oriented tools |
US6345288B1 (en) * | 1989-08-31 | 2002-02-05 | Onename Corporation | Computer-based communication system and method using metadata defining a control-structure |
US6393419B1 (en) * | 1999-02-08 | 2002-05-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Multipoint database synchronization protocol to avoid data corruption |
US20020123813A1 (en) * | 2001-03-05 | 2002-09-05 | Dell Products L.P. | Method, system and facility for monitoring resources within a manufacturing environment |
-
2001
- 2001-03-13 US US09/804,034 patent/US7058663B2/en not_active Expired - Fee Related
-
2002
- 2002-02-25 WO PCT/US2002/005665 patent/WO2002073432A1/en not_active Application Discontinuation
- 2002-02-25 CN CN02800640A patent/CN1459061A/en active Pending
- 2002-02-25 JP JP2002572023A patent/JP2004528636A/en not_active Withdrawn
- 2002-02-25 EP EP02707884A patent/EP1370959A4/en not_active Withdrawn
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5471629A (en) * | 1988-12-19 | 1995-11-28 | Hewlett-Packard Company | Method of monitoring changes in an object-oriented database with tuned monitors |
US6345288B1 (en) * | 1989-08-31 | 2002-02-05 | Onename Corporation | Computer-based communication system and method using metadata defining a control-structure |
US5581750A (en) * | 1993-03-15 | 1996-12-03 | International Business Machines Corporation | System and method for improving data recovery performance |
US5706510A (en) * | 1996-03-15 | 1998-01-06 | Hewlett-Packard Company | Zymbolic history management system |
US6006239A (en) * | 1996-03-15 | 1999-12-21 | Microsoft Corporation | Method and system for allowing multiple users to simultaneously edit a spreadsheet |
US6240414B1 (en) * | 1997-09-28 | 2001-05-29 | Eisolutions, Inc. | Method of resolving data conflicts in a shared data environment |
US6078924A (en) * | 1998-01-30 | 2000-06-20 | Aeneid Corporation | Method and apparatus for performing data collection, interpretation and analysis, in an information platform |
US6205478B1 (en) * | 1998-07-08 | 2001-03-20 | Fujitsu Limited | System for exchanging user information among users |
US6341291B1 (en) * | 1998-09-28 | 2002-01-22 | Bentley Systems, Inc. | System for collaborative engineering using component and file-oriented tools |
US6393419B1 (en) * | 1999-02-08 | 2002-05-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Multipoint database synchronization protocol to avoid data corruption |
US20020123813A1 (en) * | 2001-03-05 | 2002-09-05 | Dell Products L.P. | Method, system and facility for monitoring resources within a manufacturing environment |
Cited By (265)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9565235B2 (en) | 2000-01-28 | 2017-02-07 | Websense, Llc | System and method for controlling access to internet sites |
US8533349B2 (en) | 2000-01-28 | 2013-09-10 | Websense, Inc. | System and method for controlling access to internet sites |
US20040015586A1 (en) * | 2000-01-28 | 2004-01-22 | Ronald Hegli | System and method for controlling access to internet sites |
US20020138315A1 (en) * | 2001-03-20 | 2002-09-26 | Mineo Nozaki | Technical support system |
US7809758B2 (en) | 2001-07-20 | 2010-10-05 | Websense Uk Limited | Database and method of generating same |
US20050267902A1 (en) * | 2001-07-20 | 2005-12-01 | Surfcontrol Plc | Database and method of generating same |
US20030088453A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | System, method and computer program product for rank assignment |
US20030115087A1 (en) * | 2001-11-02 | 2003-06-19 | Toshiba Tec Kabushiki Kaisha | Technical support system |
US20030088641A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | Technical support system |
US20030088590A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | Method, system and computer program product for providing backup data for use in studying claims |
US20030088451A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | Technical support system |
US20030088330A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | Method, system and computer program product for coping with the changes in hardware |
US20030088454A1 (en) * | 2001-11-02 | 2003-05-08 | Toshiba Tec Kabushiki Kaisha | System, method and computer program product for complaint report issue |
US7024411B2 (en) * | 2001-11-02 | 2006-04-04 | Toshiba Tec Kabushiki Kaisha | Method, system and computer program product for providing backup data for use in studying claims |
US20060031504A1 (en) * | 2001-12-05 | 2006-02-09 | Hegli Ronald B | Filtering techniques for managing access to Internet sites or other software applications |
US7483982B2 (en) | 2001-12-05 | 2009-01-27 | Websense, Inc. | Filtering techniques for managing access to internet sites or other software applications |
US8751514B2 (en) | 2001-12-07 | 2014-06-10 | Websense, Inc. | System and method for adapting an internet filter |
US20030110168A1 (en) * | 2001-12-07 | 2003-06-12 | Harold Kester | System and method for adapting an internet filter |
US9503423B2 (en) | 2001-12-07 | 2016-11-22 | Websense, Llc | System and method for adapting an internet filter |
US8010552B2 (en) | 2001-12-07 | 2011-08-30 | Websense, Inc. | System and method for adapting an internet filter |
US20090287750A1 (en) * | 2002-03-29 | 2009-11-19 | International Business Machines Corporation | Method and Apparatus for Content Pre-Fetching and Preparation |
US8949420B2 (en) * | 2002-03-29 | 2015-02-03 | International Business Machines Corporation | Content pre-fetching and preparation |
US7548881B2 (en) * | 2002-11-04 | 2009-06-16 | Tradebeam, Inc. | Systems and methods for producing documentary credit and conforming shipping documents |
US20040088245A1 (en) * | 2002-11-04 | 2004-05-06 | Manoj Narayan | Systems and methods for producing documentary credit and conforming shipping documents |
US20050210035A1 (en) * | 2003-03-14 | 2005-09-22 | Kester Harold M | System and method of monitoring and controlling application files |
AU2004200620B2 (en) * | 2003-03-14 | 2010-04-29 | Websense, Inc. | System and method of monitoring and controlling application files |
US9692790B2 (en) * | 2003-03-14 | 2017-06-27 | Websense, Llc | System and method of monitoring and controlling application files |
US20070162463A1 (en) * | 2003-03-14 | 2007-07-12 | Websense, Inc. | System and method of monitoring and controlling application files |
US8020209B2 (en) | 2003-03-14 | 2011-09-13 | Websense, Inc. | System and method of monitoring and controlling application files |
US8689325B2 (en) | 2003-03-14 | 2014-04-01 | Websense, Inc. | System and method of monitoring and controlling application files |
US7529754B2 (en) * | 2003-03-14 | 2009-05-05 | Websense, Inc. | System and method of monitoring and controlling application files |
US7185015B2 (en) * | 2003-03-14 | 2007-02-27 | Websense, Inc. | System and method of monitoring and controlling application files |
US8701194B2 (en) | 2003-03-14 | 2014-04-15 | Websense, Inc. | System and method of monitoring and controlling application files |
US9253060B2 (en) | 2003-03-14 | 2016-02-02 | Websense, Inc. | System and method of monitoring and controlling application files |
US20090216729A1 (en) * | 2003-03-14 | 2009-08-27 | Websense, Inc. | System and method of monitoring and controlling application files |
US9342693B2 (en) | 2003-03-14 | 2016-05-17 | Websense, Inc. | System and method of monitoring and controlling application files |
US20040181788A1 (en) * | 2003-03-14 | 2004-09-16 | Websense Inc | System and method of monitoring and controlling application files |
US8150817B2 (en) * | 2003-03-14 | 2012-04-03 | Websense, Inc. | System and method of monitoring and controlling application files |
US20050223001A1 (en) * | 2003-03-14 | 2005-10-06 | Kester Harold M | System and method of monitoring and controlling application files |
US8645340B2 (en) | 2003-03-14 | 2014-02-04 | Websense, Inc. | System and method of monitoring and controlling application files |
US7797270B2 (en) * | 2003-03-14 | 2010-09-14 | Websense, Inc. | System and method of monitoring and controlling application files |
AU2004200620C1 (en) * | 2003-03-14 | 2010-09-30 | Websense, Inc. | System and method of monitoring and controlling application files |
US20060004636A1 (en) * | 2003-03-14 | 2006-01-05 | Kester Harold M | System and method of monitoring and controlling application files |
US7523391B1 (en) * | 2003-03-25 | 2009-04-21 | Microsoft Corporation | Indicating change to data form |
US20070050777A1 (en) * | 2003-06-09 | 2007-03-01 | Hutchinson Thomas W | Duration of alerts and scanning of large data stores |
US8131856B2 (en) * | 2003-08-11 | 2012-03-06 | Sony Corporation | Communication system and communication method |
US20070005435A1 (en) * | 2003-08-11 | 2007-01-04 | Sony Corporation | Communication system and communication method |
US20060095358A1 (en) * | 2004-02-11 | 2006-05-04 | Viarengo Steve M | Method and system for automatically detecting that international shipment movement has satisfied a threshold condition |
US7567912B2 (en) | 2004-02-11 | 2009-07-28 | Tradebeam, Inc. | Method and system for automatically detecting that international shipment movement has satisfied a threshold condition |
US7318067B2 (en) | 2004-07-22 | 2008-01-08 | International Business Machines Corporation | Synchronization of application rules across database instances |
US7720811B2 (en) | 2004-07-22 | 2010-05-18 | International Business Machines Corporation | Synchronization of application rules across database instances |
US7720810B2 (en) | 2004-07-22 | 2010-05-18 | International Business Machines Corporation | Synchronization of application documentation across database instances |
US7318068B2 (en) | 2004-07-22 | 2008-01-08 | International Business Machines Corporation | Synchronization of application documentation across database instances |
US20070294316A1 (en) * | 2004-07-22 | 2007-12-20 | Hicks Scott D | Synchronization of application rules across database instances |
US20070276877A1 (en) * | 2004-07-22 | 2007-11-29 | Locke Victoria A | Synchronization of application documentation across database instances |
US7890642B2 (en) | 2004-08-07 | 2011-02-15 | Websense Uk Limited | Device internet resource access filtering system and method |
US8141147B2 (en) | 2004-09-09 | 2012-03-20 | Websense Uk Limited | System, method and apparatus for use in monitoring or controlling internet access |
US8024471B2 (en) | 2004-09-09 | 2011-09-20 | Websense Uk Limited | System, method and apparatus for use in monitoring or controlling internet access |
US10776572B2 (en) | 2005-11-17 | 2020-09-15 | Ebay Inc. | Method and system to transmit data |
US10127217B2 (en) | 2005-11-17 | 2018-11-13 | Ebay Inc. | Method and system to transmit data |
US11347934B2 (en) | 2005-11-17 | 2022-05-31 | Ebay Inc. | Method and system to transmit data |
US10372805B2 (en) | 2005-11-17 | 2019-08-06 | Ebay Inc. | Method and system to transmit data |
US20070150956A1 (en) * | 2005-12-28 | 2007-06-28 | Sharma Rajesh K | Real time lockdown |
US8959642B2 (en) | 2005-12-28 | 2015-02-17 | Websense, Inc. | Real time lockdown |
US8453243B2 (en) | 2005-12-28 | 2013-05-28 | Websense, Inc. | Real time lockdown |
US9230098B2 (en) | 2005-12-28 | 2016-01-05 | Websense, Inc. | Real time lockdown |
US9723018B2 (en) | 2006-07-10 | 2017-08-01 | Websense, Llc | System and method of analyzing web content |
US9003524B2 (en) | 2006-07-10 | 2015-04-07 | Websense, Inc. | System and method for analyzing web content |
US8615800B2 (en) | 2006-07-10 | 2013-12-24 | Websense, Inc. | System and method for analyzing web content |
US8978140B2 (en) | 2006-07-10 | 2015-03-10 | Websense, Inc. | System and method of analyzing web content |
US8020206B2 (en) | 2006-07-10 | 2011-09-13 | Websense, Inc. | System and method of analyzing web content |
US9680866B2 (en) | 2006-07-10 | 2017-06-13 | Websense, Llc | System and method for analyzing web content |
US9654495B2 (en) | 2006-12-01 | 2017-05-16 | Websense, Llc | System and method of analyzing web addresses |
US8250081B2 (en) | 2007-01-22 | 2012-08-21 | Websense U.K. Limited | Resource access filtering system and database structure for use therewith |
US8015174B2 (en) | 2007-02-28 | 2011-09-06 | Websense, Inc. | System and method of controlling access to the internet |
US8799388B2 (en) | 2007-05-18 | 2014-08-05 | Websense U.K. Limited | Method and apparatus for electronic mail filtering |
US8244817B2 (en) | 2007-05-18 | 2012-08-14 | Websense U.K. Limited | Method and apparatus for electronic mail filtering |
US9473439B2 (en) | 2007-05-18 | 2016-10-18 | Forcepoint Uk Limited | Method and apparatus for electronic mail filtering |
US8583619B2 (en) | 2007-12-05 | 2013-11-12 | Box, Inc. | Methods and systems for open source collaboration in an application service provider environment |
US8326814B2 (en) | 2007-12-05 | 2012-12-04 | Box, Inc. | Web-based file management system and service |
US9519526B2 (en) | 2007-12-05 | 2016-12-13 | Box, Inc. | File management system and collaboration service and integration capabilities with third party applications |
US9251236B2 (en) * | 2008-02-19 | 2016-02-02 | International Business Machines Corporation | Document synchronization solution |
US8650154B2 (en) * | 2008-02-19 | 2014-02-11 | International Business Machines Corporation | Document synchronization solution |
US20090210459A1 (en) * | 2008-02-19 | 2009-08-20 | International Business Machines Corporation | Document synchronization solution |
US20140114912A1 (en) * | 2008-02-19 | 2014-04-24 | International Business Machines Corporation | Document synchronization solution |
US8725679B2 (en) | 2008-04-07 | 2014-05-13 | International Business Machines Corporation | Client side caching of synchronized data |
US20090254589A1 (en) * | 2008-04-07 | 2009-10-08 | International Business Machines Corporation | Client side caching of synchronized data |
US9378282B2 (en) | 2008-06-30 | 2016-06-28 | Raytheon Company | System and method for dynamic and real-time categorization of webpages |
US9692762B2 (en) | 2009-05-26 | 2017-06-27 | Websense, Llc | Systems and methods for efficient detection of fingerprinted data and information |
US9130972B2 (en) | 2009-05-26 | 2015-09-08 | Websense, Inc. | Systems and methods for efficient detection of fingerprinted data and information |
US20110173947A1 (en) * | 2010-01-19 | 2011-07-21 | General Electric Company | System and method for gas turbine power augmentation |
US11494460B2 (en) | 2010-04-01 | 2022-11-08 | Cloudflare, Inc. | Internet-based proxy service to modify internet responses |
US11244024B2 (en) | 2010-04-01 | 2022-02-08 | Cloudflare, Inc. | Methods and apparatuses for providing internet-based proxy services |
US10671694B2 (en) | 2010-04-01 | 2020-06-02 | Cloudflare, Inc. | Methods and apparatuses for providing internet-based proxy services |
US9009330B2 (en) | 2010-04-01 | 2015-04-14 | Cloudflare, Inc. | Internet-based proxy service to limit internet visitor connection speed |
US10313475B2 (en) | 2010-04-01 | 2019-06-04 | Cloudflare, Inc. | Internet-based proxy service for responding to server offline errors |
US10243927B2 (en) | 2010-04-01 | 2019-03-26 | Cloudflare, Inc | Methods and apparatuses for providing Internet-based proxy services |
US8751633B2 (en) | 2010-04-01 | 2014-06-10 | Cloudflare, Inc. | Recording internet visitor threat information through an internet-based proxy service |
US20120117458A1 (en) * | 2010-04-01 | 2012-05-10 | Lee Hahn Holloway | Internet-based proxy service to modify internet responses |
US9369437B2 (en) | 2010-04-01 | 2016-06-14 | Cloudflare, Inc. | Internet-based proxy service to modify internet responses |
US9548966B2 (en) | 2010-04-01 | 2017-01-17 | Cloudflare, Inc. | Validating visitor internet-based security threats |
US9049247B2 (en) | 2010-04-01 | 2015-06-02 | Cloudfare, Inc. | Internet-based proxy service for responding to server offline errors |
US8370940B2 (en) | 2010-04-01 | 2013-02-05 | Cloudflare, Inc. | Methods and apparatuses for providing internet-based proxy services |
US8572737B2 (en) | 2010-04-01 | 2013-10-29 | Cloudflare, Inc. | Methods and apparatuses for providing internet-based proxy services |
US10452741B2 (en) | 2010-04-01 | 2019-10-22 | Cloudflare, Inc. | Custom responses for resource unavailable errors |
US11321419B2 (en) | 2010-04-01 | 2022-05-03 | Cloudflare, Inc. | Internet-based proxy service to limit internet visitor connection speed |
US10855798B2 (en) | 2010-04-01 | 2020-12-01 | Cloudfare, Inc. | Internet-based proxy service for responding to server offline errors |
US9634994B2 (en) | 2010-04-01 | 2017-04-25 | Cloudflare, Inc. | Custom responses for resource unavailable errors |
US8850580B2 (en) | 2010-04-01 | 2014-09-30 | Cloudflare, Inc. | Validating visitor internet-based security threats |
US9634993B2 (en) * | 2010-04-01 | 2017-04-25 | Cloudflare, Inc. | Internet-based proxy service to modify internet responses |
US10984068B2 (en) | 2010-04-01 | 2021-04-20 | Cloudflare, Inc. | Internet-based proxy service to modify internet responses |
US9628581B2 (en) | 2010-04-01 | 2017-04-18 | Cloudflare, Inc. | Internet-based proxy service for responding to server offline errors |
US10853443B2 (en) | 2010-04-01 | 2020-12-01 | Cloudflare, Inc. | Internet-based proxy security services |
US10922377B2 (en) | 2010-04-01 | 2021-02-16 | Cloudflare, Inc. | Internet-based proxy service to limit internet visitor connection speed |
US10585967B2 (en) | 2010-04-01 | 2020-03-10 | Cloudflare, Inc. | Internet-based proxy service to modify internet responses |
US10621263B2 (en) | 2010-04-01 | 2020-04-14 | Cloudflare, Inc. | Internet-based proxy service to limit internet visitor connection speed |
US11675872B2 (en) | 2010-04-01 | 2023-06-13 | Cloudflare, Inc. | Methods and apparatuses for providing internet-based proxy services |
US10872128B2 (en) | 2010-04-01 | 2020-12-22 | Cloudflare, Inc. | Custom responses for resource unavailable errors |
US10102301B2 (en) | 2010-04-01 | 2018-10-16 | Cloudflare, Inc. | Internet-based proxy security services |
US9565166B2 (en) | 2010-04-01 | 2017-02-07 | Cloudflare, Inc. | Internet-based proxy service to modify internet responses |
US10169479B2 (en) | 2010-04-01 | 2019-01-01 | Cloudflare, Inc. | Internet-based proxy service to limit internet visitor connection speed |
US9305002B2 (en) | 2010-05-22 | 2016-04-05 | Nokia Technologies Oy | Method and apparatus for eventually consistent delete in a distributed data store |
US9015126B2 (en) * | 2010-05-22 | 2015-04-21 | Nokia Corporation | Method and apparatus for eventually consistent delete in a distributed data store |
US20110289052A1 (en) * | 2010-05-22 | 2011-11-24 | Nokia Corporation | Method and apparatus for eventually consistent delete in a distributed data store |
US8959068B2 (en) * | 2010-09-29 | 2015-02-17 | International Business Machines Corporation | Dynamic configuration of a persistence provider |
US8959069B2 (en) * | 2010-09-29 | 2015-02-17 | International Business Machines Corporation | Dynamic configuration of a persistence provider |
US20120203735A1 (en) * | 2010-09-29 | 2012-08-09 | International Business Machines Corporation | Dynamic configuration of a persistence provider |
US20120078865A1 (en) * | 2010-09-29 | 2012-03-29 | International Business Machines Corporation | Dynamic configuration of a persistence provider |
US10554426B2 (en) | 2011-01-20 | 2020-02-04 | Box, Inc. | Real time notification of activities that occur in a web-based collaboration environment |
US9342620B2 (en) | 2011-05-20 | 2016-05-17 | Cloudflare, Inc. | Loading of web resources |
US9769240B2 (en) | 2011-05-20 | 2017-09-19 | Cloudflare, Inc. | Loading of web resources |
US9015601B2 (en) | 2011-06-21 | 2015-04-21 | Box, Inc. | Batch uploading of content to a web-based collaboration environment |
US9063912B2 (en) | 2011-06-22 | 2015-06-23 | Box, Inc. | Multimedia content preview rendering in a cloud content management system |
US9223822B1 (en) * | 2011-06-24 | 2015-12-29 | Emc Corporation | Techniques for performing indication management |
US9978040B2 (en) | 2011-07-08 | 2018-05-22 | Box, Inc. | Collaboration sessions in a workspace on a cloud-based content management system |
US9652741B2 (en) | 2011-07-08 | 2017-05-16 | Box, Inc. | Desktop application for access and interaction with workspaces in a cloud-based content management system and synchronization mechanisms thereof |
US9535573B2 (en) * | 2011-08-26 | 2017-01-03 | Salesforce.Com, Inc. | Systems and methods for dynamic list views and detail pages |
US20130227479A1 (en) * | 2011-08-26 | 2013-08-29 | Salesforce.Com, Inc. | Systems and methods for dynamic list views and detail pages |
US9197718B2 (en) | 2011-09-23 | 2015-11-24 | Box, Inc. | Central management and control of user-contributed content in a web-based collaboration environment and management console thereof |
US8515902B2 (en) | 2011-10-14 | 2013-08-20 | Box, Inc. | Automatic and semi-automatic tagging features of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution |
US8990151B2 (en) | 2011-10-14 | 2015-03-24 | Box, Inc. | Automatic and semi-automatic tagging features of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution |
US9098474B2 (en) | 2011-10-26 | 2015-08-04 | Box, Inc. | Preview pre-generation based on heuristics and algorithmic prediction/assessment of predicted user behavior for enhancement of user experience |
US11210610B2 (en) | 2011-10-26 | 2021-12-28 | Box, Inc. | Enhanced multimedia content preview rendering in a cloud content management system |
US9015248B2 (en) * | 2011-11-16 | 2015-04-21 | Box, Inc. | Managing updates at clients used by a user to access a cloud-based collaboration service |
US8990307B2 (en) * | 2011-11-16 | 2015-03-24 | Box, Inc. | Resource effective incremental updating of a remote client with events which occurred via a cloud-enabled platform |
US20130124458A1 (en) * | 2011-11-16 | 2013-05-16 | Tomas Barreto | Resource effective incremental updating of a remote client with events which occurred via a cloud-enabled platform |
US11537630B2 (en) | 2011-11-29 | 2022-12-27 | Box, Inc. | Mobile platform file and folder selection functionalities for offline access and synchronization |
US10909141B2 (en) | 2011-11-29 | 2021-02-02 | Box, Inc. | Mobile platform file and folder selection functionalities for offline access and synchronization |
US9773051B2 (en) | 2011-11-29 | 2017-09-26 | Box, Inc. | Mobile platform file and folder selection functionalities for offline access and synchronization |
US11853320B2 (en) | 2011-11-29 | 2023-12-26 | Box, Inc. | Mobile platform file and folder selection functionalities for offline access and synchronization |
US9019123B2 (en) | 2011-12-22 | 2015-04-28 | Box, Inc. | Health check services for web-based collaboration environments |
US9904435B2 (en) | 2012-01-06 | 2018-02-27 | Box, Inc. | System and method for actionable event generation for task delegation and management via a discussion forum in a web-based collaboration environment |
US11232481B2 (en) | 2012-01-30 | 2022-01-25 | Box, Inc. | Extended applications of multimedia content previews in the cloud-based content management system |
US9965745B2 (en) | 2012-02-24 | 2018-05-08 | Box, Inc. | System and method for promoting enterprise adoption of a web-based collaboration environment |
US10713624B2 (en) | 2012-02-24 | 2020-07-14 | Box, Inc. | System and method for promoting enterprise adoption of a web-based collaboration environment |
US9195636B2 (en) | 2012-03-07 | 2015-11-24 | Box, Inc. | Universal file type preview for mobile devices |
US9054919B2 (en) | 2012-04-05 | 2015-06-09 | Box, Inc. | Device pinning capability for enterprise cloud service and storage accounts |
US9575981B2 (en) | 2012-04-11 | 2017-02-21 | Box, Inc. | Cloud service enabled to handle a set of files depicted to a user as a single file in a native operating system |
US9413587B2 (en) | 2012-05-02 | 2016-08-09 | Box, Inc. | System and method for a third-party application to access content within a cloud-based platform |
US9691051B2 (en) | 2012-05-21 | 2017-06-27 | Box, Inc. | Security enhancement through application access control |
US9280613B2 (en) | 2012-05-23 | 2016-03-08 | Box, Inc. | Metadata enabled third-party application access of content at a cloud-based platform via a native client to the cloud-based platform |
US9552444B2 (en) | 2012-05-23 | 2017-01-24 | Box, Inc. | Identification verification mechanisms for a third-party application to access content in a cloud-based platform |
US9027108B2 (en) | 2012-05-23 | 2015-05-05 | Box, Inc. | Systems and methods for secure file portability between mobile applications on a mobile device |
US8914900B2 (en) | 2012-05-23 | 2014-12-16 | Box, Inc. | Methods, architectures and security mechanisms for a third-party application to access content in a cloud-based platform |
US9021099B2 (en) | 2012-07-03 | 2015-04-28 | Box, Inc. | Load balancing secure FTP connections among multiple FTP servers |
US8719445B2 (en) | 2012-07-03 | 2014-05-06 | Box, Inc. | System and method for load balancing multiple file transfer protocol (FTP) servers to service FTP connections for a cloud-based service |
US10452667B2 (en) | 2012-07-06 | 2019-10-22 | Box Inc. | Identification of people as search results from key-word based searches of content in a cloud-based environment |
US9712510B2 (en) | 2012-07-06 | 2017-07-18 | Box, Inc. | Systems and methods for securely submitting comments among users via external messaging applications in a cloud-based platform |
US9792320B2 (en) | 2012-07-06 | 2017-10-17 | Box, Inc. | System and method for performing shard migration to support functions of a cloud-based service |
US9473532B2 (en) | 2012-07-19 | 2016-10-18 | Box, Inc. | Data loss prevention (DLP) methods by a cloud service including third party integration architectures |
US9237170B2 (en) | 2012-07-19 | 2016-01-12 | Box, Inc. | Data loss prevention (DLP) methods and architectures by a cloud service |
US9794256B2 (en) | 2012-07-30 | 2017-10-17 | Box, Inc. | System and method for advanced control tools for administrators in a cloud-based service |
US8868574B2 (en) | 2012-07-30 | 2014-10-21 | Box, Inc. | System and method for advanced search and filtering mechanisms for enterprise administrators in a cloud-based environment |
US9369520B2 (en) | 2012-08-19 | 2016-06-14 | Box, Inc. | Enhancement of upload and/or download performance based on client and/or server feedback information |
US8745267B2 (en) | 2012-08-19 | 2014-06-03 | Box, Inc. | Enhancement of upload and/or download performance based on client and/or server feedback information |
US9729675B2 (en) | 2012-08-19 | 2017-08-08 | Box, Inc. | Enhancement of upload and/or download performance based on client and/or server feedback information |
US9558202B2 (en) | 2012-08-27 | 2017-01-31 | Box, Inc. | Server side techniques for reducing database workload in implementing selective subfolder synchronization in a cloud-based environment |
US9450926B2 (en) | 2012-08-29 | 2016-09-20 | Box, Inc. | Upload and download streaming encryption to/from a cloud-based platform |
US9135462B2 (en) | 2012-08-29 | 2015-09-15 | Box, Inc. | Upload and download streaming encryption to/from a cloud-based platform |
US9311071B2 (en) | 2012-09-06 | 2016-04-12 | Box, Inc. | Force upgrade of a mobile application via a server side configuration file |
US9117087B2 (en) | 2012-09-06 | 2015-08-25 | Box, Inc. | System and method for creating a secure channel for inter-application communication based on intents |
US9195519B2 (en) | 2012-09-06 | 2015-11-24 | Box, Inc. | Disabling the self-referential appearance of a mobile application in an intent via a background registration |
US9292833B2 (en) | 2012-09-14 | 2016-03-22 | Box, Inc. | Batching notifications of activities that occur in a web-based collaboration environment |
US10200256B2 (en) | 2012-09-17 | 2019-02-05 | Box, Inc. | System and method of a manipulative handle in an interactive mobile user interface |
US9553758B2 (en) | 2012-09-18 | 2017-01-24 | Box, Inc. | Sandboxing individual applications to specific user folders in a cloud-based service |
US10915492B2 (en) | 2012-09-19 | 2021-02-09 | Box, Inc. | Cloud-based platform enabled with media content indexed for text-based searches and/or metadata extraction |
US9501801B2 (en) * | 2012-09-27 | 2016-11-22 | Oracle International Corporation | One click to update buyer in mass on purchaser orders and prepare changes to communicate to supplier |
US20140089150A1 (en) * | 2012-09-27 | 2014-03-27 | Oracle International Corporation | One click to update buyer in mass on purchaser orders and prepare changes to communicate to supplier |
US9959420B2 (en) | 2012-10-02 | 2018-05-01 | Box, Inc. | System and method for enhanced security and management mechanisms for enterprise administrators in a cloud-based environment |
US9495364B2 (en) | 2012-10-04 | 2016-11-15 | Box, Inc. | Enhanced quick search features, low-barrier commenting/interactive features in a collaboration platform |
US9705967B2 (en) | 2012-10-04 | 2017-07-11 | Box, Inc. | Corporate user discovery and identification of recommended collaborators in a cloud platform |
US9665349B2 (en) | 2012-10-05 | 2017-05-30 | Box, Inc. | System and method for generating embeddable widgets which enable access to a cloud-based collaboration platform |
US9628268B2 (en) | 2012-10-17 | 2017-04-18 | Box, Inc. | Remote key management in a cloud-based environment |
US10235383B2 (en) | 2012-12-19 | 2019-03-19 | Box, Inc. | Method and apparatus for synchronization of items with read-only permissions in a cloud-based environment |
US9117054B2 (en) | 2012-12-21 | 2015-08-25 | Websense, Inc. | Method and aparatus for presence based resource management |
US10044715B2 (en) | 2012-12-21 | 2018-08-07 | Forcepoint Llc | Method and apparatus for presence based resource management |
US9396245B2 (en) | 2013-01-02 | 2016-07-19 | Box, Inc. | Race condition handling in a system which incrementally updates clients with events that occurred in a cloud-based collaboration platform |
US20140195888A1 (en) * | 2013-01-04 | 2014-07-10 | International Business Machines Corporation | Tagging autofill field entries |
US9760557B2 (en) * | 2013-01-04 | 2017-09-12 | International Business Machines Corporation | Tagging autofill field entries |
US9953036B2 (en) | 2013-01-09 | 2018-04-24 | Box, Inc. | File system monitoring in a system which incrementally updates clients with events that occurred in a cloud-based collaboration platform |
US9507795B2 (en) | 2013-01-11 | 2016-11-29 | Box, Inc. | Functionalities, features, and user interface of a synchronization client to a cloud-based environment |
US10599671B2 (en) | 2013-01-17 | 2020-03-24 | Box, Inc. | Conflict resolution, retry condition management, and handling of problem files for the synchronization client to a cloud-based platform |
US10846074B2 (en) | 2013-05-10 | 2020-11-24 | Box, Inc. | Identification and handling of items to be ignored for synchronization with a cloud-based platform by a synchronization client |
US10725968B2 (en) | 2013-05-10 | 2020-07-28 | Box, Inc. | Top down delete or unsynchronization on delete of and depiction of item synchronization with a synchronization client to a cloud-based platform |
US9633037B2 (en) | 2013-06-13 | 2017-04-25 | Box, Inc | Systems and methods for synchronization event building and/or collapsing by a synchronization component of a cloud-based platform |
US10877937B2 (en) | 2013-06-13 | 2020-12-29 | Box, Inc. | Systems and methods for synchronization event building and/or collapsing by a synchronization component of a cloud-based platform |
US9805050B2 (en) | 2013-06-21 | 2017-10-31 | Box, Inc. | Maintaining and updating file system shadows on a local device by a synchronization client of a cloud-based platform |
US11531648B2 (en) | 2013-06-21 | 2022-12-20 | Box, Inc. | Maintaining and updating file system shadows on a local device by a synchronization client of a cloud-based platform |
US10229134B2 (en) | 2013-06-25 | 2019-03-12 | Box, Inc. | Systems and methods for managing upgrades, migration of user data and improving performance of a cloud-based platform |
US10110656B2 (en) | 2013-06-25 | 2018-10-23 | Box, Inc. | Systems and methods for providing shell communication in a cloud-based platform |
US9535924B2 (en) | 2013-07-30 | 2017-01-03 | Box, Inc. | Scalability improvement in a system which incrementally updates clients with events that occurred in a cloud-based collaboration platform |
US9483473B2 (en) | 2013-09-13 | 2016-11-01 | Box, Inc. | High availability architecture for a cloud-based concurrent-access collaboration platform |
US8892679B1 (en) | 2013-09-13 | 2014-11-18 | Box, Inc. | Mobile device, methods and user interfaces thereof in a mobile device platform featuring multifunctional access and engagement in a collaborative environment provided by a cloud-based platform |
US9704137B2 (en) | 2013-09-13 | 2017-07-11 | Box, Inc. | Simultaneous editing/accessing of content by collaborator invitation through a web-based or mobile application to a cloud-based collaboration platform |
US9519886B2 (en) | 2013-09-13 | 2016-12-13 | Box, Inc. | Simultaneous editing/accessing of content by collaborator invitation through a web-based or mobile application to a cloud-based collaboration platform |
US10509527B2 (en) | 2013-09-13 | 2019-12-17 | Box, Inc. | Systems and methods for configuring event-based automation in cloud-based collaboration platforms |
US11822759B2 (en) | 2013-09-13 | 2023-11-21 | Box, Inc. | System and methods for configuring event-based automation in cloud-based collaboration platforms |
US11435865B2 (en) | 2013-09-13 | 2022-09-06 | Box, Inc. | System and methods for configuring event-based automation in cloud-based collaboration platforms |
US9535909B2 (en) | 2013-09-13 | 2017-01-03 | Box, Inc. | Configurable event-based automation architecture for cloud-based collaboration platforms |
US9213684B2 (en) | 2013-09-13 | 2015-12-15 | Box, Inc. | System and method for rendering document in web browser or mobile device regardless of third-party plug-in software |
US10044773B2 (en) | 2013-09-13 | 2018-08-07 | Box, Inc. | System and method of a multi-functional managing user interface for accessing a cloud-based platform via mobile devices |
US10866931B2 (en) | 2013-10-22 | 2020-12-15 | Box, Inc. | Desktop application for accessing a cloud collaboration platform |
US9819621B2 (en) | 2013-12-27 | 2017-11-14 | Entefy Inc. | Apparatus and method for optimized multi-format communication delivery protocol prediction |
US9930002B2 (en) | 2013-12-27 | 2018-03-27 | Entefy Inc. | Apparatus and method for intelligent delivery time determination for a multi-format and/or multi-protocol communication |
US11831590B1 (en) | 2013-12-27 | 2023-11-28 | Entefy Inc. | Apparatus and method for context-driven determination of optimal cross- protocol communication delivery |
US11496426B2 (en) | 2013-12-27 | 2022-11-08 | Entefy Inc. | Apparatus and method for context-driven determination of optimal cross-protocol communication delivery |
US9843543B2 (en) | 2013-12-27 | 2017-12-12 | Entefy Inc. | Apparatus and method for multi-format and multi-protocol group messaging |
US10606870B2 (en) | 2014-02-24 | 2020-03-31 | Entefy Inc. | System and method of dynamic, encrypted searching |
US10169447B2 (en) | 2014-02-24 | 2019-01-01 | Entefy Inc. | System and method of message threading for a multi-format, multi-protocol communication system |
US9639600B2 (en) | 2014-02-24 | 2017-05-02 | Entefy Inc. | System and method of personalized message threading for a multi-format, multi-protocol communication system |
US9594827B2 (en) | 2014-02-24 | 2017-03-14 | Entefy Inc. | System and method of dynamic, encrypted searching |
US10394966B2 (en) | 2014-02-24 | 2019-08-27 | Entefy Inc. | Systems and methods for multi-protocol, multi-format universal searching |
US11366838B1 (en) | 2014-02-24 | 2022-06-21 | Entefy Inc. | System and method of context-based predictive content tagging for encrypted data |
US11755629B1 (en) | 2014-02-24 | 2023-09-12 | Entefy Inc. | System and method of context-based predictive content tagging for encrypted data |
WO2015127069A1 (en) * | 2014-02-24 | 2015-08-27 | Entefy, Inc. | System and method of message threading for a multi-format, multi-protocol communication system |
US10606871B2 (en) | 2014-02-24 | 2020-03-31 | Entefy Inc. | System and method of message threading for a multi-format, multi-protocol communication system |
US10530854B2 (en) | 2014-05-30 | 2020-01-07 | Box, Inc. | Synchronization of permissioned content in cloud-based environments |
US9602514B2 (en) | 2014-06-16 | 2017-03-21 | Box, Inc. | Enterprise mobility management and verification of a managed application by a content provider |
US9477724B2 (en) * | 2014-06-23 | 2016-10-25 | Sap Se | Framework for visualizing re-written queries to database |
US20150370865A1 (en) * | 2014-06-23 | 2015-12-24 | Sang Il Song | Framework for Visualizing Re-Written Queries to Database |
US9633075B2 (en) | 2014-06-23 | 2017-04-25 | Sap Se | Framework for re-writing database queries |
US9756022B2 (en) | 2014-08-29 | 2017-09-05 | Box, Inc. | Enhanced remote key management for an enterprise in a cloud-based environment |
US10708323B2 (en) | 2014-08-29 | 2020-07-07 | Box, Inc. | Managing flow-based interactions with cloud-based shared content |
US11146600B2 (en) | 2014-08-29 | 2021-10-12 | Box, Inc. | Configurable metadata-based automation and content classification architecture for cloud-based collaboration platforms |
US11876845B2 (en) | 2014-08-29 | 2024-01-16 | Box, Inc. | Configurable metadata-based automation and content classification architecture for cloud-based collaboration platforms |
US10038731B2 (en) | 2014-08-29 | 2018-07-31 | Box, Inc. | Managing flow-based interactions with cloud-based shared content |
US10574442B2 (en) | 2014-08-29 | 2020-02-25 | Box, Inc. | Enhanced remote key management for an enterprise in a cloud-based environment |
US9894119B2 (en) | 2014-08-29 | 2018-02-13 | Box, Inc. | Configurable metadata-based automation and content classification architecture for cloud-based collaboration platforms |
US10708321B2 (en) | 2014-08-29 | 2020-07-07 | Box, Inc. | Configurable metadata-based automation and content classification architecture for cloud-based collaboration platforms |
US11740950B2 (en) | 2015-12-31 | 2023-08-29 | Entefy Inc. | Application program interface analyzer for a universal interaction platform |
US10353754B2 (en) | 2015-12-31 | 2019-07-16 | Entefy Inc. | Application program interface analyzer for a universal interaction platform |
US10761910B2 (en) | 2015-12-31 | 2020-09-01 | Entefy Inc. | Application program interface analyzer for a universal interaction platform |
US10135764B2 (en) | 2015-12-31 | 2018-11-20 | Entefy Inc. | Universal interaction platform for people, services, and devices |
US11768871B2 (en) | 2015-12-31 | 2023-09-26 | Entefy Inc. | Systems and methods for contextualizing computer vision generated tags using natural language processing |
US11494204B2 (en) | 2016-12-31 | 2022-11-08 | Entefy Inc. | Mixed-grained detection and analysis of user life events for context understanding |
US10491690B2 (en) | 2016-12-31 | 2019-11-26 | Entefy Inc. | Distributed natural language message interpretation engine |
CN107038647A (en) * | 2017-03-15 | 2017-08-11 | 平安科技(深圳)有限公司 | Insurance application cancelling method and device |
US10587553B1 (en) | 2017-12-29 | 2020-03-10 | Entefy Inc. | Methods and systems to support adaptive multi-participant thread monitoring |
US11573990B2 (en) | 2017-12-29 | 2023-02-07 | Entefy Inc. | Search-based natural language intent determination |
US11914625B2 (en) | 2017-12-29 | 2024-02-27 | Entefy Inc. | Search-based natural language intent determination |
US20200117737A1 (en) * | 2018-10-16 | 2020-04-16 | LeapAnalysis Inc. | Fast heterogeneous multi-data source search and analytics |
US11087083B1 (en) * | 2020-03-31 | 2021-08-10 | Coupa Software Incorporated | Managing bundles of digital objects in an e-procurement system |
US11475010B2 (en) | 2020-09-09 | 2022-10-18 | Self Financial, Inc. | Asynchronous database caching |
US11641665B2 (en) | 2020-09-09 | 2023-05-02 | Self Financial, Inc. | Resource utilization retrieval and modification |
US11630822B2 (en) | 2020-09-09 | 2023-04-18 | Self Financial, Inc. | Multiple devices for updating repositories |
Also Published As
Publication number | Publication date |
---|---|
EP1370959A1 (en) | 2003-12-17 |
EP1370959A4 (en) | 2007-04-25 |
JP2004528636A (en) | 2004-09-16 |
US7058663B2 (en) | 2006-06-06 |
CN1459061A (en) | 2003-11-26 |
WO2002073432A1 (en) | 2002-09-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7058663B2 (en) | Automatic data update | |
US8271477B2 (en) | Methods and systems for accessing data | |
US7818663B2 (en) | Editable information management system and method | |
JP3873365B2 (en) | Business processing system using bulletin board type database and processing method thereof | |
US6119117A (en) | Document management method, document retrieval method, and document retrieval apparatus | |
US6978281B1 (en) | Versioned project data | |
EP1121639B1 (en) | Impact analysis of a model | |
US20140172742A1 (en) | Crm office integration | |
US20030225770A1 (en) | Collaborative data cleansing | |
US20080005189A1 (en) | Computer readable recording medium having stored therein database synchronizing process program, and apparatus for and method of performing database synchronizing process | |
KR20040054471A (en) | Contact user interface | |
US20050076068A1 (en) | System and method of synchronizing data in multi-user computer network | |
US8386503B2 (en) | Method and apparatus for entity removal from a content management solution implementing time-based flagging for certainty in a relational database environment | |
JP4207417B2 (en) | Document management device | |
US6799183B2 (en) | Operation assistance method and system and recording medium for storing operation assistance method | |
JP2007334412A (en) | Retrieval program and retrieving device | |
JP4186452B2 (en) | Document management device | |
EP1585031A1 (en) | Generating data base queries based on data dictionary. | |
EP2105836A1 (en) | Archive system storing archive data from a computer-based information system and method of operating such a system | |
CN115623008B (en) | Index construction method and system of Kubernetes resources | |
JPH07325749A (en) | Information management system | |
JP3337717B2 (en) | Database processing device and database processing method | |
JPH0212563A (en) | Information managing system | |
JP4430900B2 (en) | Database control system and database control program | |
JPH06214850A (en) | File retrieving device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AGILENT TECHNOLOGIES, INC., COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JOHNSTON, JAMES A.;SMITH, ROBERT P.;REEL/FRAME:011832/0053 Effective date: 20010514 |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees | ||
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20100606 |