US20030009753A1 - Method of synchronizing independently distributed software and database schema - Google Patents
Method of synchronizing independently distributed software and database schema Download PDFInfo
- Publication number
- US20030009753A1 US20030009753A1 US09/992,813 US99281301A US2003009753A1 US 20030009753 A1 US20030009753 A1 US 20030009753A1 US 99281301 A US99281301 A US 99281301A US 2003009753 A1 US2003009753 A1 US 2003009753A1
- Authority
- US
- United States
- Prior art keywords
- upgrade
- client
- server
- docking
- computer
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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
-
- 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/99954—Version management
Definitions
- This invention relates to a system and method for providing updates to a network of partially replicated relational database systems, and, more particularly, for providing an efficient means for computing the visibility to a client on the network of a transaction processed against the database.
- Relational databases are a commonly-employed data structure for representing data in a business or other environment.
- a relational database represents data in the form of a collection of two-dimensional tables. Each table comprises a series of cells arranged in rows and columns. Typically, a row in a table represents a particular observation. A column represents either a data field or a pointer to a row in another table.
- a database describing an organizational structure may have one table to describe each position in the organization, and another table to describe each employee in the organization.
- the employee table may include information specific to the employee, such as name, employee number, age, salary, etc.
- the position table may include information specific to the position, such as the position title (“salesman”, “vice president”, etc.), a salary range, and the like.
- the tables may be related by, for example, providing in each row of the employee table a pointer to a particular row in the position table, coordinated so that, for each row in the employee table, there is a pointer to the particular row in the position table that describes that employee's position.
- RDBMS relational database management system
- Relational databases may be much more complex than this example, with several tables and a multiplicity of relations among them.
- One disadvantage is that a full copy of the central database may require more data storage than is desired or economical. For example, a salesman working in the field may need to refer to the database for information regarding sales opportunities in his sales area, but have no need to refer to any information regarding sales opportunities outside of his area.
- One possible approach to reduce the amount of required data storage is to simply replicate only that portion of the database that is needed by the user.
- this approach does not recognize that the criteria to determine which portions of the data are required is likely to vary over time. For example, the salesman may have a new city added to his territory. Under conventional approaches, the salesman would need to re-replicate his local copy of the database, this time selecting data including the added city. Such a practice is inconvenient, subject to error, and time-consuming.
- a further disadvantage to a replicated database is the difficulties encountered in attempting to update data using the replicated copy.
- a change made to the replicated database is not made to the central database, leading to a discrepancy between the information that is stored in the replicated copy of the database and the information that is stored in the central database.
- journal modifications made to the replicated copy and apply an identical modification to the central database, one problem that this approach faces is the possibility of colliding updates; that is, where a user of a replicated copy makes a change to data that is also changed by a user of the central copy or by the user of another replicated copy.
- the present invention is directed to a method of maintaining a partially replicated database in such a way that updates made to a central database, or to another partially replicated database, are selectively propagated to the partially replicated database. Updates are propagated to a partially replicated database if the owner of the partially replicated database is deemed to have visibility to the data being updated. Visibility is determined by use of predetermined rules stored in a rules database. In one aspect of the invention, the stored rules are assessed against data content of various tables that make up a logical entity, known as a docking object, that is being updated.
- the stored rules are assessed against data content of one or more docking objects that are not necessarily updated, but that are related to a docking object being updated.
- the visibility attributes of the related docking objects are recursively determined.
- changes in visibility are determined to enable the central computer to direct the nodes to insert the docking object into its partially replicated database. Such changes in visibility are determined so as to enable the central computer to direct a node to remove a docking object from its partially replicated database.
- the predetermined rules are in declarative form and specify visibility of data based upon structure of the data without reference to data content.
- the levels of the database schema and the database access software are synchronized to prevent an updated schema from being processed by a back-level version of software.
- a still further aspect of our invention is a method of upgrading a software application from one or more upgrade package files in a server ( 1 ) to a client ( 21 a , 21 b , 21 c ).
- a copy of the upgrade package files and an upgrade database table are created on the server ( 1 ).
- a pointer is created in the client's ( 21 a , 21 b , 21 c ) file on the server ( 1 ). This pointer points to the upgrade package files on the server ( 1 ).
- the upgrade files are made active, and the upgrade database table is scanned when a client ( 21 a , 21 b , 21 c ) docks.
- the upgrade is copied to the client ( 21 a , 21 b , 21 c ) if the client ( 21 a , 21 b , 21 c ) has not received the upgrade. At this point the upgrade may be invoked at the client ( 21 a , 21 b , 21 c ).
- a still further aspect of our invention is a program product article of manufacture encompassing a computer usable medium with computer program code embodied therein for causing the upgrading of a software application from upgrade package files in a server ( 1 ) to a client ( 21 a , 21 b , 21 c ).
- the computer readable program in the program product article of manufacture contains computer readable program code means for causing a computer to effect creating a copy of the upgrade package files on the server ( 1 ), creating an upgrade database table on the server ( 1 ); creating a pointer in the client's ( 21 a , 21 b , 21 c ) file on the server ( 1 ) pointing to the upgrade package files on the server ( 1 ), making the upgrade active, scanning the upgrade database table when a client ( 21 a , 21 b , 21 c ) docks to determine the status of an upgrade with respect to the client ( 21 a , 21 b , 21 c ), copying the upgrade to a client ( 21 a , 21 b , 21 c ) if the client ( 21 a , 21 b , 21 c ) has not received the upgrade, and invoking the upgrade at the client ( 21 a , 21 b , 21 c ).
- a even further aspect of our invention is a program product in the form of a program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for of upgrading a software application from upgrade package files in a server ( 1 ) to a client ( 21 a , 21 b , 21 c ) said method steps comprising creating a copy of the upgrade package files on the server ( 1 ), creating an upgrade database table on the server ( 1 ); creating a pointer in the client's ( 21 a , 21 b , 21 c ) file on the server ( 1 ) pointing to the upgrade package files on the server ( 1 ), making the upgrade active, scanning the upgrade database table when a client ( 21 a , 21 b , 21 c ) docks to determine the status of an upgrade with respect to the client ( 21 a , 21 b , 21 c ), copying the upgrade to a client ( 21 a , 21 b , 21 c ), copying
- FIG. 1 depicts an overview of the operation of one embodiment of the present invention.
- FIG. 2 depicts a database schema that shows the relationship of the various components that make up a Docking Object.
- FIG. 3 depicts steps performed by an update manager to update a database.
- FIG. 4 depicts steps performed by a Docking Manager to transmit and/or receive one or more transaction logs.
- FIG. 5 depicts the steps performed by a merge processor to merge transaction log records into an existing database.
- FIG. 6 depicts the steps performed by a log manager to prepare a partial transaction log.
- FIG. 7 depicts the steps performed by a visibility calculator for calculating visibility for a docking object as invoked by a log manager.
- FIG. 8 depicts the steps performed to synchronize a partially replicated database in response to a change in data visibility.
- FIG. 1 depicts an overview of the operation of one embodiment of the present invention.
- FIG. 1 depicts a central computer system 1 and three remote computer systems (or “nodes”) 21 - a , 21 - b , and 21 - c .
- Each of nodes 21 - a , 21 - b and 21 - c are depicted in various states of communication with central computer system 1 , as will be more fully explained.
- Central computer system 1 includes a central database 3 , a docking manager 5 , a merge processor 7 and a log manager 9 .
- Central computer system 1 additionally optionally includes update manager 11 responsive to user input 13 .
- Node 21 - a is a remote computer system, such as a mobile client such as a laptop computer.
- Node 21 - a includes a partially replicated remote database 23 - a , update manager 31 - a responsive to user input 33 - a , docking manager 25 - a and merge manager 27 - a .
- update manager is responsive to user input 33 - a to make changes to remote database 23 - a as directed by the operator of node 21 - a . Updates made are recorded, or journaled, in node update log 35 - a.
- node docking manager 35 - a is activated, and enters into communication with central docking manager 5 .
- Update log 35 - a is taken as input by node docking manager 25 - a , and provided to central docking manager 5 .
- Central docking manager 5 creates a received node update log 19 , which contains all the information that had been recorded in update log 35 - a .
- partial log 17 - a is taken as input by central docking manager 5 and provided to node docking manager 25 - a , as more fully described herein.
- merge processor 7 is activated.
- Merge processor 7 takes as input received node update log 19 , and applies the updates described therein to central database 3 .
- merge processor journals the updates applied to central update log 15 .
- update manager 11 responsive to user input 12 makes additional changed to central database 3 as directed by the operator of central computer system 1 .
- the updates made by update manager 11 are additionally journaled in central update log 15 .
- log manager 9 is activated.
- Log manager 9 takes as input central update log 15 and produces as output a set of partial logs 17 - a , 17 - b and 17 - c according to visibility rules as will be further described herein.
- Each of partial logs 17 - a , 17 - b and 17 - c corresponds to one of nodes 21 - a , 21 - b and 21 - c .
- node docking manager 25 - a When a node docking manager such as node docking manager 25 - a enters into communication with central docking manager 5 and optionally requests transmission of its corresponding partial log, central docking manager 5 takes as input the appropriate partial log, such as partial log 17 - a , and presents it to node docking manager 25 - a . Node docking manager 25 - a then replicates partial log 17 - a as merge log 37 - a.
- merge processor 27 - a takes as input merge log 37 - a , and applies the updates described therein to partially replicated database 23 - a.
- FIG. 1 also depicts two additional nodes 21 - b and 21 - c .
- Node 21 - b is depicted in communication with central computer 1 .
- the operator of node 21 - b has requested only to send his updates to central computer system 1 , and has not requested to be presented with changes made elsewhere to be made to his partially replicated database 23 - b . This may be, for example, if the operator has an urgent update that must be made as soon as possible, but does not have the time to receive updates from other nodes. Accordingly, FIG.
- node 21 - c is depicted as not in communication with central computer system 1 . Accordingly, the docking manager for node 21 - c is not activated and is not shown.
- a Docking Object consists of Member Tables (including one Primary Table), Visibility Rules, Visibility Events, and related Docking Objects.
- a Member Table is a table of the relational database that makes up a docking object.
- the propagation takes the form of an insertion into each of the Member Tables associated with the particular docking object.
- that removal consists of deleting records from the member tables associated with the docking object.
- a docking object that represents a sales opportunity may include tables that represent the opportunity itself (e.g., named “S_OPTY”), the product whose sale is represented by the opportunity (e.g., named “S_OPTY_PROD”), the contact for the opportunity (e.g., named “S_OPTY_CONTACT”), etc.
- S_OPTY the opportunity itself
- S_OPTY_PROD the product whose sale is represented by the opportunity
- S_OPTY_CONTACT the contact for the opportunity
- a Primary Table is a Member Table that controls whether a particular instance of a Docking Object is visible to a particular node.
- the Primary Table has a Primary Row-ID value that is used to identify a row of the Primary Table being updated, deleted or inserted.
- the “Opportunity Docking Object” may have as a primary table the table S_OPTY.
- the row-id of that table, i.e., S_OPTY.row_id is the Primary Row-ID for the Opportunity Docking Object.
- a Visibility Rule is a criterion that determines whether a particular instance of a Docking Object is “visible” to a particular node 21 . If a Docking Object is visible to a particular node, that node will receive updates for data in the Docking Object. Visibility Rules are of two types, depending on the field RULE_TYPE. A Visibility Rule with a RULE TYPE of “R” is referred to as an SQL Rule. An SQL Rule includes a set of Structured Query Language (SQL) statements that is evaluated to determine if any data meeting the criteria specified in the SQL statements exists in the Docking Object. If so, the Docking Object is visible to the node.
- SQL Structured Query Language
- a Visibility Rule with a RULE_TYPE of “O” is referred to as a Docking Object Rule.
- a Docking Object Rule specifies another Docking Object to be queried for visibility. If the specified Docking Object is visible, then the Docking Object pointing to it is also visible.
- a Related Docking Object is a Docking Object that is propagated or deleted when the Docking Object under consideration is propagated or deleted.
- an Opportunity Docking Object may have related Docking Objects representing the sales contacts, the organizations, the products to be sold, and the activities needed to pursue the opportunity.
- an Opportunity Docking Object is propagated from Central Database 3 to one of node databases 23 , the related docking objects are also propagated.
- FIG. 2 depicts a database schema that shows the relationship of the various components that make up a Docking Object.
- the schema is a meta-database, in that it does not describe the data being accessed in the database. Rather, the schema is a separate database that defines the structure of the database being accessed. That is, it is a database comprising tables that describe the relationships and data contexts of another database.
- Each of the tables shown in FIG. 2 is a table in a relational database, and as such is in row-column form. Many columns represent fields that are common to all the illustrated tables. Such fields include for example, a ROW_ID to identify a particular row in the table, as well as fields to tack the date and time that a row was created and last modified, and the identity of the user who created or modified the row. In addition, each table contains fields specific to that table, and which are described in detail below.
- Table S_DOBJ 61 describes the Docking Objects in an application.
- Table S_DOBJ 61 includes the fields OBJ_NAME and PRIMARY_TABLE_ID.
- Field OBJ_NAME defines the name of the Docking Object being described.
- Field PRIMARY_TABLE_ID is used to identify the primary table associated with this Docking Object.
- Table S_DOBJ_INST 63 describes whether a particular instance of a Docking Object, described by table S_DOBJ 61 , is present on a particular node's database.
- Table S_DOBJ_INST 63 includes the fields NODE_ID, DOBJ_ID and PR_TBL_ROW_ID.
- Field NODE_ID points to a particular node table 65 .
- Field DOBJ_ID points to the Docking Object to which the Docking Object instance applies.
- Field PR_TBL_ROW_ID is used to select a particular row in the Primary Table of the Docking Object. This value identifies the Docking Object instance.
- Table S_REL_DOBJ 67 describes the related Docking Objects of a particular Docking Object, described by table S_DOBJ 61 .
- Table S_REL_DOBJ 67 includes the fields DOBJ_ID, REL_DOBJ_ID, and SQL_STATEMENT.
- Field DOBJ_ID identifies the Docking Object that owns a particular related Docking Object.
- Field REL_DOBJ_ID identifies the related Docking Object that is owned by the Docking Object identified by DOBJ_ID.
- Field SQL_STATEMENT is an SQL statement that may be executed to obtain the Primary ID value of the related Docking Object.
- Table S_DOBJ_TBL 69 describes the member tables of a particular Docking Object, described by table S_DOBJ 61 .
- Table S_DOBJ_TBL 69 includes the fields DOBJ_ID, TBL_ID, and VIS_EVENT_FLG.
- Field DOBJ_ID identifies the Docking Object that contains the member table described by the row.
- Field TBL_ID identifies the particular table in the database that is the member table described by the row.
- Field VIS_EVENT_FLG is a flag that indicates whether a change to this Docking Object can result in a visibility event. A value of “Y” indicates that a change can result in a visibility event; a value of “N” indicates that it cannot.
- Table S_DOBJ_VIS_RULE 71 contains the visibility rules associated with a particular Docking Object.
- S_DOBJ_VIS_RULE 71 contains the fields DOBJ_ID, RULE SEQUENCE, RULE_TYPE, SQL_STATEMENT and CHECK_DOBJ_ID.
- Field DOBJ_ID identifies the Docking Object with which a particular visibility rule is associated.
- Field RULE_SEQUENCE is a sequence number that indicates the sequence, relative to other visibility rules in table S_DOBJ_VIS_RULE 71 , in which the particular visibility rule should be run.
- RULE_TYPE specifies whether the particular visibility rule is of type “R,” indicating an SQL visibility rule or of type “O,” indicating a Docking Object visibility rule.
- field SQL_STATEMENT contains an SQL statement that is evaluated using the Primary ROW-ID of the primary table associated with this Docking Object and a particular Node 21 . If the SQL statement returns any records, the Docking Object is deemed to be visible to the Node 21 for which visibility is being determined.
- Field CHECK_DOBJ_ID specifies a docking object whose visibility should be determined. If the specified docking object is deemed to be visible, then the docking object associated with the visibility rule is also visible.
- Field SQL_STATEMENT contains a SQL statement that, when executed, returns the Row-ID of the docking object identified by CHECK_DOBJ_ID that corresponds to the docking object instance associated with the visibility rule.
- Table S_APP_TBL 73 is an Application Table that describes all the tables used in a particular application. It is pointed to by table S_DOBJ_TBL 69 for each member table in a docking object, and by table S_DOBJ for the primary table in a docking object.
- S_APP_TBL 73 points to table S_APP_COL 75 , which is an Application Column Table that describes the columns of data in a particular application.
- S_APP_TBL 73 points to table S_APP_COL 75 directly through a primary key and indirectly through such means as a Foreign Key Column Table 81 , User Key Column Table 83 , and Column Group Table 85 .
- the relationship of an Application Table, Application Column Table, Foreign Key Column Table, User Key Column Table and Column Group Table are well known in the art and are not further described.
- FIG. 3 depicts steps performed by an update manager 31 such as update manager 31 - a , 31 - b or 31 - c in updating a database, such as a node database 23 - a , 23 - b or 23 - c , responsive to user input.
- Execution of update manager 31 begins in step 101 .
- the update manager 31 accepts from the user input 33 in the form of a command requesting that the data in database 23 be altered.
- the request may be in the form of a request to delete a row of a table, to add a row to a table, or to change the value of a cell at a particular column of a particular row in a table.
- step 105 using a well-known means, the update manager 31 applies the requested update to database 23 .
- the update manager 31 creates a log record describing the update and writes it to update log 35 .
- Each log record indicates the node identifier of the node making the update, an identification of the table being updated, and an identification of the type of update being made, i.e., an insertion of a new row, a deletion of an existing row, or an update to an existing row.
- the log record additionally includes an identifier of the row being inserted, including its primary key and the values of the other columns in the row.
- the log record identifies the primary key of the row being deleted.
- the log record identifies the primary key of the row being updated, the column within the row being updated, the old value of the cell at the addressed row and column, and the new value of the cell.
- the update processor After writing a log record in step 107 , the update processor exits for this update.
- the foregoing description of the update processing preferably includes additional steps not material to the present invention, for example, to assure authorization of the user to make the update, to stage and commit the write to the database to allow for rollback in the event of software or hardware failure, and the like. These steps are well-known in the art and are not described further.
- An update manager 11 executing in central computer system I operates in an analogous manner, except that it updates central database 3 and writes its log records to central update log 11 .
- FIG. 4 depicts steps performed by a Docking Manager 25 such as Docking Manager 25 - a , 25 - b or 25 - c to transmit and/or receive one or more transaction logs.
- Docking Manager 25 is invoked by the user of a remote node such as node 21 - a , 21 - b or 21 - c , whereby the user requests that the node dock with central computer 1 to upload an update log such as update log 35 - a to central computer 1 , to download a partial log such as partial log 17 - a , or both.
- Execution of Docking Manager 25 begins in step 121 .
- step 123 Docking Manager 25 connects with central computer 1 under the control of Central Docking Manager 5 .
- connection can be any connection that enables data exchange. It is anticipated that the most common form of a connection is a telephone line used in conjunction with a modem, but other forms of data connection, such as a Local Area Network or a TCP/IP connection may also be used.
- Step 125 checks to see whether the user has requested that node update log 35 - a be uploaded to the Central Computer 1 . If so, execution proceeds to step 127 . If not, step 127 is skipped and control is given to step 129 .
- Docking Manager 25 uploads its update log to central computer 1 . The upload may be accomplished with any known file transfer means, such as XMODEM, ZMODEM, KERMIT, FTP, ASCII transfer, or any other method of transmitting data.
- step 129 Docking Manager 25 checks to see whether the user has requested that a partial log such as partial log 17 - a be downloaded from Central Computer 1 . If so, execution proceeds to step 131 . If not, step 131 is skipped and control is given to step 133 .
- step 131 Docking Manager 25 downloads its partial log from central computer 1 . The download may be accomplished with any known file transfer means, such as XMODEM, ZMODEM, KERMIT, FTP, ASCII transfer, or any other method of transmitting data.
- step 133 having completed the requested data transfer, Docking Manager 25 exits.
- Merge processing is performed by a processor such as node merge processor 27 - a , 27 - b , or 27 - c , or central merge processor 7 .
- the merge process serves to update its associated database with a transaction that has been entered by a user of a computer remote from the computer where merge processing is being performed.
- Merge processing is analogous to update processing and is similar in form to update processing as previously disclosed with reference to FIG. 3, with three differences.
- the input to a merge processor is not an update entered directly by a user, but rather is a log file that is obtained from a computer remote from the computer where the merge is executing.
- a second difference is that, as shown by in FIG. 1, merge processing does not produce a log when performed at a node.
- the function of a log on a node is to record a transaction for propagation to Central Computer system 1 and thence to other nodes as required.
- a transaction that is the subject of a merge in a node has been communicated to Central Computer System 1 , and there is no need to re-communicate it.
- a third difference is that merge processing must be capable of detecting and resolving multiple conflicting transactions. For example, assume that a field contains the value “Keith Palmer.” Assume further that a user at node 27 - a enters a transaction to update that field to “Carl Lake,” and a user at node 27 - b enters a transaction to update the same field to “Greg Emerson.” Without collision detection, data among various nodes may become corrupt.
- each node When the transaction for user 27 - a is merged, the field is updated from “Keith Palmer” to “Carl Lake.” Without collision handling, when the transaction for node 27 - b is merged, the field would be updated to “Greg Emerson,” and the central database would then be out of synch with the database of node 27 - a . Furthermore, when merge processing is performed on each of nodes 27 - a and 27 - b , each node will update its database with the other's transactions, leaving at least one node out of synch with the other node and with central database.
- merge processing must also have a means of detecting collisions and correcting them.
- a simple way to detect and correct a collision is to compare the value in the database to the value that the merge log reflects as being the previous value in the node database. If the two values do not match, Merge processor 7 may reject the transaction and generate a corrective transaction to be sent to the node from which the conflicting transaction originated.
- merge processor 7 would compare “Keith Palmer,” the prior value of the field as recorded by node 27 - b to “Carl Lake,” the present value of the field as recorded in central database 3 .
- merge processor 7 may then generate a transaction to change the value “Greg Emerson” to “Carl Lake,” and write that transaction to update log 15 . In a subsequent docking operation, that transaction would be routed back to node 27 - b to bring its database 23 - b in synch with the other databases.
- collision processing must detect and correct each of these collisions. This may be performed using any of a number of well-known methods, and is not discussed further.
- FIG. 5 depicts the steps performed by merge processor such as central merge processor 7 . Although it depicts merge processor 7 writing to central database 3 and to transaction log 15 , it is equally representative of a node merge processor such as node merge processor 27 - a , 27 - b or 27 - c updating a node database 23 - a , 23 - b or 23 - c .
- Merge processing begins at step 141 .
- merge processor 7 finds the first unprocessed transaction on received log 19 .
- merge processor 7 selects a transaction from received log 19 .
- merge processor 149 attempts to update database 3 according to the transaction selected in step 147 .
- step 151 merge processor 7 determines whether the database update of step 149 failed due to a collision. If so, merge processor proceeds to step 153 , which generates a corrective transaction. Following the generation of the corrective transaction, the merge processor returns to step 149 and again attempts to update database 3 . If no collision was detected in step 151 , execution proceeds to step 157 .
- step 157 merge processing checks to see if it is executing on central computer 1 . If so, step 155 is executed to journal the transaction to log 15 . In any case, either if step 157 determines that the merge processing is being performed on a node or after step 155 , execution proceeds to step 159 . Step 159 checks to see if any transactions remain to be processed from log 19 . If so, execution repeats from step 147 , where the next transaction is selected. If not, merge processing exits in step 161 .
- FIG. 6 depicts the steps to be performed by log manager 9 to prepare a partial transaction log such as partial transaction log 17 - a , 17 - b , or 17 - c .
- the procedure depicted in FIG. 6 is executed for each node available to dock with central computer system 1 .
- Log manager 9 begins execution in step 171 .
- step 173 Log Manager 9 finds the first unprocessed transaction for the node whose partial transaction log is being prepared.
- log manager 9 selects a transaction for processing.
- step 177 log manager 9 checks to see whether the selected transaction originated on the same node for which processing is being performed. If so, there is no need to route the transaction back to the node, and control proceeds to step 179 .
- Step 179 checks to see whether there are any transactions remaining to be processed. If so, control is given again to step 175 . If not, control passes to step 189 , which records the last transaction that was processed for this node, and then exits at step 191 . If the transaction originates in other than the same node as the node for which processing is being performed, control is given to step 181 . Step 181 calls a visibility calculator to determine whether the selected transaction is visible to the node being processed. The Visibility calculator routine is described in detail further herein. In step 183 , merge processor 9 checks to see whether the visibility calculator determined that the transaction is visible. If it is not visible, control is passed to step 179 , which performs as disclosed above. If the transaction is visible, control is passed to step 185 .
- Step 185 writes a record for this transaction to the partial transaction log for the node being processed, for example, partial transaction log 17 - a for node 21 - a .
- the log manager 9 records the last transaction that was processed for this node, and then passes control to step 179 , which determines whether to select additional transactions or exit, as disclosed above.
- FIG. 7 depicts a flowchart describing the process a visibility calculator for calculating visibility for a docking object as invoked by step 181 of log manager 9 .
- the visibility calculator is called with the node-id of the node for which visibility is being calculated, the docking object for which the visibility is being calculated, and the row-id of the docking object whose visibility id being calculated.
- the visibility calculator uses this information, in conjunction with information obtained from meta-data stored in the schema depicted in FIG. 2, to determine whether a particular transaction that updates a particular row of a particular docking object is visible to a particular node.
- the Visibility calculator begins execution at step 201 .
- the visibility calculator makes a default finding that the transaction is not visible. Therefore, unless the visibility calculator determines that a transaction is visible, it will exit with a finding of no visibility.
- the visibility calculator selects the first visibility rule associated with the docking object. This is done by finding the table S_DOBJ_VIS_RULE 71 associated with the current Docking Object as pointed to by table S_DOBJ 61 .
- the visibility calculator selects the row of table S_DOBJ_VIS_RULE 71 with the lowest value for field RULE_SEQUENCE.
- step 207 the Visibility Calculator checks the field RULE_TYPE for a value of “R.” The value of “R” indicates that the rule is a SQL visibility rule. If so, the Visibility Calculator proceeds to step 209 .
- step 209 the Visibility Calculator obtains a SQL statement from field SQL_STATEMENT and executes it.
- An example of such an SQL statement might be:
- This SQL statement causes a query to be made of application table S_OPTY_EMP.
- the query selects any records meeting two criteria.
- the records selected must have a field OPTY_ID, which is a row id or key, equal to the Primary Row-ID of the Docking Object whose visibility is being determined.
- the records selected must have a field EMP_ID, which may be for example, an identifier of a particular employee, equal to the NodeId of the node for whom visibility is being determined.
- EMP_ID which may be for example, an identifier of a particular employee, equal to the NodeId of the node for whom visibility is being determined.
- this SQL statement will return records only if a row is found in a table that matches employees to opportunities, where the opportunity is equal to the one being updated, and the employee to whom the opportunity is assigned is the operator of the node.
- This rule queries the tables S_ACCT_POSTN (which relates a particular account with a particular position in the organization that is responsible for the account) and S_EMP_POSTN (which relates what employee corresponds to a particular position).
- the condition “ap.POSITION_ID ep.POSITION_ID” requires finding a row in the account-to-position table that has the same position as a row in the employee-to-position table.
- Step 211 evaluates whether the execution of SQL_STATEMENT in step 209 returned any records. If records were returned, this indicates that the Node for which visibility is being checked has visibility to the docking object being processed. Accordingly, if records are returned, the Visibility Calculator proceeds to step 213 . In step 213 , the transaction is marked visible. Because no further rules need to be evaluated to determine visibility, the visibility calculator proceeds to step 228 . Step 228 synchronizes the databases by determining whether the calculated visibility requires the insertion or deletion of a docking object into a particular node's partially replicated database. This may occur, for example, if a node is determined to have visibility to a docking object due to a change to a related docking object. For example, an owner of a node may be assigned to a particular activity that is related to a particular sales opportunity. As a result, the node should be provided with a copy of the object representing the sales opportunity.
- FIG. 8 depicts the steps performed to synchronize a partially replicated database in response to a change in data visibility.
- Execution begins in step 241 .
- the Visibility Calculator references the visibility just calculated for a docking object. If the Docking Object is visible, execution proceeds to step 245 .
- Step 245 references the S_DOBJ_INST table, to verify that a row exists for the Docking Object for the current node. If a row exists, this indicates that the node in question already has a copy of the referenced Docking Object, and the routine proceeds to step 255 , where it exits.
- step 247 a transaction is generated to direct the node to insert the Docking Object into its partially replicated database.
- step 243 determines that the Docking Object is not visible, execution proceeds to step 249 .
- Step 249 references the S DOBJ_INST table, to verify that no row exists for the Docking Object for the current node. If step 243 determines that no row exists in the S_DOBJ_INST table for the current docking object for the current row, this indicates that the node in question does not have a copy of the referenced Docking Object, and the routine proceeds to step 255 , where it exits. If, however, a row exists for the Docking Object at the node being processed, this indicates that the node in question does have a copy of the Docking Object on its partially replicated database. The routine then proceeds to step 251 , where a transaction is generated to direct the node to delete the Docking Object from its partially replicated database.
- step 229 the Visibility Calculator proceeds to step 229 , where it exits.
- the resulting finding of visibility is available to be checked by the log manager in step 183 to determine to write the transaction.
- step 211 determines that no records were returned by the execution of the SQL statement in step 209 .
- execution proceeds with step 215 .
- Step 215 checks to see whether there are any remaining visibility rules to be assessed. If not, the visibility calculator proceeds to step 228 to synchronize the database, and then to step 229 , where it exits. In this case, the default mark of no visibility that was set in step 203 remains set. This value will also be used by the log manager as shown in FIG. 6, step 183 , to determine not to write the transaction.
- step 217 selects the next rule to be processed. Control is then given again to step 207 to begin processing the new rule.
- step 207 determines that the visibility rule is not of type “R,” the visibility rule is of type “O.”
- Type “O” indicates a docking-object visibility rule. In such a case, the docking object being processed will be considered to be visible if it is related to a particular related docking object that is visible. If field RULE_TYPE is not equal to “R,” then. execution proceeds to step 221 .
- Step 221 determines the related Docking Object whose visibility must be determined to determine whether the current docking object is visible.
- the related Docking Object identifier is obtained from field CHECK_DOBJ_ID in table S_DOBJ_VIS_RULE 71 .
- the Visibility Calculator determines which row in the related Docking Object must be queried for visibility. In order to determine this, the Visibility Calculator obtains a predetermined SQL statement from the field SQL_STATEMENT and executes it.
- the SQL statement is a query that select one or more rows of the Docking Object that, for example, correspond to the docking object for which the Visibility Calculator was invoked.
- This SQL statement accesses a table S_DOC_QUOTE that contains all sales quotes.
- the WHERE clause specifies retrieval of all rows where the Opportunity ID of the row is equal to the Row-ID of the opportunity for which visibility is being calculated.
- the Visibility manager retrieves the specified Row-Ids, thereby identifying the rows of the S_DOC_QUOTE table whose visibility must checked.
- the Visibility Calculator proceeds to step 225 .
- the Visibility Calculator recursively invokes itself to determine visibility of the related docking object.
- the recursively invoked Visibility Calculator operates in the same manner as the Visibility Calculator as called from the Log Manager 9 , including the capability to further recursively invoke itself.
- the recursive call concludes, it returns a visibility indicator for the related Docking Object, and control proceeds to step 227 .
- the Visibility calculator determines whether the related Docking Object was determined to have been visible.
- step 213 the Visibility Calculator proceeds to step 213 to mark the originally current Docking Object as visible, and then to step 228 to synchronize the database and then to step 229 to exit. If the related Docking Object was not determined to be visible, control proceeds to step 215 to determine whether additional visibility rules remain to be assessed.
- the Visibility Calculator in conjunction with the Log Manager is therefore able to determine what subset of update transaction data is required to be routed to any particular node. This operation serves to reduce the transmission of unneeded data from the Central Computer 1 to the various nodes such as nodes 21 - a , 21 - b and 21 - c that utilize partially replicated databases, and to reduce the system resources such as disk space needed to store, and the CPU time needed to process, what would otherwise be required to maintain a fully replicated database on each remote node.
- the docking facility of the present invention also permits the distribution of software upgrades and related database schema. This provides an easy process to allow administrators to notify remote users of the existence of software upgrades and to distribute software upgrades to remote users. It provides an easy process for remote users to receive notification of software upgrades and to apply the software upgrade. It provides a means to associate a software upgrade with a remote schema upgrade so that the software upgrade is not applied before the remote schema upgrade. It provides a means for a remote user to provide feedback regarding a successful or unsuccessful completion of the software upgrade to the administrator.
- a copy of the upgrade package files and an upgrade database table are created on the server ( 1 ).
- a pointer is created in the client's ( 21 a , 21 b , 21 c ) file on the server ( 1 ). This pointer points to the upgrade package files on the server ( 1 );
- the upgrade files are made active, and the upgrade database table is scanned when a client ( 21 a , 21 b , 21 c ) docks.
- the upgrade is copied to the client ( 21 a , 21 b , 21 c ) if the client ( 21 a , 21 b , 21 c ) has not received the upgrade. At this point the upgrade may be invoked at the client ( 21 a , 21 b , 21 c ).
- the upgrade can be invoked at any point during a docking session, for example, at the beginning of a client ( 21 a , 21 b , 21 c ) session., or, and most preferably, at the end of a client ( 21 a , 21 b , 21 c ) session.
- the upgrade can be invoked at the client user's option, or at the server's option, that is, by forced downloading as will be described hereinbelow.
- One way of implementing the invention is to create a docking item file type to scan the upgrade database table when the client ( 21 a , 21 b , 21 c ) docks to thereby determine the status of an upgrade with respect to the client ( 21 a , 21 b , 21 c ).
- the computer readable program in the program product article of manufacture contains computer readable program code means for causing a computer to effect creating a copy of the upgrade package files on the server ( 1 ), creating an upgrade database table on the server ( 1 ); creating a pointer in the client's ( 21 a , 21 b , 21 c ) file on the server ( 1 ) pointing to the upgrade package files on the server ( 1 ), making the upgrade active, scanning the upgrade database table when a client ( 21 a , 21 b , 21 c ) docks to determine the status of an upgrade with respect to the client ( 21 a , 21 b , 21 c ), copying the upgrade to a client ( 21 a , 21 b , 21 c ) if the client ( 21 a , 21 b , 21 c ) has not received the upgrade, and invoking the upgrade at the client ( 21 a , 21 b , 21 c ).
- our invention may be implemented as a program product in the form of a program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for of upgrading a software application from upgrade package files in a server ( 1 ) to a client ( 21 a , 21 b , 21 c ) said method steps comprising creating a copy of the upgrade package files on the server ( 1 ), creating an upgrade database table on the server ( 1 ); creating a pointer in the client's ( 21 a , 21 b , 21 c ) file on the server ( 1 ) pointing to the upgrade package files on the server ( 1 ), making the upgrade active, scanning the upgrade database table when a client ( 21 a , 21 b , 21 c ) docks to determine the status of an upgrade with respect to the client ( 21 a , 21 b , 21 c ), copying the upgrade to a client ( 21 a , 21 b , 21 c ), copying the upgrade
- the integrated update works as follows. At the end of a normal docking session, the user is prompted with the information regarding the availability of a software upgrade. The user has the option to download the software upgrade or to defer and download the software upgrade later. This can be overridden by the system administrator, who has the ability to mark the file as a force download. In such a case, the user is not prompted to download the file; instead, the file is downloaded without input from the user. The user is prompted using a message box that has the ability to time out.
- the installation component is invoked and the database application is closed. The installation component then guides the user through the necessary steps needed to apply the software.
- the system administrator uses a dialog to specify the association of files, messages and schema upgrades for an upgrade package.
- the dialog includes a master section and a detail section.
- the master section allows for the creation of a header record that names the upgrade package and specifies some general attributes regarding the upgrade.
- the detail section associates software upgrade files, messages and schema upgrades.
- the attributes of the master record include the name of the upgrade package; the schema version of the database after the upgrade is applied; a message supplied to users to view prior to downloading the upgrade; a message to be displayed when the upgrade is applied; a download attribute indicating how the file must be downloaded, e.g., whether the file must be downloaded immediately or whether it may be deferred by the user; an application attribute indicating how the upgrade may be applied, e.g., whether the upgrade must be applied immediately, may be deferred by the user, or must be deferred pending a corresponding upgrade of a corresponding schema or software upgrade; and a description.
- the attributes of the detail record include a record type indicating whether the file is a message, a software upgrade, etc., and the name of the file.
- Upgrades are denoted by a record in an upgrade table in the database. Once a record is created in the upgrade table and the associated upgrade package is made active, Log Manager routes this information using the previously described docking mechanisms to remote users by creating an entry in the users' server.ts files. This entry points to a global upgrade table of contents (TOC) file.
- TOC global upgrade table of contents
- a single TOC file serves all docking users per application server installation.
- the upgrade TOC file contains the detailed information regarding the upgrade package. In this embodiment, only one upgrade package is active at a given time.
- the docking client scans the server.ts file for the existence of upgrade entries.
- the upgrade files be downloaded immediately or a message is displayed to the user.
- the user optionally has have the option either download the files during the current docking session or defer download until a later docking session.
- the installation component may be invoked automatically or the user may defer applying the upgrade. If the software upgrade is associated with a schema upgrade, then after the schema upgrade has been applied, the status of software upgrade files is checked to verify that all files associated with the upgrade have been downloaded. Any files not yet downloaded will be downloaded, making a connection to the application server if necessary. The software upgrade will then be invoked by the installation component.
- the file types are represented by the field UTLTocFileType.
- a file type of UTLTocFileTOCUpg indicates the Upgrade TOC file
- a file type of UTLTocFileUpgrade indicates a file that is a constituent part of an upgrade.
- a file type of UTLTocFileMessage indicates a file containing a message to be displayed to the user.
- the upgrade is represented to the user as a new dock item type, named CSSDockUpg.
- the CSSDockUpg class is derived from the CSSDockItem class.
- the CSSDockUpg dock item type is created. When executed, this class examines the server.ts file for an entry type of UTLTocFileTOCUpg. If found, either the message specified by the entry pre-download message will be displayed to the user using a time-out dialog box at the end of the docking session or the files will be downloaded immediately depending on the attributes of the entry type UTLTocFileTOCUpg.
- the apply message from the upgrade TOC file is displayed to the user at the end of the docking session.
- the installation component is invoked by the mobile client.
- the installation component is invoked. If the user defers application of the upgrade, then each time the user issues docks to the headquarters server, the docking client looks for the upgrade TOC file in the upgrade directory on the client machine. If the file exists, the apply message is displayed to the user.
- the upgrade TOC file is stored locally on the client. This file will then be examined after the schema upgrade process has completed.
- the master copy of the upgrade package files is placed on the file server.
- Log Manager process When a Log Manager process is processing a user and encounters the transaction that makes the upgrade package active, Log Manager copies these files to the local application server upgrade directory if the files do not already exist. Log Manager also creates the upgrade TOC file in this directory if the TOC file does not already exist.
- a record in the docking transaction log is created. This record will cause the log preprocessor to create the global upgrade TOC file. The contents of the file are inserted into a text column of the upgrade package. When the log router is executing for a particular user, this record will cause the log router to create an entry in the user's server.ts file, which that points to the global upgrade TOC file. The log router also ensures that the global upgrade TOC file exists in a predetermined directory. If the file exists, the log router reads the text column of the upgrade package that contains the contents of the TOC file and creates the global upgrade TOC file. Alternatively, the log router may read the text column and create an upgrade TOC file for each user. This would prevent more than one log router executable from creating the global upgrade TOC file.
- a schema upgrade will require a corresponding software upgrade in order for the schema to function properly. This may occur, for example, when the vendor supplies a new software-schema pair. A customer cannot cause a software version conflict with the ability for dbinit/data merge to apply the schema changes. If schema upgrade that requires a corresponding software upgrade is to be applied, the software upgrade must be applied first, because it is the new software that provides support for the schema upgrade.
- An example of this scenario is when the vendor ships new software and a new version of the database.
- the system administrator packages the software and makes it available for download by the user.
- the system administrator then applies the database upgrade to the central database.
- a remote user docks and is informed that the central database has been updated, and that the user's docking operation is limited to downloading changes to the database; that is, the user is not permitted to upload transactions until his own partially replicated database has been upgraded to match the central database schema.
- the user then downloads the database upgrade files corresponding to the upgrade installed on the central database.
- the installation component is invoked (either by the client-side software upon detecting the upgrade condition, or expressly invoked by the user, depending on the upgrade file's attributes).
- the installation component opens the database upgrade files and contains a checksum value for the upgrade file set. The checksum is compared against a value in the user's configuration file that uniquely identifies the user's software level. If the checksum value is different, then the client software does not have the ability to apply the schema changes. The schema changes will be deferred until the user separately upgrades his or her software level.
- a checksum may also be included in the DX files that represent transactions.
- the data merge component verifies the checksum associated with the transaction against the checksum in the configuration file. If the checksums do not match, the application of the DX file is deferred. This prevents a user from inadvertently applying changes that cannot be supported by the software.
- Input Parameters • LaptopNodeId - node_id of the destination laptop • UserTxnLogFileName - full path of the file where txns will be written • MaxBatchTxns - number of txns between commits and updates to the S_DOCK_STATUS table • MaxTxns - number of txns to process in this session. Use this parameter to limit processing.
- PKTable is a Member Table of the Docking Object THEN - - If there's more than one FK, then there is more than one path - - out of the current table.
- PKTable PrimaryTable THEN RETURN; ELSE AddPKTable (PKTable, DockingObject, GenStmt, StmtNum); END IF; - - Only count FKs to other member tables in the same Docking Object ++numFKs; END IF; END LOOP; RETURN; ⁇ Process Visibility Events - - Download an Object Instance to a Laptop - - This function also downloads all Related Docking Object instances.
- BOOL DownloadObjectInstance (LaptopNodeId, ObjectName, PrimaryRowId) ⁇ - - Check if the object instance is already downloaded to the laptop Find the object instance in the S_DOBJ_INST table IF exists on laptop THEN return TRUE; END IF; - - Register object instance in S_DOBJ_INST table - - Write Download Object records to the Txn Log FOR each member table of the docking object LOOP Generate SQL select statement to download records Write each retrieved record to the User Txn Log file END LOOP; - - Download records for Parent Object instances FOR each RelatedDockingObject LOOP Run ParameterSQL to get newPrimaryId of RelatedDockingObjects FOR each newPrimaryId retrieved LOOP - - Check if the instance of the object is visible to the laptop user CheckObjectVisibility (LaptopNodeId, ObjectName, PrimaryRowId) IF visible THEN DownloadObjectInstance (Lap
- BOOL RemoveObjectInstance (LaptopNodeId, ObjectName, PrimaryRowId) ⁇ - - Check if the object instance is already downloaded to the laptop Find the object instance in the S_DOBJ_INST table IF does not exist on laptop THEN return TRUE; END IF; - - Delete the object instance from S_DOBJ_INST table - - Write Remove Object records to the Txn Log FOR each member table of the docking object LOOP Generate SQL select statement to get records to delete Write each retrieved record to the User Txn Log file END LOOP; - - Remove for Parent Object instances FOR each RelatedDockingObject LOOP Run ParameterSQL to get newPrimaryId of RelatedDockingObjects FOR each newPrimaryId retrieved LOOP - - Check if the instance of the object is visible to the laptop user CheckObjectVisibility (LaptopNodeId, ObjectName, PrimaryRowId) IF not visible THEN Remove
Abstract
Upgrading a software application from one or more upgrade package files in a server (1) to a client (21 a , 21 b , 21 c). According to this method a copy of the upgrade package files and an upgrade database table are created on the server (1). A pointer is created in the client's (21 a , 21 b , 21 c) file on the server (1). This pointer points to the upgrade package files on the server (1); In invoking the upgrade the, the upgrade files are made active, and the upgrade database table is scanned when a client (21 a , 21 b , 21 c) docks. This is to determine the status of an upgrade with respect to the particular client (21 a , 21 b , 21 c). The upgrade is copied to the client (21 a , 21 b , 21 c) if the client (21 a , 21 b , 21 c) has not received the upgrade. At this point the upgrade may be invoked at the client (21 a , 21 b , 21 c). Also disclosed is a program product carrying code for the upgrade method.
Description
- I. Technical Field
- This invention relates to a system and method for providing updates to a network of partially replicated relational database systems, and, more particularly, for providing an efficient means for computing the visibility to a client on the network of a transaction processed against the database.
- II. Background
- Relational databases are a commonly-employed data structure for representing data in a business or other environment. A relational database represents data in the form of a collection of two-dimensional tables. Each table comprises a series of cells arranged in rows and columns. Typically, a row in a table represents a particular observation. A column represents either a data field or a pointer to a row in another table.
- For example, a database describing an organizational structure may have one table to describe each position in the organization, and another table to describe each employee in the organization. The employee table may include information specific to the employee, such as name, employee number, age, salary, etc. The position table may include information specific to the position, such as the position title (“salesman”, “vice president”, etc.), a salary range, and the like. The tables may be related by, for example, providing in each row of the employee table a pointer to a particular row in the position table, coordinated so that, for each row in the employee table, there is a pointer to the particular row in the position table that describes that employee's position. A relational database management system (RDBMS) supports “joining” these tables in response to a query from a user, so that the user making a query about, for example, a particular employee, may be provided with a report of the selected employee, including not only the information in the employee table, but also the information in the related position table.
- Relational databases may be much more complex than this example, with several tables and a multiplicity of relations among them.
- With the widespread use of inexpensive portable computers, it is advantageous to replicate a database onto a portable computer for reference at locations remote from the central computer. The replicated database may then be referenced by the user of the portable computer, without requiring reference to the main database, which may be maintained at a central location inconvenient to the user of the portable computer. However, there are a number of difficulties with the use of a replicated database.
- One disadvantage is that a full copy of the central database may require more data storage than is desired or economical. For example, a salesman working in the field may need to refer to the database for information regarding sales opportunities in his sales area, but have no need to refer to any information regarding sales opportunities outside of his area. One possible approach to reduce the amount of required data storage is to simply replicate only that portion of the database that is needed by the user. However, this approach does not recognize that the criteria to determine which portions of the data are required is likely to vary over time. For example, the salesman may have a new city added to his territory. Under conventional approaches, the salesman would need to re-replicate his local copy of the database, this time selecting data including the added city. Such a practice is inconvenient, subject to error, and time-consuming.
- A further disadvantage to a replicated database is the difficulties encountered in attempting to update data using the replicated copy. A change made to the replicated database is not made to the central database, leading to a discrepancy between the information that is stored in the replicated copy of the database and the information that is stored in the central database. Although it is possible to journal modifications made to the replicated copy and apply an identical modification to the central database, one problem that this approach faces is the possibility of colliding updates; that is, where a user of a replicated copy makes a change to data that is also changed by a user of the central copy or by the user of another replicated copy.
- It is therefore desirable to provide a capability to maintain one or more partially-replicated copies of a central database, in such a way that the degree of replication may be easily changed without requiring a refresh of the entire replicated database, and that permits updates to be coordinated among users of the central database and users of the partially replicated databases.
- The present invention is directed to a method of maintaining a partially replicated database in such a way that updates made to a central database, or to another partially replicated database, are selectively propagated to the partially replicated database. Updates are propagated to a partially replicated database if the owner of the partially replicated database is deemed to have visibility to the data being updated. Visibility is determined by use of predetermined rules stored in a rules database. In one aspect of the invention, the stored rules are assessed against data content of various tables that make up a logical entity, known as a docking object, that is being updated.
- In another aspect of the invention, the stored rules are assessed against data content of one or more docking objects that are not necessarily updated, but that are related to a docking object being updated. In one embodiment, the visibility attributes of the related docking objects are recursively determined.
- In yet another aspect of the invention, changes in visibility are determined to enable the central computer to direct the nodes to insert the docking object into its partially replicated database. Such changes in visibility are determined so as to enable the central computer to direct a node to remove a docking object from its partially replicated database.
- In a further aspect of the invention, the predetermined rules are in declarative form and specify visibility of data based upon structure of the data without reference to data content.
- In still another aspect of the invention, the levels of the database schema and the database access software are synchronized to prevent an updated schema from being processed by a back-level version of software.
- A still further aspect of our invention is a method of upgrading a software application from one or more upgrade package files in a server (1) to a client (21 a, 21 b, 21 c). According to this method a copy of the upgrade package files and an upgrade database table are created on the server (1). A pointer is created in the client's (21 a, 21 b, 21 c) file on the server (1). This pointer points to the upgrade package files on the server (1). In invoking the upgrade the, the upgrade files are made active, and the upgrade database table is scanned when a client (21 a, 21 b, 21 c) docks. This is to determine the status of an upgrade with respect to the particular client (21 a, 21 b, 21 c). The upgrade is copied to the client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade. At this point the upgrade may be invoked at the client (21 a, 21 b, 21 c).
- A still further aspect of our invention is a program product article of manufacture encompassing a computer usable medium with computer program code embodied therein for causing the upgrading of a software application from upgrade package files in a server (1) to a client (21 a, 21 b, 21 c). The computer readable program in the program product article of manufacture contains computer readable program code means for causing a computer to effect creating a copy of the upgrade package files on the server (1), creating an upgrade database table on the server (1); creating a pointer in the client's (21 a, 21 b, 21 c) file on the server (1) pointing to the upgrade package files on the server (1), making the upgrade active, scanning the upgrade database table when a client (21 a, 21 b, 21 c) docks to determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c), copying the upgrade to a client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade, and invoking the upgrade at the client (21 a, 21 b, 21 c).
- A even further aspect of our invention is a program product in the form of a program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for of upgrading a software application from upgrade package files in a server (1) to a client (21 a, 21 b, 21 c) said method steps comprising creating a copy of the upgrade package files on the server (1), creating an upgrade database table on the server (1); creating a pointer in the client's (21 a, 21 b, 21 c) file on the server (1) pointing to the upgrade package files on the server (1), making the upgrade active, scanning the upgrade database table when a client (21 a, 21 b, 21 c) docks to determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c), copying the upgrade to a client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade, and invoking the upgrade at the client (21 a, 21 b, 21 c).
- FIG. 1 depicts an overview of the operation of one embodiment of the present invention.
- FIG. 2 depicts a database schema that shows the relationship of the various components that make up a Docking Object.
- FIG. 3 depicts steps performed by an update manager to update a database.
- FIG. 4 depicts steps performed by a Docking Manager to transmit and/or receive one or more transaction logs.
- FIG. 5 depicts the steps performed by a merge processor to merge transaction log records into an existing database.
- FIG. 6 depicts the steps performed by a log manager to prepare a partial transaction log.
- FIG. 7 depicts the steps performed by a visibility calculator for calculating visibility for a docking object as invoked by a log manager.
- FIG. 8 depicts the steps performed to synchronize a partially replicated database in response to a change in data visibility.
- Overview
- FIG. 1 depicts an overview of the operation of one embodiment of the present invention. FIG. 1 depicts a central computer system1 and three remote computer systems (or “nodes”) 21-a, 21-b, and 21-c. Each of nodes 21-a, 21-b and 21-c are depicted in various states of communication with central computer system 1, as will be more fully explained. Central computer system 1 includes a
central database 3, adocking manager 5, amerge processor 7 and alog manager 9. Central computer system 1 additionally optionally includesupdate manager 11 responsive touser input 13. - Node21-a is a remote computer system, such as a mobile client such as a laptop computer. Node 21-a includes a partially replicated remote database 23-a, update manager 31-a responsive to user input 33-a, docking manager 25-a and merge manager 27-a. In operation, update manager is responsive to user input 33-a to make changes to remote database 23-a as directed by the operator of node 21-a. Updates made are recorded, or journaled, in node update log 35-a.
- At some point at the convenience of the operator of node21-a, node docking manager 35-a is activated, and enters into communication with
central docking manager 5. Update log 35-a is taken as input by node docking manager 25-a, and provided tocentral docking manager 5.Central docking manager 5 creates a receivednode update log 19, which contains all the information that had been recorded in update log 35-a. Optionally, partial log 17-a is taken as input bycentral docking manager 5 and provided to node docking manager 25-a, as more fully described herein. - At some point in time, at the convenience of the operator of central computer system1, merge
processor 7 is activated.Merge processor 7 takes as input receivednode update log 19, and applies the updates described therein tocentral database 3. In the process of applying the updates from receivednode update log 19, merge processor journals the updates applied tocentral update log 15. Optionally,update manager 11, responsive to user input 12 makes additional changed tocentral database 3 as directed by the operator of central computer system 1. The updates made byupdate manager 11 are additionally journaled incentral update log 15. - At some point in time, at the convenience of the operator of central computer system1,
log manager 9 is activated.Log manager 9 takes as inputcentral update log 15 and produces as output a set of partial logs 17-a, 17-b and 17-c according to visibility rules as will be further described herein. Each of partial logs 17-a, 17-b and 17-c corresponds to one of nodes 21-a, 21-b and 21-c. When a node docking manager such as node docking manager 25-a enters into communication withcentral docking manager 5 and optionally requests transmission of its corresponding partial log,central docking manager 5 takes as input the appropriate partial log, such as partial log 17-a, and presents it to node docking manager 25-a. Node docking manager 25-a then replicates partial log 17-a as merge log 37-a. - At some point in the future, at the convenience of the operator of node21-a, merge processor 27-a is activated. Merge processor 27-a takes as input merge log 37-a, and applies the updates described therein to partially replicated database 23-a.
- In addition to node21-a, FIG. 1 also depicts two additional nodes 21-b and 21-c. Node 21-b is depicted in communication with central computer 1. However, unlike node 21-a, the operator of node 21-b has requested only to send his updates to central computer system 1, and has not requested to be presented with changes made elsewhere to be made to his partially replicated database 23-b. This may be, for example, if the operator has an urgent update that must be made as soon as possible, but does not have the time to receive updates from other nodes. Accordingly, FIG. 1 shows only transmission of node update log 35-a from node docking manager 25-b to
central docking manager 5, and no transmission fromcentral docking manager 5 to node docking manager 25-b. Accordingly, the merge manager for node 21-b is not activated and is not shown. - Likewise, node21-c is depicted as not in communication with central computer system 1. Accordingly, the docking manager for node 21-c is not activated and is not shown.
- By the cycle described above, updates made by each of nodes21-a, 21-b and 21-c are presented to central computer system 1, permitting
central database 3 to be updated accordingly. In addition, each of the updates made by each of the nodes 21-a, 21-b and 21-c, as well as updates made on central computer system 1, are routed back to each of nodes 21-a, 21-b, and 21-c, thereby keeping each of partial databases 23-a, 23-b and 23-c in synchronization with each other and withcentral database 3. - Database Structure
- The synchronization of
central database 3 with node databases 23-a, 23-b and 23-c is performed using a construct called a Docking Object. A Docking Object consists of Member Tables (including one Primary Table), Visibility Rules, Visibility Events, and related Docking Objects. - A Member Table is a table of the relational database that makes up a docking object. When a docking object is propagated from
central database 3 to one of node databases 23-a, 23-b or 23-c, the propagation takes the form of an insertion into each of the Member Tables associated with the particular docking object. Similarly, when a docking object is scheduled to be removed from a database, that removal consists of deleting records from the member tables associated with the docking object. For example, a docking object that represents a sales opportunity may include tables that represent the opportunity itself (e.g., named “S_OPTY”), the product whose sale is represented by the opportunity (e.g., named “S_OPTY_PROD”), the contact for the opportunity (e.g., named “S_OPTY_CONTACT”), etc. Each of these tables is said to be a member table of the “Opportunity Docking Object.” - A Primary Table is a Member Table that controls whether a particular instance of a Docking Object is visible to a particular node. The Primary Table has a Primary Row-ID value that is used to identify a row of the Primary Table being updated, deleted or inserted. For example, the “Opportunity Docking Object” may have as a primary table the table S_OPTY. The row-id of that table, i.e., S_OPTY.row_id, is the Primary Row-ID for the Opportunity Docking Object.
- A Visibility Rule is a criterion that determines whether a particular instance of a Docking Object is “visible” to a particular node21. If a Docking Object is visible to a particular node, that node will receive updates for data in the Docking Object. Visibility Rules are of two types, depending on the field RULE_TYPE. A Visibility Rule with a RULE TYPE of “R” is referred to as an SQL Rule. An SQL Rule includes a set of Structured Query Language (SQL) statements that is evaluated to determine if any data meeting the criteria specified in the SQL statements exists in the Docking Object. If so, the Docking Object is visible to the node. A Visibility Rule with a RULE_TYPE of “O” is referred to as a Docking Object Rule. A Docking Object Rule specifies another Docking Object to be queried for visibility. If the specified Docking Object is visible, then the Docking Object pointing to it is also visible.
- A Related Docking Object is a Docking Object that is propagated or deleted when the Docking Object under consideration is propagated or deleted. For example, an Opportunity Docking Object may have related Docking Objects representing the sales contacts, the organizations, the products to be sold, and the activities needed to pursue the opportunity. When an Opportunity Docking Object is propagated from
Central Database 3 to one ofnode databases 23, the related docking objects are also propagated. - FIG. 2 depicts a database schema that shows the relationship of the various components that make up a Docking Object. The schema is a meta-database, in that it does not describe the data being accessed in the database. Rather, the schema is a separate database that defines the structure of the database being accessed. That is, it is a database comprising tables that describe the relationships and data contexts of another database.
- Each of the tables shown in FIG. 2 is a table in a relational database, and as such is in row-column form. Many columns represent fields that are common to all the illustrated tables. Such fields include for example, a ROW_ID to identify a particular row in the table, as well as fields to tack the date and time that a row was created and last modified, and the identity of the user who created or modified the row. In addition, each table contains fields specific to that table, and which are described in detail below.
-
Table S_DOBJ 61 describes the Docking Objects in an application.Table S_DOBJ 61 includes the fields OBJ_NAME and PRIMARY_TABLE_ID. Field OBJ_NAME defines the name of the Docking Object being described. Field PRIMARY_TABLE_ID is used to identify the primary table associated with this Docking Object. -
Table S_DOBJ_INST 63 describes whether a particular instance of a Docking Object, described bytable S_DOBJ 61, is present on a particular node's database.Table S_DOBJ_INST 63 includes the fields NODE_ID, DOBJ_ID and PR_TBL_ROW_ID. Field NODE_ID points to a particular node table 65. Field DOBJ_ID points to the Docking Object to which the Docking Object instance applies. Field PR_TBL_ROW_ID is used to select a particular row in the Primary Table of the Docking Object. This value identifies the Docking Object instance. -
Table S_REL_DOBJ 67 describes the related Docking Objects of a particular Docking Object, described bytable S_DOBJ 61.Table S_REL_DOBJ 67 includes the fields DOBJ_ID, REL_DOBJ_ID, and SQL_STATEMENT. Field DOBJ_ID identifies the Docking Object that owns a particular related Docking Object. Field REL_DOBJ_ID identifies the related Docking Object that is owned by the Docking Object identified by DOBJ_ID. Field SQL_STATEMENT is an SQL statement that may be executed to obtain the Primary ID value of the related Docking Object. -
Table S_DOBJ_TBL 69 describes the member tables of a particular Docking Object, described bytable S_DOBJ 61.Table S_DOBJ_TBL 69 includes the fields DOBJ_ID, TBL_ID, and VIS_EVENT_FLG. Field DOBJ_ID identifies the Docking Object that contains the member table described by the row. Field TBL_ID identifies the particular table in the database that is the member table described by the row. Field VIS_EVENT_FLG is a flag that indicates whether a change to this Docking Object can result in a visibility event. A value of “Y” indicates that a change can result in a visibility event; a value of “N” indicates that it cannot. -
Table S_DOBJ_VIS_RULE 71 contains the visibility rules associated with a particular Docking Object.S_DOBJ_VIS_RULE 71 contains the fields DOBJ_ID, RULE SEQUENCE, RULE_TYPE, SQL_STATEMENT and CHECK_DOBJ_ID. Field DOBJ_ID identifies the Docking Object with which a particular visibility rule is associated. Field RULE_SEQUENCE is a sequence number that indicates the sequence, relative to other visibility rules intable S_DOBJ_VIS_RULE 71, in which the particular visibility rule should be run. RULE_TYPE specifies whether the particular visibility rule is of type “R,” indicating an SQL visibility rule or of type “O,” indicating a Docking Object visibility rule. - If RULE_TYPE is equal to “R,” field CHECK_DOBJ_ID is not meaningful, and field SQL_STATEMENT contains an SQL statement that is evaluated using the Primary ROW-ID of the primary table associated with this Docking Object and a particular Node21. If the SQL statement returns any records, the Docking Object is deemed to be visible to the Node 21 for which visibility is being determined.
- If RULE_TYPE is equal to “O,” both field CHECK_DOBJ_ID and field SQL_STATEMENT are meaningful. Field CHECK_DOBJ_ID specifies a docking object whose visibility should be determined. If the specified docking object is deemed to be visible, then the docking object associated with the visibility rule is also visible. Field SQL_STATEMENT contains a SQL statement that, when executed, returns the Row-ID of the docking object identified by CHECK_DOBJ_ID that corresponds to the docking object instance associated with the visibility rule.
-
Table S_APP_TBL 73 is an Application Table that describes all the tables used in a particular application. It is pointed to bytable S_DOBJ_TBL 69 for each member table in a docking object, and by table S_DOBJ for the primary table in a docking object.S_APP_TBL 73 points to tableS_APP_COL 75, which is an Application Column Table that describes the columns of data in a particular application.S_APP_TBL 73 points to tableS_APP_COL 75 directly through a primary key and indirectly through such means as a Foreign Key Column Table 81, User Key Column Table 83, and Column Group Table 85. The relationship of an Application Table, Application Column Table, Foreign Key Column Table, User Key Column Table and Column Group Table are well known in the art and are not further described. - Update Processing
- FIG. 3 depicts steps performed by an
update manager 31 such as update manager 31-a, 31-b or 31-c in updating a database, such as a node database 23-a, 23-b or 23-c, responsive to user input. Execution ofupdate manager 31 begins instep 101. Instep 103, theupdate manager 31 accepts from theuser input 33 in the form of a command requesting that the data indatabase 23 be altered. The request may be in the form of a request to delete a row of a table, to add a row to a table, or to change the value of a cell at a particular column of a particular row in a table. Instep 105, using a well-known means, theupdate manager 31 applies the requested update todatabase 23. Instep 107, theupdate manager 31 creates a log record describing the update and writes it to updatelog 35. - The contents of a log record describe the update made. Each log record indicates the node identifier of the node making the update, an identification of the table being updated, and an identification of the type of update being made, i.e., an insertion of a new row, a deletion of an existing row, or an update to an existing row. For an insertion, the log record additionally includes an identifier of the row being inserted, including its primary key and the values of the other columns in the row. For a deletion, the log record identifies the primary key of the row being deleted. For an update, the log record identifies the primary key of the row being updated, the column within the row being updated, the old value of the cell at the addressed row and column, and the new value of the cell.
- After writing a log record in
step 107, the update processor exits for this update. The foregoing description of the update processing preferably includes additional steps not material to the present invention, for example, to assure authorization of the user to make the update, to stage and commit the write to the database to allow for rollback in the event of software or hardware failure, and the like. These steps are well-known in the art and are not described further. - An
update manager 11 executing in central computer system I operates in an analogous manner, except that it updatescentral database 3 and writes its log records tocentral update log 11. - Docking Processing
- FIG. 4 depicts steps performed by a
Docking Manager 25 such as Docking Manager 25-a, 25-b or 25-c to transmit and/or receive one or more transaction logs. DockingManager 25 is invoked by the user of a remote node such as node 21-a, 21-b or 21-c, whereby the user requests that the node dock with central computer 1 to upload an update log such as update log 35-a to central computer 1, to download a partial log such as partial log 17-a, or both. Execution ofDocking Manager 25 begins instep 121. Instep 123,Docking Manager 25 connects with central computer 1 under the control ofCentral Docking Manager 5. This connection can be any connection that enables data exchange. It is anticipated that the most common form of a connection is a telephone line used in conjunction with a modem, but other forms of data connection, such as a Local Area Network or a TCP/IP connection may also be used. Step 125 checks to see whether the user has requested that node update log 35-a be uploaded to the Central Computer 1. If so, execution proceeds to step 127. If not, step 127 is skipped and control is given to step 129. Instep 127,Docking Manager 25 uploads its update log to central computer 1. The upload may be accomplished with any known file transfer means, such as XMODEM, ZMODEM, KERMIT, FTP, ASCII transfer, or any other method of transmitting data. Instep 129,Docking Manager 25 checks to see whether the user has requested that a partial log such as partial log 17-a be downloaded from Central Computer 1. If so, execution proceeds to step 131. If not, step 131 is skipped and control is given to step 133. Instep 131,Docking Manager 25 downloads its partial log from central computer 1. The download may be accomplished with any known file transfer means, such as XMODEM, ZMODEM, KERMIT, FTP, ASCII transfer, or any other method of transmitting data. Instep 133, having completed the requested data transfer,Docking Manager 25 exits. - Merge Processing
- Merge processing is performed by a processor such as node merge processor27-a, 27-b, or 27-c, or
central merge processor 7. The merge process serves to update its associated database with a transaction that has been entered by a user of a computer remote from the computer where merge processing is being performed. Merge processing is analogous to update processing and is similar in form to update processing as previously disclosed with reference to FIG. 3, with three differences. First, the input to a merge processor is not an update entered directly by a user, but rather is a log file that is obtained from a computer remote from the computer where the merge is executing. A second difference is that, as shown by in FIG. 1, merge processing does not produce a log when performed at a node. The function of a log on a node is to record a transaction for propagation to Central Computer system 1 and thence to other nodes as required. A transaction that is the subject of a merge in a node has been communicated to Central Computer System 1, and there is no need to re-communicate it. - A third difference is that merge processing must be capable of detecting and resolving multiple conflicting transactions. For example, assume that a field contains the value “Keith Palmer.” Assume further that a user at node27-a enters a transaction to update that field to “Carl Lake,” and a user at node 27-b enters a transaction to update the same field to “Greg Emerson.” Without collision detection, data among various nodes may become corrupt. When the transaction for user 27-a is merged, the field is updated from “Keith Palmer” to “Carl Lake.” Without collision handling, when the transaction for node 27-b is merged, the field would be updated to “Greg Emerson,” and the central database would then be out of synch with the database of node 27-a. Furthermore, when merge processing is performed on each of nodes 27-a and 27-b, each node will update its database with the other's transactions, leaving at least one node out of synch with the other node and with central database.
- Therefore, merge processing must also have a means of detecting collisions and correcting them. In the above example, a simple way to detect and correct a collision is to compare the value in the database to the value that the merge log reflects as being the previous value in the node database. If the two values do not match,
Merge processor 7 may reject the transaction and generate a corrective transaction to be sent to the node from which the conflicting transaction originated. In the above example, when the transaction for node 27-b was presented to mergeprocessor 7, mergeprocessor 7 would compare “Keith Palmer,” the prior value of the field as recorded by node 27-b to “Carl Lake,” the present value of the field as recorded incentral database 3. Detecting the mismatch, mergeprocessor 7 may then generate a transaction to change the value “Greg Emerson” to “Carl Lake,” and write that transaction to updatelog 15. In a subsequent docking operation, that transaction would be routed back to node 27-b to bring its database 23-b in synch with the other databases. - The above is one example of a collision and a resulting corrective action. Other types of collisions include, for example, an update to a row that has previously been deleted, inserting a row that has previously been inserted, and the like. Merge processing must detect and correct each of these collisions. This may be performed using any of a number of well-known methods, and is not discussed further.
- FIG. 5 depicts the steps performed by merge processor such as
central merge processor 7. Although it depicts mergeprocessor 7 writing tocentral database 3 and totransaction log 15, it is equally representative of a node merge processor such as node merge processor 27-a, 27-b or 27-c updating a node database 23-a, 23-b or 23-c. Merge processing begins atstep 141. Instep 143, mergeprocessor 7 finds the first unprocessed transaction on receivedlog 19. Instep 147, mergeprocessor 7 selects a transaction from receivedlog 19. Instep 149, mergeprocessor 149 attempts to updatedatabase 3 according to the transaction selected instep 147. Instep 151, mergeprocessor 7 determines whether the database update ofstep 149 failed due to a collision. If so, merge processor proceeds to step 153, which generates a corrective transaction. Following the generation of the corrective transaction, the merge processor returns to step 149 and again attempts to updatedatabase 3. If no collision was detected instep 151, execution proceeds to step 157. Instep 157, merge processing checks to see if it is executing on central computer 1. If so,step 155 is executed to journal the transaction to log 15. In any case, either ifstep 157 determines that the merge processing is being performed on a node or afterstep 155, execution proceeds to step 159. Step 159 checks to see if any transactions remain to be processed fromlog 19. If so, execution repeats fromstep 147, where the next transaction is selected. If not, merge processing exits instep 161. - Log Management
- FIG. 6 depicts the steps to be performed by
log manager 9 to prepare a partial transaction log such as partial transaction log 17-a, 17-b, or 17-c. The procedure depicted in FIG. 6 is executed for each node available to dock with central computer system 1.Log manager 9 begins execution instep 171. Instep 173,Log Manager 9 finds the first unprocessed transaction for the node whose partial transaction log is being prepared. Instep 175,log manager 9 selects a transaction for processing. Instep 177,log manager 9 checks to see whether the selected transaction originated on the same node for which processing is being performed. If so, there is no need to route the transaction back to the node, and control proceeds to step 179. Step 179 checks to see whether there are any transactions remaining to be processed. If so, control is given again to step 175. If not, control passes to step 189, which records the last transaction that was processed for this node, and then exits atstep 191. If the transaction originates in other than the same node as the node for which processing is being performed, control is given to step 181. Step 181 calls a visibility calculator to determine whether the selected transaction is visible to the node being processed. The Visibility calculator routine is described in detail further herein. Instep 183, mergeprocessor 9 checks to see whether the visibility calculator determined that the transaction is visible. If it is not visible, control is passed to step 179, which performs as disclosed above. If the transaction is visible, control is passed to step 185. Step 185 writes a record for this transaction to the partial transaction log for the node being processed, for example, partial transaction log 17-a for node 21-a. Instep 187, thelog manager 9 records the last transaction that was processed for this node, and then passes control to step 179, which determines whether to select additional transactions or exit, as disclosed above. - Visibility Calculation
- FIG. 7 depicts a flowchart describing the process a visibility calculator for calculating visibility for a docking object as invoked by
step 181 oflog manager 9. The visibility calculator is called with the node-id of the node for which visibility is being calculated, the docking object for which the visibility is being calculated, and the row-id of the docking object whose visibility id being calculated. The visibility calculator uses this information, in conjunction with information obtained from meta-data stored in the schema depicted in FIG. 2, to determine whether a particular transaction that updates a particular row of a particular docking object is visible to a particular node. - The Visibility calculator begins execution at
step 201. Instep 203, the visibility calculator makes a default finding that the transaction is not visible. Therefore, unless the visibility calculator determines that a transaction is visible, it will exit with a finding of no visibility. Instep 205, the visibility calculator selects the first visibility rule associated with the docking object. This is done by finding thetable S_DOBJ_VIS_RULE 71 associated with the current Docking Object as pointed to bytable S_DOBJ 61. Instep 205, the visibility calculator selects the row oftable S_DOBJ_VIS_RULE 71 with the lowest value for field RULE_SEQUENCE. - In
step 207, the Visibility Calculator checks the field RULE_TYPE for a value of “R.” The value of “R” indicates that the rule is a SQL visibility rule. If so, the Visibility Calculator proceeds to step 209. Instep 209 the Visibility Calculator obtains a SQL statement from field SQL_STATEMENT and executes it. An example of such an SQL statement might be: - SELECT ‘X’ FROM S_OPTY_EMP
- WHERE OPTY_ID=:PrimaryRowId
- AND EMP_ID=:NodeId;
- This SQL statement causes a query to be made of application table S_OPTY_EMP. The query selects any records meeting two criteria. First, the records selected must have a field OPTY_ID, which is a row id or key, equal to the Primary Row-ID of the Docking Object whose visibility is being determined. Second, the records selected must have a field EMP_ID, which may be for example, an identifier of a particular employee, equal to the NodeId of the node for whom visibility is being determined. In ordinary language, this SQL statement will return records only if a row is found in a table that matches employees to opportunities, where the opportunity is equal to the one being updated, and the employee to whom the opportunity is assigned is the operator of the node.
- This is a simplistic example, provided for maximum comprehension. More complex SQL statements are possible. For example, the rule:
- SELECT ‘X’ FROM
- &Table_Owner.S_ACCT_POSTN ap
- &Table_Owner.S_EMP_POSTN ep
- WHERE ap.POSITION_ID=ep.POSITION_ID
- AND ep.EMP_ID=:NodeId;
- This rule queries the tables S_ACCT_POSTN (which relates a particular account with a particular position in the organization that is responsible for the account) and S_EMP_POSTN (which relates what employee corresponds to a particular position). The condition “ap.POSITION_ID =ep.POSITION_ID” requires finding a row in the account-to-position table that has the same position as a row in the employee-to-position table. The condition “ep.EMP_ID=:NodeId” further requires that the selected row in the employee-to-position table also have an Employee ID equal to the ID of the user of the Node for which visibility is being determined. In ordinary language, this condition allows visibility if the employee occupies the position that has responsibility for the account in the docking object being updated.
- There is no particular limit to the complexity of the conditions in the SQL statement used to evaluate visibility. Particular implementations of SQL may impose limitations, and resource considerations may make it desirable to use less complex statements, but these limitations are not inherent in the invention.
-
Step 211 evaluates whether the execution of SQL_STATEMENT instep 209 returned any records. If records were returned, this indicates that the Node for which visibility is being checked has visibility to the docking object being processed. Accordingly, if records are returned, the Visibility Calculator proceeds to step 213. Instep 213, the transaction is marked visible. Because no further rules need to be evaluated to determine visibility, the visibility calculator proceeds to step 228. Step 228 synchronizes the databases by determining whether the calculated visibility requires the insertion or deletion of a docking object into a particular node's partially replicated database. This may occur, for example, if a node is determined to have visibility to a docking object due to a change to a related docking object. For example, an owner of a node may be assigned to a particular activity that is related to a particular sales opportunity. As a result, the node should be provided with a copy of the object representing the sales opportunity. - FIG. 8 depicts the steps performed to synchronize a partially replicated database in response to a change in data visibility. Execution begins in
step 241. Instep 243, the Visibility Calculator references the visibility just calculated for a docking object. If the Docking Object is visible, execution proceeds to step 245. Step 245 references the S_DOBJ_INST table, to verify that a row exists for the Docking Object for the current node. If a row exists, this indicates that the node in question already has a copy of the referenced Docking Object, and the routine proceeds to step 255, where it exits. If, however, no row exists for the Docking Object at the node being processes, this indicates that the node in question does not have a copy of the Docking Object on its partially replicated database. The routine then proceeds to step 247, where a transaction is generated to direct the node to insert the Docking Object into its partially replicated database. - If
step 243 determines that the Docking Object is not visible, execution proceeds to step 249. Step 249 references the S DOBJ_INST table, to verify that no row exists for the Docking Object for the current node. Ifstep 243 determines that no row exists in the S_DOBJ_INST table for the current docking object for the current row, this indicates that the node in question does not have a copy of the referenced Docking Object, and the routine proceeds to step 255, where it exits. If, however, a row exists for the Docking Object at the node being processed, this indicates that the node in question does have a copy of the Docking Object on its partially replicated database. The routine then proceeds to step 251, where a transaction is generated to direct the node to delete the Docking Object from its partially replicated database. - Referring again to FIG. 7, following the data synchronization routine of
step 228, the Visibility Calculator proceeds to step 229, where it exits. Referring to FIG. 6, as previously described, the resulting finding of visibility is available to be checked by the log manager instep 183 to determine to write the transaction. - Referring again to FIG. 7, if
step 211 determines that no records were returned by the execution of the SQL statement instep 209, execution proceeds withstep 215. Step 215 checks to see whether there are any remaining visibility rules to be assessed. If not, the visibility calculator proceeds to step 228 to synchronize the database, and then to step 229, where it exits. In this case, the default mark of no visibility that was set instep 203 remains set. This value will also be used by the log manager as shown in FIG. 6,step 183, to determine not to write the transaction. - Referring again to FIG. 7, if rules remain to be assessed, control proceeds to step217, which selects the next rule to be processed. Control is then given again to step 207 to begin processing the new rule.
- The preceding text provided a description of the processing or SQL visibility rule; that is, visibility rules of type “R.” If
step 207 determines that the visibility rule is not of type “R,” the visibility rule is of type “O.” Type “O” indicates a docking-object visibility rule. In such a case, the docking object being processed will be considered to be visible if it is related to a particular related docking object that is visible. If field RULE_TYPE is not equal to “R,” then. execution proceeds to step 221. Step 221 determines the related Docking Object whose visibility must be determined to determine whether the current docking object is visible. The related Docking Object identifier is obtained from field CHECK_DOBJ_ID intable S_DOBJ_VIS_RULE 71. Instep 223, the Visibility Calculator determines which row in the related Docking Object must be queried for visibility. In order to determine this, the Visibility Calculator obtains a predetermined SQL statement from the field SQL_STATEMENT and executes it. The SQL statement is a query that select one or more rows of the Docking Object that, for example, correspond to the docking object for which the Visibility Calculator was invoked. - For example, assume that it is desired to indicate that a record for a sales opportunity should be visible if the Node has visibility to any sales quote made for that sales opportunity. This may be accomplished using the following SQL statement:
- SELECT“_ID” FROM
- &Table_Owner.S_DOC_QUOTE
- WHERE OPTY_ID=:Primary Rowld
- This SQL statement accesses a table S_DOC_QUOTE that contains all sales quotes. The WHERE clause specifies retrieval of all rows where the Opportunity ID of the row is equal to the Row-ID of the opportunity for which visibility is being calculated. The Visibility manager retrieves the specified Row-Ids, thereby identifying the rows of the S_DOC_QUOTE table whose visibility must checked.
- Having determined the a related docking object and the row-ID of that related docking object upon whose visibility the visibility of the current docking object depends, the Visibility Calculator proceeds to step225. In
step 225, the Visibility Calculator recursively invokes itself to determine visibility of the related docking object. The recursively invoked Visibility Calculator operates in the same manner as the Visibility Calculator as called from theLog Manager 9, including the capability to further recursively invoke itself. When the recursive call concludes, it returns a visibility indicator for the related Docking Object, and control proceeds to step 227. Instep 227, the Visibility calculator determines whether the related Docking Object was determined to have been visible. If so, the Visibility Calculator proceeds to step 213 to mark the originally current Docking Object as visible, and then to step 228 to synchronize the database and then to step 229 to exit. If the related Docking Object was not determined to be visible, control proceeds to step 215 to determine whether additional visibility rules remain to be assessed. - The Visibility Calculator, in conjunction with the Log Manager is therefore able to determine what subset of update transaction data is required to be routed to any particular node. This operation serves to reduce the transmission of unneeded data from the Central Computer1 to the various nodes such as nodes 21-a, 21-b and 21-c that utilize partially replicated databases, and to reduce the system resources such as disk space needed to store, and the CPU time needed to process, what would otherwise be required to maintain a fully replicated database on each remote node.
- The operation of the
log manager 9 in conjunction with the Visibility Calculator herein described will be apparent from reference to the description and to the drawings. However, as a further aid in the description of these facilities, a pseudocode representation of these facilities is hereto attached as an Appendix. - Software Distribution Integration with Remote Upgrade
- The docking facility of the present invention also permits the distribution of software upgrades and related database schema. This provides an easy process to allow administrators to notify remote users of the existence of software upgrades and to distribute software upgrades to remote users. It provides an easy process for remote users to receive notification of software upgrades and to apply the software upgrade. It provides a means to associate a software upgrade with a remote schema upgrade so that the software upgrade is not applied before the remote schema upgrade. It provides a means for a remote user to provide feedback regarding a successful or unsuccessful completion of the software upgrade to the administrator.
- Typically, implementation of software upgrades is very passive. The user does not actively receive information about the availability of software that should be downloaded. Users are required to download the file manually, and, once received, the upgrade is installed using an installer package separate from the software package being upgraded. It would be advantageous to provide a means in the software package to publish the availability of software for download to remote users so that the remote users are informed of the need to download software and are prompted when the download should occur, and provide for the dependency of a software upgrade on an accompanying schema upgrade.
- According to one embodiment of our invention there is provided is a method of upgrading a software application from one or more upgrade package files in a server (1) to a client (21 a, 21 b, 21 c). According to this method a copy of the upgrade package files and an upgrade database table are created on the server (1). A pointer is created in the client's (21 a, 21 b, 21 c) file on the server (1). This pointer points to the upgrade package files on the server (1); In invoking the upgrade the, the upgrade files are made active, and the upgrade database table is scanned when a client (21 a, 21 b, 21 c) docks. This is to determine the status of an upgrade with respect to the particular client (21 a, 21 b, 21 c). The upgrade is copied to the client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade. At this point the upgrade may be invoked at the client (21 a, 21 b, 21 c).
- The upgrade can be invoked at any point during a docking session, for example, at the beginning of a client (21 a, 21 b, 21 c) session., or, and most preferably, at the end of a client (21 a, 21 b, 21 c) session. The upgrade can be invoked at the client user's option, or at the server's option, that is, by forced downloading as will be described hereinbelow.
- One way of implementing the invention, as will be described more fully hereinbelow, is to create a docking item file type to scan the upgrade database table when the client (21 a, 21 b, 21 c) docks to thereby determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c).
- These various aspects of our invention may be implemented as program products. That is, they may be implemented as a computer usable medium with computer program code embodied therein for causing the upgrading of a software application from upgrade package files in a server (1) to a client (21 a, 21 b, 21 c). The computer readable program in the program product article of manufacture contains computer readable program code means for causing a computer to effect creating a copy of the upgrade package files on the server (1), creating an upgrade database table on the server (1); creating a pointer in the client's (21 a, 21 b, 21 c) file on the server (1) pointing to the upgrade package files on the server (1), making the upgrade active, scanning the upgrade database table when a client (21 a, 21 b, 21 c) docks to determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c), copying the upgrade to a client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade, and invoking the upgrade at the client (21 a, 21 b, 21 c).
- Additionally, our invention may be implemented as a program product in the form of a program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for of upgrading a software application from upgrade package files in a server (1) to a client (21 a, 21 b, 21 c) said method steps comprising creating a copy of the upgrade package files on the server (1), creating an upgrade database table on the server (1); creating a pointer in the client's (21 a, 21 b, 21 c) file on the server (1) pointing to the upgrade package files on the server (1), making the upgrade active, scanning the upgrade database table when a client (21 a, 21 b, 21 c) docks to determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c), copying the upgrade to a client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade, and invoking the upgrade at the client (21 a, 21 b, 21 c).
- The integrated update works as follows. At the end of a normal docking session, the user is prompted with the information regarding the availability of a software upgrade. The user has the option to download the software upgrade or to defer and download the software upgrade later. This can be overridden by the system administrator, who has the ability to mark the file as a force download. In such a case, the user is not prompted to download the file; instead, the file is downloaded without input from the user. The user is prompted using a message box that has the ability to time out.
- There are two classes of software upgrades: software that is being distributed in conjunction with a schema upgrade and software that is not associated with a schema upgrade. If the software is associated with a schema upgrade, the software upgrade is not applied until after the schema upgrade has been applied. The applying of the schema upgrade invokes the software upgrade at the end of the processing of the schema upgrade. If the software is not associated with a schema upgrade, then after successfully downloading the software upgrade files, the user will be prompted to apply the upgrade now or to defer. The administrator will have the ability to force the applying of the software upgrade immediately upon completion of the docking session.
- Once the user chooses to apply the software upgrade, the installation component is invoked and the database application is closed. The installation component then guides the user through the necessary steps needed to apply the software.
- The system administrator uses a dialog to specify the association of files, messages and schema upgrades for an upgrade package. The dialog includes a master section and a detail section. The master section allows for the creation of a header record that names the upgrade package and specifies some general attributes regarding the upgrade. The detail section associates software upgrade files, messages and schema upgrades.
- The attributes of the master record include the name of the upgrade package; the schema version of the database after the upgrade is applied; a message supplied to users to view prior to downloading the upgrade; a message to be displayed when the upgrade is applied; a download attribute indicating how the file must be downloaded, e.g., whether the file must be downloaded immediately or whether it may be deferred by the user; an application attribute indicating how the upgrade may be applied, e.g., whether the upgrade must be applied immediately, may be deferred by the user, or must be deferred pending a corresponding upgrade of a corresponding schema or software upgrade; and a description.
- The attributes of the detail record include a record type indicating whether the file is a message, a software upgrade, etc., and the name of the file.
- Upgrades are denoted by a record in an upgrade table in the database. Once a record is created in the upgrade table and the associated upgrade package is made active, Log Manager routes this information using the previously described docking mechanisms to remote users by creating an entry in the users' server.ts files. This entry points to a global upgrade table of contents (TOC) file. A single TOC file serves all docking users per application server installation. The upgrade TOC file contains the detailed information regarding the upgrade package. In this embodiment, only one upgrade package is active at a given time.
- When a user docks and retrieves the server.ts file, the docking client scans the server.ts file for the existence of upgrade entries. Depending upon the attributes of any upgrade entries in the server.ts file, either the upgrade files be downloaded immediately or a message is displayed to the user. The user optionally has have the option either download the files during the current docking session or defer download until a later docking session.
- Depending upon the attributes of the upgrade package, the installation component may be invoked automatically or the user may defer applying the upgrade. If the software upgrade is associated with a schema upgrade, then after the schema upgrade has been applied, the status of software upgrade files is checked to verify that all files associated with the upgrade have been downloaded. Any files not yet downloaded will be downloaded, making a connection to the application server if necessary. The software upgrade will then be invoked by the installation component.
- The file types are represented by the field UTLTocFileType. A file type of UTLTocFileTOCUpg indicates the Upgrade TOC file, and a file type of UTLTocFileUpgrade indicates a file that is a constituent part of an upgrade. Optionally, a file type of UTLTocFileMessage indicates a file containing a message to be displayed to the user.
- The upgrade is represented to the user as a new dock item type, named CSSDockUpg. The CSSDockUpg class is derived from the CSSDockItem class.
- When the user docks and is sending or receiving data from the server, the CSSDockUpg dock item type is created. When executed, this class examines the server.ts file for an entry type of UTLTocFileTOCUpg. If found, either the message specified by the entry pre-download message will be displayed to the user using a time-out dialog box at the end of the docking session or the files will be downloaded immediately depending on the attributes of the entry type UTLTocFileTOCUpg.
- Once the files are downloaded, the apply message from the upgrade TOC file is displayed to the user at the end of the docking session. Alternatively, the installation component is invoked by the mobile client.
- When the upgrade is applied, the installation component is invoked. If the user defers application of the upgrade, then each time the user issues docks to the headquarters server, the docking client looks for the upgrade TOC file in the upgrade directory on the client machine. If the file exists, the apply message is displayed to the user.
- After the upgrade files have been downloaded the upgrade TOC file is stored locally on the client. This file will then be examined after the schema upgrade process has completed.
- The master copy of the upgrade package files is placed on the file server. When a Log Manager process is processing a user and encounters the transaction that makes the upgrade package active, Log Manager copies these files to the local application server upgrade directory if the files do not already exist. Log Manager also creates the upgrade TOC file in this directory if the TOC file does not already exist.
- Once an upgrade package is marked as active, a record in the docking transaction log is created. This record will cause the log preprocessor to create the global upgrade TOC file. The contents of the file are inserted into a text column of the upgrade package. When the log router is executing for a particular user, this record will cause the log router to create an entry in the user's server.ts file, which that points to the global upgrade TOC file. The log router also ensures that the global upgrade TOC file exists in a predetermined directory. If the file exists, the log router reads the text column of the upgrade package that contains the contents of the TOC file and creates the global upgrade TOC file. Alternatively, the log router may read the text column and create an upgrade TOC file for each user. This would prevent more than one log router executable from creating the global upgrade TOC file.
- In some cases, a schema upgrade will require a corresponding software upgrade in order for the schema to function properly. This may occur, for example, when the vendor supplies a new software-schema pair. A customer cannot cause a software version conflict with the ability for dbinit/data merge to apply the schema changes. If schema upgrade that requires a corresponding software upgrade is to be applied, the software upgrade must be applied first, because it is the new software that provides support for the schema upgrade.
- An example of this scenario is when the vendor ships new software and a new version of the database. The system administrator packages the software and makes it available for download by the user. The system administrator then applies the database upgrade to the central database.
- At some point, a remote user docks and is informed that the central database has been updated, and that the user's docking operation is limited to downloading changes to the database; that is, the user is not permitted to upload transactions until his own partially replicated database has been upgraded to match the central database schema. The user then downloads the database upgrade files corresponding to the upgrade installed on the central database. The installation component is invoked (either by the client-side software upon detecting the upgrade condition, or expressly invoked by the user, depending on the upgrade file's attributes). The installation component opens the database upgrade files and contains a checksum value for the upgrade file set. The checksum is compared against a value in the user's configuration file that uniquely identifies the user's software level. If the checksum value is different, then the client software does not have the ability to apply the schema changes. The schema changes will be deferred until the user separately upgrades his or her software level.
- A checksum may also be included in the DX files that represent transactions. The data merge component verifies the checksum associated with the transaction against the checksum in the configuration file. If the checksums do not match, the application of the DX file is deferred. This prevents a user from inadvertently applying changes that cannot be supported by the software.
- Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of inventive faculty. Thus, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
- All publications and patent applications mentioned in this specification are herein incorporated by reference to the same extent as if each individual publication or patent application was specifically and individually indicated to be incorporated by reference.
- The invention now being fully described, it will be apparent to one of ordinary skill in the art that many changes and modifications can be made thereto without departing therefrom.
APPENDIX Writing User Transaction Log File for a Given Laptop Node This program will be called by a server-side process that processes transaction log entries for all Laptop Nodes. For each Laptop Node, the calling process building the UserTrxnLogFileName and calling Program 1. Input Parameters • LaptopNodeId - node_id of the destination laptop • UserTxnLogFileName - full path of the file where txns will be written • MaxBatchTxns - number of txns between commits and updates to the S_DOCK_STATUS table • MaxTxns - number of txns to process in this session. Use this parameter to limit processing. Main Algorithm - - Check parameters IF (MaxTxns < 1 ∥ MaxBatchTxns < 1) THEN Invalid Parameter END IF - - Get last LOG_EXTRACT number for the Laptop from S_DOCK_STATUS last_txn_commit_number = UTLDStatGetLogNum(LaptopNodeId); - - Initialize Variables NumTxns = 0; - - Total number of txns processed NumBatchTxns = 0; - - Total number of txns written in the current batch - - Read Docking Object and Table definitions into memory structures StartDictApi ( ); - - Open the User Log Txn file Open User Log Txn file - - Select and process new txns in S_DOCK_TRANSACTION_LOG - - where txn_commit_number > last_txn_commit_number FOR each new txn LOOP - - Stop processing if reach MaxTxns IF NumTxns = MaxTxns THEN break; END IF; - - Prevent circular txns. Do not send the txn back to the originating laptop IF txn.OriginNodeId = LaptopNodeId THEN Goto next transaction END IF; - - Process all other types of transactions - - This is the visibility calculator! - - This routine also processes implicit visibility events - - Later: Data Merge can call this function to check whether a txn is - - still visible when merging txns into a laptop or server database. CheckVisibility (LaptopNodeId, LogRecordType, TableName, TransRowId); IF txn is visible THEN - - Write transactions to UserTxnLog file depending on the - - type of LogRecordType. Write the txn to the user log file ++NumBatchTxns END IF; - - Finished processing the txn - - Commit (if needed) IF NumBatchTxns = MaxBatchTxns THEN - - Assume that separate process comes around and deletes - - Txns in S_DOCK_TRANSACTION_LOG that have been processed - - for all nodes. So, no need to delete the txns from the log. Update last LOG_EXTRACT number for Laptop in S_DOCK_STATUS Commit; NumBatchTxns = 0 END IF; ++NumTxns End Loop; /* Each transaction in the Txn Log table */ - - Commit Update last LOG_EXTRACT number for Laptop in S_DOCK_STATUS Commit; - - Close log file (if needed) IF UserTxnLogFileP != NULL THEN Close File; END IF; StopDictApi ( ); Check Visibility Routines - - Check if a record in the txn log is visible to a LaptopNodeId BOOL CheckVisibility (LaptopNodeId, LogRecordType, TableName, TransRowId) { - - SQLStatements routed based on the destination list IF LogRecordType in (‘SQLStatement’) THEN IF Laptop Node in destination list THEN return TRUE; END IF; - - Shadow and Multi Record LogRecordTypes are routed to all nodes - - No visibility events with these LogRecordTypes. ELSIF LogRecordType in (‘ShadowOperation’, ‘MultiRecordDelete’, ‘MultiRecordUpdate’) THEN return TRUE; - - Simple Deletes need more processing ELSIF LogRecordType in (—Simple Delete’) THEN IF (table.visibility in (‘Enterprise’, ‘Limited’)) THEN return TRUE; END IF; - - Simple Inserts and Simple Updates need more processing - - CheckTxnVisibility( ) also processes implicit visibility events ELSIF LogRecordType in (‘Simple Insert’, ‘Simple Update’) THEN IF (table.visibility = ‘Enterprise’) THEN return TRUE; ELSIF table.visibility = ‘Limited’ THEN IF CheckTxnVisibility (LaptopNodeId, Table, RowId) THEN return TRUE; END IF; END IF; END IF; } - - Check if a record in the txn log is visible to a LaptopNodeId static BOOL CheckTxnVisibility (LaptopNodeId, Table, RowId) { BOOL bVisible = FALSE; Find the Table in the Dictionary; IF Table not found THEN Error: Table not defined END IF; FOR all docking objects that the table belongs to LOOP - - Generate SQL to get PrimaryId values of the Docking Object GeneratePrimaryIdSQL (Table, RowId, DockingObject); FOR each PrimaryId value retrieved LOOP CheckObjectVisibility (LaptopNodeId, PrimaryTable, PrimaryRowId) IF object is visible THEN - - Because CheckObjectVisibility( ) also processes implicit - - visibility events, we must loop through ALL docking objects - - even if we already know that the Txn is visible. - - Exception: if the table has VIS_event_FLG = ‘N’ - - then we can return immediately. IF Table.visibilityEventFLG = ‘N’ THEN return TRUE; ELSE bVisible = TRUE; END IF; END IF; END LOOP; END LOOP; return bVisible; } - - Check if an instance of a docking object is visible to the laptop user. - - Also processes implicit visibility events! BOOL CheckObjectVisibility (LaptopNodeId, DockingObjectName, PrimaryRowId) { FOR each visibility rule for the Docking Object LOOP IF RuleType = RuleSQL THEN Run the select SQL statement using PrimaryRowId; IF any rows returned THEN - - row is visible - - Process an implicit Download Object DownloadObjectInstance (LaptopNodeId, PrimaryTableName, PrimaryRowId); return TRUE; END IF; ELSIF RuleType = CheckDockingObject THEN Run the ParameterSQL using PrimaryRowId to get newPrimaryRowId FOR each record retrieved by ParameterSQL LOOP - - RECURSIVE! CheckObjectVisibility (LaptopNodeId, CheckDockingObjectName, newPrimaryRowId); IF rc = TRUE THEN - - Process an implicit Download Object DownloadObjectInstance (LaptopNodeId, PrimaryTableName, PrimaryRowId); return TRUE; END IF; END LOOP; END IF; END LOOP; - - Object is not visible. - - Process an implicit Remove Object RemoveObjectInstance (LaptopNodeId, PrimaryTableName, PrimaryRowId); return FALSE; } Generate SQL Statement to Get PrimaryId - - Generate the SELECT SQL statement to get the PrimaryId value of - - the docking object for the given MemberTable - - - - SQL statement looks like: - - SELECT tp.<row_id> - - FROM <table_owner>.<Table> t1, - - <table_owner>.<PKTable> t2, - - ... one or more intermediate tables between the table - - and the PrimaryTable - - <table_owner>.<PKTable> tN - - <table_owner>.<PrimaryTable> tp - - WHERE t1.ROW_ID = :row_id /* row_id in transaction log */ - - /* join to PK table t2 */ - - AND t1.<FKColumn> = t2.<PKColumn> - - AND <t1 FKCondition> - - /* any number of joins until reach the table that joins - - to the PrimaryTable */ - - /* join from t2 to tN */ - - AND t2.<FKColumn> = tN.<PKColumn> - - AND <t2 FKCondition> - - /* join to the PrimaryTable */ - - AND tN.<FKColumn> = tp.<PKColumn> - - AND <tN FKCondition> - - Note that there may be one or more paths from the Member Table - - to the Primary Table. We need to generate a SQL select statement - - for each of the paths and UNION the statements together. - - - - This function assumes that there are no loops in the definition. - - - - These SQL statement do not change for each Table in a Docking Object, - - so we can calculate them one and store them in memory. - - struct { CHAR* selectList; CHAR* fromClause; CHAR* whereClause; UINT numTables; /* also the number of joint to reach the Primary Table */ } GenStmt; GeneratePrimaryIdSQL (Table, DockingObject) { /* there may be more than one SQL statement, so we have a dynamic array of SQL statements. Each element in the array is a path from the Table to the Primary Table*/ DynArrId GenStmtArr; GenStmt newGenStmt; CHAR* sqlStmt; DynArrCreate (GenStmtArr); - - Create the first element and initialize newGenStmt = malloc( ); newGenStmt.numTables = 1; newGenStmt.selectList = “SELECT row_id”; newGenStmt.fromClause = “FROM <Table> t1”; newGenStmt.whereClause = “WHERE t1.ROW_ID = :row_id”; DynArrAppend (GenStmtArr, &newGenStmt); /* Recursively follow FKs to the PrimaryTable */ Build the select, from and where clause simultaneously */ AddPKTable (Table, DockingObject, GenStmtArr, 0); - - Union all the paths together numStmts = DynArrSize (GenStmtArr); FOR all elements in the array LOOP tmpSqlStmt = GenStmtArr[j].selectList∥ GenStmtArr[j].fromClause ∥ GenStmtArr[j].whereClause; sqlStmt = sqlStmt ∥ ‘UNION’ ∥ tmpSqlStmt; END LOOP; DynArrDestroy (GenStmtArr); IF sqlStmt = NULL THEN Error: no path from Table to Primary Table. END IF; } - - Recursively follow all FKs to the Primary Table AddPKTable (Table, DockingObject, GenStmt, InputStmtNum) { UINT numFKS = 0; UINT StmtNum; GenStmt newGenStmt; FOR all FKs for the table LOOP IF PKTable is a Member Table of the Docking Object THEN - - If there's more than one FK, then there is more than one path - - out of the current table. - - Copy the SQL stmt to a new DynArrElmt to create a new path IF numFKs > 0 THEN - - Create a new element and copy from GenStmt[InputStmtNum] newGenStmt = malloc( ); newGenStmt.numTables = GenStmt[InputStmtNum].numTables; newGenStmt.selectList = GenStmt[InputStmtNum].selectList; newGenStmt.fromClause = GenStmt[InputStmtNum].fromClause; newGenStmt.whereClause = GenStmt[InputStmtNum].whereClause; DynArrAppend (GenStmtArr, &newGenStmt); StmtNum = DynArrSize (GenStmtArr); - - Put a check here for infinite loops IF StmtNum == 20 THEN Error: Probably got an Infinite loop? END IF; ELSE StmtNum = InputStmtNum; END IF; - - Append the new PKTable to the fromClause and whereClause GenStmt[StmtNum].fromClause = GenStmt[StmtNum].fromClause ∥ “,\n <Table> t<numTables + 1>”; GenStmt[StmtNum].whereClause = GenStmt[StmtNum].whereclause ∥ “AND t<numTables>.<FKColumn> = t<numTables + 1>.<PKColumn>” ∥ “AND <FKCondition for Table if any>”; ++GenStmt.numTables; - - PKTable is the Primary Table then Done. IF PKTable = PrimaryTable THEN RETURN; ELSE AddPKTable (PKTable, DockingObject, GenStmt, StmtNum); END IF; - - Only count FKs to other member tables in the same Docking Object ++numFKs; END IF; END LOOP; RETURN; } Process Visibility Events - - Download an Object Instance to a Laptop - - This function also downloads all Related Docking Object instances. BOOL DownloadObjectInstance (LaptopNodeId, ObjectName, PrimaryRowId) { - - Check if the object instance is already downloaded to the laptop Find the object instance in the S_DOBJ_INST table IF exists on laptop THEN return TRUE; END IF; - - Register object instance in S_DOBJ_INST table - - Write Download Object records to the Txn Log FOR each member table of the docking object LOOP Generate SQL select statement to download records Write each retrieved record to the User Txn Log file END LOOP; - - Download records for Parent Object instances FOR each RelatedDockingObject LOOP Run ParameterSQL to get newPrimaryId of RelatedDockingObjects FOR each newPrimaryId retrieved LOOP - - Check if the instance of the object is visible to the laptop user CheckObjectVisibility (LaptopNodeId, ObjectName, PrimaryRowId) IF visible THEN DownloadObjectInstance (LaptopNodeId, RelatedDockingObject, newPrimaryRowId); END IF; END LOOP; END LOOP; return TRUE; } - - Remove an Object Instance to a Laptop - - This function also removes all Related Docking Object instances. BOOL RemoveObjectInstance (LaptopNodeId, ObjectName, PrimaryRowId) { - - Check if the object instance is already downloaded to the laptop Find the object instance in the S_DOBJ_INST table IF does not exist on laptop THEN return TRUE; END IF; - - Delete the object instance from S_DOBJ_INST table - - Write Remove Object records to the Txn Log FOR each member table of the docking object LOOP Generate SQL select statement to get records to delete Write each retrieved record to the User Txn Log file END LOOP; - - Remove for Parent Object instances FOR each RelatedDockingObject LOOP Run ParameterSQL to get newPrimaryId of RelatedDockingObjects FOR each newPrimaryId retrieved LOOP - - Check if the instance of the object is visible to the laptop user CheckObjectVisibility (LaptopNodeId, ObjectName, PrimaryRowId) IF not visible THEN RemoveObjectInstance (LaptopNodeId, RelatedDockingObject, newPrimaryRowId); END IF; END LOOP; END LOOP; return TRUE; }
Claims (18)
1. A method of upgrading a software application from upgrade package files in a server (1) to a client (21 a, 21 b, 21 c) comprising the steps of:
a) creating a copy of the upgrade package files on the server (1);
b) creating an upgrade database table on the server (1);
b) creating a pointer in the client's (21 a, 21 b, 21 c) file on the server (1) pointing to the upgrade package files on the server (1);
c) making the upgrade active;
d) scanning the upgrade database table when a client (21 a, 21 b, 21 c) docks to determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c);
d) copying the upgrade to a client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade; and
e) invoking the upgrade at the client (21 a, 21 b, 21 c).
2. The method of claim 1 comprising invoking the upgrade at the beginning of a client (21 a, 21 b, 21 c) session.
3. The method of claim 1 comprising invoking the upgrade at the end of a client (21 a, 21 b, 21 c) session.
4. The method of claim 1 comprising invoking the upgrade at the client's (21 a, 21 b, 21 c) option.
5. The method of claim 1 comprising invoking the upgrade at the server's (1) option.
6. The method of claim 1 comprising creating a docking item file type to scan the upgrade database table when the client (21 a, 21 b, 21 c) docks to thereby determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c).
7. An article of manufacture comprising a computer usable medium having computer program code means embodied therein for causing upgrading a software application from upgrade package files in a server (1) to a client (21 a, 21 b, 21 c), the computer readable program means in said article of manufacture comprising:
a) computer readable program code means for causing a computer to effect creating a copy of the upgrade package files on the server (1);
b) computer readable program code means for causing a computer to effect creating an upgrade database table on the server (1);
b) computer readable program code means for causing a computer to effect creating a pointer in the client's (21 a, 21 b, 21 c) file on the server (1) pointing to the upgrade package files on the server (1);
c) computer readable program code means for causing a computer to effect making the upgrade active;
d) computer readable program code means for causing a computer to effect scanning the upgrade database table when a client (21 a, 21 b, 21 c) docks to determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c);
d) computer readable program code means for causing a computer to effect copying the upgrade to a client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade; and
e) computer readable program code means for causing a computer to effect invoking the upgrade at the client (21 a, 21 b, 21 c).
8. The article of manufacture of claim 7 further comprising computer readable program code means for causing a computer to effect invoking the upgrade at the beginning of a client (21 a, 21 b, 21 c) session.
9. The article of manufacture of claim 7 further comprising computer readable program code means for causing a computer to effect invoking the upgrade at the end of a client (21 a, 21 b, 21 c) session.
10. The article of manufacture of claim 7 further comprising computer readable program code means for causing a computer to effect invoking the upgrade at the client's (21 a, 21 b, 21 c) option.
11. The article of manufacture of claim 7 further comprising computer readable program code means for causing a computer to effect invoking the upgrade at the server's (1) option.
12. The article of manufacture of claim 7 further comprising computer readable program code means for causing a computer to effect creating a docking item file type to scan the upgrade database table when the client (21 a, 21 b, 21 c) docks to thereby determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c).
13. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for of upgrading a software application from upgrade package files in a server (1) to a client (21 a, 21 b, 21 c) said method steps comprising:
a) creating a copy of the upgrade package files on the server (1);
b) creating an upgrade database table on the server (1);
b) creating a pointer in the client's (21 a, 21 b, 21 c) file on the server (1) pointing to the upgrade package files on the server (1);
c) making the upgrade active;
d) scanning the upgrade database table when a client (21 a, 21 b, 21 c) docks to determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c);
d) copying the upgrade to a client (21 a, 21 b, 21 c) if the client (21 a, 21 b, 21 c) has not received the upgrade; and
e) invoking the upgrade at the client (21 a, 21 b, 21 c).
14. The program storage device of claim 13 wherein said method steps further comprise invoking the upgrade at the beginning of a client (21 a, 21 b, 21 c) session.
15. The program storage device of claim 13 wherein said method steps further comprise invoking the upgrade at the end of a client (21 a, 21 b, 21 c) session.
16. The program storage device of claim 13 wherein said method steps further comprise invoking the upgrade at the client's (21 a, 21 b, 21 c) option.
17. The program storage device of claim 13 wherein said method steps further comprise invoking the upgrade at the server's (1) option.
18. The program storage device of claim 13 wherein said method steps further comprise creating a docking item file type to scan the upgrade database table when the client (21 a, 21 b, 21 c) docks to thereby determine the status of an upgrade with respect to the client (21 a, 21 b, 21 c).
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/992,813 US20030009753A1 (en) | 1997-03-12 | 2001-11-27 | Method of synchronizing independently distributed software and database schema |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US4053497P | 1997-03-12 | 1997-03-12 | |
PCT/US1998/003572 WO1998040805A2 (en) | 1997-02-27 | 1998-02-24 | Method of synchronizing independently distributed software and database schema |
US09/375,427 US6324693B1 (en) | 1997-03-12 | 1999-08-17 | Method of synchronizing independently distributed software and database schema |
US09/992,813 US20030009753A1 (en) | 1997-03-12 | 2001-11-27 | Method of synchronizing independently distributed software and database schema |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/375,427 Continuation US6324693B1 (en) | 1997-03-12 | 1999-08-17 | Method of synchronizing independently distributed software and database schema |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030009753A1 true US20030009753A1 (en) | 2003-01-09 |
Family
ID=21911513
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/375,427 Expired - Lifetime US6324693B1 (en) | 1997-03-12 | 1999-08-17 | Method of synchronizing independently distributed software and database schema |
US09/992,813 Abandoned US20030009753A1 (en) | 1997-03-12 | 2001-11-27 | Method of synchronizing independently distributed software and database schema |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/375,427 Expired - Lifetime US6324693B1 (en) | 1997-03-12 | 1999-08-17 | Method of synchronizing independently distributed software and database schema |
Country Status (3)
Country | Link |
---|---|
US (2) | US6324693B1 (en) |
AU (1) | AU6336798A (en) |
WO (1) | WO1998040805A2 (en) |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020016959A1 (en) * | 2000-08-04 | 2002-02-07 | Networks Associates Technology, Inc. | Updating computer files |
US20030217031A1 (en) * | 2002-05-16 | 2003-11-20 | International Business Machines Corporation | Apparatus and method for validating a database record before applying journal data |
US6789215B1 (en) * | 2000-04-21 | 2004-09-07 | Sprint Communications Company, L.P. | System and method for remediating a computer |
US20050132351A1 (en) * | 2003-12-12 | 2005-06-16 | Randall Roderick K. | Updating electronic device software employing rollback |
US20050268307A1 (en) * | 1999-05-10 | 2005-12-01 | Apple Computer, Inc. | Distributing and synchronizing objects |
US20060106894A1 (en) * | 2004-11-03 | 2006-05-18 | Honeywell International Inc. | Object replication using information quality of service |
US20070180151A1 (en) * | 2005-09-20 | 2007-08-02 | Honeywell International Inc. | Model driven message processing |
US20070207800A1 (en) * | 2006-02-17 | 2007-09-06 | Daley Robert C | Diagnostics And Monitoring Services In A Mobile Network For A Mobile Device |
US20080028395A1 (en) * | 2006-07-27 | 2008-01-31 | Giovanni Motta | User Experience And Dependency Management In A Mobile Device |
US20080175372A1 (en) * | 2000-11-17 | 2008-07-24 | Jeffrey Brunet | Operator network that routes customer care calls based on subscriber / device profile and csr skill set |
US20090138523A1 (en) * | 2007-11-28 | 2009-05-28 | Wan-Chang Pi | Content engine asynchronous upgrade framework |
US20090248760A1 (en) * | 2008-03-27 | 2009-10-01 | Fujitsu Limited | Backup method of computer system |
US20100153351A1 (en) * | 2008-12-16 | 2010-06-17 | Yung Alex P | Techniques for real-time database processing |
US20100287526A1 (en) * | 2006-04-14 | 2010-11-11 | Apple Inc. | Mirrored file system |
US20110173598A1 (en) * | 2004-04-21 | 2011-07-14 | Chris Cassapakis | Updating an electronic device with update agent code |
US20120036199A1 (en) * | 2010-08-09 | 2012-02-09 | Thomas Stephen Slee | Sharing Data on Mobile Devices |
US20120254214A1 (en) * | 2010-04-09 | 2012-10-04 | Computer Associates Think, Inc | Distributed system having a shared central database |
US20130036412A1 (en) * | 2011-08-02 | 2013-02-07 | Roche Diagnostics Operations, Inc. | Software distribution amongst medical devices taking into account dependencies between devices |
US8555273B1 (en) * | 2003-09-17 | 2013-10-08 | Palm. Inc. | Network for updating electronic devices |
US8893110B2 (en) | 2006-06-08 | 2014-11-18 | Qualcomm Incorporated | Device management in a network |
US9977671B2 (en) | 2015-07-20 | 2018-05-22 | Google Llc | Methods for multi-source configuration of mobile applications |
Families Citing this family (1432)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6802061B1 (en) | 1996-12-12 | 2004-10-05 | Microsoft Corporation | Automatic software downloading from a computer network |
US7080371B1 (en) * | 1998-03-03 | 2006-07-18 | Siebel Systems, Inc. | Method, system, apparatus and program product for distribution and instantiation of software upgrades |
US20020107837A1 (en) * | 1998-03-31 | 2002-08-08 | Brian Osborne | Method and apparatus for logically reconstructing incomplete records in a database using a transaction log |
US6626953B2 (en) * | 1998-04-10 | 2003-09-30 | Cisco Technology, Inc. | System and method for retrieving software release information |
US6381742B2 (en) * | 1998-06-19 | 2002-04-30 | Microsoft Corporation | Software package management |
US8914507B2 (en) | 1998-09-01 | 2014-12-16 | International Business Machines Corporation | Advice provided for offering highly targeted advice without compromising individual privacy |
US7197534B2 (en) | 1998-09-01 | 2007-03-27 | Big Fix, Inc. | Method and apparatus for inspecting the properties of a computer |
US7246150B1 (en) | 1998-09-01 | 2007-07-17 | Bigfix, Inc. | Advice provided for offering highly targeted advice without compromising individual privacy |
US6263362B1 (en) | 1998-09-01 | 2001-07-17 | Bigfix, Inc. | Inspector for computed relevance messaging |
US6366898B2 (en) | 1998-09-21 | 2002-04-02 | Sun, Microsystems, Inc. | Method and apparatus for managing classfiles on devices without a file system |
US6836794B1 (en) * | 1998-09-21 | 2004-12-28 | Microsoft Corporation | Method and system for assigning and publishing applications |
JP2000148622A (en) * | 1998-11-10 | 2000-05-30 | Sony Corp | Device and method for processing information and distribution medium |
SE521456C2 (en) * | 1998-12-15 | 2003-11-04 | Ericsson Telefon Ab L M | Method and apparatus of a distributed system |
US7607572B2 (en) * | 1999-03-19 | 2009-10-27 | Bigfix, Inc. | Formalizing, diffusing, and enforcing policy advisories and monitoring policy compliance in the management of networks |
US7277919B1 (en) | 1999-03-19 | 2007-10-02 | Bigfix, Inc. | Relevance clause for computed relevance messaging |
US6678741B1 (en) * | 1999-04-09 | 2004-01-13 | Sun Microsystems, Inc. | Method and apparatus for synchronizing firmware |
US6931440B1 (en) * | 1999-04-21 | 2005-08-16 | Emc Corporation | Method and apparatus for dynamically determining whether access to a resource connected to a computer has changed and determining how to access the resource with a new identifier |
US7107329B1 (en) * | 1999-05-21 | 2006-09-12 | Lucent Technologies Inc. | In networks of interconnected router nodes for routing data traffic, a method of and system for imperceptibly upgrading router node software and the like without traffic interruption |
US6981034B2 (en) * | 1999-06-30 | 2005-12-27 | Nortel Networks Limited | Decentralized management architecture for a modular communication system |
US6597700B2 (en) * | 1999-06-30 | 2003-07-22 | Nortel Networks Limited | System, device, and method for address management in a distributed communication environment |
US6888802B1 (en) | 1999-06-30 | 2005-05-03 | Nortel Networks Limited | System, device, and method for address reporting in a distributed communication environment |
US7130879B1 (en) | 1999-08-10 | 2006-10-31 | Alexandre Dayon | System for publishing, organizing, accessing and distributing information in a computer network |
US6493727B1 (en) * | 2000-02-07 | 2002-12-10 | Hewlett-Packard Company | System and method for synchronizing database in a primary device and a secondary device that are derived from a common database |
US6842861B1 (en) * | 2000-03-24 | 2005-01-11 | Networks Associates Technology, Inc. | Method and system for detecting viruses on handheld computers |
US6799207B1 (en) * | 2000-04-10 | 2004-09-28 | International Business Machines Corporation | Method and system for downloading software managed trees in a network processing system |
US8037418B2 (en) * | 2000-04-18 | 2011-10-11 | Samsung Electronics Co., Ltd. | System and method for ensuring integrity of data-driven user interface of a wireless mobile station |
US7140013B2 (en) * | 2000-06-01 | 2006-11-21 | Aduva, Inc. | Component upgrading with dependency conflict resolution, knowledge based and rules |
US7103650B1 (en) * | 2000-09-26 | 2006-09-05 | Microsoft Corporation | Client computer configuration based on server computer update |
US6964044B1 (en) * | 2000-10-06 | 2005-11-08 | Genworth Financial, Inc. | System and process for management of changes and modifications in a process |
US6636875B1 (en) * | 2000-10-25 | 2003-10-21 | International Business Machines Corporation | System and method for synchronizing related data elements in disparate storage systems |
JP4609682B2 (en) * | 2000-11-29 | 2011-01-12 | ソニー株式会社 | Communication system and information processing method |
US6658330B2 (en) | 2000-12-29 | 2003-12-02 | General Electric Co. | Method and system for upgrading software for controlling locomotives |
US6847983B2 (en) | 2001-02-28 | 2005-01-25 | Kiran Somalwar | Application independent write monitoring method for fast backup and synchronization of open files |
US6985915B2 (en) | 2001-02-28 | 2006-01-10 | Kiran Somalwar | Application independent write monitoring method for fast backup and synchronization of files |
US6965928B1 (en) * | 2001-03-09 | 2005-11-15 | Networks Associates Technology, Inc. | System and method for remote maintenance of handheld computers |
US7788399B2 (en) | 2001-03-26 | 2010-08-31 | Salesforce.Com, Inc. | System and method for mapping of services |
US7689711B2 (en) | 2001-03-26 | 2010-03-30 | Salesforce.Com, Inc. | System and method for routing messages between applications |
US9948644B2 (en) | 2001-03-26 | 2018-04-17 | Salesforce.Com, Inc. | Routing messages between applications |
US7363388B2 (en) * | 2001-03-28 | 2008-04-22 | Siebel Systems, Inc. | Method and system for direct server synchronization with a computing device |
JP2002318692A (en) * | 2001-04-19 | 2002-10-31 | Sony Corp | Installation support system, installation support device, installation support method, program for supporting installation and recording medium in which the same program is recorded |
US20020169849A1 (en) * | 2001-05-14 | 2002-11-14 | Schroath Leonard T. | Method and apparatus for providing software for office equipment at point-of-sale |
US20030005426A1 (en) * | 2001-06-08 | 2003-01-02 | Scholtens Dale A. | Methods and apparatus for upgrading software without affecting system service |
US7257649B2 (en) | 2001-09-28 | 2007-08-14 | Siebel Systems, Inc. | Method and system for transferring information during server synchronization with a computing device |
US7415539B2 (en) | 2001-09-28 | 2008-08-19 | Siebel Systems, Inc. | Method and apparatus for detecting insufficient memory for data extraction processes |
US7761535B2 (en) | 2001-09-28 | 2010-07-20 | Siebel Systems, Inc. | Method and system for server synchronization with a computing device |
US7526575B2 (en) | 2001-09-28 | 2009-04-28 | Siebel Systems, Inc. | Method and system for client-based operations in server synchronization with a computing device |
US9231827B2 (en) * | 2001-11-09 | 2016-01-05 | International Business Machines Corporation | Formalizing, diffusing and enforcing policy advisories and monitoring policy compliance in the management of networks |
US6993760B2 (en) * | 2001-12-05 | 2006-01-31 | Microsoft Corporation | Installing software on a mobile computing device using the rollback and security features of a configuration manager |
JP4343704B2 (en) * | 2002-02-25 | 2009-10-14 | シーベル・システムズ・インコーポレーテッド | Method and system for server-based operations in server synchronization with computing devices |
US20030172070A1 (en) * | 2002-03-06 | 2003-09-11 | Sawadsky Nicholas Justin | Synchronous peer-to-peer multipoint database synchronization |
US9171049B2 (en) | 2002-06-13 | 2015-10-27 | Salesforce.Com, Inc. | Offline simulation of online session between client and server |
US20030237081A1 (en) * | 2002-06-21 | 2003-12-25 | Taylor Keith M. | Updating an application using database replication |
DE10241957A1 (en) * | 2002-09-10 | 2004-03-18 | Siemens Ag | Data communication system and system for updating of software of computers connected to the network wherein prior to transfer of upgrade data, the type of communications medium is first determined |
US7290018B2 (en) * | 2002-10-23 | 2007-10-30 | Sap Aktiengesellschaft | Change-driven replication of data |
US7177886B2 (en) | 2003-02-07 | 2007-02-13 | International Business Machines Corporation | Apparatus and method for coordinating logical data replication with highly available data replication |
US7398272B2 (en) * | 2003-03-24 | 2008-07-08 | Bigfix, Inc. | Enterprise console |
US7529775B2 (en) * | 2003-08-20 | 2009-05-05 | Microsoft Corporation | Method and system for collecting information about applications on a computer system |
US7779039B2 (en) | 2004-04-02 | 2010-08-17 | Salesforce.Com, Inc. | Custom entities and fields in a multi-tenant database system |
US8543566B2 (en) | 2003-09-23 | 2013-09-24 | Salesforce.Com, Inc. | System and methods of improving a multi-tenant database query using contextual knowledge about non-homogeneously distributed tenant data |
US7529728B2 (en) | 2003-09-23 | 2009-05-05 | Salesforce.Com, Inc. | Query optimization in a multi-tenant database system |
US8453196B2 (en) | 2003-10-14 | 2013-05-28 | Salesforce.Com, Inc. | Policy management in an interoperability network |
US20050097346A1 (en) * | 2003-10-31 | 2005-05-05 | Brent Pipal | Program code version enforcement |
WO2005052759A2 (en) | 2003-11-24 | 2005-06-09 | Ebay Inc. | Business language schema design framework |
US7844639B2 (en) | 2003-11-24 | 2010-11-30 | Ebay Inc. | Backward compatibility in database schemas |
US7802007B2 (en) | 2004-05-19 | 2010-09-21 | Salesforce.Com, Inc. | Techniques for providing connections to services in a network environment |
US7665063B1 (en) | 2004-05-26 | 2010-02-16 | Pegasystems, Inc. | Integration of declarative rule-based processing with procedural programming |
US7725605B2 (en) | 2004-08-06 | 2010-05-25 | Salesforce.Com, Inc. | Providing on-demand access to services in a wide area network |
US8526940B1 (en) | 2004-08-17 | 2013-09-03 | Palm, Inc. | Centralized rules repository for smart phone customer care |
US20060074841A1 (en) * | 2004-09-27 | 2006-04-06 | Harikrishnan Sugumaran | Method, system, and program for translating and interfacing between data pools and product information management (PIM) systems |
US9645712B2 (en) | 2004-10-01 | 2017-05-09 | Grand Central Communications, Inc. | Multiple stakeholders for a single business process |
US7721328B2 (en) | 2004-10-01 | 2010-05-18 | Salesforce.Com Inc. | Application identity design |
US8335704B2 (en) | 2005-01-28 | 2012-12-18 | Pegasystems Inc. | Methods and apparatus for work management and routing |
US7774366B2 (en) | 2005-03-08 | 2010-08-10 | Salesforce.Com, Inc. | Systems and methods for implementing multi-application tabs and tab sets |
JP4764056B2 (en) * | 2005-04-14 | 2011-08-31 | キヤノン株式会社 | Image processing apparatus, control program update method, and program |
JP5395434B2 (en) | 2005-09-09 | 2014-01-22 | セールスフォース ドット コム インコーポレイティッド | System and method for exporting, publishing, browsing and installing on-demand applications in a multi-tenant database environment |
US8645376B2 (en) | 2008-05-02 | 2014-02-04 | Salesforce.Com, Inc. | Method and system for managing recent data in a mobile device linked to an on-demand service |
US9135304B2 (en) | 2005-12-02 | 2015-09-15 | Salesforce.Com, Inc. | Methods and systems for optimizing text searches over structured data in a multi-tenant environment |
US9201939B2 (en) | 2006-06-02 | 2015-12-01 | Salesforce.Com, Inc. | Method and system for pushing data to a plurality of devices in an on-demand service environment |
US8069153B2 (en) | 2005-12-02 | 2011-11-29 | Salesforce.Com, Inc. | Systems and methods for securing customer data in a multi-tenant environment |
WO2007089951A1 (en) * | 2006-02-04 | 2007-08-09 | Tn20 Incorporated | Trusted acquaintances network system |
US8751579B1 (en) | 2006-03-02 | 2014-06-10 | Salesforce.Com, Inc. | Method and system of maintaining a browser in a design application workflow |
US8924335B1 (en) | 2006-03-30 | 2014-12-30 | Pegasystems Inc. | Rule-based user interface conformance methods |
US7818740B2 (en) * | 2006-05-05 | 2010-10-19 | Microsoft Corporation | Techniques to perform gradual upgrades |
US8438239B2 (en) * | 2006-05-11 | 2013-05-07 | Vocollect, Inc. | Apparatus and method for sharing data among multiple terminal devices |
US8775315B2 (en) | 2006-10-02 | 2014-07-08 | Salesforce.Com, Inc. | Method and system for integrating a PBX-equipped client and an on-demand database service |
US7827138B2 (en) | 2006-10-02 | 2010-11-02 | Salesforce.Com, Inc. | Method and system for synchronizing a server and an on-demand database service |
US8572057B2 (en) | 2006-10-02 | 2013-10-29 | Salesforce.Com, Inc. | Method and system for applying a group of instructions to metadata |
US8255374B2 (en) | 2006-10-02 | 2012-08-28 | Salesforce.Com, Inc. | Method and system for selecting amongst a plurality of processes to send a message |
US8370848B2 (en) | 2006-10-02 | 2013-02-05 | Salesforce.Com, Inc. | Method and system for providing a client access to an external service via an application services platform |
US8370849B2 (en) | 2006-10-02 | 2013-02-05 | Salesforce.Com, Inc. | API method and system for providing access to an external service via an application services platform |
US8095531B2 (en) | 2006-10-03 | 2012-01-10 | Salesforce.Com, Inc. | Methods and systems for controlling access to custom objects in a database |
US9230068B2 (en) | 2006-10-03 | 2016-01-05 | Salesforce.Com, Inc. | Method and system for managing license objects to applications in an application platform |
US8332435B2 (en) | 2006-10-03 | 2012-12-11 | Salesforce.Com, Inc. | Method and system for customizing a user interface to an on-demand database service |
US8601467B2 (en) | 2006-10-03 | 2013-12-03 | Salesforce.Com, Inc. | Methods and systems for upgrading and installing application packages to an application platform |
US8131580B2 (en) | 2006-10-04 | 2012-03-06 | Salesforce.Com, Inc. | Method and system for load balancing a sales forecast system by selecting a synchronous or asynchronous process based on a type of an event affecting the sales forecast |
US8161010B2 (en) | 2006-10-04 | 2012-04-17 | Salesforce.Com, Inc. | Methods and systems for providing fault recovery to side effects occurring during data processing |
US7730478B2 (en) * | 2006-10-04 | 2010-06-01 | Salesforce.Com, Inc. | Method and system for allowing access to developed applications via a multi-tenant on-demand database service |
US8682863B2 (en) | 2006-10-04 | 2014-03-25 | Salesforce.Com, Inc. | Methods and systems for bulk row save logic in an object relational mapping layer and application framework |
US8548942B2 (en) | 2006-10-04 | 2013-10-01 | Salesforce.Com, Inc. | Methods and systems for recursive saving of hierarchical objects to a database |
US8195605B2 (en) * | 2006-10-27 | 2012-06-05 | Purdue Pharma L.P. | Data cache techniques in support of synchronization of databases in a distributed environment |
US8595635B2 (en) | 2007-01-25 | 2013-11-26 | Salesforce.Com, Inc. | System, method and apparatus for selecting content from web sources and posting content to web logs |
US8250525B2 (en) | 2007-03-02 | 2012-08-21 | Pegasystems Inc. | Proactive performance management for multi-user enterprise software systems |
US8495157B2 (en) * | 2007-03-07 | 2013-07-23 | International Business Machines Corporation | Method and apparatus for distributed policy-based management and computed relevance messaging with remote attributes |
US20100332640A1 (en) * | 2007-03-07 | 2010-12-30 | Dennis Sidney Goodrow | Method and apparatus for unified view |
US8161149B2 (en) | 2007-03-07 | 2012-04-17 | International Business Machines Corporation | Pseudo-agent |
US8706696B2 (en) | 2007-05-04 | 2014-04-22 | Salesforce.Com, Inc. | Method and system for on-demand communities |
US8781988B1 (en) | 2007-07-19 | 2014-07-15 | Salesforce.Com, Inc. | System, method and computer program product for messaging in an on-demand database service |
US8140576B1 (en) | 2007-07-19 | 2012-03-20 | Salesforce.Com, Inc. | On-demand database service system, method and computer program product for conditionally allowing an application of an entity access to data of another entity |
US8359647B1 (en) | 2007-07-19 | 2013-01-22 | Salesforce.Com, Inc. | System, method and computer program product for rendering data of an on-demand database service safe |
US7991790B2 (en) | 2007-07-20 | 2011-08-02 | Salesforce.Com, Inc. | System and method for storing documents accessed by multiple users in an on-demand service |
CA2637975A1 (en) * | 2007-08-16 | 2009-02-16 | Radian6 Technologies Inc. | Method and system for determining topical on-line influence of an entity |
US20090157668A1 (en) * | 2007-12-12 | 2009-06-18 | Christopher Daniel Newton | Method and system for measuring an impact of various categories of media owners on a corporate brand |
EP2179352A4 (en) | 2007-08-17 | 2010-12-29 | Salesforce Com Inc | On-demand database service system, method, and computer program product for verifying that a developed application will operate properly with at least one other application |
US9798784B1 (en) | 2008-08-22 | 2017-10-24 | Salesforce.Com, Inc. | System, method and computer program product for defining custom junction objects in an on-demand database service |
CN101849233B (en) * | 2007-11-06 | 2013-01-09 | 艾利森电话股份有限公司 | Lightweight directory access protocol (ldap) collision detection mechanism and method |
US8584212B1 (en) | 2007-11-15 | 2013-11-12 | Salesforce.Com, Inc. | On-demand service security system and method for managing a risk of access as a condition of permitting access to the on-demand service |
US8875259B2 (en) | 2007-11-15 | 2014-10-28 | Salesforce.Com, Inc. | On-demand service security system and method for managing a risk of access as a condition of permitting access to the on-demand service |
US9501453B2 (en) | 2007-12-23 | 2016-11-22 | Salesforce.Com Inc. | Method and system for a flexible-data column user interface |
US8468117B1 (en) | 2008-01-22 | 2013-06-18 | Salesforce.Com, Inc. | System, method and computer program product for creating a visual component for tenants of an on-demand database service |
US8239501B1 (en) | 2008-01-22 | 2012-08-07 | Salesforce.Com, Inc. | System, method and computer program product for creating mobile custom views with filtering for tenants of an on-demand database service |
US8677470B1 (en) | 2008-01-22 | 2014-03-18 | Salesforce.Com, Inc. | System, method, and computer program product for security verification of communications to tenants of an on-demand database service |
CA2650319C (en) * | 2008-01-24 | 2016-10-18 | Radian6 Technologies Inc. | Method and system for targeted advertising based on topical memes |
WO2009132444A1 (en) | 2008-04-28 | 2009-11-05 | Sitemasher Corporation | Object-oriented system for creating and managing websites and their content |
US9245252B2 (en) * | 2008-05-07 | 2016-01-26 | Salesforce.Com, Inc. | Method and system for determining on-line influence in social media |
US9791993B2 (en) | 2008-05-08 | 2017-10-17 | Salesforce.Com, Inc | System, method and computer program product for creating a re-usable component utilizing a multi-tenant on-demand database service |
US8478782B1 (en) | 2008-05-08 | 2013-07-02 | Salesforce.Com, Inc. | System, method and computer program product for sharing tenant information utilizing a multi-tenant on-demand database service |
US9251239B1 (en) | 2008-05-15 | 2016-02-02 | Salesforce.Com, Inc. | System, method and computer program product for applying a public tag to information |
US9361366B1 (en) | 2008-06-03 | 2016-06-07 | Salesforce.Com, Inc. | Method and system for controlling access to a multi-tenant database system using a virtual portal |
US8473518B1 (en) | 2008-07-03 | 2013-06-25 | Salesforce.Com, Inc. | Techniques for processing group membership data in a multi-tenant database system |
US8473469B1 (en) | 2008-08-25 | 2013-06-25 | Salesforce.Com, Inc. | Techniques for implementing batch processing in a multi-tenant on-demand database system |
US8966250B2 (en) | 2008-09-08 | 2015-02-24 | Salesforce.Com, Inc. | Appliance, system, method and corresponding software components for encrypting and processing data |
US9535967B2 (en) | 2008-09-10 | 2017-01-03 | Salesforce.Com, Inc. | Method and system for providing efficient and complex database functionality to a mobile device |
US8447745B2 (en) * | 2008-09-12 | 2013-05-21 | Salesforce.Com, Inc. | Synchronizing field values in an on-demand database prior to committing a change |
US8726179B2 (en) | 2008-09-12 | 2014-05-13 | Salesforce.Com, Inc. | Method and system for providing in-line scheduling in an on-demand service |
US8423524B1 (en) | 2008-09-12 | 2013-04-16 | Salesforce.Com, Inc. | System, method and computer program product for storing reports for use by tenants of a multi-tenant on-demand database service |
US9047479B1 (en) | 2008-09-12 | 2015-06-02 | Salesforce.Com, Inc. | System, method and computer program product for providing a team object in association with an object |
US8417723B1 (en) | 2008-09-12 | 2013-04-09 | Salesforce.Com, Inc. | System, method and computer program product for enabling access to a resource of a multi-tenant on-demand database service utilizing a token |
US8538942B2 (en) | 2008-09-12 | 2013-09-17 | Salesforce.Com, Inc. | Method and system for sharing documents between on-demand services |
US8407338B2 (en) * | 2008-09-12 | 2013-03-26 | Salesforce.Com | Methods and systems for polling an on demand service |
US8577918B2 (en) | 2008-09-12 | 2013-11-05 | Salesforce.Com, Inc. | Method and system for apportioning opportunity among campaigns in a CRM system |
US8661056B1 (en) | 2008-11-03 | 2014-02-25 | Salesforce.Com, Inc. | System, method and computer program product for publicly providing web content of a tenant using a multi-tenant on-demand database service |
US20100223100A1 (en) * | 2009-01-23 | 2010-09-02 | Salesforce.Com, Inc. | Methods and Systems for Sales Networking |
US20100192067A1 (en) * | 2009-01-23 | 2010-07-29 | Salesforce.Com, Inc. | Customer service & support systems and methods for use in an on demand database service |
US9286364B2 (en) | 2009-01-23 | 2016-03-15 | Salesforce.Com Inc. | Methods and systems for sharing information in a supply chain |
US8959341B2 (en) * | 2009-01-23 | 2015-02-17 | Salesforce.Com, Inc. | Methods and systems for sharing database content |
US8296321B2 (en) | 2009-02-11 | 2012-10-23 | Salesforce.Com, Inc. | Techniques for changing perceivable stimuli associated with a user interface for an on-demand database service |
US8843435B1 (en) | 2009-03-12 | 2014-09-23 | Pegasystems Inc. | Techniques for dynamic data processing |
US8468492B1 (en) | 2009-03-30 | 2013-06-18 | Pegasystems, Inc. | System and method for creation and modification of software applications |
US8751826B2 (en) * | 2009-04-01 | 2014-06-10 | Salesforce.Com, Inc. | Enhanced system security |
GB0906004D0 (en) * | 2009-04-07 | 2009-05-20 | Omnifone Ltd | MusicStation desktop |
US8812533B1 (en) | 2009-05-21 | 2014-08-19 | Salesforce.Com, Inc. | System, method and computer program product for automatically presenting selectable options in a lookup field |
US8966110B2 (en) | 2009-09-14 | 2015-02-24 | International Business Machines Corporation | Dynamic bandwidth throttling |
US9367876B2 (en) | 2009-09-18 | 2016-06-14 | Salesforce.Com, Inc. | Systems and methods for multimedia multipoint real-time conferencing allowing real-time bandwidth management and prioritized media distribution |
US10482425B2 (en) | 2009-09-29 | 2019-11-19 | Salesforce.Com, Inc. | Techniques for managing functionality changes of an on-demand database system |
US8706715B2 (en) | 2009-10-05 | 2014-04-22 | Salesforce.Com, Inc. | Methods and systems for joining indexes for query optimization in a multi-tenant database |
US10229157B2 (en) | 2009-10-05 | 2019-03-12 | Salesforce.Com, Inc. | Implementing composite custom indices in a multi-tenant database |
US8621015B2 (en) | 2009-10-30 | 2013-12-31 | Salesforce.Com, Inc. | Integrating and managing social networking information in an on-demand database system |
WO2011060306A2 (en) | 2009-11-12 | 2011-05-19 | Salesforce.Com, Inc. | Enterprise level business information networking for changes in a database |
US8560575B2 (en) | 2009-11-12 | 2013-10-15 | Salesforce.Com, Inc. | Methods and apparatus for selecting updates to associated records to publish on an information feed in an on-demand database service environment |
US8443366B1 (en) | 2009-12-11 | 2013-05-14 | Salesforce.Com, Inc. | Techniques for establishing a parallel processing framework for a multi-tenant on-demand database system |
US8776067B1 (en) | 2009-12-11 | 2014-07-08 | Salesforce.Com, Inc. | Techniques for utilizing computational resources in a multi-tenant on-demand database system |
US9059851B2 (en) | 2010-02-23 | 2015-06-16 | Salesforce.Com, Inc. | Method and computer program product for order preserving symbol based encryption |
WO2011106308A2 (en) | 2010-02-23 | 2011-09-01 | Navia Systems, Inc. | Configurable circuitry for solving stochastic problems |
US8732663B2 (en) * | 2010-02-24 | 2014-05-20 | Salesforce.Com, Inc. | System, method and computer program product for providing automated testing by utilizing a preconfigured point of entry in a test or by converting a test to a predefined format |
US8898287B2 (en) | 2010-02-24 | 2014-11-25 | Salesforce.Com, Inc. | System, method and computer program product for monitoring data activity utilizing a shared data store |
US9600512B2 (en) | 2010-02-25 | 2017-03-21 | Salesforce.Com, Inc. | Systems and methods for implementing customized drop-down menus |
US9715555B2 (en) | 2010-02-26 | 2017-07-25 | Salesforce.Com, Inc. | System, method and computer program product for user registration with a multi-tenant on-demand database system |
US20110213789A1 (en) * | 2010-02-26 | 2011-09-01 | Salesforce.Com, Inc. | System, method and computer program product for determining an amount of access to data, based on a role |
US9251164B2 (en) * | 2010-02-26 | 2016-02-02 | Salesforce.Com, Inc. | System, method and computer program product for using a database to access content stored outside of the database |
US9405426B2 (en) | 2010-03-01 | 2016-08-02 | Salesforce.Com, Inc. | Method and system for providing an adaptive input user interface for data entry applications |
US8713043B2 (en) | 2010-03-01 | 2014-04-29 | Salesforce.Com, Inc. | System, method and computer program product for sharing a single instance of a database stored using a tenant of a multi-tenant on-demand database system |
US9471648B2 (en) | 2010-03-01 | 2016-10-18 | Salesforce.Com, Inc. | System, method and computer program product for displaying one or more data sets to a user |
US9477369B2 (en) * | 2010-03-08 | 2016-10-25 | Salesforce.Com, Inc. | System, method and computer program product for displaying a record as part of a selected grouping of data |
US8583587B2 (en) | 2010-03-08 | 2013-11-12 | Salesforce.Com, Inc. | System, method and computer program product for performing one or more actions utilizing a uniform resource locator |
US8898582B2 (en) | 2010-03-10 | 2014-11-25 | Salesforce.Com, Inc. | Configurable highlights panel for display of database records |
US8739030B2 (en) | 2010-03-10 | 2014-05-27 | Salesforce.Com, Inc. | Providing a quote template in a multi-tenant database system environment |
US8914539B2 (en) | 2010-03-12 | 2014-12-16 | Salesforce.Com, Inc. | Service cloud console |
US8930332B2 (en) | 2010-03-12 | 2015-01-06 | Salesforce.Com, Inc. | Method and system for partitioning search indexes |
US9117003B2 (en) * | 2010-03-12 | 2015-08-25 | Salesforce.Com, Inc. | System, method and computer program product for navigating content on a single page |
US9268955B2 (en) * | 2010-03-12 | 2016-02-23 | Salesforce.Com, Inc. | System, method and computer program product for conditionally sharing an object with one or more entities |
US8996610B1 (en) | 2010-03-15 | 2015-03-31 | Salesforce.Com, Inc. | Proxy system, method and computer program product for utilizing an identifier of a request to route the request to a networked device |
US9031996B2 (en) * | 2010-03-15 | 2015-05-12 | Salesforce.Com | System, method and computer program product for creating a plurality of CNAMES for a website |
US8688802B2 (en) | 2010-03-15 | 2014-04-01 | Salesforce.Com, Inc. | System, method and computer program product for serving an application from a custom subdomain |
US8793291B2 (en) * | 2010-03-15 | 2014-07-29 | Salesforce.Com, Inc. | System, method and computer program product for deploying an update between environments of a multi-tenant on-demand database system |
US9246707B2 (en) | 2010-03-16 | 2016-01-26 | Salesforce.Com, Inc. | Cost-based SMTP email routing |
US9098365B2 (en) * | 2010-03-16 | 2015-08-04 | Salesforce.Com, Inc. | System, method and computer program product for conditionally enabling an installation aspect |
US9111006B2 (en) * | 2010-03-16 | 2015-08-18 | Salesforce.Com, Inc. | System, method and computer program product for communicating data between a database and a cache |
US9009709B2 (en) | 2010-03-16 | 2015-04-14 | Salesforce.Com, Inc. | Asynchronous rollup numbers forecasting methods and systems |
US8370809B2 (en) | 2010-03-18 | 2013-02-05 | Salesforce.Com, Inc. | System, method and computer program product for automated test case generation and scheduling |
US8566917B2 (en) * | 2010-03-19 | 2013-10-22 | Salesforce.Com, Inc. | Efficient single sign-on and identity provider configuration and deployment in a database system |
US8930933B2 (en) * | 2010-03-19 | 2015-01-06 | Salesforce.Com, Inc. | System, method and computer program product for associating a plurality of stored elements with a creation of a patch |
US9037546B2 (en) * | 2010-03-25 | 2015-05-19 | Salesforce.Com, Inc. | System, method and computer program product for automatic code generation for database object deletion |
US9275033B2 (en) * | 2010-03-25 | 2016-03-01 | Salesforce.Com, Inc. | System, method and computer program product for creating an object within a system, utilizing a template |
US20110238705A1 (en) * | 2010-03-25 | 2011-09-29 | Salesforce.Com, Inc. | System, method and computer program product for extending a master-detail relationship |
US9053136B2 (en) * | 2010-03-26 | 2015-06-09 | Salesforce.Com, Inc. | Systems and methods for identifying contacts as users of a multi-tenant database and application system |
US8977675B2 (en) | 2010-03-26 | 2015-03-10 | Salesforce.Com, Inc. | Methods and systems for providing time and date specific software user interfaces |
US9361350B2 (en) | 2010-03-26 | 2016-06-07 | Salesforce.Com, Inc. | Data transfer between first and second databases |
US9189090B2 (en) | 2010-03-26 | 2015-11-17 | Salesforce.Com, Inc. | Techniques for interpreting signals from computer input devices |
US8539234B2 (en) | 2010-03-30 | 2013-09-17 | Salesforce.Com, Inc. | Secure client-side communication between multiple domains |
US9619652B2 (en) | 2010-03-31 | 2017-04-11 | Salesforce.Com, Inc. | System, method and computer program product for determining a risk score for an entity |
US8645341B2 (en) | 2010-03-31 | 2014-02-04 | Salesforce.Com, Inc. | Method and system for automatically updating a software QA test repository |
US9239722B1 (en) | 2010-03-31 | 2016-01-19 | Salesforce.Com, Inc. | System, method and computer program product for interacting with a process diagram |
US8924419B2 (en) | 2010-03-31 | 2014-12-30 | Salesforce.Com, Inc. | Method and system for performing an authority analysis |
US9767136B2 (en) | 2010-03-31 | 2017-09-19 | Salesforce.Com, Inc. | System, method and computer program product for maintaining data stored in a data structure |
US8646048B2 (en) | 2010-03-31 | 2014-02-04 | saleforce.com, inc | System, method and computer program product for authenticating and authorizing an external entity |
US9183088B2 (en) | 2010-03-31 | 2015-11-10 | Salesforce.Com, Inc. | Reducing database downtime |
US20110246524A1 (en) | 2010-04-01 | 2011-10-06 | Salesforce.Com, Inc. | System, method and computer program product for portal user data access in a multi-tenant on-demand database system |
US9195681B2 (en) | 2010-04-01 | 2015-11-24 | Salesforce.Com, Inc. | System, method and computer program product for transmitting a group of data elements |
US8818938B2 (en) | 2010-04-01 | 2014-08-26 | Salesforce.Com, Inc. | System, method and computer program product for synchronizing entities within a system |
US8925041B2 (en) | 2010-04-01 | 2014-12-30 | Salesforce.Com, Inc. | System, method and computer program product for performing one or more actions based on a determined access permissions for a plurality of users |
US8799327B2 (en) | 2010-04-01 | 2014-08-05 | Salesforce.Com, Inc. | System, method and computer program product for deriving commonalities among data entries |
US8965860B2 (en) | 2010-04-01 | 2015-02-24 | Salesforce.Com, Inc. | Methods and systems for bulk uploading of data in an on-demand service environment |
US8818985B2 (en) | 2010-04-06 | 2014-08-26 | Salesforce.Com, Inc. | Rule-based prioritization of social data |
US8793691B2 (en) | 2010-04-15 | 2014-07-29 | Salesforce.Com, Inc. | Managing and forwarding tasks to handler for processing using a message queue |
US9111031B2 (en) | 2010-04-16 | 2015-08-18 | Salesforce.Com, Inc. | Method and system for simulating and analyzing code execution in an on-demand service environment |
US10162851B2 (en) | 2010-04-19 | 2018-12-25 | Salesforce.Com, Inc. | Methods and systems for performing cross store joins in a multi-tenant store |
US10198463B2 (en) | 2010-04-16 | 2019-02-05 | Salesforce.Com, Inc. | Methods and systems for appending data to large data volumes in a multi-tenant store |
US8972953B2 (en) | 2010-04-16 | 2015-03-03 | Salesforce.Com, Inc. | Methods and systems for internally debugging code in an on-demand service environment |
US8666974B2 (en) | 2010-04-16 | 2014-03-04 | Salesforce.Com, Inc. | Methods and systems for performing high volume searches in a multi-tenant store |
US8447754B2 (en) | 2010-04-19 | 2013-05-21 | Salesforce.Com, Inc. | Methods and systems for optimizing queries in a multi-tenant store |
US9824108B2 (en) | 2010-04-19 | 2017-11-21 | Salesforce.Com, Inc. | Methods and systems for performing transparent object migration across storage tiers |
US8554793B2 (en) | 2010-04-19 | 2013-10-08 | Salesforce.Com, Inc. | Methods and systems for providing custom settings in an on-demand service environment |
US9189367B2 (en) | 2010-04-20 | 2015-11-17 | Salesforce.Com, Inc. | Methods and systems for debugging bytecode in an on-demand service environment |
US8584124B2 (en) | 2010-04-20 | 2013-11-12 | Salesforce.Com, Inc. | Methods and systems for batch processing in an on-demand service environment |
US8984009B2 (en) | 2010-04-21 | 2015-03-17 | Salesforce.Com, Inc. | Methods and systems for utilizing bytecode in an on-demand service environment including providing multi-tenant runtime environments and systems |
US8875152B2 (en) | 2010-04-22 | 2014-10-28 | Salesforce.Com, Inc. | System, method and computer program product for dynamically increasing resources utilized for processing tasks |
US9229793B2 (en) | 2010-04-22 | 2016-01-05 | Salesforce.Com, Inc. | System, method and computer program product for routing messages to a server |
US8751939B2 (en) | 2010-04-26 | 2014-06-10 | Salesforce.Com, Inc. | Side tab navigation and page views personalization systems and methods |
US8635250B2 (en) | 2010-04-26 | 2014-01-21 | Vinod Mehra | Methods and systems for deleting large amounts of data from a multitenant database |
US9411907B2 (en) | 2010-04-26 | 2016-08-09 | Salesforce.Com, Inc. | Method and system for performing searches in a multi-tenant database environment |
US8719243B2 (en) | 2010-04-27 | 2014-05-06 | Salesforce.Com, Inc. | Methods and systems for filtering data for interactive display of database data |
US9355270B2 (en) | 2010-04-28 | 2016-05-31 | Salesforce.Com, Inc. | Security configuration systems and methods for portal users in a multi-tenant database environment |
US8977739B2 (en) | 2010-05-03 | 2015-03-10 | Salesforce.Com, Inc. | Configurable frame work for testing and analysis of client-side web browser page performance |
US8930327B2 (en) | 2010-05-04 | 2015-01-06 | Salesforce.Com, Inc. | Method and system for scrubbing information from heap dumps |
US8972431B2 (en) | 2010-05-06 | 2015-03-03 | Salesforce.Com, Inc. | Synonym supported searches |
US8566792B2 (en) | 2010-05-07 | 2013-10-22 | Salesforce, Inc. | Validating visual components |
US9781049B2 (en) | 2010-05-07 | 2017-10-03 | Salesforce.Com, Inc. | Resolving information in a database environment |
US8693649B2 (en) | 2010-05-07 | 2014-04-08 | Salesforce.Com, Inc. | Methods and apparatus for interfacing with a phone system in an on-demand service environment |
US9009669B2 (en) | 2010-05-07 | 2015-04-14 | Salesforce.Com, Inc. | Visual user interface validator |
US8521780B2 (en) | 2010-05-07 | 2013-08-27 | Salesforce.Com, Inc. | Methods and systems for sharing email in a multi-tenant database system |
US8935193B2 (en) | 2010-05-07 | 2015-01-13 | Salesforce.Com, Inc. | Methods and systems for performing email management customizations in a multi-tenant database system |
US9230224B2 (en) | 2010-05-11 | 2016-01-05 | Salesforce.Com, Inc. | Providing a timeline control in a multi-tenant database environment |
US8839209B2 (en) | 2010-05-12 | 2014-09-16 | Salesforce.Com, Inc. | Software performance profiling in a multi-tenant environment |
US8566274B2 (en) | 2010-05-12 | 2013-10-22 | Salesforce.Com, Inc. | Methods and systems for implementing a compositional recommender framework |
US8549359B2 (en) | 2010-05-12 | 2013-10-01 | Salesforce.Com, Inc. | Method and system for identifying errors in code |
US8972439B2 (en) | 2010-05-13 | 2015-03-03 | Salesforce.Com, Inc. | Method and system for exploring objects in a data dictionary |
US8655867B2 (en) | 2010-05-13 | 2014-02-18 | Salesforce.Com, Inc. | Method and system for optimizing queries in a multi-tenant database environment |
US8583653B2 (en) | 2010-05-13 | 2013-11-12 | Salesforce.Com, Inc. | Methods and systems for determining candidates for a custom index in a multi-tenant database environment |
US8959483B2 (en) | 2010-05-13 | 2015-02-17 | Salesforce.Com, Inc. | Test framework of visual components in a multitenant database environment |
US8850219B2 (en) | 2010-05-13 | 2014-09-30 | Salesforce.Com, Inc. | Secure communications |
US8762340B2 (en) | 2010-05-14 | 2014-06-24 | Salesforce.Com, Inc. | Methods and systems for backing up a search index in a multi-tenant database environment |
US9141690B2 (en) | 2010-05-14 | 2015-09-22 | Salesforce.Com, Inc. | Methods and systems for categorizing data in an on-demand database environment |
US8752017B2 (en) | 2010-05-17 | 2014-06-10 | Salesforce.Com, Inc. | Method and system for remote debug protocol proxying for production debugging; selective session and user routing for debugging in multi-tenant cloud computing infrastructure |
US8676979B2 (en) | 2010-05-18 | 2014-03-18 | Salesforce.Com, Inc. | Methods and systems for efficient API integrated login in a multi-tenant database environment |
US8707264B2 (en) | 2010-05-18 | 2014-04-22 | Salesforce.Com, Inc. | Methods and systems for testing methods in a multi-tenant database environment |
US10417611B2 (en) | 2010-05-18 | 2019-09-17 | Salesforce.Com, Inc. | Methods and systems for providing multiple column custom indexes in a multi-tenant database environment |
US9075677B2 (en) | 2010-05-18 | 2015-07-07 | Salesforce.Com, Inc. | Methods and systems for automating deployment of applications in a database environment |
US9021435B2 (en) | 2010-05-20 | 2015-04-28 | Salesforce.Com, Inc. | Methods and systems for providing a user interface in a multi-tenant database environment |
US9275160B2 (en) | 2010-05-20 | 2016-03-01 | Salesforce.Com, Inc. | Performing an upgrade in a multi-tenant database system environment |
US8738603B2 (en) | 2010-05-20 | 2014-05-27 | Salesforce.Com, Inc. | Metrics-based accessing of social threads |
US20110289401A1 (en) | 2010-05-20 | 2011-11-24 | Salesforce.Com, Inc. | Multiple graphical annotations of documents using overlays |
US8566779B2 (en) | 2010-05-21 | 2013-10-22 | Salesforce.Com, Inc. | Visually prioritizing information in an agile system |
US9311664B2 (en) | 2010-05-25 | 2016-04-12 | Salesforce.Com, Inc. | Systems and methods for automatically collection of performance data in a multi-tenant database system environment |
US10599454B2 (en) | 2010-05-27 | 2020-03-24 | Salesforce.Com, Inc. | Database systems and related methods for validation workflows |
US8863119B2 (en) | 2010-05-27 | 2014-10-14 | Salesforce.Com, Inc. | Methods and systems for generating a dynamic workflow in a multi-tenant database environment |
US8386471B2 (en) | 2010-05-27 | 2013-02-26 | Salesforce.Com, Inc. | Optimizing queries in a multi-tenant database system environment |
US9262138B2 (en) | 2010-05-27 | 2016-02-16 | Salesforce.Com, Inc. | Adding directives for JavaScript files directly into source code in a multi-tenant database environment |
US8782605B2 (en) | 2010-05-28 | 2014-07-15 | Salesforce.Com, Inc. | Methods and systems for presenting different versions of an application |
US8694558B2 (en) | 2010-05-28 | 2014-04-08 | Salesforce.Com, Inc. | Methods and systems for tracking work in a multi-tenant database environment |
US8583964B2 (en) | 2010-05-28 | 2013-11-12 | Salesforce.Com, Inc. | Identifying bugs in a database system environment |
US8862632B2 (en) | 2010-05-28 | 2014-10-14 | Salesforce.Com, Inc. | Customizing standard formula fields in a multi-tenant database system environment |
US8572029B2 (en) | 2010-05-31 | 2013-10-29 | Salesforce.Com, Inc. | Methods and systems for synchronizing data in a multi-tenant database environment |
US8452726B2 (en) | 2010-06-04 | 2013-05-28 | Salesforce.Com, Inc. | Sharing information between tenants of a multi-tenant database |
US8572080B2 (en) | 2010-06-04 | 2013-10-29 | Salesforce.Com, Inc. | Methods and systems for analyzing a network feed in a multi-tenant database system environment |
US9426142B2 (en) | 2010-06-07 | 2016-08-23 | Salesforce.Com, Inc. | Systems and methods for logging into an application on a second domain from a first domain in a multi-tenant database system environment |
US9053231B2 (en) | 2010-06-07 | 2015-06-09 | Salesforce.Com, Inc. | Systems and methods for analyzing operations in a multi-tenant database system environment |
US9246699B2 (en) | 2010-06-07 | 2016-01-26 | Salesforce.Com, Inc. | Method and system for testing multiple components of a multi-tenant, multi-domain, multi-tiered website |
US8539068B2 (en) | 2010-06-07 | 2013-09-17 | Salesforce.Com, Inc. | Methods and systems for providing customized domain messages |
US8595382B2 (en) | 2010-06-07 | 2013-11-26 | Salesforce.Com, Inc. | System, method and computer program product for performing a synchronization of data |
US8407184B2 (en) | 2010-06-07 | 2013-03-26 | Salesforce.Com, Inc. | Maintaining applications that are occasionally connected to an online services system |
US8271837B2 (en) | 2010-06-07 | 2012-09-18 | Salesforce.Com, Inc. | Performing asynchronous testing of an application occasionally connected to an online services system |
US9223852B2 (en) | 2010-06-11 | 2015-12-29 | Salesforce.Com, Inc. | Methods and systems for analyzing search terms in a multi-tenant database system environment |
US8595207B2 (en) | 2010-06-14 | 2013-11-26 | Salesforce.Com | Methods and systems for dynamically suggesting answers to questions submitted to a portal of an online service |
US8230062B2 (en) | 2010-06-21 | 2012-07-24 | Salesforce.Com, Inc. | Referred internet traffic analysis system and method |
US9495282B2 (en) | 2010-06-21 | 2016-11-15 | Salesforce.Com, Inc. | Method and systems for a dashboard testing framework in an online demand service environment |
US9177070B2 (en) | 2010-06-21 | 2015-11-03 | Salesforce.Com, Inc. | System, method and computer program product for performing actions associated with a portal |
US9251204B2 (en) | 2010-06-23 | 2016-02-02 | Salesforce.Com, Inc. | Static query optimization |
US8620305B2 (en) | 2010-06-23 | 2013-12-31 | Salesforce.Com, Inc. | Methods and systems for a mobile device testing framework |
US8566956B2 (en) | 2010-06-23 | 2013-10-22 | Salesforce.Com, Inc. | Monitoring and reporting of data access behavior of authorized database users |
US10447729B2 (en) | 2010-06-24 | 2019-10-15 | Salesforce.Com, Inc. | Methods and systems for accessing a resource with multiple user identities |
US9442783B2 (en) | 2010-06-25 | 2016-09-13 | Salesforce.Com, Inc. | Methods and systems for providing security for page framing |
US9407603B2 (en) | 2010-06-25 | 2016-08-02 | Salesforce.Com, Inc. | Methods and systems for providing context-based outbound processing application firewalls |
US9350705B2 (en) | 2010-06-25 | 2016-05-24 | Salesforce.Com, Inc. | Methods and systems for providing a token-based application firewall correlation |
US9160710B2 (en) | 2010-06-25 | 2015-10-13 | Salesforce.Com, Inc. | Methods and systems for context-based application firewalls |
US9817637B2 (en) | 2010-07-01 | 2017-11-14 | Salesforce.Com, Inc. | Methods and systems for providing enhancements to a business networking feed |
US9280596B2 (en) | 2010-07-01 | 2016-03-08 | Salesforce.Com, Inc. | Method and system for scoring articles in an on-demand services environment |
US8832061B2 (en) | 2010-07-02 | 2014-09-09 | Salesforce.Com, Inc. | Optimizing data synchronization between mobile clients and database systems |
US8819632B2 (en) | 2010-07-09 | 2014-08-26 | Salesforce.Com, Inc. | Techniques for distributing information in a computer network related to a software anomaly |
US9529698B2 (en) | 2010-07-13 | 2016-12-27 | Salesforce.Com, Inc. | Method and system for multi-mode testing through operation interface and scenario abstraction in a multi-tenant database environment |
US8762881B2 (en) | 2010-07-15 | 2014-06-24 | Salesforce.Com, Inc. | Taking screenshots of a failed application |
US8510602B2 (en) | 2010-07-23 | 2013-08-13 | Salesforce.Com, Inc. | Testing a software application used in a database system |
US8738970B2 (en) | 2010-07-23 | 2014-05-27 | Salesforce.Com, Inc. | Generating performance alerts |
US8499286B2 (en) | 2010-07-27 | 2013-07-30 | Salesforce.Com, Inc. | Module testing adjustment and configuration |
US8701198B2 (en) | 2010-08-10 | 2014-04-15 | Salesforce.Com, Inc. | Performing security analysis on a software application |
US9507940B2 (en) | 2010-08-10 | 2016-11-29 | Salesforce.Com, Inc. | Adapting a security tool for performing security analysis on a software application |
US8812977B2 (en) | 2010-08-12 | 2014-08-19 | Salesforce.Com, Inc. | Accessing multi-page data using a page index in a scrollbar |
US8868981B2 (en) | 2010-08-12 | 2014-10-21 | Salesforce.Com, Inc. | On-demand services environment testing framework |
US8566654B2 (en) | 2010-08-13 | 2013-10-22 | Salesforce.Com, Inc. | Debugging site errors by an admin as a guest user in a multi-tenant database environment |
US8826451B2 (en) | 2010-08-16 | 2014-09-02 | Salesforce.Com, Inc. | Mechanism for facilitating communication authentication between cloud applications and on-premise applications |
US9069901B2 (en) | 2010-08-19 | 2015-06-30 | Salesforce.Com, Inc. | Software and framework for reusable automated testing of computer software systems |
US8904541B2 (en) | 2010-08-26 | 2014-12-02 | Salesforce.Com, Inc. | Performing security assessments in an online services system |
US8560541B2 (en) | 2010-08-26 | 2013-10-15 | Salesforce.Com, Inc. | Generating reports in an online services system |
US8566283B2 (en) | 2010-08-31 | 2013-10-22 | Salesforce.Com, Inc. | Changing records associated with a software application |
US9262393B2 (en) | 2010-08-31 | 2016-02-16 | Salesforce.Com, Inc. | Method and system for providing simplified form filling in an on-demand service |
US8739126B2 (en) | 2010-09-03 | 2014-05-27 | Salesforce.Com, Inc. | Web services environment testing framework |
US8769704B2 (en) | 2010-09-10 | 2014-07-01 | Salesforce.Com, Inc. | Method and system for managing and monitoring of a multi-tenant system |
US9619534B2 (en) | 2010-09-10 | 2017-04-11 | Salesforce.Com, Inc. | Probabilistic tree-structured learning system for extracting contact data from quotes |
US9058309B2 (en) | 2010-09-17 | 2015-06-16 | Salesforce.Com, Inc. | Methods and systems for multiple styling HyperText Markup Language (HTML) form fields |
US8504880B2 (en) | 2010-09-17 | 2013-08-06 | Salesforce.Com, Inc. | Mechanism for facilitating efficient error handling in a network environment |
US9106761B2 (en) | 2010-09-23 | 2015-08-11 | Salesforce.Com, Inc. | Methods and apparatus for inviting users to follow records in an on-demand database service environment |
US8732150B2 (en) | 2010-09-23 | 2014-05-20 | Salesforce.Com, Inc. | Methods and apparatus for suppressing network feed activities using an information feed in an on-demand database service environment |
US8661076B2 (en) | 2010-09-23 | 2014-02-25 | Salesforce.Com, Inc. | Business networking information feed alerts |
US8560554B2 (en) | 2010-09-23 | 2013-10-15 | Salesforce.Com, Inc. | Methods and apparatus for selecting updates to associated records to publish on an information feed using importance weights in an on-demand database service environment |
US8489929B2 (en) | 2010-09-30 | 2013-07-16 | Salesforce.Com, Inc. | Facilitating large-scale testing using virtualization technology in a multi-tenant database environment |
US9223892B2 (en) | 2010-09-30 | 2015-12-29 | Salesforce.Com, Inc. | Device abstraction for page generation |
US8898186B2 (en) | 2010-10-08 | 2014-11-25 | Salesforce.Com, Inc. | Methods and systems for latency-free contacts search |
US9031957B2 (en) | 2010-10-08 | 2015-05-12 | Salesforce.Com, Inc. | Structured data in a business networking feed |
US20120086544A1 (en) | 2010-10-08 | 2012-04-12 | Salesforce.Com, Inc. | Following Data Records in an Information Feed |
US8949939B2 (en) | 2010-10-13 | 2015-02-03 | Salesforce.Com, Inc. | Methods and systems for provisioning access to customer organization data in a multi-tenant system |
US8903770B2 (en) | 2010-10-15 | 2014-12-02 | Salesforce.Com, Inc. | Methods and apparatus for discontinuing the following of records in an on-demand database service environment |
US9304614B2 (en) | 2010-10-20 | 2016-04-05 | Salesforce.Com, Inc. | Framework for custom actions on an information feed |
US8732606B2 (en) | 2010-10-25 | 2014-05-20 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for dynamic windowing in user interfaces |
US20120102153A1 (en) | 2010-10-25 | 2012-04-26 | Salesforce.Com, Inc. | Triggering actions in an information feed system |
US8886766B2 (en) | 2010-10-25 | 2014-11-11 | Salesforce.Com, Inc. | Systems and methods for tracking responses on an online social network |
US8782238B2 (en) | 2010-11-05 | 2014-07-15 | Verizon Patent And Licensing Inc. | Server clustering in a computing-on-demand system |
US8819060B2 (en) | 2010-11-19 | 2014-08-26 | Salesforce.Com, Inc. | Virtual objects in an on-demand database environment |
US8682918B2 (en) | 2010-11-22 | 2014-03-25 | Salesforce.Com, Inc. | Method and system for making content-based recommendations |
US9690808B2 (en) | 2010-12-01 | 2017-06-27 | Salesforce.Com, Inc. | Methods and systems for loose coupling between triggers and entities |
US8533786B2 (en) | 2010-12-02 | 2013-09-10 | Salesforce.Com, Inc. | Method and apparatus for protecting against attacks from outside content |
US9021374B2 (en) | 2010-12-03 | 2015-04-28 | Salesforce.Com, Inc. | Systems and methods for generating a dashboard in a multi-tenant database system environment |
US10055702B2 (en) | 2010-12-03 | 2018-08-21 | Salesforce.Com, Inc. | Facilitating dynamic collection of data and generation of visual workflow in an on-demand services environment |
US8660881B2 (en) | 2010-12-03 | 2014-02-25 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic visual workflow and task generation in an on-demand services environment |
US9069448B2 (en) | 2010-12-03 | 2015-06-30 | Salesforce.Com, Inc. | Filtering objects in a multi-tenant environment |
US8566449B2 (en) | 2010-12-03 | 2013-10-22 | Salesforce.Com, Inc. | Method and system for validating configuration data in a multi-tenant environment |
US8498994B2 (en) | 2010-12-03 | 2013-07-30 | Salesforce.Com, Inc. | Social files |
US9465885B2 (en) | 2010-12-03 | 2016-10-11 | Salesforce.Com, Inc. | Method and system for providing information to a mobile handheld device from a database system |
US8566740B2 (en) | 2010-12-03 | 2013-10-22 | Salesforce.Com, Inc. | Interactive data forecasting features for a graphical user interface |
US8935360B2 (en) | 2010-12-03 | 2015-01-13 | Salesforce.Com, Inc. | Techniques for metadata-driven dynamic content serving |
US9965613B2 (en) | 2010-12-03 | 2018-05-08 | Salesforce.Com, Inc. | Method and system for user session discovery |
US8565422B2 (en) | 2010-12-03 | 2013-10-22 | Salesforce.Com, Inc. | Method and system for enryption key versioning and key rotation in a multi-tenant environment |
US20120151479A1 (en) | 2010-12-10 | 2012-06-14 | Salesforce.Com, Inc. | Horizontal splitting of tasks within a homogenous pool of virtual machines |
US8812630B2 (en) | 2011-01-24 | 2014-08-19 | Salesforce.Com, Inc. | Session table framework |
US8690666B2 (en) | 2011-01-24 | 2014-04-08 | Salesforce.Com, Inc. | Systems and methods for data valuation |
US9141983B2 (en) | 2011-02-01 | 2015-09-22 | Salesforce.Com, Inc. | Shared data sets combined with user-specific purchased data sets |
US10503728B2 (en) | 2011-02-01 | 2019-12-10 | Salesforce.Com, Inc. | Shared data set with user-specific changes |
US9275082B2 (en) | 2011-02-01 | 2016-03-01 | Salesforce.Com, Inc. | User-extensible common schema in a shared database |
US8566648B2 (en) | 2011-02-02 | 2013-10-22 | Salesforce, Inc. | Automated testing on devices |
US9276929B2 (en) | 2013-03-15 | 2016-03-01 | Salesforce.Com, Inc. | Method and apparatus for multi-domain authentication |
US8903943B2 (en) | 2011-02-15 | 2014-12-02 | Salesforce.Com, Inc. | Integrating cloud applications and remote jobs |
US8880487B1 (en) | 2011-02-18 | 2014-11-04 | Pegasystems Inc. | Systems and methods for distributed rules processing |
US8535162B2 (en) | 2011-02-18 | 2013-09-17 | Salesforce.Com, Inc. | Methods and systems for providing a challenge user interface for an enterprise social network |
US9646246B2 (en) | 2011-02-24 | 2017-05-09 | Salesforce.Com, Inc. | System and method for using a statistical classifier to score contact entities |
US9443224B2 (en) | 2011-03-01 | 2016-09-13 | Salesforce.Com, Inc. | Systems, apparatus and methods for selecting updates to associated records to publish on an information feed |
US8713165B2 (en) | 2011-03-03 | 2014-04-29 | Salesforce.Com, Inc. | Method and system for providing status of a machine |
US8949270B2 (en) | 2011-03-10 | 2015-02-03 | Salesforce.Com, Inc. | Methods and systems for processing social media data |
US8818940B2 (en) | 2011-03-29 | 2014-08-26 | Salesforce.Com, Inc. | Systems and methods for performing record actions in a multi-tenant database and application system |
US9396242B2 (en) | 2011-04-11 | 2016-07-19 | Salesforce.Com, Inc. | Multi-master data replication in a distributed multi-tenant system |
US9405896B2 (en) | 2011-04-12 | 2016-08-02 | Salesforce.Com, Inc. | Inter-application management of user credential data |
US9430583B1 (en) | 2011-06-10 | 2016-08-30 | Salesforce.Com, Inc. | Extracting a portion of a document, such as a web page |
US20120330924A1 (en) | 2011-06-21 | 2012-12-27 | Salesforce.Com, Inc. | Method and system for querying an on demand database service |
US9165036B2 (en) | 2011-06-21 | 2015-10-20 | Salesforce.Com, Inc. | Streaming transaction notifications |
US10324946B2 (en) | 2011-06-23 | 2019-06-18 | Salesforce.Com Inc. | Methods and systems for caching data shared between organizations in a multi-tenant database system |
US9069593B2 (en) | 2011-06-23 | 2015-06-30 | Salesforce.Com, Inc. | Systems and methods for deletion of untracked datastore paths |
US9864762B2 (en) | 2011-06-23 | 2018-01-09 | Salesforce.Com, Inc. | Systems and methods for mapping a value to a new domain |
US9208187B2 (en) | 2011-06-24 | 2015-12-08 | Salesforce.Com, Inc. | Using a database system for selective inclusion and exclusion of types of updates to provide a configuration feed of a social networking system |
US8838526B2 (en) | 2011-06-24 | 2014-09-16 | Salesforce.Com, Inc. | Systems and methods for supporting transactional message handling |
US9064339B2 (en) | 2011-06-28 | 2015-06-23 | Salesforce.Com, Inc. | Computer implemented systems and methods for providing a mobile social enterprise interface |
US8943011B2 (en) | 2011-06-28 | 2015-01-27 | Salesforce.Com, Inc. | Methods and systems for using map-reduce for large-scale analysis of graph-based data |
US9953273B2 (en) | 2011-06-28 | 2018-04-24 | Salesforce.Com, Inc. | Systems and methods for creating a rich social media profile |
US9468855B2 (en) | 2011-06-30 | 2016-10-18 | Salesforce.Com, Inc. | Systems and methods for creating and joining tournaments in a multi-tenant database system environment |
US9069788B2 (en) | 2011-07-01 | 2015-06-30 | Salesforce.Com, Inc. | Truncating data associated with objects in a multi-tenant database |
US8874593B2 (en) | 2011-07-01 | 2014-10-28 | Salesforce.Com, Inc. | Testing data silo |
US9123028B2 (en) | 2011-07-01 | 2015-09-01 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for controlling the inclusion of edited information in an information feed |
US9367431B2 (en) | 2011-07-01 | 2016-06-14 | Salesforce.Com, Inc. | Testing data silo |
US9015494B2 (en) | 2011-07-11 | 2015-04-21 | Salesforce.Com, Inc. | Methods and apparatus for digital steganography |
US9195971B2 (en) | 2011-07-12 | 2015-11-24 | Salesforce.Com, Inc. | Method and system for planning a meeting in a cloud computing environment |
US9395881B2 (en) | 2011-07-12 | 2016-07-19 | Salesforce.Com, Inc. | Methods and systems for navigating display sequence maps |
US9071658B2 (en) | 2011-07-12 | 2015-06-30 | Salesforce.Com, Inc. | Method and system for presenting a meeting in a cloud computing environment |
US8954449B2 (en) | 2011-07-12 | 2015-02-10 | Salesforce.Com, Inc. | Method and system for determining a user's brand influence |
US9229934B2 (en) | 2011-07-12 | 2016-01-05 | Salesforce.Com, Inc. | Method and system for document integration |
US9037681B2 (en) | 2011-07-12 | 2015-05-19 | Salesforce.Com, Inc. | Methods and systems for prioritizing multiple network feeds |
US9489660B2 (en) | 2011-07-12 | 2016-11-08 | Salesforce.Com, Inc. | Methods and systems for public collaborative interface for private network groups |
US10108648B2 (en) | 2011-07-13 | 2018-10-23 | Salesforce.Com, Inc. | Creating a custom index in a multi-tenant database environment |
US8935806B2 (en) | 2011-07-13 | 2015-01-13 | Salesforce.Com, Inc. | Mechanism for facilitating management of data in an on-demand services environment |
US9563712B2 (en) | 2011-07-14 | 2017-02-07 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing internal custom feed items |
US9443225B2 (en) | 2011-07-18 | 2016-09-13 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for presentation of feed items in an information feed to be displayed on a display device |
US8869114B2 (en) | 2011-07-18 | 2014-10-21 | Salesforce.Com, Inc. | Mechanism for facilitating customized data overriding for software programs in an on-demand services environment |
US8762870B2 (en) | 2011-07-19 | 2014-06-24 | Salesforce.Com, Inc. | Multifunction drag-and-drop selection tool for selection of data objects in a social network application |
US8910128B2 (en) | 2011-07-19 | 2014-12-09 | Salesforce.Com, Inc. | Methods and apparatus for application performance and capacity analysis |
US8521782B2 (en) | 2011-07-20 | 2013-08-27 | Salesforce.Com, Inc. | Methods and systems for processing large graphs using density-based processes using map-reduce |
US8984156B2 (en) | 2011-07-21 | 2015-03-17 | Salesforce.Com, Inc. | Multi-party mesh conferencing with stream processing |
US20130024910A1 (en) | 2011-07-22 | 2013-01-24 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for integrating a social network information feed with a network communications application |
US8620875B2 (en) | 2011-07-25 | 2013-12-31 | Salesforce.Com, Inc. | Fraud analysis in a contact database |
US9256859B2 (en) | 2011-07-26 | 2016-02-09 | Salesforce.Com, Inc. | Systems and methods for fragmenting newsfeed objects |
US8984051B2 (en) | 2011-07-26 | 2015-03-17 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for communicating feed information to one or more recipients |
US8713693B2 (en) | 2011-07-26 | 2014-04-29 | Salesforce.Com, Inc. | Secure access to customer log data in a multi-tenant environment |
US8972421B2 (en) | 2011-07-26 | 2015-03-03 | Salesforce.Com, Inc. | Systems and methods for propagating a global filter to individual datasets |
US8745625B2 (en) | 2011-07-26 | 2014-06-03 | Salesforce.Com, Inc. | System, method and computer program product for conditionally executing related reports in parallel based on an estimated execution time |
US9325750B2 (en) | 2011-07-26 | 2016-04-26 | Salesforce.Com, Inc. | Method and system for viewing a contact network feed in a business directory environment |
US9323634B2 (en) | 2011-07-26 | 2016-04-26 | Salesforce.Com, Inc. | Generating a configuration file based upon an application registry |
US9613326B2 (en) | 2011-07-26 | 2017-04-04 | Salesforce.Com, Inc. | Method and system for filtering common fields across multiple data sets |
US9189532B2 (en) | 2011-07-26 | 2015-11-17 | Salesforce.Com, Inc. | System, method and computer program product for locally defining related reports using a global definition |
US9195724B2 (en) | 2011-07-27 | 2015-11-24 | Salesforce.Com, Inc. | Associating objects in multi-tenant systems |
US10121110B2 (en) | 2011-07-27 | 2018-11-06 | Salesforce.Com, Inc. | System, method and computer program product for progressive rendering of report results |
US8954587B2 (en) | 2011-07-27 | 2015-02-10 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic load balancing at application servers in an on-demand services environment |
US9203934B2 (en) | 2011-08-01 | 2015-12-01 | Salesforce.com. inc. | Synchronization of clocks between two communication terminals using TCP/IP |
US8756588B2 (en) | 2011-08-01 | 2014-06-17 | Salesforce.Com, Inc | Contextual exception management in multi-tenant systems |
US8875120B2 (en) | 2011-08-01 | 2014-10-28 | Salesforce.Com, Inc. | Methods and apparatus for providing software bug-fix notifications for networked computing systems |
US8676864B2 (en) | 2011-08-19 | 2014-03-18 | Salesforce.Com, Inc. | Methods and systems for providing schema layout in an on-demand services environment |
US9591090B2 (en) | 2011-08-22 | 2017-03-07 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for sharing data of an information feed of an online social network |
US9395882B2 (en) | 2011-08-24 | 2016-07-19 | Salesforce.Com, Inc. | Systems and methods for promoting related lists |
US9569511B2 (en) | 2011-08-25 | 2017-02-14 | Salesforce.Com, Inc. | Dynamic data management |
US8683443B2 (en) | 2011-08-25 | 2014-03-25 | Salesforce.Com, Inc. | Streamlined methodology for resolving software integration conflicts |
US8549047B2 (en) | 2011-08-25 | 2013-10-01 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for feed-based case management |
US9280387B2 (en) | 2011-08-25 | 2016-03-08 | Salesforce.Com, Inc. | Systems and methods for assigning code lines to clusters with storage and other constraints |
US8725721B2 (en) | 2011-08-25 | 2014-05-13 | Salesforce.Com, Inc. | Personalizing scoping and ordering of object types for search |
US9215096B2 (en) | 2011-08-26 | 2015-12-15 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing communication between network domains in a service cloud |
US9535573B2 (en) | 2011-08-26 | 2017-01-03 | Salesforce.Com, Inc. | Systems and methods for dynamic list views and detail pages |
US8849887B2 (en) | 2011-08-29 | 2014-09-30 | Salesforce.Com, Inc. | Mechanism for facilitating spin mode-based dynamic updating of application servers in an on-demand services environment |
US8898656B2 (en) | 2011-08-29 | 2014-11-25 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic format transformation of software applications in an on-demand services environment |
US8959347B2 (en) | 2011-08-29 | 2015-02-17 | Salesforce.Com, Inc. | Methods and systems of data security in browser storage |
US8966440B2 (en) | 2011-08-29 | 2015-02-24 | Salesforce.Com, Inc. | Custom application creation in multi-tenant systems |
US8412178B2 (en) | 2011-08-30 | 2013-04-02 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic and segment-based monitoring of cellular network performance in an on-demand services environment |
US10158638B2 (en) | 2011-08-31 | 2018-12-18 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing access to an online social network |
US8677346B1 (en) * | 2011-09-27 | 2014-03-18 | Symantec Corporation | Providing installer package information to a user |
US9038074B2 (en) | 2011-10-04 | 2015-05-19 | Salesforce.Com, Inc. | System, method and computer program product for recursively executing a process control operation to use an ordered list of tags to initiate corresponding functional operations |
US8844013B2 (en) | 2011-10-04 | 2014-09-23 | Salesforce.Com, Inc. | Providing third party authentication in an on-demand service environment |
US9830435B2 (en) | 2011-10-04 | 2017-11-28 | Salesforce.Com, Inc. | Method and system for providing login as a service |
US10885179B2 (en) | 2011-10-05 | 2021-01-05 | Salesforce.Com, Inc. | Just-in-time user provisioning framework in a multitenant environment |
US9058363B2 (en) | 2011-10-07 | 2015-06-16 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing a distribution list of users in an online social network |
US9467424B2 (en) | 2011-10-07 | 2016-10-11 | Salesforce.Com, Inc. | Methods and systems for proxying data |
US9542711B2 (en) | 2011-10-07 | 2017-01-10 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing selective notifications in an online social network |
US9183090B2 (en) | 2011-10-10 | 2015-11-10 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a streaming platform IO pump and regulator |
US9276856B2 (en) | 2011-10-10 | 2016-03-01 | Salesforce.Com, Inc. | Slipstream bandwidth management algorithm |
US9589070B2 (en) | 2011-10-10 | 2017-03-07 | Salesforce.Com, Inc. | Method and system for updating a filter logic expression representing a boolean filter |
US9767132B2 (en) | 2011-10-10 | 2017-09-19 | Salesforce.Com, Inc. | Systems and methods for real-time de-duplication |
US9639616B2 (en) | 2011-10-10 | 2017-05-02 | Salesforce.Com, Inc. | Methods and systems for performing time-partitioned collaborative filtering |
US9727924B2 (en) | 2011-10-10 | 2017-08-08 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for informing a user of social network data when the data is relevant to the user |
US9007364B2 (en) | 2011-10-12 | 2015-04-14 | Salesforce.Com, Inc. | Augmented reality display apparatus and related methods using database record data |
US9195648B2 (en) | 2011-10-12 | 2015-11-24 | Salesforce.Com, Inc. | Multi-lingual knowledge base |
US9064287B2 (en) | 2011-10-13 | 2015-06-23 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing group-related social network information |
US8839448B2 (en) | 2011-10-18 | 2014-09-16 | Salesforce.Com, Inc. | Generation of a human readable output message in a format that is unreadable by a computer-based device |
US8924361B2 (en) | 2011-10-21 | 2014-12-30 | Salesforce.Com, Inc. | Monitoring entitlement usage in an on-demand system |
US8959114B2 (en) | 2011-10-21 | 2015-02-17 | Salesforce.Com, Inc. | Entitlement management in an on-demand system |
US9471666B2 (en) | 2011-11-02 | 2016-10-18 | Salesforce.Com, Inc. | System and method for supporting natural language queries and requests against a user's personal data cloud |
US9443007B2 (en) | 2011-11-02 | 2016-09-13 | Salesforce.Com, Inc. | Tools and techniques for extracting knowledge from unstructured data retrieved from personal data sources |
US9047070B2 (en) | 2011-11-03 | 2015-06-02 | Salesforce.Com, Inc. | System, method and computer program product for defining applications using metadata records created from an object specifying a predefined metadata format |
US9977814B2 (en) | 2011-11-04 | 2018-05-22 | Salesforce.Com, Inc. | Custom metadata in loosely coupled triggers |
US9152725B2 (en) | 2011-11-04 | 2015-10-06 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for configuring and performing a custom rule to process a preference indication |
US9830050B2 (en) | 2011-11-23 | 2017-11-28 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing a reminder regarding a feed item of a feed of an online social network |
US8763098B2 (en) | 2011-12-06 | 2014-06-24 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic and continuous testing of security assertion markup language credentials in an on-demand services environment |
US9195936B1 (en) | 2011-12-30 | 2015-11-24 | Pegasystems Inc. | System and method for updating or modifying an application without manual coding |
US20130185654A1 (en) | 2012-01-17 | 2013-07-18 | Salesforce.Com, Inc. | Systems and methods for mapping relevant personal connections |
US8812438B2 (en) | 2012-01-20 | 2014-08-19 | Salesforce.Com, Inc. | System, method and computer program product for synchronizing data using data identifying messages |
US9397521B2 (en) | 2012-01-20 | 2016-07-19 | Salesforce.Com, Inc. | Site management in an on-demand system |
US8996588B2 (en) | 2012-02-02 | 2015-03-31 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic management of assets in an on-demand services environment |
US9026563B2 (en) | 2012-02-02 | 2015-05-05 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic social media-based management of assets in an on-demand services environment |
US8731151B2 (en) | 2012-02-02 | 2014-05-20 | Salesforce.Com, Inc. | Methods and apparatus for partially updating a web page using an embedded iFrame |
US9306878B2 (en) | 2012-02-14 | 2016-04-05 | Salesforce.Com, Inc. | Intelligent automated messaging for computer-implemented devices |
US9330145B2 (en) | 2012-02-22 | 2016-05-03 | Salesforce.Com, Inc. | Systems and methods for context-aware message tagging |
US9477698B2 (en) | 2012-02-22 | 2016-10-25 | Salesforce.Com, Inc. | System and method for inferring reporting relationships from a contact database |
US9195835B2 (en) | 2012-03-01 | 2015-11-24 | Salesforce.Com, Inc. | System and method for initializing tokens in a dictionary encryption scheme |
US9503535B2 (en) | 2012-03-06 | 2016-11-22 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for automatically following entities in an online social network |
US9348614B2 (en) | 2012-03-07 | 2016-05-24 | Salesforce.Com, Inc. | Verification of shared display integrity in a desktop sharing system |
US10542043B2 (en) | 2012-03-08 | 2020-01-21 | Salesforce.Com.Inc. | System and method for enhancing trust for person-related data sources |
US9135556B2 (en) | 2012-03-08 | 2015-09-15 | Salesforce.Com, Inc. | System and method for fast evaluation of standing queries in conjunctive normal form |
US9626523B2 (en) | 2012-03-08 | 2017-04-18 | Salesforce.Com, Inc. | Systems and methods of audit trailing of data incorporation |
US10991000B2 (en) | 2012-03-09 | 2021-04-27 | Salesforce.Com, Inc. | Advertisement distribution system, method and computer program product using a multi-tenant on-demand database system |
US8996674B2 (en) | 2012-03-19 | 2015-03-31 | Salesforce.Com, Inc. | System, method and computer program product for SNMP based mobile device management |
US9832156B2 (en) | 2012-03-23 | 2017-11-28 | Salesforce.Com, Inc. | Social networking system communities and associated user privileges implemented using a database system |
US8938520B2 (en) | 2012-04-03 | 2015-01-20 | Salesforce.Com, Inc. | Methods and systems for smart adapters in a social media content analytics environment |
US9572614B2 (en) | 2012-04-03 | 2017-02-21 | Salesforce.Com, Inc. | Mechanism for facilitating user-controlled management of webpage elements for dynamic customization of information |
US9558277B2 (en) | 2012-04-04 | 2017-01-31 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for identifying topical influence in an online social network |
US9075889B2 (en) | 2012-04-09 | 2015-07-07 | Salesforce.Com, Inc. | Mechanism for facilitating user-controlled management of site network mapping and synchronization |
US9307006B2 (en) | 2012-04-11 | 2016-04-05 | Salesforce.Com, Inc. | System and method for synchronizing data objects in a cloud based social networking environment |
US9195726B2 (en) | 2012-04-17 | 2015-11-24 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic integration of disparate database architectures for efficient management of resources in an on-demand services environment |
US9361468B2 (en) | 2012-04-17 | 2016-06-07 | Salesforce.Com, Inc. | Method and system for granting access to secure data |
US9032488B2 (en) | 2012-04-17 | 2015-05-12 | Salesforce.Com, Inc. | Cross instance user authentication architecture |
US8996553B2 (en) | 2012-04-18 | 2015-03-31 | Salesforce.Com, Inc. | Mechanism for facilitating management and customization of lightweight objects in an on-demand services environment |
US8996569B2 (en) | 2012-04-18 | 2015-03-31 | Salesforce.Com, Inc. | Mechanism for facilitating evaluation of data types for dynamic lightweight objects in an on-demand services environment |
US9031956B2 (en) | 2012-04-18 | 2015-05-12 | Salesforce.Com, Inc. | Mechanism for facilitating conversion and correction of data types for dynamic lightweight objects via a user interface in an on-demand services environment |
US9262037B2 (en) | 2012-04-30 | 2016-02-16 | Salesforce.Com, Inc. | Selective capture of incoming email messages for diagnostic analysis |
US11010701B2 (en) | 2012-04-30 | 2021-05-18 | Salesforce.Com, Inc. | System and method for managing sales meetings |
US9753926B2 (en) | 2012-04-30 | 2017-09-05 | Salesforce.Com, Inc. | Extracting a portion of a document, such as a web page |
US9137172B2 (en) | 2012-05-02 | 2015-09-15 | Salesforce.Com, Inc. | Managing multiple proxy servers in a multi-tenant application system environment |
US8972336B2 (en) | 2012-05-03 | 2015-03-03 | Salesforce.Com, Inc. | System and method for mapping source columns to target columns |
US9197513B2 (en) | 2012-05-03 | 2015-11-24 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for representing a portion of a user interface as a network address |
US8973106B2 (en) | 2012-05-03 | 2015-03-03 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing permissions to users in an on-demand service environment |
US9110959B2 (en) | 2012-05-03 | 2015-08-18 | Salesforce.Com, Inc. | System and method for geo-location data type searching in an on demand environment |
US10621372B2 (en) | 2012-05-03 | 2020-04-14 | Salesforce.Com, Inc. | Method and system for generating database access objects |
US9628412B2 (en) | 2012-05-08 | 2017-04-18 | Salesforce.Com, Inc. | System and method for generic loop detection |
US9252976B2 (en) | 2012-05-09 | 2016-02-02 | Salesforce.Com, Inc. | Method and system for social media cooperation protocol |
US9094359B2 (en) | 2012-05-09 | 2015-07-28 | Salesforce.Com, Inc. | Method and system for inter-social network communications |
US9177007B2 (en) | 2012-05-14 | 2015-11-03 | Salesforce.Com, Inc. | Computer implemented methods and apparatus to interact with records using a publisher of an information feed of an online social network |
US9264388B2 (en) | 2012-05-18 | 2016-02-16 | Salesforce.Com, Inc. | Re-routing incoming email for a multi-tenant database system |
US9916592B2 (en) | 2012-05-18 | 2018-03-13 | Oracle International Corporation | Method and system for implementing implicit follow and automatic unfollow |
US9237156B2 (en) | 2012-05-21 | 2016-01-12 | Salesforce.Com, Inc. | Systems and methods for administrating access in an on-demand computing environment |
US8954923B2 (en) | 2012-05-22 | 2015-02-10 | Salesforce.Com, Inc. | Mechanism for facilitating dynamic interaction with development applications and tools an on-demand services enviroment |
US9378263B2 (en) | 2012-06-19 | 2016-06-28 | Salesforce.Com, Inc. | Method and system for creating indices and loading key-value pairs for NoSQL databases |
US9979587B2 (en) | 2012-06-19 | 2018-05-22 | Salesforce.Com, Inc. | Method and system for semi-synchronously exporting data |
US9479387B2 (en) | 2012-06-22 | 2016-10-25 | Salesforce.Com, Inc. | Methods and systems for priority-based notifications for mobile devices |
US9148438B2 (en) | 2012-06-25 | 2015-09-29 | Salesforce.Com, Inc. | System, method and computer program product for publishing non-malicious third party content to a data feed |
US9665331B2 (en) | 2012-06-25 | 2017-05-30 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for accepting late joiners with screen sharing |
US9715879B2 (en) | 2012-07-02 | 2017-07-25 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for selectively interacting with a server to build a local database for speech recognition at a device |
US10049131B2 (en) | 2012-07-02 | 2018-08-14 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for determining user access to custom metadata |
US10146510B2 (en) | 2012-07-02 | 2018-12-04 | Salesforce.Com, Inc. | Custom metametadata with packagable records |
US9766881B2 (en) | 2012-07-02 | 2017-09-19 | Salesforce.Com, Inc. | Social project management system and marketplace |
US9658933B2 (en) | 2012-07-02 | 2017-05-23 | Salesforce.Com, Inc. | Automatically modifying a test for a program on multiple electronic devices |
US10311107B2 (en) | 2012-07-02 | 2019-06-04 | Salesforce.Com, Inc. | Techniques and architectures for providing references to custom metametadata in declarative validations |
US9286343B2 (en) | 2012-07-03 | 2016-03-15 | Salesforce.Com, Inc. | Statistics mechanisms in multitenant database environments |
US9628493B2 (en) | 2012-07-03 | 2017-04-18 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for managing permission sets and validating user assignments |
US9383988B2 (en) | 2012-07-03 | 2016-07-05 | Salesforce, Inc. | System and method for using directed acyclic graph (DAG) for application updates |
US10447737B2 (en) | 2012-07-03 | 2019-10-15 | Salesforce.Com, Inc. | Delegating administration rights using application containers |
US9436701B2 (en) | 2012-07-03 | 2016-09-06 | Salesforce.Com, Inc. | Methods and systems for regulating user engagement |
US9241017B2 (en) | 2012-07-03 | 2016-01-19 | Salesforce.Com, Inc. | Systems and methods for cross domain service component interaction |
US9678935B2 (en) | 2012-07-09 | 2017-06-13 | Salesforce.Com, Inc. | Facilitating dynamic cross-block joining of reports in an on-demand services environment |
US10148603B2 (en) | 2012-07-12 | 2018-12-04 | Salesforce.Com, Inc. | Methods and systems for generating electronic messages based upon dynamic content |
US10482135B2 (en) | 2012-07-12 | 2019-11-19 | Salesforce.Com, Inc. | Facilitating dynamic generation and customization of software applications at client computing devices using server metadata in an on-demand services environment |
US9075766B2 (en) | 2012-07-12 | 2015-07-07 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for determining whether to continue relationships in an online social network |
US10146955B2 (en) | 2012-07-12 | 2018-12-04 | Salesforce.Com, Inc. | System and method for access control for data of heterogeneous origin |
US9245145B2 (en) | 2012-07-16 | 2016-01-26 | Salesforce.Com, Inc. | Methods and systems for regulating database activity |
US10097667B2 (en) | 2012-07-16 | 2018-10-09 | Salesforce.Com, Inc. | Methods and systems for regulating database activity |
US9268822B2 (en) | 2012-07-18 | 2016-02-23 | Salesforce.Com, Inc. | System and method for determining organizational hierarchy from business card data |
US9659059B2 (en) | 2012-07-20 | 2017-05-23 | Salesforce.Com, Inc. | Matching large sets of words |
US9619458B2 (en) | 2012-07-20 | 2017-04-11 | Salesforce.Com, Inc. | System and method for phrase matching with arbitrary text |
US10319046B2 (en) | 2012-07-20 | 2019-06-11 | Salesforce.Com, Inc. | System and method for aggregating social network feed information |
US9367626B2 (en) | 2012-07-23 | 2016-06-14 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for implementing a topical-based highlights filter |
US9984126B2 (en) | 2012-07-23 | 2018-05-29 | Salesforce.Com, Inc. | Identifying relevant feed items to display in a feed of an enterprise social networking system |
US9569060B2 (en) | 2012-07-25 | 2017-02-14 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for composing and batch publishing feed items in a feed-based interaction context |
US9886695B2 (en) | 2012-07-27 | 2018-02-06 | Salesforce.Com Inc. | Sales force automation system and method for real-time traveling salesperson location tracking and account visit selection |
US9432320B2 (en) | 2012-07-30 | 2016-08-30 | Salesforce.Com, Inc. | System and method for providing an information-centric application |
US9747388B2 (en) | 2012-08-31 | 2017-08-29 | Salesforce.Com, Inc. | Systems and methods for providing access to external content objects |
US8990958B2 (en) | 2012-08-31 | 2015-03-24 | Salesforce.Com, Inc. | Systems and methods for content management in an on demand environment |
US9990426B2 (en) | 2012-08-31 | 2018-06-05 | Salesforce.Com, Inc. | Systems and methods for content management in an on-demand environment |
US9292589B2 (en) | 2012-09-04 | 2016-03-22 | Salesforce.Com, Inc. | Identifying a topic for text using a database system |
US9830385B2 (en) | 2012-09-04 | 2017-11-28 | Salesforce.Com, Inc. | Methods and apparatus for partitioning data |
US9575871B2 (en) | 2012-09-04 | 2017-02-21 | Salesforce.Com, Inc. | System and method for dynamically debugging data in a multi-tenant database environment |
US9396231B2 (en) | 2012-09-04 | 2016-07-19 | Salesforce.Com, Inc. | Facilitating dynamically controlled fetching of data at client computing devices in an on-demand services environment |
US9569509B2 (en) | 2012-09-04 | 2017-02-14 | Salesforce.Com, Inc. | Optimizing result presentation of a database operation |
US9495342B2 (en) | 2012-09-05 | 2016-11-15 | Salesforce.Com, Inc. | System and method for automatically inserting correct escaping functions for field references in a multi-tenant computing environment |
US9442974B2 (en) | 2012-09-05 | 2016-09-13 | Salesforce.Com, Inc. | Systems, methods and techniques for polymorphic queries |
US9495430B2 (en) | 2012-09-06 | 2016-11-15 | Salesforce.Com | Systems and methods for batch processing of data records in an on-demand system |
US10460270B2 (en) | 2012-09-12 | 2019-10-29 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing cross-organizational processing of business intelligence metrics |
US10768983B2 (en) | 2012-09-12 | 2020-09-08 | Salesforce.Com, Inc. | Mechanism for facilitating a quorum-based coordination of broker health for management of resources for application servers in an on-demand services environment |
US10169090B2 (en) | 2012-09-12 | 2019-01-01 | Salesforce.Com, Inc. | Facilitating tiered service model-based fair allocation of resources for application servers in multi-tenant environments |
US10152511B2 (en) | 2012-09-14 | 2018-12-11 | Salesforce.Com, Inc. | Techniques for optimization of inner queries |
US9495403B2 (en) | 2012-09-14 | 2016-11-15 | Salesforce.Com, Inc. | Method and system for cleaning data in a customer relationship management system |
US20140082183A1 (en) | 2012-09-14 | 2014-03-20 | Salesforce.Com, Inc. | Detection and handling of aggregated online content using characterizing signatures of content items |
US9898519B2 (en) | 2012-09-14 | 2018-02-20 | Salesforce.Com, Inc. | Systems and methods of enriching CRM data with social data |
US9774555B2 (en) | 2012-09-14 | 2017-09-26 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for managing objectives in an organization in a social network environment |
US9977788B2 (en) | 2012-09-14 | 2018-05-22 | Salesforce.Com, Inc. | Methods and systems for managing files in an on-demand system |
US9553783B2 (en) | 2012-09-14 | 2017-01-24 | Salesforce.Com, Inc. | Spam flood detection methodologies |
US9424336B2 (en) | 2012-09-14 | 2016-08-23 | Salesforce.Com, Inc. | Facilitating distributed data processing for dynamic and efficient generation of search results in an on-demand services environment |
US9253283B2 (en) | 2012-09-14 | 2016-02-02 | Salesforce.Com, Inc. | Systems and methods for ghosting and providing proxies in a network feed |
US9503501B2 (en) | 2012-09-17 | 2016-11-22 | Salesforce.Com, Inc. | Cross domain in-browser proxy |
US10733358B2 (en) | 2012-09-17 | 2020-08-04 | Salesforce.Com, Inc. | Method and system for site migration |
US10089638B2 (en) | 2012-09-17 | 2018-10-02 | Salesforce, Inc. | Streamlined data entry paths using individual account context on a mobile device |
US9495557B2 (en) | 2012-09-18 | 2016-11-15 | Salesforce.Com, Inc. | Methods and systems for managing access to data in an on-demand system |
US9626637B2 (en) | 2012-09-18 | 2017-04-18 | Salesforce.Com, Inc. | Method and system for managing business deals |
US9069858B1 (en) | 2012-09-18 | 2015-06-30 | Salesforce.Com, Inc. | Systems and methods for identifying entity mentions referencing a same real-world entity |
US9495411B2 (en) | 2012-09-24 | 2016-11-15 | Salesforce.Com, Inc. | Increased parallelism performance of batch requests |
US9489415B2 (en) | 2012-09-27 | 2016-11-08 | Salesforce.Com, Inc. | System and method for updating infographics based on multiple online social networks |
US9634977B2 (en) | 2012-10-01 | 2017-04-25 | Salesforce.Com, Inc. | Systems and methods of redactive messaging |
US9442778B2 (en) | 2012-10-01 | 2016-09-13 | Salesforce.Com, Inc. | Method and system for secured inter-application communication in mobile devices |
US9418003B2 (en) | 2012-10-10 | 2016-08-16 | Salesforce.Com, Inc. | System, method and computer program product for conditionally performing garbage collection |
US9246959B2 (en) | 2012-10-10 | 2016-01-26 | Salesforce.Com, Inc. | System and method for location-based social network feeds |
US9185342B2 (en) | 2012-10-10 | 2015-11-10 | Salesforce.Com, Inc. | Systems and methods for implementing instant social image cobrowsing through the cloud |
US9076072B2 (en) | 2012-10-11 | 2015-07-07 | Salesforce.Com, Inc. | System and method for web page rendering test automation suite |
US9264391B2 (en) | 2012-11-01 | 2016-02-16 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing near real-time predicted engagement level feedback to a user composing a social media message |
US9479563B2 (en) | 2012-12-13 | 2016-10-25 | Salesforce.Com, Inc. | Adaptive configuration management databases |
US9171150B2 (en) | 2012-12-14 | 2015-10-27 | Salesforce.Com, Inc. | System and method for dynamic analysis tracking objects for application dataflow |
US9170908B2 (en) | 2012-12-14 | 2015-10-27 | Salesforce.Com, Inc. | System and method for dynamic analysis bytecode injection for application dataflow |
US9177137B2 (en) | 2012-12-14 | 2015-11-03 | Salesforce.Com, Inc. | System and method for dynamic analysis tracking object associations for application dataflow |
US9171169B2 (en) | 2012-12-14 | 2015-10-27 | Salesforce.Com, Inc. | System and method for dynamic analysis wrapper objects for application dataflow |
US9703815B2 (en) | 2012-12-17 | 2017-07-11 | Salesforce.Com, Inc. | Third party files in an on-demand database service |
US9185078B2 (en) | 2012-12-18 | 2015-11-10 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing cross organizational data sharing |
US10318924B2 (en) | 2012-12-18 | 2019-06-11 | salesforce.com,inc. | User interface date selectors for historical reports |
US9767133B2 (en) | 2012-12-18 | 2017-09-19 | Salesforce.Com, Inc. | Systems and methods for alternative change processes for changes to data objects |
US9727598B2 (en) | 2012-12-19 | 2017-08-08 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for fixing logical or physical corruption in databases using LSM trees |
US9195438B2 (en) | 2012-12-19 | 2015-11-24 | Salesforce.Com, Inc. | System, method and computer program product for creating an application within a system |
US9519801B2 (en) | 2012-12-19 | 2016-12-13 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing data masking via compression dictionaries |
US9195854B2 (en) | 2012-12-19 | 2015-11-24 | Salesforce.Com, Inc. | System and method for controlling the on and off state of features at runtime |
US10496640B2 (en) | 2012-12-19 | 2019-12-03 | Salesforce.Com, Inc. | Querying a not only structured query language (NoSQL) database using structured query language (SQL) commands |
US9495079B2 (en) | 2013-01-10 | 2016-11-15 | Salesforce.Com, Inc. | Persistent feeder component for displaying feed items received from information feeds of online social networks |
US9778820B2 (en) | 2013-01-18 | 2017-10-03 | Salesforce.Com, Inc. | Managing applications on a computing device |
US9607090B2 (en) | 2013-01-21 | 2017-03-28 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for recommending events |
US10175873B2 (en) | 2013-01-21 | 2019-01-08 | Salesforce.Com, Inc. | System and method for retrieving data based on scrolling velocity |
US9465828B2 (en) | 2013-01-22 | 2016-10-11 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for identifying similar labels using collaborative filtering |
US20140279629A1 (en) | 2013-03-12 | 2014-09-18 | Salesforce.Com, Inc. | System and method for generating an organization profile based on skill information |
US10860557B2 (en) | 2013-03-13 | 2020-12-08 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing change value indication and historical value comparison |
US20140280577A1 (en) | 2013-03-15 | 2014-09-18 | Salesforce.Com, Inc. | Systems and methods for interacting with an application in a publisher |
US9823813B2 (en) | 2013-03-15 | 2017-11-21 | Salesforce.Com, Inc. | Apparatus and methods for performing an action on a database record |
US10120914B2 (en) | 2013-03-15 | 2018-11-06 | Salesforce.Com, Inc. | Mechanism for facilitating improved searching |
US9594790B2 (en) | 2013-03-21 | 2017-03-14 | Salesforce.Com, Inc. | System and method for evaluating claims to update a record from conflicting data sources |
US9483526B2 (en) | 2013-03-21 | 2016-11-01 | Salesforce.Com, Inc. | Automatically subscribing users of an enterprise network to a record |
US9203881B2 (en) | 2013-03-25 | 2015-12-01 | Salesforce.Com, Inc. | Systems and methods of online social environment based translation of entity methods |
US10430332B2 (en) | 2013-03-25 | 2019-10-01 | Salesforce.Com, Inc. | System and method for performance tuning of garbage collection algorithms |
US9400840B2 (en) | 2013-03-25 | 2016-07-26 | Salesforce.Com, Inc. | Combining topic suggestions from different topic sources to assign to textual data items |
US9306906B2 (en) | 2013-03-25 | 2016-04-05 | Salesforce.Com, Inc. | Systems and methods for utilizing uni-directional inter-host communication in an air gap environment |
US9672575B2 (en) | 2013-04-03 | 2017-06-06 | Salesforce.Com, Inc. | Capturing information regarding an interaction to a database |
US9659303B2 (en) | 2013-04-03 | 2017-05-23 | Salesforce.Com, Inc. | System and method for handling gamification fraud |
US9521040B2 (en) | 2013-04-03 | 2016-12-13 | Salesforce.Com, Inc. | System and method for generic configuration management system application programming interface |
US9965524B2 (en) | 2013-04-03 | 2018-05-08 | Salesforce.Com, Inc. | Systems and methods for identifying anomalous data in large structured data sets and querying the data sets |
US9734187B2 (en) | 2013-04-03 | 2017-08-15 | Salesforce.Com, Inc. | Atomic transactions in a NOSQL database |
US9953301B2 (en) | 2013-04-03 | 2018-04-24 | Salesforce.Com, Inc. | Searchable screen sharing sessions |
US9246892B2 (en) | 2013-04-03 | 2016-01-26 | Salesforce.Com, Inc. | System, method and computer program product for managing access to systems, products, and data based on information associated with a physical location of a user |
US10019297B2 (en) | 2013-04-03 | 2018-07-10 | Salesforce.Com, Inc. | Systems and methods for implementing bulk handling in asynchronous processing |
US9448773B2 (en) | 2013-04-03 | 2016-09-20 | Salesforce.Com, Inc. | Systems and methods for implementing a uniform application user interface across a multi-tenant environment |
US10684752B2 (en) | 2013-04-12 | 2020-06-16 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for responding to actionable text patterns in a feed item |
US9398156B2 (en) | 2013-04-12 | 2016-07-19 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for managing agent workload in a customer service environment |
US10114873B2 (en) | 2013-04-17 | 2018-10-30 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for retrieving content related to a feed item of an online social network |
US9830398B2 (en) | 2013-04-17 | 2017-11-28 | Salesforce.Com, Inc. | System and method for associating dynamic objects with database records |
US9785560B2 (en) | 2013-04-19 | 2017-10-10 | Salesforce.Com, Inc. | Scene-isolated internet application |
US9542472B2 (en) | 2013-04-19 | 2017-01-10 | Salesforce.Com, Inc. | Facilitating collaboration on a record among a group of users of a feed-based enterprise network |
US11068492B2 (en) | 2013-04-19 | 2021-07-20 | Salesforce.Com, Inc. | Systems and methods for combined search and content creation |
US9953054B2 (en) | 2013-04-22 | 2018-04-24 | Salesforce.Com, Inc. | Systems and methods for implementing and maintaining sampled tables in a database system |
US9641349B2 (en) | 2013-04-22 | 2017-05-02 | Salesforce.Com, Inc. | Systems and methods of viral enablement of features by peer-to-peer connection |
US9460474B2 (en) | 2013-05-03 | 2016-10-04 | Salesforce.Com, Inc. | Providing access to a private resource in an enterprise social networking system |
US9647922B2 (en) | 2013-05-15 | 2017-05-09 | Salesforce, Inc. | Computer implemented methods and apparatus for trials onboarding |
US9529917B2 (en) | 2013-05-21 | 2016-12-27 | Saleforce.com, inc. | System and method for generating information feed based on contextual data |
US10430608B2 (en) | 2013-06-14 | 2019-10-01 | Salesforce.Com, Inc. | Systems and methods of automated compliance with data privacy laws |
US11314770B2 (en) | 2013-06-17 | 2022-04-26 | Salesforce.Com, Inc. | Database multiplexing architectures |
US9892177B2 (en) | 2013-07-11 | 2018-02-13 | Salesforce.Com, Inc. | Systems and methods for interacting with external content objects |
US9600155B2 (en) | 2013-07-15 | 2017-03-21 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for customizing a data interface in an on-demand service environment |
US9467434B2 (en) | 2013-07-15 | 2016-10-11 | Salesforce.Com, Inc. | Document rendering service |
US9875321B2 (en) | 2013-07-19 | 2018-01-23 | Salesforce.Com, Inc. | Geo-location custom indexes |
US9881076B2 (en) | 2013-07-22 | 2018-01-30 | Salesforce.Com, Inc. | Facilitating management of user queries and dynamic filtration of responses based on group filters in an on-demand services environment |
US9760620B2 (en) | 2013-07-23 | 2017-09-12 | Salesforce.Com, Inc. | Confidently adding snippets of search results to clusters of objects |
US10147054B2 (en) | 2013-07-26 | 2018-12-04 | Salesforce.Com, Inc. | Displaying content of an enterprise social network feed on a mobile device |
US9798813B2 (en) | 2013-07-31 | 2017-10-24 | Salesforce.Com, Inc. | Extensible person container |
US9866537B2 (en) | 2013-08-02 | 2018-01-09 | Salesforce.Com, Inc. | Systems and methods for long universal resource locator compression |
US9426249B2 (en) | 2013-08-05 | 2016-08-23 | Salesforce.Com, Inc. | Providing an improved web user interface framework for building web applications |
US9524157B2 (en) | 2013-08-06 | 2016-12-20 | Salesforce.Com, Inc. | Providing an improved web user interface framework for building web applications |
US9244660B2 (en) | 2013-08-13 | 2016-01-26 | Salesforce.Com, Inc. | Responsive self-service website template |
US9921724B2 (en) | 2013-08-15 | 2018-03-20 | Salesforce.Com, Inc. | Presenting data on a mobile device in communication with an on-demand database system |
US10191939B2 (en) | 2013-08-23 | 2019-01-29 | Salesforce.Com, Inc. | Systems and methods for social append |
US9973550B2 (en) | 2013-09-11 | 2018-05-15 | Salesforce.Com, Inc. | Systems and methods for applying intelligence and prioritization to calendared events |
US9972015B2 (en) | 2013-09-13 | 2018-05-15 | Salesforce.Com, Inc. | Methods and systems for facilitating customer support using a social post case feed and publisher |
US10089407B2 (en) | 2013-09-20 | 2018-10-02 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing analytics on demand functionality |
US11714923B2 (en) | 2013-09-26 | 2023-08-01 | Salesforce, Inc. | Methods and systems for protecting data integrity |
US20150095283A1 (en) * | 2013-09-27 | 2015-04-02 | Microsoft Corporation | Master schema shared across multiple tenants with dynamic update |
US10454843B2 (en) | 2013-10-09 | 2019-10-22 | Salesforce.Com, Inc. | Extensible mechanisms for workload shaping and anomaly mitigation |
US9898743B2 (en) | 2013-10-09 | 2018-02-20 | Salesforce.Com, Inc. | Systems and methods for automatic generation of a relationship management system |
US9898383B2 (en) | 2013-10-09 | 2018-02-20 | Salesforce.Com, Inc. | Techniques and mechanisms for managing and analyzing database query activities |
US9277432B2 (en) | 2013-10-09 | 2016-03-01 | Salesforce.Com, Inc. | Systems and methods for automated on-device performance testing of mobile applications |
US9703814B1 (en) | 2013-10-15 | 2017-07-11 | Amazon Technologies, Inc. | Local key-value database synchronization |
US10902004B2 (en) | 2013-10-16 | 2021-01-26 | Salesforce.Com, Inc. | Processing user-submitted updates based on user reliability scores |
US10423907B2 (en) | 2013-10-18 | 2019-09-24 | Salesforce.Com, Inc. | Geolocation based work data on a mobile device using a database system |
US10021205B2 (en) | 2013-10-22 | 2018-07-10 | Salesforce.Com, Inc. | Rules-based multipoint routing of real-time information using client-server architecture |
US9547689B2 (en) | 2013-10-24 | 2017-01-17 | Salesforce.Com, Inc. | Security descriptors for record access queries |
US10257259B2 (en) | 2013-10-25 | 2019-04-09 | Salesforce.Com, Inc. | Manifest schema to provide application flows |
US9590943B2 (en) | 2013-10-25 | 2017-03-07 | Salesforce.Com, Inc. | Offline prompts of online social network mentions |
US9665261B2 (en) | 2013-10-28 | 2017-05-30 | Salesforce.Com, Inc. | Providing a user interface for customizing state transitions of panes in a bounding window |
US9686348B2 (en) | 2013-10-28 | 2017-06-20 | Salesforce.Com, Inc. | Inter-entity connection maps |
US9152796B2 (en) | 2013-10-30 | 2015-10-06 | Salesforce.Com, Inc. | Dynamic analysis interpreter modification for application dataflow |
US10740413B2 (en) | 2013-10-30 | 2020-08-11 | Salesforce.Com, Inc. | System and method for user information management via a user interface page |
US10409808B2 (en) | 2013-10-30 | 2019-09-10 | Salesforce.Com, Inc. | System and method for metadata management via a user interface page |
US10332129B2 (en) | 2013-11-01 | 2019-06-25 | Salesforce.Com, Inc. | Methods and systems for processing a log file |
US10268721B2 (en) | 2013-11-07 | 2019-04-23 | Salesforce.Com, Inc | Protected handling of database queries |
US9529652B2 (en) | 2013-11-07 | 2016-12-27 | Salesforce.Com, Inc. | Triaging computing systems |
US10482094B2 (en) | 2013-11-08 | 2019-11-19 | Salesforce.Com, Inc. | Conditional selection of compound fields from structured objects |
US10482070B2 (en) | 2013-11-12 | 2019-11-19 | Salesforce.Com, Inc. | Form field creation systems and methods |
US10367649B2 (en) | 2013-11-13 | 2019-07-30 | Salesforce.Com, Inc. | Smart scheduling and reporting for teams |
US9893905B2 (en) | 2013-11-13 | 2018-02-13 | Salesforce.Com, Inc. | Collaborative platform for teams with messaging and learning across groups |
US10146597B2 (en) | 2013-11-14 | 2018-12-04 | Salesforce.Com, Inc. | Delegating handling of computing events of a mobile device application |
US10607165B2 (en) | 2013-11-14 | 2020-03-31 | Salesforce.Com, Inc. | Systems and methods for automatic suggestions in a relationship management system |
US10366056B2 (en) | 2013-11-15 | 2019-07-30 | Salesforce.Com, Inc. | Asynchronous search for big objects |
US11157859B2 (en) | 2013-11-15 | 2021-10-26 | Salesforce.Com, Inc. | Systems and methods for performance summary citations |
US10311364B2 (en) | 2013-11-19 | 2019-06-04 | Salesforce.Com, Inc. | Predictive intelligence for service and support |
US9798764B2 (en) | 2013-12-20 | 2017-10-24 | Salesforce.Com, Inc. | Identifying recurring sequences of user interactions with an application |
US10902459B2 (en) | 2013-12-31 | 2021-01-26 | Salesforce.Com, Inc. | Facilitating smart advertising on curated content-based networking websites in an on-demand services environment |
US10346882B2 (en) | 2014-01-02 | 2019-07-09 | Salesforce.Com, Inc. | System and method for aggregating web clipping data |
US10198490B2 (en) | 2014-01-06 | 2019-02-05 | Salesforce.Com, Inc. | Systems and methods for interactively configuring multiple conditions and multiple actions in a workflow application |
US9633100B2 (en) * | 2014-01-15 | 2017-04-25 | Dell Products, L.P. | System and method for data structure synchronization |
US10412016B2 (en) | 2014-01-30 | 2019-09-10 | Salesforce.Com, Inc. | Streaming information based on available bandwidth |
US9753703B2 (en) | 2014-02-04 | 2017-09-05 | Salesforce.Com, Inc. | Generating identifiers for user interface elements of a web page of a web application |
US9577835B2 (en) | 2014-02-07 | 2017-02-21 | Salesforce.Com, Inc. | Online chats without displaying confidential information |
US10324922B2 (en) | 2014-02-13 | 2019-06-18 | Salesforce.Com, Inc. | Providing a timeline of events regarding a database record |
US9813516B2 (en) | 2014-02-18 | 2017-11-07 | Salesforce.Com, Inc. | Transparent sharding of traffic across messaging brokers |
US9247051B2 (en) | 2014-02-28 | 2016-01-26 | Salesforce.Com, Inc. | Systems and methods for tracking and responding to mobile events in a relationship management system |
US10354264B2 (en) | 2014-03-24 | 2019-07-16 | Salesforce.Com, Inc. | Contact recommendations based on purchase history |
US10089286B2 (en) | 2014-03-25 | 2018-10-02 | Salesforce.Com, Inc. | Systems and methods for collaborative editing of interactive walkthroughs of content |
US10169396B2 (en) | 2014-03-27 | 2019-01-01 | Salesforce.Com, Inc. | Maintaining data consistency between transactional and non-transactional data stores |
US9983943B2 (en) | 2014-03-27 | 2018-05-29 | Salesforce.Com, Inc. | Reversing object manipulations in association with a walkthrough for an application or online service |
US9501661B2 (en) | 2014-06-10 | 2016-11-22 | Salesforce.Com, Inc. | Systems and methods for implementing an encrypted search index |
US9294719B2 (en) | 2014-06-30 | 2016-03-22 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing in-app live support functionality |
US9519630B2 (en) | 2014-06-30 | 2016-12-13 | Salesforce.Com, Inc. | Fast CSS parser engineered for runtime use |
US10423611B2 (en) | 2014-07-30 | 2019-09-24 | Salesforce.Com, Inc. | Advanced searching of relational data via a mobile device |
US10339126B2 (en) | 2014-08-11 | 2019-07-02 | Salesforce.Com, Inc. | Processing log files using a database system |
US9509715B2 (en) | 2014-08-21 | 2016-11-29 | Salesforce.Com, Inc. | Phishing and threat detection and prevention |
US9774603B2 (en) | 2014-08-22 | 2017-09-26 | Salesforce.Com, Inc. | Managing user permissions in relation to system events occurring in a database system |
US9865313B2 (en) | 2014-08-22 | 2018-01-09 | Salesforce.Com, Inc. | System and method for dynamic caching |
US9538377B2 (en) | 2014-08-22 | 2017-01-03 | Salesforce.Com, Inc. | Switching between restricted-access websites on mobile user devices |
US9632852B2 (en) | 2014-08-25 | 2017-04-25 | Salesforce.Com, Inc. | Detecting and managing flooding of multi-tenant message queues |
US10296753B2 (en) | 2014-08-26 | 2019-05-21 | Salesforce.Com, Inc. | Permission comparator |
US10223367B2 (en) | 2014-08-27 | 2019-03-05 | Salesforce.Com, Inc. | Distributed sorting of event log files |
US9349101B2 (en) | 2014-08-29 | 2016-05-24 | Salesforce.Com, Inc. | Systems and methods for partitioning sets of features for a bayesian classifier |
US9805051B2 (en) | 2014-09-10 | 2017-10-31 | Salesforce.Com, Inc. | Synchronization and strategic storage of multiple versions of a file |
US10178156B2 (en) | 2014-09-11 | 2019-01-08 | Salesforce.Com, Inc. | Extraction and capture of information from customizable header |
US9619655B2 (en) | 2014-09-12 | 2017-04-11 | Salesforce.Com, Inc. | Cloud-based security profiling, threat analysis and intelligence |
US10491398B2 (en) | 2014-09-12 | 2019-11-26 | Salesforce.Com, Inc. | Facilitating dynamic end-to-end integrity for data repositories in an on-demand services environment |
US9729556B2 (en) | 2014-09-12 | 2017-08-08 | Salesforce.Com, Inc. | Digital badging for facilitating virtual recognition of an achievement |
US9417840B2 (en) | 2014-09-16 | 2016-08-16 | Salesforce.Com, Inc. | In-memory buffer service |
US10209973B2 (en) | 2014-09-16 | 2019-02-19 | Salesforce.Com, Inc. | Private application distribution mechanisms and architectures |
US10114627B2 (en) | 2014-09-17 | 2018-10-30 | Salesforce.Com, Inc. | Direct build assistance |
US9774688B2 (en) | 2014-09-18 | 2017-09-26 | Salesforce.Com, Inc. | Discovery of server functions |
US9460442B2 (en) | 2014-09-19 | 2016-10-04 | Salesforce.Com, Inc. | Sensor data gathering |
US10204120B2 (en) | 2014-09-19 | 2019-02-12 | Salesforce.Com, Inc. | Error checking database records |
US9158786B1 (en) | 2014-10-01 | 2015-10-13 | Bertram Capital Management, Llc | Database selection system and method to automatically adjust a database schema based on an input data |
US10095797B2 (en) | 2014-10-03 | 2018-10-09 | Salesforce.Com, Inc. | Suggesting actions for evaluating user performance in an enterprise social network |
US10133795B2 (en) | 2014-10-06 | 2018-11-20 | Salesforce.Com, Inc. | Personalized metric tracking |
US9710127B2 (en) | 2014-10-09 | 2017-07-18 | Salesforce.Com, Inc. | User-customizable permissions in a computing environment |
US10341279B2 (en) | 2014-10-09 | 2019-07-02 | Salesforce.Com, Inc. | Action links |
US10469396B2 (en) | 2014-10-10 | 2019-11-05 | Pegasystems, Inc. | Event processing with enhanced throughput |
US10290127B2 (en) | 2014-10-10 | 2019-05-14 | Saleforce.com, inc. | Responsive line display |
US10120544B2 (en) | 2014-10-10 | 2018-11-06 | Salesforce.Com, Inc. | Chart selection tooltip |
US10049141B2 (en) | 2014-10-10 | 2018-08-14 | salesforce.com,inc. | Declarative specification of visualization queries, display formats and bindings |
US9716730B2 (en) | 2014-10-10 | 2017-07-25 | Salesforce.Com, Inc. | System, method and computer program product for sharing content via links |
US10438168B2 (en) | 2014-10-10 | 2019-10-08 | Salesforce.Com, Inc. | Facilitating dynamic customization of reporting tools in an on-demand services environment |
US10592841B2 (en) | 2014-10-10 | 2020-03-17 | Salesforce.Com, Inc. | Automatic clustering by topic and prioritizing online feed items |
US9984166B2 (en) | 2014-10-10 | 2018-05-29 | Salesforce.Com, Inc. | Systems and methods of de-duplicating similar news feed items |
US9462002B2 (en) | 2014-10-10 | 2016-10-04 | Salesforce.Com, Inc. | System, method, and computer program product for sharing files based on user profile visibility |
US9756110B2 (en) | 2014-10-10 | 2017-09-05 | Salesforce.Com, Inc. | Systems and methods for optimizing web page load time |
US10491664B2 (en) | 2014-10-13 | 2019-11-26 | Salesforce.Com, Inc. | Asynchronous web service callouts and servlet handling |
US9740743B2 (en) | 2014-10-20 | 2017-08-22 | Salesforce.Com, Inc. | Matching objects using keys based on match rules |
US10083488B2 (en) | 2014-10-23 | 2018-09-25 | Salesforce.Com, Inc. | Purchasing contact information from an electronically displayed map |
US10904122B2 (en) | 2014-10-28 | 2021-01-26 | Salesforce.Com, Inc. | Facilitating workload-aware shuffling and management of message types in message queues in an on-demand services environment |
US10776373B2 (en) | 2014-10-28 | 2020-09-15 | Salesforce.Com, Inc. | Facilitating elastic allocation of organization-specific queue resources in an on-demand services environment |
US10491537B2 (en) | 2014-10-28 | 2019-11-26 | Salesforce.Com, Inc. | Facilitating dynamic hierarchical management of queue resources in an on-demand services environment |
US20160117318A1 (en) | 2014-10-28 | 2016-04-28 | Salesforce.Com, Inc. | Facilitating dynamically unified system of record in an on-demand services environment |
US10110533B2 (en) | 2014-10-28 | 2018-10-23 | Salesforce.Com, Inc. | Identifying entities in email signature blocks |
US9544307B2 (en) | 2014-10-29 | 2017-01-10 | Salesforce.Com, Inc. | Providing a security mechanism on a mobile device |
US10120848B2 (en) | 2014-12-09 | 2018-11-06 | Salesforce.Com, Inc. | Methods and systems for applying responsive design to subframes on a web page |
US9646064B2 (en) | 2014-12-10 | 2017-05-09 | Salesforce.Com, Inc. | Template based software container |
US9792008B2 (en) | 2014-12-16 | 2017-10-17 | Salesforce.Com, Inc. | User interface with analytics overlay |
US10489405B2 (en) | 2014-12-18 | 2019-11-26 | Salesforce.Com, Inc. | Data extraction using object relationship templates |
US10552464B2 (en) | 2014-12-18 | 2020-02-04 | Salesforce.Com, Inc. | Identifying relevant material for cases |
US9805427B2 (en) | 2015-01-29 | 2017-10-31 | Salesforce.Com, Inc. | Systems and methods of data mining to customize software trial demonstrations |
US9766960B2 (en) | 2015-01-30 | 2017-09-19 | Salesforce.Com, Inc. | Workload-driven techniques for providing biased service level guarantees |
US9785620B2 (en) | 2015-02-05 | 2017-10-10 | Salesforce.Com, Inc. | Creating linked communications |
US9965541B2 (en) | 2015-02-24 | 2018-05-08 | Salesforce.Com, Inc. | Interest groups based on network feed items |
US10175999B2 (en) | 2015-02-25 | 2019-01-08 | Salesforce.Com, Inc. | Converting video into a walkthrough for an application or an online service |
US10541811B2 (en) | 2015-03-02 | 2020-01-21 | Salesforce.Com, Inc. | Systems and methods for securing data |
US10374987B2 (en) | 2015-03-11 | 2019-08-06 | Salesforce.Com, Inc. | Electronic notifications of users concurrently interacting with the same feed item of a social network feed |
US10713594B2 (en) | 2015-03-20 | 2020-07-14 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing machine learning model training and deployment with a rollback mechanism |
US9762520B2 (en) | 2015-03-31 | 2017-09-12 | Salesforce.Com, Inc. | Automatic generation of dynamically assigned conditional follow-up tasks |
US10021089B2 (en) | 2015-04-09 | 2018-07-10 | Salesforce.Com, Inc. | Customized user validation |
US9940411B2 (en) | 2015-04-17 | 2018-04-10 | Salesforce.Com, Inc. | Systems and methods of bypassing suppression of event bubbling for popup controls |
US10031730B2 (en) | 2015-04-22 | 2018-07-24 | Salesforce.Com, Inc. | Systems and methods of implementing extensible browser executable components |
US10353905B2 (en) | 2015-04-24 | 2019-07-16 | Salesforce.Com, Inc. | Identifying entities in semi-structured content |
US10452244B2 (en) | 2015-05-04 | 2019-10-22 | Salesforce.Com, Inc. | Systems and methods of optimizing delivery of form factor specific content |
US10397309B2 (en) | 2015-05-13 | 2019-08-27 | Salesforce.Com, Inc. | Systems and methods of implementing tracking of resource usage for a cloud-based system |
US10296717B2 (en) | 2015-05-14 | 2019-05-21 | Salesforce.Com, Inc. | Automated prescription workflow for device management |
US11227261B2 (en) | 2015-05-27 | 2022-01-18 | Salesforce.Com, Inc. | Transactional electronic meeting scheduling utilizing dynamic availability rendering |
US10235476B2 (en) | 2015-05-28 | 2019-03-19 | Salesforce.Com, Inc. | Matching objects using match rules and lookup key |
US10083236B2 (en) | 2015-05-29 | 2018-09-25 | Salesforce.Com, Inc. | Database searching using a graph of nodes and edges formed using log node pairs |
US10210218B2 (en) | 2015-06-16 | 2019-02-19 | Salesforce.Com, Inc. | Processing a file to generate a recommendation using a database system |
US9773050B2 (en) | 2015-06-19 | 2017-09-26 | Salesforce.Com, Inc. | User interface for aggregated task data |
US10296440B2 (en) | 2015-06-24 | 2019-05-21 | Salesforce.Com, Inc. | Multi-tenant aware debugging methods and systems |
US10909575B2 (en) | 2015-06-25 | 2021-02-02 | Salesforce.Com, Inc. | Account recommendations for user account sets |
US10715626B2 (en) | 2015-06-26 | 2020-07-14 | Salesforce.Com, Inc. | Account routing to user account sets |
US9979689B2 (en) | 2015-06-29 | 2018-05-22 | Salesforce.Com, Inc. | Authoring tool for creating new electronic posts |
US10180837B2 (en) | 2015-07-20 | 2019-01-15 | Salesforce.Com, Inc. | Version control and management |
US10152489B2 (en) | 2015-07-24 | 2018-12-11 | Salesforce.Com, Inc. | Synchronize collaboration entity files |
US9948743B2 (en) | 2015-07-28 | 2018-04-17 | Salesforce.Com, Inc. | Managing memory usage in server systems |
US9811444B2 (en) | 2015-08-04 | 2017-11-07 | Salesforce.Com, Inc. | Testing software enhancements in database applications |
US9990223B2 (en) | 2015-08-10 | 2018-06-05 | Salesforce.Com, Inc. | Systems and methods of improving parallel functional processing |
US10157196B2 (en) | 2015-08-12 | 2018-12-18 | Salesforce.Com, Inc. | Intra-platform data migration |
US10270753B2 (en) | 2015-08-14 | 2019-04-23 | Salesforce.Com, Inc. | Background authentication refresh |
US9923960B2 (en) | 2015-08-18 | 2018-03-20 | Salesforce.Com, Inc. | Partition balancing in an on-demand services environment |
US9420104B1 (en) | 2015-08-18 | 2016-08-16 | Salesforce.Com, Inc. | Systems and methods for an omni-channel routing broker |
US9710638B2 (en) | 2015-08-28 | 2017-07-18 | Salesforce.Com, Inc. | Unicode-based image generation and testing |
US9619642B2 (en) | 2015-08-28 | 2017-04-11 | Salesforce.Com, Inc. | Unicode-based image generation and testing |
US9710637B2 (en) | 2015-08-28 | 2017-07-18 | Salesforce.Com, Inc. | Unicode-based image generation and testing |
US10515326B2 (en) | 2015-08-28 | 2019-12-24 | Exacttarget, Inc. | Database systems and related queue management methods |
US10235637B2 (en) | 2015-08-28 | 2019-03-19 | Salesforce.Com, Inc. | Generating feature vectors from RDF graphs |
US10049337B2 (en) | 2015-08-31 | 2018-08-14 | Salesforce.Com, Inc. | Quantitative metrics for assessing status of a platform architecture for cloud computing |
US9767040B2 (en) | 2015-08-31 | 2017-09-19 | Salesforce.Com, Inc. | System and method for generating and storing real-time analytics metric data using an in memory buffer service consumer framework |
US10372421B2 (en) | 2015-08-31 | 2019-08-06 | Salesforce.Com, Inc. | Platform provider architecture creation utilizing platform architecture type unit definitions |
US10572820B2 (en) | 2015-09-02 | 2020-02-25 | Salesforce.Com, Inc. | Evaluating personalized recommendation models |
US10198484B2 (en) | 2015-09-10 | 2019-02-05 | Salesforce.Com, Inc. | Displaying reduced and detailed visual representations of calendar items based on mouse cursor movement |
US10296661B2 (en) | 2015-09-11 | 2019-05-21 | Salesforce.Com, Inc. | Processing log files using a database system |
US10387439B2 (en) | 2015-09-11 | 2019-08-20 | Salesforce.Com, Inc. | Configuring service consoles based on service feature templates using a database system |
US10430765B2 (en) | 2015-09-11 | 2019-10-01 | Salesforce.Com, Inc. | Processing keyboard input to perform events in relation to calendar items using a web browser-based application or online service |
US10592474B2 (en) | 2015-09-11 | 2020-03-17 | Salesforce.Com, Inc. | Processing log files using a database system |
US10114737B2 (en) | 2015-09-14 | 2018-10-30 | Salesforce.Com, Inc. | Methods and systems for computing code coverage using grouped/filtered source classes during testing of an application |
US9905034B2 (en) | 2015-09-14 | 2018-02-27 | Salesforce.Com, Inc. | Secure isolation of scripting from native graphic rendering of animated data visualizations |
US10261890B2 (en) | 2015-09-14 | 2019-04-16 | Salesforce.Com, Inc. | Methods and systems for executing tests using grouped/filtered test classes during testing of an application |
US10146915B2 (en) | 2015-09-14 | 2018-12-04 | Salesforce.Com, Inc. | Publication of collaborative file to library |
US9658801B2 (en) | 2015-09-15 | 2017-05-23 | Salesforce.Com, Inc. | System having in-memory buffer service, temporary events file storage system and backup events file uploader service |
US10115213B2 (en) | 2015-09-15 | 2018-10-30 | Salesforce, Inc. | Recursive cell-based hierarchy for data visualizations |
US10191768B2 (en) | 2015-09-16 | 2019-01-29 | Salesforce.Com, Inc. | Providing strong ordering in multi-stage streaming processing |
US10324773B2 (en) | 2015-09-17 | 2019-06-18 | Salesforce.Com, Inc. | Processing events generated by internet of things (IoT) |
US10756991B2 (en) | 2015-09-17 | 2020-08-25 | Salesforce.Com, Inc. | Simplified entity engagement automation |
US9842000B2 (en) | 2015-09-18 | 2017-12-12 | Salesforce.Com, Inc. | Managing processing of long tail task sequences in a stream processing framework |
US9946593B2 (en) | 2015-09-18 | 2018-04-17 | Salesforce.Com, Inc. | Recovery strategy for a stream processing system |
US9965330B2 (en) | 2015-09-18 | 2018-05-08 | Salesforce.Com, Inc. | Maintaining throughput of a stream processing framework while increasing processing load |
US10146592B2 (en) | 2015-09-18 | 2018-12-04 | Salesforce.Com, Inc. | Managing resource allocation in a stream processing framework |
US10089368B2 (en) | 2015-09-18 | 2018-10-02 | Salesforce, Inc. | Systems and methods for making visual data representations actionable |
US10325107B2 (en) | 2015-09-23 | 2019-06-18 | Salesforce.Com, Inc. | Systems and methods for securing data using encryption |
US9977797B2 (en) | 2015-09-28 | 2018-05-22 | Salesforce.Com, Inc. | Combined directed graphs |
US10331689B2 (en) | 2015-10-01 | 2019-06-25 | Salesforce.Com, Inc. | Methods and apparatus for presenting search results according to a priority order determined by user activity |
US11120015B2 (en) | 2015-10-05 | 2021-09-14 | Salesforce.Com, Inc. | Importing data using a mobile computing device |
US10528211B2 (en) | 2015-10-08 | 2020-01-07 | Salesforce.Com, Inc. | Computing systems and processes for simultaneous co-development of dashboard interfaces |
US10389774B2 (en) | 2015-10-09 | 2019-08-20 | Salesforce.Com, Inc. | System for broadcasting events |
US10101870B2 (en) * | 2015-10-16 | 2018-10-16 | Microsoft Technology Licensing, Llc | Customizing program features on a per-user basis |
US10915299B2 (en) | 2015-10-16 | 2021-02-09 | Salesforce.Com, Inc. | Automatically matching start criteria and completion criteria of a walkthrough for an application or online service |
US10936611B2 (en) | 2015-10-30 | 2021-03-02 | Salesforce.Com, Inc. | Search promotion systems and method |
US10324991B2 (en) | 2015-10-30 | 2019-06-18 | Salesforce.Com, Inc. | Search promotion systems and method |
US10223389B2 (en) | 2015-11-03 | 2019-03-05 | Salesforce.Com, Inc. | System and method for analyzing complex metadata |
US9766965B2 (en) | 2015-11-25 | 2017-09-19 | Salesforce.Com, Inc. | System and method for monitoring and detecting faulty storage devices |
US11481440B2 (en) | 2015-11-30 | 2022-10-25 | Salesforce.Com, Inc. | System and method for processing metadata to determine an object sequence |
US10083024B2 (en) | 2015-12-01 | 2018-09-25 | Salesforce.Com, Inc. | Application aware virtual patching |
US10187403B2 (en) | 2015-12-02 | 2019-01-22 | Salesforce.Com, Inc. | False positive detection reduction system for network-based attacks |
US10949426B2 (en) | 2015-12-28 | 2021-03-16 | Salesforce.Com, Inc. | Annotating time series data points with alert information |
US10776318B2 (en) | 2015-12-28 | 2020-09-15 | Salesforce.Com, Inc. | Self-monitoring time series database system |
US10776506B2 (en) | 2015-12-28 | 2020-09-15 | Salesforce.Com, Inc. | Self-monitoring time series database system that enforces usage policies |
US10210276B2 (en) | 2015-12-28 | 2019-02-19 | Salesforce.Com, Inc. | Managing information displayed in web pages |
US10776374B2 (en) | 2015-12-28 | 2020-09-15 | Salesforce.Com, Inc. | Self-monitoring time series database system based on monitored rate of change |
US11244238B2 (en) | 2018-01-29 | 2022-02-08 | Salesforce.Com, Inc. | Search query result set count estimation |
US10402367B2 (en) | 2016-01-13 | 2019-09-03 | Salesforce.Com, Inc. | Batch job processing using a database system |
US9965634B2 (en) | 2016-01-15 | 2018-05-08 | Salesforce.Com, Inc. | Space-efficient storage of encrypted data |
US9992264B2 (en) | 2016-02-02 | 2018-06-05 | Salesforce.Com, Inc. | High-speed trace functionality in an on-demand services environment |
US10459597B2 (en) | 2016-02-03 | 2019-10-29 | Salesforce.Com, Inc. | System and method to navigate 3D data on mobile and desktop |
US10909118B2 (en) | 2016-02-04 | 2021-02-02 | Salesforce.Com, Inc. | Cache optimization for missing data |
US10437635B2 (en) | 2016-02-10 | 2019-10-08 | Salesforce.Com, Inc. | Throttling events in entity lifecycle management |
US10212057B2 (en) | 2016-02-23 | 2019-02-19 | Salesforce.Com Inc. | Disparate monitoring for IoT |
US10116502B2 (en) | 2016-02-23 | 2018-10-30 | Salesforce.Com, Inc. | System and method for providing configuration settings to services in a cloud infrastructure |
US9864867B2 (en) | 2016-02-23 | 2018-01-09 | Salesforce.Com, Inc. | Secure persistent communication between related domains using cookies |
US10713588B2 (en) | 2016-02-23 | 2020-07-14 | Salesforce.Com, Inc. | Data analytics systems and methods with personalized sentiment models |
US10901996B2 (en) | 2016-02-24 | 2021-01-26 | Salesforce.Com, Inc. | Optimized subset processing for de-duplication |
US10152497B2 (en) | 2016-02-24 | 2018-12-11 | Salesforce.Com, Inc. | Bulk deduplication detection |
US10262032B2 (en) | 2016-02-24 | 2019-04-16 | Salesforce.Com, Inc. | Cache based efficient access scheduling for super scaled stream processing systems |
US10409650B2 (en) | 2016-02-24 | 2019-09-10 | Salesforce.Com, Inc. | Efficient access scheduling for super scaled stream processing systems |
US10182063B2 (en) | 2016-03-02 | 2019-01-15 | Salesforce.Com, Inc. | In-app behavior-based attack dectection |
US9846635B2 (en) | 2016-03-18 | 2017-12-19 | Salesforce.Com, Inc. | Making production data available for testing in a non-production environment |
US10956450B2 (en) | 2016-03-28 | 2021-03-23 | Salesforce.Com, Inc. | Dense subset clustering |
US10949395B2 (en) | 2016-03-30 | 2021-03-16 | Salesforce.Com, Inc. | Cross objects de-duplication |
US10203889B2 (en) | 2016-04-01 | 2019-02-12 | Salesforce.Com, Inc. | Multi-tier file system with transparent holes |
US10678757B2 (en) | 2016-04-08 | 2020-06-09 | Salesforce.Com, Inc. | Reliable generation of a unique key in a distributed system |
US10713376B2 (en) | 2016-04-14 | 2020-07-14 | Salesforce.Com, Inc. | Fine grain security for analytic data sets |
US10057206B2 (en) | 2016-04-18 | 2018-08-21 | Salesforce.Com, Inc. | Combining updates of a social network feed |
US10423799B2 (en) | 2016-04-28 | 2019-09-24 | Salesforce.Com, Inc. | Methods and apparatus for scalable metrics gathering from secure data centers |
US10235081B2 (en) | 2016-04-28 | 2019-03-19 | Salesforce.Com, Inc | Provisioning timestamp-based storage units for time series data |
US10282361B2 (en) | 2016-04-29 | 2019-05-07 | Salesforce.Com, Inc. | Transforming time series data points from concurrent processes |
US10614393B2 (en) | 2016-04-29 | 2020-04-07 | Salesforce.Com, Inc. | Associating job responsibilities with job titles |
US10567311B2 (en) | 2016-04-29 | 2020-02-18 | Salesforce.Com, Inc. | Publisher and share action integration in a user interface for automated messaging |
US10178125B2 (en) | 2016-05-03 | 2019-01-08 | Salesforce.Com, Inc. | Stateless prevention of login-based cross-site request forgery |
US10282352B2 (en) | 2016-05-03 | 2019-05-07 | Salesforce.Com, Inc. | Computing systems and processes for improved database junction relationships |
US11188542B2 (en) | 2016-05-03 | 2021-11-30 | Salesforce.Com, Inc. | Conditional processing based on data-driven filtering of records |
US10296563B2 (en) | 2016-05-09 | 2019-05-21 | Salesforce.Com, Inc. | Automated testing of perceptible web page elements |
US10135847B2 (en) | 2016-05-18 | 2018-11-20 | Salesforce.Com, Inc. | Reverse shell network intrusion detection |
US10114628B2 (en) | 2016-05-25 | 2018-10-30 | Salesforce.Com, Inc. | Architectures and techniques for record protection and field management |
US10642851B2 (en) | 2016-05-26 | 2020-05-05 | Salesforce.Com, Inc. | Caching time series data |
US10108733B2 (en) | 2016-05-26 | 2018-10-23 | Salesforce.Com, Inc. | Methods and systems for providing customized web pages to users of a website |
EP3249553B1 (en) | 2016-05-27 | 2020-10-28 | Salesforce.com, Inc. | Worm hashing |
US10346451B2 (en) | 2016-05-27 | 2019-07-09 | Salesforce.Com, Inc. | Identifying conversations in unstructured media |
US10102133B2 (en) | 2016-05-31 | 2018-10-16 | Salesforce.Com, Inc. | Reducing latency by caching derived data at an edge server |
US10007607B2 (en) | 2016-05-31 | 2018-06-26 | Salesforce.Com, Inc. | Invalidation and refresh of multi-tier distributed caches |
US10698599B2 (en) | 2016-06-03 | 2020-06-30 | Pegasystems, Inc. | Connecting graphical shapes using gestures |
US10140456B2 (en) | 2016-06-08 | 2018-11-27 | Salesforce.Com, Inc. | Runtime analysis of software security vulnerabilities |
US10380347B2 (en) | 2016-06-08 | 2019-08-13 | Salesforce.Com., Inc. | Hierarchical runtime analysis framework for defining vulnerabilities |
US10122661B2 (en) | 2016-06-10 | 2018-11-06 | Salesforce.Com, Inc. | Messaging systems and methods that employ a blockchain to ensure integrity of message delivery |
US10204345B2 (en) | 2016-06-28 | 2019-02-12 | Salesforce.Com, Inc. | Driving customer service interactions on social media |
US10482068B2 (en) | 2016-06-29 | 2019-11-19 | Salesforce.Com, Inc. | Automated systems and techniques to manage cloud-based metadata configurations |
US11227005B2 (en) | 2016-06-30 | 2022-01-18 | Salesforce.Com, Inc. | Gesture-based database actions |
US10250715B2 (en) | 2016-06-30 | 2019-04-02 | Salesforce.Com, Inc. | Dynamic adjustment of boxcarring of action requests from component-driven cloud applications |
US10250716B2 (en) | 2016-06-30 | 2019-04-02 | Salesforce.Com, Inc. | Priority-driven boxcarring of action requests from component-driven cloud applications |
US10503707B2 (en) | 2016-07-01 | 2019-12-10 | Salesforce.Com, Inc. | Field types defined via custom metadata types |
US10268772B2 (en) | 2016-07-01 | 2019-04-23 | Salesforce.Com, Inc. | System and method for encouraging user engagement during a presentation |
US10698647B2 (en) | 2016-07-11 | 2020-06-30 | Pegasystems Inc. | Selective sharing for collaborative application usage |
US10685004B2 (en) | 2016-07-11 | 2020-06-16 | Salesforce.Com, Inc. | Multiple feature hash map to enable feature selection and efficient memory usage |
US10719428B2 (en) | 2016-07-20 | 2020-07-21 | Salesforce.Com, Inc. | Automation framework for testing user interface applications |
US10237733B2 (en) | 2016-07-20 | 2019-03-19 | Salesforce.Com, Inc | Behavioral authentication |
US11138222B2 (en) | 2016-07-22 | 2021-10-05 | Salesforce.Com, Inc. | Enabling multiple third-party data services to update custom data objects |
US11138176B2 (en) | 2016-07-21 | 2021-10-05 | salfesforce.com, inc. | Enabling a third-party data service to update custom data objects |
US11222010B2 (en) | 2016-07-21 | 2022-01-11 | Salesforce.Com, Inc. | Value transformations that enable data services to update data objects |
US10372934B2 (en) | 2016-07-21 | 2019-08-06 | Salesforce.Com, Inc. | Access controlled queries against user data in a datastore |
US10693922B2 (en) | 2016-07-25 | 2020-06-23 | Salesforce.Com, Inc. | Multi-channel customer engagement platform |
US10432697B2 (en) | 2016-07-26 | 2019-10-01 | Salesforce.Com, Inc. | Method and system for re-deploying metadata and associated data from a source organization to a destination organization |
US10410107B2 (en) | 2016-07-26 | 2019-09-10 | Salesforce.Com, Inc. | Natural language platform for database system |
US10412158B2 (en) | 2016-07-27 | 2019-09-10 | Salesforce.Com, Inc. | Dynamic allocation of stateful nodes for healing and load balancing |
US10001983B2 (en) | 2016-07-27 | 2018-06-19 | Salesforce.Com, Inc. | Rolling version update deployment utilizing dynamic node allocation |
US10241890B2 (en) | 2016-07-28 | 2019-03-26 | Salesforce.Com, Inc. | Hybrid code modification in intermediate language for software application |
US11726842B2 (en) | 2016-08-02 | 2023-08-15 | Salesforce, Inc. | Techniques and architectures for non-blocking parallel batching |
US10409701B2 (en) | 2016-08-11 | 2019-09-10 | Salesforce.Com, Inc. | Per-statement monitoring in a database environment |
US11281770B2 (en) | 2016-08-11 | 2022-03-22 | Salesforce.Com, Inc. | Detection of structured query language (SQL) injection events using simple statistical analysis |
US10409816B2 (en) | 2016-08-23 | 2019-09-10 | Salesforce.Com, Inc. | Accessing and displaying shared data |
US10164859B2 (en) | 2016-08-29 | 2018-12-25 | Salesforce.Com, Inc. | Methods and apparatus to perform elastic monitoring of software applications using embedded watchdogs |
US10417210B2 (en) | 2016-08-30 | 2019-09-17 | Salesforce.Com, Inc. | Multi-token matching scheme |
US10942903B2 (en) | 2016-08-30 | 2021-03-09 | Salesforce.Com, Inc. | Rate limiting in a moderation framework of a database system |
US10482141B2 (en) | 2016-08-30 | 2019-11-19 | Salesforce.Com, Inc. | Extensible moderation framework |
US10346370B2 (en) | 2016-08-30 | 2019-07-09 | Salesforce.Com, Inc. | Rate limiting in a moderation framework of a database system |
US10268574B2 (en) | 2016-09-01 | 2019-04-23 | Salesforce.Com, Inc. | Deployment testing for infrastructure delivery automation |
US10558634B2 (en) | 2016-09-06 | 2020-02-11 | Salesforce.Com, Inc. | Multi-user probabalistic array |
US10896192B2 (en) | 2016-09-08 | 2021-01-19 | Salesforce.Com, Inc. | Allowing in-line edit to data table of linked data of a data store |
US10915519B2 (en) | 2016-09-09 | 2021-02-09 | Salesforce.Com, Inc. | Processing offline updates to records of a database system |
US11232223B2 (en) | 2016-09-13 | 2022-01-25 | Salesforce.Com, Inc. | Providing web application components within remote systems |
US10515082B2 (en) | 2016-09-14 | 2019-12-24 | Salesforce.Com, Inc. | Identifying frequent item sets |
US10637861B2 (en) | 2016-09-16 | 2020-04-28 | Salesforce.Com, Inc. | Validating state change requests |
US10778718B2 (en) | 2016-09-16 | 2020-09-15 | Salesforce.Com, Inc. | Phishing detection and prevention |
US10635659B2 (en) | 2016-09-19 | 2020-04-28 | Salesforce.Com, Inc. | Mobile application bundled with metadata database |
US10956503B2 (en) | 2016-09-20 | 2021-03-23 | Salesforce.Com, Inc. | Suggesting query items based on frequent item sets |
US10671626B2 (en) | 2016-09-27 | 2020-06-02 | Salesforce.Com, Inc. | Identity consolidation in heterogeneous data environment |
US10642474B2 (en) | 2016-09-28 | 2020-05-05 | Salesforce.Com, Inc. | Processing keyboard input to cause movement of items in a user interface of a web browser-based application |
US10572031B2 (en) | 2016-09-28 | 2020-02-25 | Salesforce.Com, Inc. | Processing keyboard input to cause re-sizing of items in a user interface of a web browser-based application |
US10613709B2 (en) | 2016-09-30 | 2020-04-07 | Salesforce.Com, Inc. | Leveraging and managing assessment environments in an assessment hub |
US10469584B2 (en) | 2016-09-30 | 2019-11-05 | Salesforce.Com, Inc. | Techniques and architectures for managing disparate heterogeneous cloud-based resources |
US10521406B2 (en) | 2016-09-30 | 2019-12-31 | Salesforce.Com, Inc. | Merging along object hierarchies |
US11489731B2 (en) | 2016-09-30 | 2022-11-01 | Salesforce.Com, Inc. | Techniques and architectures for efficient allocation of under-utilized resources |
US10963311B2 (en) | 2016-09-30 | 2021-03-30 | Salesforce.Com, Inc. | Techniques and architectures for protection of efficiently allocated under-utilized resources |
US10223136B2 (en) | 2016-09-30 | 2019-03-05 | Salesforce.Com, Inc. | Generating content objects using an integrated development environment |
US10380094B2 (en) | 2016-09-30 | 2019-08-13 | Salesforce.Com, Inc. | Custom multi-tenant non-relational platform objects |
US10713604B2 (en) | 2016-09-30 | 2020-07-14 | Salesforce.Com, Inc. | Bi-directional notification framework |
US10275281B2 (en) | 2016-09-30 | 2019-04-30 | Salesforce.Com, Inc. | Scheduling jobs for processing log files using a database system |
US10984665B2 (en) | 2016-09-30 | 2021-04-20 | Salesforce.Com, Inc. | Customizing sequences of content objects |
US10212189B2 (en) | 2016-10-11 | 2019-02-19 | Salesforce.Com, Inc. | Authentication of client devices using modified images |
US10275298B2 (en) | 2016-10-12 | 2019-04-30 | Salesforce.Com, Inc. | Alerting system having a network of stateful transformation nodes |
US10452630B2 (en) | 2016-10-17 | 2019-10-22 | Salesforce.Com, Inc. | Techniques and architectures for reverse mapping of database queries |
US10778559B2 (en) | 2016-10-17 | 2020-09-15 | Salesforce.Com, Inc. | Facilitating simulation of network conditions in a hybrid application environment |
US10762085B2 (en) | 2016-10-17 | 2020-09-01 | Salesforce.Com, Inc. | Automated database query tuning |
US11232102B2 (en) | 2016-10-17 | 2022-01-25 | Salesforce.Com, Inc. | Background processing to provide automated database query tuning |
US10824620B2 (en) | 2016-10-21 | 2020-11-03 | Salesforce.Com, Inc. | Compiling a relational datastore query from a user input |
US10642872B2 (en) | 2016-10-21 | 2020-05-05 | Salesforce.Com, Inc. | System for optimizing content queries |
US10509843B2 (en) | 2016-10-28 | 2019-12-17 | Salesforce.Com, Inc. | Systems and methods for managing tabs in web applications |
US10447672B2 (en) | 2016-11-01 | 2019-10-15 | Salesforce.Com, Inc. | Facilitating encrypted persistent storage in browsers |
US10423461B2 (en) | 2016-11-03 | 2019-09-24 | Salesforce.Com, Inc. | Single table multiple thread-safe resource pools |
US10733003B2 (en) | 2016-11-03 | 2020-08-04 | Salesforce.Com, Inc. | Cost efficient and on-demand pool of running instances in a virtual machine environment |
US10776336B2 (en) | 2016-11-04 | 2020-09-15 | Salesforce.Com, Inc. | Dynamic creation and maintenance of multi-column custom indexes for efficient data management in an on-demand services environment |
US10496526B2 (en) | 2016-11-04 | 2019-12-03 | Salesforce.Com, Inc. | Creation and utilization of ephemeral organization structures in a multitenant environment |
US10558626B2 (en) | 2016-11-07 | 2020-02-11 | Salesforce.Com, Inc. | Merging and unmerging objects using graphical representation |
US10666722B2 (en) | 2016-11-22 | 2020-05-26 | Salesforce.Com, Inc. | Message delivery in a distributed server environment |
US9980112B1 (en) | 2016-11-23 | 2018-05-22 | Salesforce.Com, Inc. | System and method for coordinating an emergency response at a facility |
US10726039B2 (en) | 2016-11-29 | 2020-07-28 | Salesforce.Com, Inc. | Systems and methods for updating database indexes |
US10116660B2 (en) | 2016-11-30 | 2018-10-30 | Salesforce.Com, Inc. | Security modes for a component-based web security model |
US10318330B2 (en) | 2016-11-30 | 2019-06-11 | Salesforce.Com, Inc. | Data-persisting temporary virtual machine environments |
US10482086B2 (en) | 2016-11-30 | 2019-11-19 | Salesforce.Com, Inc. | Identifying similar database queries |
US10659433B2 (en) | 2016-11-30 | 2020-05-19 | Salesforce.Com, Inc. | Encrypting and securing data with reverse proxies across frames in an on-demand services environment |
US11089019B2 (en) | 2016-11-30 | 2021-08-10 | Salesforce.Com, Inc. | Techniques and architectures for secure session usage and logging |
US10129258B2 (en) | 2016-11-30 | 2018-11-13 | Salesforce.Com, Inc. | Secure component-based web applications |
US10552744B2 (en) | 2016-12-02 | 2020-02-04 | Salesforce.Com, Inc. | Rule set induction |
US10628384B2 (en) | 2016-12-09 | 2020-04-21 | Salesforce.Com, Inc. | Optimized match keys for fields with prefix structure |
US10817549B2 (en) | 2016-12-09 | 2020-10-27 | Salesforce.Com, Inc. | Augmenting match indices |
US10891263B2 (en) | 2016-12-09 | 2021-01-12 | Salesforce.Com, Inc. | Systems and methods for providing database updates for data visualization |
US10817465B2 (en) | 2016-12-09 | 2020-10-27 | Salesforce.Com, Inc. | Match index creation |
US10908947B2 (en) | 2016-12-09 | 2021-02-02 | Salesforce.Com, Inc. | Big object bulk data ingest |
US10592307B2 (en) | 2016-12-13 | 2020-03-17 | Salesforce.Com, Inc. | Multi user threaded executor |
US10540369B2 (en) | 2016-12-19 | 2020-01-21 | Salesforce.Com, Inc. | Org sync suspend and resume data sync |
US10382463B2 (en) | 2016-12-20 | 2019-08-13 | Salesforce.Com, Inc. | Techniques and architectures for cross-organization threat detection |
US10237336B2 (en) | 2016-12-22 | 2019-03-19 | Salesforce.Com, Inc. | Methods and systems for protecting computing resources |
US10496673B2 (en) | 2016-12-27 | 2019-12-03 | Salesforce.Com, Inc. | Org sync async subscribe emails |
US11249995B2 (en) | 2016-12-30 | 2022-02-15 | Salesforce.Com, Inc. | Techniques and architectures for providing and operating an application-aware database environment with predictive execution of queries and query flows |
US10936587B2 (en) | 2016-12-30 | 2021-03-02 | Salesforce.Com, Inc. | Techniques and architectures for providing and operating an application-aware database environment |
US10733613B2 (en) | 2017-01-04 | 2020-08-04 | Salesforce.Com, Inc. | Methods and systems for performing data assessment |
US10387388B2 (en) | 2017-01-04 | 2019-08-20 | Salesforce.Com, Inc. | Database schema for efficient data assessment |
US10373046B2 (en) | 2017-01-06 | 2019-08-06 | Salesforce.Com, Inc. | Client-server hybrid AI scores for customized actions |
US10146581B2 (en) | 2017-01-13 | 2018-12-04 | Salesforce.Com, Inc. | Dynamically configuring a process based on environmental characteristics monitored by a mobile device |
US10397249B2 (en) | 2017-01-18 | 2019-08-27 | Salesforce.Com, Inc. | Intrusion detection based on login attempts |
US10628590B2 (en) | 2017-01-24 | 2020-04-21 | Salesforce.Com, Inc. | Application security assessment |
US10282175B2 (en) | 2017-01-24 | 2019-05-07 | Salesforce.Com, Inc. | Methods and systems for performing a partial build |
US10650028B2 (en) | 2017-01-25 | 2020-05-12 | Salesforce.Com, Inc. | Relational database instruction validation |
US10411907B2 (en) | 2017-01-25 | 2019-09-10 | Salesforce.Com, Inc. | Secure remote user authentication leveraging public key cryptography and key splitting |
US10637658B2 (en) | 2017-01-25 | 2020-04-28 | Salesforce.Com, Inc. | Secure internal user authentication leveraging public key cryptography and key splitting |
US11190344B2 (en) | 2017-01-25 | 2021-11-30 | Salesforce.Com, Inc. | Secure user authentication based on multiple asymmetric cryptography key pairs |
US10545962B2 (en) | 2017-01-25 | 2020-01-28 | Salesforce.Com, Inc. | Relational database instruction validation |
US10356088B1 (en) | 2017-01-25 | 2019-07-16 | Salesforce.Com, Inc. | User authentication based on multiple asymmetric cryptography key pairs |
US11436223B2 (en) | 2017-01-30 | 2022-09-06 | Salesforce, Inc. | Query pin planner |
US10489139B2 (en) | 2017-01-31 | 2019-11-26 | Salesforce.Com, Inc. | Additive packaging through smart wrapping of packages and customizations in an on-demand environment |
US10776349B2 (en) | 2017-01-31 | 2020-09-15 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing dynamic macros within a multi-tenant aware structured query language |
US10768905B2 (en) | 2017-01-31 | 2020-09-08 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing schema-driven on-the-fly code generation within a cloud based computing environment |
US10803062B2 (en) | 2017-01-31 | 2020-10-13 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a by partition command term within a multi-tenant aware structured query language |
US10649987B2 (en) | 2017-01-31 | 2020-05-12 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing conditional statement execution within a multi-tenant aware structured query language |
US10649986B2 (en) | 2017-01-31 | 2020-05-12 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a BY ORGID command term within a multi-tenant aware structured query language |
US10467117B2 (en) | 2017-01-31 | 2019-11-05 | Salesforce.Com, Inc. | Techniques for providing application contextual information |
US10904267B2 (en) | 2017-02-03 | 2021-01-26 | Salesforce.Com, Inc. | Non-intrusive threat detection in a computer network |
US10719555B2 (en) | 2017-02-07 | 2020-07-21 | Salesforce.Com, Inc. | System and method in a database system for sharing a data item with an entity in another tenant domain |
US10735426B2 (en) | 2017-02-09 | 2020-08-04 | Salesforce.Com, Inc. | Secure asynchronous retrieval of data behind a firewall |
US10891627B2 (en) | 2017-02-15 | 2021-01-12 | Salesforce.Com, Inc. | Methods and apparatus for using artificial intelligence entities to provide information to an end user |
US10783188B2 (en) | 2017-02-17 | 2020-09-22 | Salesforce.Com, Inc. | Intelligent embedded self-help service |
US10136044B2 (en) | 2017-02-22 | 2018-11-20 | Salesforce.Com, Inc. | Method, apparatus, and system for communicating information of selected objects of interest displayed in a video-chat application |
US10459941B2 (en) | 2017-02-22 | 2019-10-29 | Salesforce.Com, Inc. | Providing context-specific content relating to a displayed personal information management (PIM) message for display in a user interface of a PIM application |
US10409697B2 (en) | 2017-02-23 | 2019-09-10 | Salesforce.Com, Inc. | Automated self-healing database system and method for implementing the same |
US10469438B2 (en) | 2017-02-27 | 2019-11-05 | Salesforce.Com, Inc. | Facilitating integration of collaborative communication platform and document collaboration tool |
US10178424B2 (en) | 2017-02-27 | 2019-01-08 | Salesforce.Com, Inc. | Content delivery system and method for providing customized channels and content to terminal devices |
US10880255B2 (en) | 2017-02-27 | 2020-12-29 | Salesforce.Com, Inc. | System and method in a social networking system for filtering updates in an information feed |
US10467292B2 (en) | 2017-02-28 | 2019-11-05 | Salesforce.Com, Inc. | Suggesting query items based on database fields |
US10909103B2 (en) | 2017-02-28 | 2021-02-02 | Salesforce.Com, Inc. | Techniques and architectures for data field lifecycle management |
US10372600B2 (en) | 2017-03-01 | 2019-08-06 | Salesforce.Com, Inc. | Systems and methods for automated web performance testing for cloud apps in use-case scenarios |
US10963444B2 (en) | 2017-03-08 | 2021-03-30 | Salesforce.Com, Inc. | Techniques and architectures for providing functionality to undo a metadata change |
US10169312B2 (en) | 2017-03-08 | 2019-01-01 | Salesforce.Com, Inc. | System and method in a social networking system for displaying updates in an information feed |
US10459718B2 (en) | 2017-03-08 | 2019-10-29 | Salesforce.Com, Inc. | Techniques and architectures for maintaining metadata version controls |
US10579368B2 (en) | 2017-03-10 | 2020-03-03 | Salesforce.Com, Inc. | Blockchain version control systems |
US10417183B2 (en) | 2017-03-14 | 2019-09-17 | Salesforce.Com, Inc. | Database and file structure configurations for managing text strings to be provided by a graphical user interface |
US11049025B2 (en) | 2017-03-15 | 2021-06-29 | Salesforce.Com, Inc. | Systems and methods for compute node management protocols |
US10332289B2 (en) | 2017-03-15 | 2019-06-25 | Salesforce.Com, Inc. | Methods and systems for providing a visual feedback representation of performance metrics |
US10810230B2 (en) | 2017-03-21 | 2020-10-20 | Salesforce.Com, Inc. | Thread record provider |
US10803080B2 (en) | 2017-03-21 | 2020-10-13 | Salesforce.Com, Inc. | Thread record provider |
US10860377B2 (en) | 2017-03-22 | 2020-12-08 | Salesforce.Com, Inc. | Technologies for identifying thread memory allocation |
US10817815B2 (en) | 2017-03-27 | 2020-10-27 | Salesforce.Com, Inc. | Providing attendees from a different organization with supplemental information related to a calendar event |
US10474673B2 (en) | 2017-03-28 | 2019-11-12 | Salesforce.Com, Inc. | Methods and apparatus for performing machine learning to improve capabilities of an artificial intelligence (AI) entity used for online communications |
US10891298B2 (en) | 2017-03-28 | 2021-01-12 | Salesforce.Com, Inc. | Systems and methods for package component visualizations |
US10587401B2 (en) | 2017-04-03 | 2020-03-10 | Salesforce.Com, Inc. | Secure handling of customer-supplied encryption secrets |
US10977236B2 (en) | 2017-04-03 | 2021-04-13 | Salesforce.Com, Inc. | Dynamic recommendation methods and systems for database changes |
US10594815B2 (en) | 2017-04-03 | 2020-03-17 | Salesforce.Com, Inc. | Systems and methods for electronic notification broadcasts |
US10452462B2 (en) | 2017-04-07 | 2019-10-22 | Salesforce.Com, Inc. | Parsing complex log entry types |
US10664455B2 (en) | 2017-04-07 | 2020-05-26 | Salesforce.Com, Inc. | Complex log entry type schemas |
US10803465B2 (en) | 2017-04-10 | 2020-10-13 | Salesforce.Com, Inc. | Enabling hierarchical structure representation of entities |
US10423522B2 (en) | 2017-04-12 | 2019-09-24 | Salesforce.Com, Inc. | System and method for detecting an error in software |
US10776250B2 (en) | 2017-04-12 | 2020-09-15 | Salesforce.Com, Inc. | Switchable environments for test cases |
US10831783B2 (en) | 2017-04-25 | 2020-11-10 | Salesforce.Com, Inc. | Updating a hierarchical data structure |
US10754831B2 (en) | 2017-04-25 | 2020-08-25 | Salesforce.Com, Inc. | Generating a hierarchical data structure |
US10721152B2 (en) | 2017-04-27 | 2020-07-21 | Salesforce.Com, Inc. | Automated analysis and recommendations for highly performant single page web applications |
US10645138B2 (en) | 2017-05-02 | 2020-05-05 | Salesforce.Com, Inc | Event stream processing system using a coordinating spout instance |
US10430611B2 (en) | 2017-05-03 | 2019-10-01 | Salesforce.Com, Inc. | Techniques and architectures for selective obfuscation of personally identifiable information (PII) in environments capable of replicating data |
US10514951B2 (en) | 2017-05-04 | 2019-12-24 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a stateless, deterministic scheduler and work discovery system with interruption recovery |
US10956222B2 (en) | 2017-05-04 | 2021-03-23 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a scheduler and workload manager with dynamic workload termination based on cost-benefit analysis |
US11237865B2 (en) | 2017-05-04 | 2022-02-01 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a scheduler and workload manager that identifies and consumes global virtual resources |
US11237866B2 (en) | 2017-05-04 | 2022-02-01 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a scheduler and workload manager with scheduling redundancy and site fault isolation |
US11243818B2 (en) | 2017-05-04 | 2022-02-08 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a scheduler and workload manager that identifies and optimizes horizontally scalable workloads |
US11226848B2 (en) | 2017-05-04 | 2022-01-18 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a scheduler and workload manager with snapshot and resume functionality |
US10545796B2 (en) | 2017-05-04 | 2020-01-28 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a scheduler with preemptive termination of existing workloads to free resources for high priority items |
US11663205B2 (en) | 2017-05-04 | 2023-05-30 | Salesforce, Inc. | Technologies for asynchronous querying |
US11243807B2 (en) | 2017-05-04 | 2022-02-08 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a scheduler and workload manager with workload re-execution functionality for bad execution runs |
US11294726B2 (en) | 2017-05-04 | 2022-04-05 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing a scalable scheduler with heterogeneous resource allocation of large competing workloads types using QoS |
US11082519B2 (en) | 2017-05-08 | 2021-08-03 | Salesforce.Com, Inc. | System and method of providing web content using a proxy cache |
US10536439B2 (en) | 2017-05-08 | 2020-01-14 | Salesforce.Com, Inc. | Client fingerprinting for information system security |
US10635561B2 (en) | 2017-05-11 | 2020-04-28 | Salesforce.Com, Inc. | Techniques and architectures for managing database failure in a single-node database architecture |
US10425274B2 (en) | 2017-05-11 | 2019-09-24 | Salesforce.Com, Inc. | Techniques and architectures for recovering from a service disruption in a multi-server environment |
US10592866B2 (en) | 2017-05-12 | 2020-03-17 | Salesforce.Com, Inc. | Calendar application, system and method for creating records in a cloud computing platform from within the context of the calendar application |
US10504069B2 (en) | 2017-05-12 | 2019-12-10 | Salesforce.Com, Inc. | Calendar application, system and method for performing actions on records in a cloud computing platform from within the context of the calendar application |
US10579222B2 (en) | 2017-05-17 | 2020-03-03 | Salesforce.Com, Inc. | Keyboard access to hover functionality |
US11005864B2 (en) | 2017-05-19 | 2021-05-11 | Salesforce.Com, Inc. | Feature-agnostic behavior profile based anomaly detection |
US10318349B2 (en) | 2017-05-22 | 2019-06-11 | Salesforce.Com, Inc. | Distributed scheduling in a virtual machine environment |
US10360136B2 (en) | 2017-05-23 | 2019-07-23 | Salesforce.Com., Inc. | Dashboard execution engine |
US10852926B2 (en) | 2017-05-23 | 2020-12-01 | Salesforce.Com., Inc. | Filter of data presentations via user-generated links |
US11054971B2 (en) | 2017-05-23 | 2021-07-06 | Salesforce.Com., Inc. | Modular runtime environment |
US10713223B2 (en) | 2017-06-01 | 2020-07-14 | Salesforce.Com, Inc. | Opportunistic gossip-type dissemination of node metrics in server clusters |
US10296289B2 (en) | 2017-06-01 | 2019-05-21 | Salesforce.Com, Inc. | Multimodal commands |
US10693951B2 (en) | 2017-06-01 | 2020-06-23 | Salesforce.Com, Inc. | Decentralized, resource aware load distribution in a distributed system |
US11475064B2 (en) | 2017-06-08 | 2022-10-18 | Salesforce.Com, Inc. | System and method in a database system for creating a field service work order |
US10838941B2 (en) | 2017-06-14 | 2020-11-17 | Salesforce.Com, Inc. | Automated image-based record creation and related database systems |
US11586696B2 (en) | 2017-06-19 | 2023-02-21 | Salesforce, Inc. | Enhanced web browsing |
US10853440B2 (en) | 2017-06-19 | 2020-12-01 | Salesforce.Com, Inc. | Displaying an object having a link to a database record in response to a user selection of a highlighted reference |
US10489170B2 (en) | 2017-06-19 | 2019-11-26 | Salesforce.Com, Inc. | Application warmup engine |
US11269938B2 (en) | 2017-06-21 | 2022-03-08 | Salesforce.Com, Inc. | Database systems and methods for conversational database interaction |
US10523425B2 (en) | 2017-06-22 | 2019-12-31 | Salesforce.Com, Inc. | Database password changes |
US11586593B2 (en) | 2017-06-22 | 2023-02-21 | Salesforce.Com, Inc. | Mechanism for synchronization of hierarchical data between a mobile device and multi tenant database |
US11295068B2 (en) | 2017-06-23 | 2022-04-05 | Salesforce.Com, Inc. | Techniques and architectures for native data field lifecycle management |
US10817479B2 (en) | 2017-06-23 | 2020-10-27 | Salesforce.Com, Inc. | Recommending data providers' datasets based on database value densities |
US10416952B2 (en) | 2017-06-27 | 2019-09-17 | Salesforce.Com, Inc. | Identifying a viewport within a browser window |
US10644890B1 (en) | 2017-06-29 | 2020-05-05 | Salesforce.Com | Language-agnostic secure application deployment |
US10749689B1 (en) | 2017-06-29 | 2020-08-18 | Salesforce.Com, Inc. | Language-agnostic secure application development |
US11163910B2 (en) | 2017-06-29 | 2021-11-02 | Salesforce.Com, Inc. | Methods and systems for data migration |
US10686741B2 (en) | 2017-06-29 | 2020-06-16 | Salesforce.Com, Inc. | Method and system for real-time blocking of content from an organization activity timeline |
US10719811B2 (en) | 2017-06-29 | 2020-07-21 | Salesforce.Com, Inc. | Method and system for retroactive removal of content from an organization activity timeline |
US10374794B1 (en) | 2017-06-30 | 2019-08-06 | Salesforce.Com, Inc. | Secure transmission of tokens using private key fragments |
US10425224B1 (en) | 2017-06-30 | 2019-09-24 | Salesforce.Com, Inc. | Identity confirmation using private keys |
US11068483B2 (en) | 2017-08-01 | 2021-07-20 | Salesforce.Com, Inc. | Dynamic selection and application of rules for processing of queries in an on-demand environment |
US11314741B2 (en) | 2017-08-01 | 2022-04-26 | Salesforce.Com, Inc. | Metadata-based statistics-oriented processing of queries in an on-demand environment |
US9961519B1 (en) | 2017-08-01 | 2018-05-01 | Salesforce.Com, Inc. | Facilitating mobile device interaction with an enterprise database system |
US10579641B2 (en) | 2017-08-01 | 2020-03-03 | Salesforce.Com, Inc. | Facilitating mobile device interaction with an enterprise database system |
US11012317B2 (en) | 2017-08-18 | 2021-05-18 | Salesforce.Com, Inc. | Visualization for monitoring infrastructure entities |
US10664244B2 (en) | 2017-08-22 | 2020-05-26 | Salesforce.Com, Inc. | Dynamic page previewer for a web application builder |
US10775969B2 (en) | 2017-08-25 | 2020-09-15 | Salesforce.Com, Inc. | System and method for notifying a softphone of navigation change events |
US10678773B2 (en) | 2017-08-25 | 2020-06-09 | Salesforce.Com, Inc. | Parallel processing of disjoint change streams into a single stream |
US10402174B2 (en) | 2017-08-25 | 2019-09-03 | Salesforce.Com, Inc. | Overriding component attributes in a web application builder |
US10609140B2 (en) | 2017-08-28 | 2020-03-31 | Salesforce.Com, Inc. | Dynamic resource management systems and methods |
US10476855B1 (en) | 2017-08-29 | 2019-11-12 | Salesforce.Com, Inc. | Identity confirmation using private keys |
US10540149B2 (en) | 2017-08-30 | 2020-01-21 | Salesforce.Com, Inc. | Property editor component in a web application builder framework |
US10846068B2 (en) | 2017-08-30 | 2020-11-24 | Salesforce.Com, Inc. | Interactions layer in a web application builder framework |
US10509633B2 (en) | 2017-08-30 | 2019-12-17 | Salesforce.Com, Inc. | Base editor component in a web application builder framework |
US10514896B2 (en) | 2017-08-30 | 2019-12-24 | Salesforce.Com, Inc. | Web application builder framework |
US10509546B2 (en) | 2017-08-31 | 2019-12-17 | Salesforce.Com, Inc. | History component for single page application |
US10909070B2 (en) | 2017-08-31 | 2021-02-02 | Salesforce.Com, Inc. | Memory efficient policy-based file deletion system |
US11138195B2 (en) | 2017-08-31 | 2021-10-05 | Salesforce.Com, Inc. | Systems and methods for translating n-ary trees to binary query trees for query execution by a relational database management system |
US10586025B2 (en) | 2017-09-07 | 2020-03-10 | Salesforce.Com, Inc. | Managing the display of hidden proprietary software code to authorized licensed users |
US10579691B2 (en) | 2017-09-27 | 2020-03-03 | Salesforce.Com, Inc. | Application programming interface representation of multi-tenant non-relational platform objects |
US11036357B2 (en) | 2017-09-27 | 2021-06-15 | Salesforce.Com, Inc. | Generating or updating cross-community streams |
US10579692B2 (en) | 2017-09-27 | 2020-03-03 | Salesforce.Com, Inc. | Composite keys for multi-tenant non-relational platform objects |
US11714811B2 (en) | 2017-09-27 | 2023-08-01 | Salesforce, Inc. | Run-time querying of multi-tenant non-relational platform objects |
US10489390B2 (en) | 2017-09-29 | 2019-11-26 | Salesforce.Com, Inc. | Content management in an on-demand environment |
US10467412B2 (en) | 2017-10-05 | 2019-11-05 | Salesforce.Com, Inc. | Software container modeling |
US10802738B2 (en) | 2017-10-11 | 2020-10-13 | Salesforce.Com, Inc. | Criteria-based cost-efficient routing and deployment of metadata packages in an on-demand environment |
US10733212B2 (en) | 2017-10-16 | 2020-08-04 | Salesforce.Com, Inc. | Entity identifier clustering based on context scores |
US10984070B2 (en) | 2017-10-18 | 2021-04-20 | Salesforce.Com, Inc. | Dynamic content placeholders for microblogging posts |
US10693952B2 (en) | 2017-10-23 | 2020-06-23 | Salesforce.Com, Inc. | Technologies for low latency messaging |
US11003662B2 (en) | 2017-10-30 | 2021-05-11 | Salesforce.Com, Inc. | Trigger-free asynchronous maintenance of custom indexes and skinny performance meta-structures |
US10387041B2 (en) | 2017-11-02 | 2019-08-20 | Salesforce.Com, Inc. | Data migration system |
US11048663B2 (en) | 2017-11-15 | 2021-06-29 | Salesforce.Com, Inc. | Database systems and methods for automated database modifications |
US10754735B2 (en) | 2017-11-20 | 2020-08-25 | Salesforce.Com, Inc. | Distributed storage reservation for recovering distributed data |
US10853131B2 (en) | 2017-11-20 | 2020-12-01 | Salesforce.Com, Inc. | Dataflow life cycles |
US10409583B2 (en) | 2017-11-27 | 2019-09-10 | Salesforce.Com, Inc. | Content deployment system having a content publishing engine with a filter module for selectively extracting content items provided from content sources for integration into a specific release and methods for implementing the same |
US10684847B2 (en) | 2017-11-27 | 2020-06-16 | Salesforce.Com, Inc. | Content deployment system having a proxy for continuously providing selected content items to a content publishing engine for integration into a specific release and methods for implementing the same |
US10642862B2 (en) | 2017-11-28 | 2020-05-05 | Salesforce.Com, Inc. | System and method for referencing master data in a multi-tenant application-platform-as-a-service architecture |
US10642819B2 (en) | 2017-11-28 | 2020-05-05 | Salesforce.Com, Inc. | Automate telling data-rich stories within analytics dashboard |
US10528816B2 (en) | 2017-11-30 | 2020-01-07 | Salesforce.Com, Inc. | System and method for retrieving and displaying supplemental information and pertinent data using augmented reality |
US10936596B2 (en) | 2017-11-30 | 2021-03-02 | Salesforce.Com, Inc. | Dynamic selection of data sources for streaming dynamic data |
US10872097B2 (en) | 2017-12-01 | 2020-12-22 | Salesforce.Com, Inc. | Data resolution system for management of distributed data |
US11088925B2 (en) | 2017-12-04 | 2021-08-10 | Salesforce.Com, Inc. | Technologies for capacity remediation in multi-tenant cloud environments |
US10866894B2 (en) | 2017-12-13 | 2020-12-15 | Salesforce.Com, Inc. | Controlling memory usage in a cache |
US10904197B2 (en) | 2017-12-19 | 2021-01-26 | Salesforce.Com, Inc. | Management of members of social network conversations |
US10887281B2 (en) | 2017-12-19 | 2021-01-05 | Salesforce.Com, Inc. | Automated host-based firewall configuration management |
US11163759B2 (en) | 2017-12-21 | 2021-11-02 | Salesforce.Com, Inc. | Predicting entities for database query results |
US11030210B2 (en) | 2018-01-03 | 2021-06-08 | Salesforce.Com, Inc. | Hierarchical rules for displaying user interface pages |
US10681039B2 (en) | 2018-01-08 | 2020-06-09 | Salesforce.Com, Inc. | User authentication across multiple environments |
US10671975B2 (en) | 2018-01-10 | 2020-06-02 | Salesforce.Com, Inc. | Smart streaming of data between external systems and service providers in an on-demand environment |
US10713101B2 (en) | 2018-01-11 | 2020-07-14 | Salesforce.Com, Inc. | Client-based control and experience of application programming interfaces in an on-demand environment |
US11048684B2 (en) | 2018-01-16 | 2021-06-29 | Salesforce.Com, Inc. | Lazy tracking of user system web cache |
US10671739B2 (en) | 2018-01-17 | 2020-06-02 | Salesforce.Com, Inc. | Managing the sharing of common library packages with subscribers |
US10802884B2 (en) | 2018-01-17 | 2020-10-13 | Salesforce.Com, Inc. | Efficient provisioning of an infrastructure based on different factors |
US10671248B2 (en) | 2018-01-18 | 2020-06-02 | Salesforce.Com, Inc. | Live agent chat console |
US10725829B2 (en) | 2018-01-22 | 2020-07-28 | Salesforce.Com, Inc. | Scheduling capacity in a data-processing cluster to an application queue by repurposing monitoring-based capacity of a delegator queue for job execution in the application queue |
US10693883B2 (en) | 2018-01-22 | 2020-06-23 | Salesforce.Com, Inc. | Technologies for integrating and sandboxing web resources |
US10616230B2 (en) | 2018-01-23 | 2020-04-07 | Salesforce.Com, Inc. | Managing authorization tokens for calling third-party vendors |
US10616352B2 (en) | 2018-01-24 | 2020-04-07 | Salesforce.Com, Inc. | Integrating third-party vendors' APIs |
US11151269B2 (en) | 2018-01-24 | 2021-10-19 | Salesforce.Com, Inc. | Regulation-compliant processing of queries and storing of data in an on-demand environment |
US10812544B2 (en) | 2018-01-26 | 2020-10-20 | Salesforce.Com, Inc. | Transfer of data streaming services to provide continuous data flow |
US11016959B2 (en) | 2018-01-31 | 2021-05-25 | Salesforce.Com, Inc. | Trie-based normalization of field values for matching |
US11206273B2 (en) | 2018-01-31 | 2021-12-21 | Salesforce.Com, Inc. | Content management system connect |
US11126608B2 (en) | 2018-01-31 | 2021-09-21 | Salesforce.Com, Inc. | Techniques and architectures for partition mapping in a multi-node computing environment |
US11416116B2 (en) | 2018-01-31 | 2022-08-16 | Salesforce.Com, Inc. | Generation of mobile device notifications |
US10642803B2 (en) | 2018-01-31 | 2020-05-05 | Salesforce.Com, Inc. | Adding a partition to an existing table stored on a distributed file system |
US10860606B2 (en) | 2018-01-31 | 2020-12-08 | Salesforce.Com, Inc. | Efficiently deleting data from objects in a multi tenant database system |
US10936477B2 (en) | 2018-01-31 | 2021-03-02 | Salesforce.Com, Inc. | End-to-end user interface component testing |
US10778543B2 (en) | 2018-01-31 | 2020-09-15 | Salesforce.Com, Inc. | Opaque interface for enclosed/wrapped asynchronous pushing and/or pulling data between policy enforcement as a service (PEaaS) components |
US10560349B2 (en) | 2018-01-31 | 2020-02-11 | Salesforce.Com, Inc. | Data consistency of policy enforcement for distributed applications |
US10771353B2 (en) | 2018-01-31 | 2020-09-08 | Salesforce.Com, Inc. | Policy enforcement as a service for third party platforms with asynchronous user tracking mechanisms |
US11086819B2 (en) | 2018-04-23 | 2021-08-10 | Salesforce.Com, Inc. | Efficiently deleting data from objects in a multi-tenant database system |
US10680958B2 (en) | 2018-01-31 | 2020-06-09 | Salesforce.Com, Inc. | Policy enforcement as a service for third party platforms |
CN110209642A (en) * | 2018-02-05 | 2019-09-06 | 北京智明星通科技股份有限公司 | Method, apparatus, server and the computer-readable medium of information processing |
US10853334B2 (en) | 2018-03-02 | 2020-12-01 | Salesforce.Com, Inc. | Technologies for providing service isolation, scalability, and proactive tenant migration in multi-tenant ecosystems |
US10708420B2 (en) | 2018-03-22 | 2020-07-07 | Salesforce.Com, Inc. | Method and system for automatically transcribing a call and updating a record based on transcribed voice data |
US10664192B2 (en) | 2018-04-26 | 2020-05-26 | Salesforce.Com, Inc. | In-memory service with plural buffer type assignment |
US10936308B2 (en) | 2018-04-30 | 2021-03-02 | Salesforce.Com, Inc. | Multi-tenant collaborative learning |
US10742806B2 (en) | 2018-05-08 | 2020-08-11 | Salesforce.Com, Inc. | Method, system and bot architecture for automatically sending a user content, that is responsive to user messages from that user, to solicit additional information from that user |
US10992740B2 (en) | 2018-05-14 | 2021-04-27 | Salesforce.Com, Inc. | Dynamically balancing partitions within a distributed streaming storage platform |
US10909125B2 (en) | 2018-05-22 | 2021-02-02 | Salesforce.Com, Inc. | Asymmetric rank-biased overlap |
US11132501B2 (en) | 2018-05-25 | 2021-09-28 | Salesforce.Com, Inc. | Smart column selection for table operations in data preparation |
US10958431B2 (en) | 2018-05-30 | 2021-03-23 | Salesforce.Com, Inc. | Authenticating computing system requests across tenants of a multi-tenant database system |
US11252119B2 (en) | 2018-06-04 | 2022-02-15 | Salesforce.Com, Inc. | Message logging using two-stage message logging mechanisms |
US10915295B2 (en) | 2018-06-07 | 2021-02-09 | Salesforce.Com, Inc. | Automated generation of audio daily activity overview powered by a database |
US11233806B2 (en) | 2018-06-18 | 2022-01-25 | Salesforce.Com, Inc. | Techniques and architectures for privilege escalation detection |
US10878218B2 (en) | 2018-06-18 | 2020-12-29 | Salesforce.Com, Inc. | Device fingerprinting, tracking, and management |
US11061896B2 (en) | 2018-06-19 | 2021-07-13 | Salesforce.Com, Inc. | Maximizing operator parallelism |
US10721323B2 (en) | 2018-06-19 | 2020-07-21 | Salesforce.Com, Inc. | High-performance data streaming |
US11494378B2 (en) | 2018-06-19 | 2022-11-08 | Salesforce, Inc. | Runtime optimization of grouping operators |
US11218461B2 (en) | 2018-06-29 | 2022-01-04 | Salesforce.Com, Inc. | Authenticating computing system requests with an unknown destination across tenants of a multi-tenant system |
US11797866B2 (en) | 2018-07-18 | 2023-10-24 | Salesforce.Com, Inc. | Systems and methods for accelerating execution of processes based on artificial intelligence (AI) prediction of blockchain consensus |
US11315055B2 (en) | 2018-07-26 | 2022-04-26 | Salesforce.Com, Inc. | System and method for visualizing an order allocation process |
US10705860B2 (en) | 2018-07-27 | 2020-07-07 | Salesforce.Com, Inc. | Method and system for declarative configuration of user self-registration and log in pages and processes for a service provider and automatic deployment of the same |
US11010272B2 (en) | 2018-07-31 | 2021-05-18 | Salesforce.Com, Inc. | Systems and methods for secure data transfer between entities in a multi-user on-demand computing environment |
US11423063B2 (en) | 2018-07-31 | 2022-08-23 | Salesforce, Inc. | Flattening hierarchical database records using inverted indexing |
US11010481B2 (en) | 2018-07-31 | 2021-05-18 | Salesforce.Com, Inc. | Systems and methods for secure data transfer between entities in a multi-user on-demand computing environment |
US11132185B2 (en) | 2018-08-07 | 2021-09-28 | Microsoft Technology Licensing, Llc | Embedding of multiple versions in monolithic applications during compilation |
US11048488B2 (en) | 2018-08-14 | 2021-06-29 | Pegasystems, Inc. | Software code optimizer and method |
US10664266B2 (en) | 2018-09-04 | 2020-05-26 | Salesforce.Com, Inc. | Maintaining client version affinity during a server cluster upgrade |
US10671236B2 (en) | 2018-09-20 | 2020-06-02 | Salesforce.Com, Inc. | Stateful, contextual, and draggable embedded widget |
US10866959B2 (en) | 2018-09-20 | 2020-12-15 | Salesforce.Com, Inc. | Debug tracing of next best action strategy engine |
US11308067B2 (en) | 2018-09-21 | 2022-04-19 | Salesforce.Com, Inc. | Associating flows in different states to a database record |
US10891308B2 (en) | 2018-09-24 | 2021-01-12 | Salesforce.Com, Inc. | Automated self-scaling database system for automatically scaling out write operations and method for implementing the same in a multi-tenant, cloud-based computing environment |
US11235460B2 (en) | 2018-09-24 | 2022-02-01 | Salesforce.Com, Inc. | Techniques and architectures for managing heterogeneous robots to manage deliveries |
US10873635B2 (en) | 2018-09-24 | 2020-12-22 | Salesforce.Com, Inc. | Multi-channel session connection management mechanism |
US11227069B2 (en) | 2018-09-24 | 2022-01-18 | Salesforce.Com, Inc. | Techniques and architectures for managing privacy information and permissions across disparate database tables |
US11199944B2 (en) | 2018-09-24 | 2021-12-14 | Salesforce.Com, Inc. | System and method for navigation within widget-sized browser panels |
US10838698B2 (en) | 2018-09-24 | 2020-11-17 | Salesforce.Com, Inc. | Providing a reuse capability for visual programming logic within a building tool |
US10902021B2 (en) | 2018-09-24 | 2021-01-26 | Salesforce.Com, Inc. | Automated self-scaling database system for automatically scaling out read operations and method for implementing the same |
US11580179B2 (en) | 2018-09-24 | 2023-02-14 | Salesforce.Com, Inc. | Method and system for service agent assistance of article recommendations to a customer in an app session |
US10915827B2 (en) | 2018-09-24 | 2021-02-09 | Salesforce.Com, Inc. | System and method for field value recommendations based on confidence levels in analyzed dataset |
US11216435B2 (en) | 2018-09-24 | 2022-01-04 | Salesforce.Com, Inc. | Techniques and architectures for managing privacy information and permissions queries across disparate database tables |
US11640407B2 (en) | 2018-09-24 | 2023-05-02 | Salesforce, Inc. | Driving application experience via search inputs |
US11016722B2 (en) | 2018-09-24 | 2021-05-25 | Salesforce.Com, Inc. | Database systems and methods for conversation-driven dynamic updates |
US11095448B2 (en) | 2018-09-24 | 2021-08-17 | Salesforce.Com, Inc. | HASSH profiling mechanism |
US10642916B2 (en) | 2018-09-25 | 2020-05-05 | Salesforce, Inc. | Systems and methods for providing client-side enablement of server communications via a single communication session for a plurality of browser-based presentation interfaces |
US11256772B2 (en) | 2018-09-25 | 2022-02-22 | Salesforce.Com, Inc. | Systems and methods for providing client-side enablement of server communications via a single communication session for a plurality of browser-based presentation interfaces |
US11379192B2 (en) | 2018-09-25 | 2022-07-05 | Salesforce, Inc. | Saving a snippet of visual programming logic for reuse amongst programs created using an automation building tool |
US11416830B2 (en) | 2018-09-25 | 2022-08-16 | Salesforce.Com, Inc. | Method and system for automatically creating action plans based on an action plan template |
US10938755B1 (en) | 2019-10-07 | 2021-03-02 | Salesforce.Com, Inc. | Browser-independent multi-tab communication methods and systems |
US10817266B2 (en) | 2018-09-25 | 2020-10-27 | Salesforce.Com, Inc. | Converting a captured image to visual programming logic for an automation building tool |
US10902254B2 (en) | 2018-09-26 | 2021-01-26 | Salesforce.Com, Inc. | Converting a captured image of a layout to a structured document template |
US11010143B2 (en) | 2018-09-28 | 2021-05-18 | Salesforce.Com, Inc. | Executing formulas written using formula language |
US11003427B2 (en) | 2018-09-28 | 2021-05-11 | Salesforce.Com, Inc. | Interface for generating and testing formulas using a formula language |
US10353733B1 (en) | 2018-10-02 | 2019-07-16 | Capital One Services, Llc | Systems and methods for performing virtual machine updates without rebuild of distributed databases thereon |
US10686739B2 (en) | 2018-10-18 | 2020-06-16 | Salesforce.Com, Inc. | Systems and methods for enabling client-side rendering of rich content by a plurality of browser-based messaging interfaces communicating with a server via a single communication session |
US10783063B2 (en) | 2018-10-23 | 2020-09-22 | Salesforce.Com, Inc. | Systems and methods for testing a customer environment |
US11921750B2 (en) | 2018-10-29 | 2024-03-05 | Salesforce, Inc. | Database systems and applications for assigning records to chunks of a partition in a non-relational database system with auto-balancing |
US10789052B2 (en) | 2018-10-29 | 2020-09-29 | Salesforce.Com, Inc. | User interface (UI) design system mapping platform for automatically mapping design system components to a design document file from a design tool to generate a mapped specification |
US11012443B2 (en) | 2018-10-30 | 2021-05-18 | Salesforce.Com, Inc. | Dynamic deployment of access controls anchored on request actions |
US11190420B2 (en) | 2018-10-31 | 2021-11-30 | Salesforce.Com, Inc. | Generating events from host based logging for consumption by a network logging host |
US11061894B2 (en) | 2018-10-31 | 2021-07-13 | Salesforce.Com, Inc. | Early detection and warning for system bottlenecks in an on-demand environment |
US10698787B2 (en) | 2018-10-31 | 2020-06-30 | Salesforce.Com, Inc. | Log event management mechanism |
US10929367B2 (en) | 2018-10-31 | 2021-02-23 | Salesforce.Com, Inc. | Automatic rearrangement of process flows in a database system |
US11055162B2 (en) | 2018-10-31 | 2021-07-06 | Salesforce.Com, Inc. | Database system performance degradation detection |
US10824446B2 (en) | 2018-11-02 | 2020-11-03 | Salesforce.Com, Inc. | Methods and systems for autocompletion |
US11409742B2 (en) | 2018-12-06 | 2022-08-09 | Salesforce, Inc. | Efficient database searching for queries using wildcards |
US10853046B2 (en) | 2018-12-13 | 2020-12-01 | Salesforce.Com, Inc. | Deployment of software applications on server clusters |
US11182144B2 (en) | 2018-12-31 | 2021-11-23 | Salesforce.Com, Inc. | Preventing database package updates to fail customer requests and cause data corruptions |
US10747551B2 (en) | 2019-01-23 | 2020-08-18 | Salesforce.Com, Inc. | Software application optimization |
US10802944B2 (en) | 2019-01-23 | 2020-10-13 | Salesforce.Com, Inc. | Dynamically maintaining alarm thresholds for software application performance management |
US11194591B2 (en) | 2019-01-23 | 2021-12-07 | Salesforce.Com, Inc. | Scalable software resource loader |
US11140142B2 (en) | 2019-01-24 | 2021-10-05 | Salesforce.Com, Inc. | Method and system for authentication |
US11436233B2 (en) | 2019-01-25 | 2022-09-06 | Salesforce, Inc. | Generating adaptive match keys |
US11099973B2 (en) | 2019-01-28 | 2021-08-24 | Salesforce.Com, Inc. | Automated test case management systems and methods |
US11157337B2 (en) | 2019-01-28 | 2021-10-26 | Salesforce.Com, Inc. | Method and system for processing a stream of incoming messages sent from a specific input message source and validating each incoming message of that stream before sending them to a specific target system |
US11126673B2 (en) | 2019-01-29 | 2021-09-21 | Salesforce.Com, Inc. | Method and system for automatically enriching collected seeds with information extracted from one or more websites |
US10866996B2 (en) | 2019-01-29 | 2020-12-15 | Saleforce.com, inc. | Automated method and system for clustering enriched company seeds into a cluster and selecting best values for each attribute within the cluster to generate a company profile |
US11037085B2 (en) | 2019-01-30 | 2021-06-15 | Salesforce.Com, Inc. | Computation of customer experience metrics in a multi-tenant cloud computing environment |
US11755725B2 (en) | 2019-01-30 | 2023-09-12 | Salesforce, Inc. | Machine learning anomaly detection mechanism |
US11210198B2 (en) | 2019-01-30 | 2021-12-28 | Salesforce.Com, Inc | Distributed web page performance monitoring methods and systems |
US11928090B2 (en) | 2019-01-30 | 2024-03-12 | Salesforce, Inc. | Anomaly detection mechanism |
US11386380B2 (en) | 2019-01-30 | 2022-07-12 | Salesforce.Com, Inc. | System and method for visual, artificial intelligence, and rule based quality assurance |
US10789048B2 (en) | 2019-01-30 | 2020-09-29 | Salesforce.Com, Inc. | Namespace and class utilities for managed packages |
US11263178B2 (en) | 2019-01-31 | 2022-03-01 | Salesforce.Com, Inc. | Intelligent prediction of future generation of types of data objects based on past growth |
US11042434B2 (en) | 2019-01-31 | 2021-06-22 | Salesforce.Com, Inc. | Database ingestion across internal and external data sources using error rate handling |
US11526539B2 (en) | 2019-01-31 | 2022-12-13 | Salesforce, Inc. | Temporary reservations in non-relational datastores |
US10860296B2 (en) | 2019-01-31 | 2020-12-08 | Salesforce.Com, Inc. | Techniques and architectures for managing and analyzing system updates |
US10897405B2 (en) | 2019-01-31 | 2021-01-19 | Salesforce.Com, Inc. | Target availability threshold calculation mechanism |
US11010771B2 (en) | 2019-01-31 | 2021-05-18 | Salesforce.Com, Inc. | Machine learning from data steward feedback for data matching |
US11216444B2 (en) | 2019-01-31 | 2022-01-04 | Salesforce.Com, Inc. | Scalable event sourcing datastore |
US10977011B2 (en) | 2019-01-31 | 2021-04-13 | Salesforce.Com, Inc. | Structured development for web application frameworks |
US11755914B2 (en) | 2019-01-31 | 2023-09-12 | Salesforce, Inc. | Machine learning from data steward feedback for merging records |
US11061734B2 (en) | 2019-01-31 | 2021-07-13 | Salesforce.Com, Inc. | Performing customized data compaction for efficient parallel data processing amongst a set of computing resources |
US10971159B2 (en) | 2019-02-19 | 2021-04-06 | Salesforce.Com, Inc. | Cross account access for a virtual personal assistant via voice printing |
US11150939B2 (en) | 2019-02-28 | 2021-10-19 | Salesforce.Com, Inc. | Composite batching to manage throughput for online commerce applications |
US11429714B2 (en) | 2019-03-12 | 2022-08-30 | Salesforce.Com, Inc. | Centralized privacy management system for automatic monitoring and handling of personal data across data system platforms |
US11488082B2 (en) | 2019-03-27 | 2022-11-01 | Salesforce, Inc. | Monitoring and verification system for end-to-end distribution of messages |
US10963307B2 (en) | 2019-04-08 | 2021-03-30 | Salesforce.Com, Inc. | Client-side memory management in component-driven console applications |
US11579940B2 (en) | 2019-04-11 | 2023-02-14 | Salesforce.Com, Inc. | Techniques and architectures for managing global installations and configurations |
US10922062B2 (en) | 2019-04-15 | 2021-02-16 | Salesforce.Com, Inc. | Software application optimization |
US10922095B2 (en) | 2019-04-15 | 2021-02-16 | Salesforce.Com, Inc. | Software application performance regression analysis |
US11113302B2 (en) | 2019-04-23 | 2021-09-07 | Salesforce.Com, Inc. | Updating one or more databases based on dataflow events |
US11520759B2 (en) | 2019-04-26 | 2022-12-06 | Salesforce.Com, Inc. | Processing time series metrics data |
US11231923B2 (en) | 2019-04-26 | 2022-01-25 | Salesforce.Com, Inc. | Configurable transaction status interface |
US11436005B2 (en) | 2019-04-30 | 2022-09-06 | Salesforce.Com, Inc. | Generic integrated development environment extension tool for design systems |
US11100813B2 (en) | 2019-05-09 | 2021-08-24 | Salesforce.Com, Inc. | System and method for managing screen reader announcements on web pages |
US11176156B2 (en) | 2019-05-10 | 2021-11-16 | Salesforce.Com, Inc. | Efficiently and accurately assessing the number of identifiable records for creating personal profiles |
US11157298B2 (en) | 2019-05-21 | 2021-10-26 | Salesforce.Com, Inc. | Method and system for automatically invoking functionality while using a primary application without user action |
US11360990B2 (en) | 2019-06-21 | 2022-06-14 | Salesforce.Com, Inc. | Method and a system for fuzzy matching of entities in a database system based on machine learning |
US11113256B2 (en) | 2019-06-27 | 2021-09-07 | Salesforce.Com, Inc. | Automated data discovery with external knowledge bases |
US11245729B2 (en) | 2019-07-09 | 2022-02-08 | Salesforce.Com, Inc. | Group optimization for network communications |
US11023556B2 (en) | 2019-07-10 | 2021-06-01 | Salesforce.Com, Inc. | Web page designing with content beam to device preview |
US11221845B2 (en) | 2019-07-25 | 2022-01-11 | Salesforce.Com, Inc. | Visual media metadata-based software configuration using design systems |
US11221843B2 (en) | 2019-07-25 | 2022-01-11 | Salesforce.Com, Inc. | Auditory media metadata-based software configuration using design systems |
US11748029B2 (en) | 2019-07-26 | 2023-09-05 | Salesforce, Inc. | Protecting writes to shared storage in a distributed search system |
US11138202B2 (en) | 2019-07-29 | 2021-10-05 | Salesforce.Com, Inc. | Techniques for determining and presenting dataset join candidates |
US11163740B2 (en) | 2019-07-30 | 2021-11-02 | Salesforce.Com, Inc. | Machine-learnt field-specific tokenization |
US11087333B2 (en) | 2019-07-30 | 2021-08-10 | Salesforce.Com, Inc. | Facilitating session-based read/write of context variables to share information across multiple microservices |
US11698891B2 (en) | 2019-07-30 | 2023-07-11 | Salesforce.Com, Inc. | Database systems and related multichannel communication methods |
US11886461B2 (en) | 2019-07-31 | 2024-01-30 | Salesforce, Inc. | Machine-learnt field-specific standardization |
US11151088B2 (en) | 2019-08-02 | 2021-10-19 | Salesforce.Com, Inc. | Systems and methods for verifying performance of a modification request in a database system |
US11586945B2 (en) | 2019-08-06 | 2023-02-21 | Salesforce.Com, Inc. | Methods and systems for automated, intelligent application process development that recommend how to modify applications based on usage patterns of end users |
US11347795B2 (en) | 2019-08-08 | 2022-05-31 | Salesforce.Com, Inc. | Tools and methods that format mapping information from a data integration system |
US11170322B2 (en) | 2019-08-13 | 2021-11-09 | Salesforce.Com, Inc. | Using a client-side machine learning model dynamically in a mobile enterprise application on a mobile device |
US11288640B2 (en) | 2019-08-30 | 2022-03-29 | Salesforce.Com, Inc. | Cloud computing platform, method and system having a payments platform for integrating an asynchronous payment gateway service with the cloud computing platform |
US11538000B2 (en) | 2019-08-30 | 2022-12-27 | Salesforce.Com, Inc. | Cloud computing platform, method and system having a payments platform for integrating a synchronous payment gateway service with the cloud computing platform |
US11080704B2 (en) | 2019-08-30 | 2021-08-03 | Salesforce.Com, Inc. | Payments platform, method and system having external and internal operating modes for ingesting payment transaction data from payment gateway services at a cloud computing platform |
US11074559B2 (en) | 2019-08-30 | 2021-07-27 | Salesforce.Com, Inc. | Payments platform, method and system for a cloud computing platform |
US11481365B2 (en) | 2019-09-07 | 2022-10-25 | Salesforce.Com, Inc. | Model instantiation mechanism |
US10984283B2 (en) | 2019-09-10 | 2021-04-20 | Salesforce.Com, Inc. | Recognition of biases in data and models |
US11379266B2 (en) | 2019-09-10 | 2022-07-05 | Salesforce.Com, Inc. | Automatically identifying and right sizing instances |
US11321490B2 (en) | 2019-09-11 | 2022-05-03 | Salesforce.Com, Inc. | Protected access to metadata based on package membership |
US11151150B2 (en) | 2019-09-13 | 2021-10-19 | Salesforce.Com, Inc. | Adjustable connection pool mechanism |
US11403280B2 (en) | 2019-09-25 | 2022-08-02 | Salesforce.Com, Inc. | Master data management technologies |
US11567957B2 (en) | 2019-09-25 | 2023-01-31 | Salesforce.Com, Inc. | Incremental addition of data to partitions in database tables |
US11567850B2 (en) | 2019-10-01 | 2023-01-31 | Salesforce, Inc. | Detecting application events based on encoding application log values |
US11068244B2 (en) | 2019-10-01 | 2021-07-20 | Salesforce.Com, Inc. | Optimized transpilation |
US11514008B2 (en) | 2019-10-02 | 2022-11-29 | Salesforce, Inc. | Dynamically controlling data migration |
US11403265B2 (en) | 2019-10-02 | 2022-08-02 | Salesforce, Inc. | Dynamically controlling data migration |
US11636067B2 (en) | 2019-10-04 | 2023-04-25 | Salesforce.Com, Inc. | Performance measurement mechanism |
US11637831B2 (en) | 2019-10-09 | 2023-04-25 | Salesforce, Inc. | Application programmer interface platform with direct data center access |
US11416484B2 (en) | 2019-10-15 | 2022-08-16 | Salesforce, Inc. | Performance optimization of hybrid sharing model queries |
US11244004B2 (en) | 2019-10-23 | 2022-02-08 | Salesforce.Com, Inc. | Generating adaptive match keys based on estimating counts |
US11165857B2 (en) | 2019-10-23 | 2021-11-02 | Salesforce.Com, Inc. | Connection pool anomaly detection mechanism |
US11431663B2 (en) | 2019-10-24 | 2022-08-30 | Salesforce, Inc. | Technologies for predicting personalized message send times |
US10986051B1 (en) | 2019-10-31 | 2021-04-20 | Salesforce.Com, Inc. | System and method for dynamic chat message customization |
US11086764B2 (en) | 2019-10-31 | 2021-08-10 | Salesforce.Com, Inc. | Identification of code ownership through test coverage in database systems |
US11381540B2 (en) | 2019-10-31 | 2022-07-05 | Salesforce, Inc. | Tracking premature events in electronic message processing |
US11693853B2 (en) | 2019-10-31 | 2023-07-04 | Salesforce, Inc. | Capture and replay of user requests for performance analysis |
US11431481B2 (en) | 2019-11-07 | 2022-08-30 | Salesforce, Inc. | System for securing memory dumps |
US11307957B2 (en) | 2019-11-07 | 2022-04-19 | Salesforce.Com, Inc. | Systems and methods for determining optimal cost-to-serve for cloud applications in the public cloud |
US11410107B2 (en) | 2019-11-07 | 2022-08-09 | Salesforce.Com, Inc. | Systems and methods for real-time determination of cost-to-serve metrics and cost attribution for cloud applications in the public cloud |
US11507617B2 (en) | 2019-11-15 | 2022-11-22 | Salesforce, Inc. | Unsupervised dialogue topic extraction |
US20210150483A1 (en) | 2019-11-18 | 2021-05-20 | Salesforce.Com, Inc. | System and method for automatically creating personalized courses and trackable achievements |
US11314790B2 (en) | 2019-11-18 | 2022-04-26 | Salesforce.Com, Inc. | Dynamic field value recommendation methods and systems |
US11481540B2 (en) | 2019-11-19 | 2022-10-25 | Salesforce.Com, Inc. | Discrepancy resolution processor and methods for implementing the same |
US11544762B2 (en) | 2019-11-19 | 2023-01-03 | Salesforce.Com, Inc. | Techniques and architectures for recommending products based on work orders |
US11431500B2 (en) | 2019-11-26 | 2022-08-30 | Salesforce, Inc. | Authorization code management for published static applications |
US11120702B2 (en) | 2019-12-01 | 2021-09-14 | Salesforce.Com, Inc. | Systems and methods for validating localized assessments in an external system |
US11593220B2 (en) | 2019-12-10 | 2023-02-28 | Salesforce.Com, Inc. | Ticketing system for managing computing services |
US11531554B2 (en) | 2019-12-10 | 2022-12-20 | Salesforce.Com, Inc. | Automated hierarchical tuning of configuration parameters for a multi-layer service |
US11157314B2 (en) | 2019-12-10 | 2021-10-26 | Salesforce.Com, Inc. | Convergence scheduling |
US11443205B2 (en) | 2019-12-13 | 2022-09-13 | Salesforce.Com, Inc. | Self-managing database system using machine learning |
US11481363B2 (en) | 2019-12-13 | 2022-10-25 | Salesforce.Com, Inc. | Adaptable database deployment |
US11354726B2 (en) | 2019-12-20 | 2022-06-07 | Salesforce.Com, Inc. | Change order application programming interfaces |
US11055093B1 (en) | 2019-12-23 | 2021-07-06 | Salesforce.Com, Inc. | Methods and systems for automated, intelligent application development by scanning metadata by a plug-in to make recommendations |
US11249752B2 (en) | 2020-01-07 | 2022-02-15 | Salesforce.Com, Inc. | Code classification mechanism |
US11494202B2 (en) | 2020-01-08 | 2022-11-08 | Salesforce.Com, Inc. | Database replication plugins as a service |
US11126351B2 (en) | 2020-01-09 | 2021-09-21 | Salesforce.Com, Inc. | Policy-based management of disk storage for consumer storge buckets |
US11636071B2 (en) | 2020-01-10 | 2023-04-25 | Salesforce.Com, Inc. | Database replication error recovery based on supervised learning |
US11177973B2 (en) | 2020-01-10 | 2021-11-16 | Salesforce.Com, Inc. | Distributed audience computation software service |
US11442989B2 (en) | 2020-01-13 | 2022-09-13 | Salesforce, Inc. | Scalable roll-up summary field calculation using graphs |
US11775287B2 (en) | 2020-01-15 | 2023-10-03 | Salesforce, Inc. | Manifest and content delivery |
US11620483B2 (en) | 2020-01-17 | 2023-04-04 | Salesforce, Inc. | Discovering suspicious person profiles |
US11887088B2 (en) | 2020-01-22 | 2024-01-30 | Salesforce, Inc. | Smart moderation and/or validation of product and/or service details in database systems |
US11755680B2 (en) | 2020-01-22 | 2023-09-12 | Salesforce, Inc. | Adaptive recognition of entities |
US11349923B2 (en) | 2020-01-23 | 2022-05-31 | Salesforce.Com, Inc. | Persistent volumes for stateful applications |
US11799901B2 (en) | 2020-01-23 | 2023-10-24 | Salesforce, Inc. | Predictive rate limiting system for cloud computing services |
US11243812B2 (en) | 2020-01-23 | 2022-02-08 | Salesforce.Com, Inc. | Automated operating system patching using auto scaling group and persistent volumes |
US11372667B2 (en) | 2020-01-27 | 2022-06-28 | Salesforce, Inc. | Restoring the state of paused virtual machine environments with external attached volumes |
US11494286B2 (en) | 2020-01-27 | 2022-11-08 | Salesforce.Com, Inc. | Dynamic adjustment of web product-based performance factors in database systems |
US11573880B2 (en) | 2020-01-27 | 2023-02-07 | Salesforce.Com, Inc. | Performance simulation for selected platforms for web products in database systems |
US11151638B2 (en) | 2020-01-27 | 2021-10-19 | Salesforce.Com, Inc. | Methods and systems for performing change management at login |
US11429577B2 (en) | 2020-01-27 | 2022-08-30 | Salesforce.Com, Inc. | Performance simulation and cost-benefit analysis for performance factors for web products in database systems |
US11397736B2 (en) | 2020-01-27 | 2022-07-26 | Salesforce, Inc. | Large scale data ingestion |
US11281563B2 (en) | 2020-01-27 | 2022-03-22 | Salesforce.Com, Inc. | Actionable insights for performance of web products in database systems |
US11663169B2 (en) | 2020-01-28 | 2023-05-30 | Salesforce.Com, Inc. | Dynamic asset management system and methods for automatically tracking assets, generating asset records for assets, and linking asset records to other types of records in a database of a cloud computing system |
US11461559B2 (en) | 2020-01-28 | 2022-10-04 | Salesforce.Com, Inc. | Mechanism to facilitate image translation |
US11922382B2 (en) | 2020-01-28 | 2024-03-05 | Salesforce, Inc. | Transaction system having a serverless architecture that provides multi-language multi-platform transaction support for multiple vendors in conjunction with a cloud-based computing platform |
US11663544B2 (en) | 2020-01-28 | 2023-05-30 | Salesforce.Com, Inc. | System and methods for risk assessment in a multi-tenant cloud environment |
US11580276B2 (en) | 2020-01-28 | 2023-02-14 | Salesforce.Com, Inc. | Dynamic asset management system and methods for generating interactive simulations representing assets based on automatically generated asset records |
US11392581B2 (en) | 2020-01-28 | 2022-07-19 | Salesforce.Com, Inc. | System and method for providing dynamically grouped search results from a hierarchy |
US11875393B2 (en) | 2020-01-28 | 2024-01-16 | Salesforce, Inc. | Generation of recommendations from dynamically-mapped data |
US11082284B1 (en) | 2020-01-28 | 2021-08-03 | Salesforce.Com, Inc. | Applying configurations to applications in a multi-server environment |
US11372928B2 (en) | 2020-01-29 | 2022-06-28 | Salesforce.Com, Inc. | Adaptive match indexes |
US11314735B2 (en) | 2020-01-29 | 2022-04-26 | Salesforce.Com, Inc. | Generation of query stacks from object relationships |
US11755720B2 (en) | 2020-01-31 | 2023-09-12 | Salesforce, Inc. | Secure membranes and cross namespace communication |
US11934351B2 (en) | 2020-01-31 | 2024-03-19 | Salesforce, Inc. | Lossless conversion of expressive metadata |
US11588840B2 (en) | 2020-01-31 | 2023-02-21 | Salesforce, Inc. | Automated encryption degradation detection, reporting and remediation |
US11005801B1 (en) | 2020-01-31 | 2021-05-11 | Salesforce.Com, Inc. | Personalized dashboard chart for email subscriptions |
US11113180B2 (en) | 2020-01-31 | 2021-09-07 | Salesforce.Com, Inc. | Efficiently tracking code location of run-time events in system software |
US11790414B2 (en) | 2020-01-31 | 2023-10-17 | Salesforce, Inc. | Techniques and architectures for customizable modular line item evaluation |
US11711330B2 (en) | 2020-01-31 | 2023-07-25 | Salesforce, Inc. | Out of office message configuration |
US11537503B2 (en) | 2020-01-31 | 2022-12-27 | Salesforce.Com, Inc. | Code editor for user interface component testing |
US11798044B2 (en) | 2020-01-31 | 2023-10-24 | Salesforce, Inc. | Pluggable architecture for performance of pricing operations |
US11233787B2 (en) | 2020-01-31 | 2022-01-25 | Salesforce.Com, Inc. | Automated on call and ad hoc access to restricted resources |
US11475049B2 (en) | 2020-01-31 | 2022-10-18 | Salesforce, Inc. | Methods and systems for organization extensibility and cluster scalability |
US11297501B2 (en) | 2020-01-31 | 2022-04-05 | Salesforce.Com, Inc. | Firewall discovery and management |
US11915834B2 (en) | 2020-04-09 | 2024-02-27 | Salesforce, Inc. | Efficient volume matching of patients and providers |
US11416677B2 (en) | 2020-04-09 | 2022-08-16 | Salesforce.Com, Inc. | Dynamic resource management systems and form integration methods |
US11526551B2 (en) | 2020-04-10 | 2022-12-13 | Salesforce, Inc. | Search query generation based on audio processing |
US11509608B2 (en) | 2020-04-13 | 2022-11-22 | Salesforce, Inc. | Methods and systems for configuring an email engine |
US11539652B2 (en) | 2020-04-13 | 2022-12-27 | Salesforce, Inc. | Rate limiting actions with a message queue |
US11916918B2 (en) | 2020-04-14 | 2024-02-27 | Salesforce, Inc. | System mode override during flow execution |
US11552802B2 (en) | 2020-04-15 | 2023-01-10 | Salesforce, Inc. | Stateless mutual authentication between services |
US11880835B2 (en) | 2020-04-24 | 2024-01-23 | Salesforce, Inc. | Prevention of duplicate transactions across multiple transaction entities in database systems |
US11847642B2 (en) | 2020-04-24 | 2023-12-19 | Salesforce, Inc. | Secure communication of data during transactions across multiple transaction entities in database systems |
US10936571B1 (en) | 2020-04-28 | 2021-03-02 | Salesforce.Com, Inc. | Undo based logical rewind in a multi-tenant system |
US11755582B2 (en) | 2020-04-30 | 2023-09-12 | Salesforce, Inc. | Adaptive field-level matching |
US11663038B2 (en) | 2020-05-01 | 2023-05-30 | Salesforce.Com, Inc. | Workflow data migration management |
US11163731B1 (en) | 2020-05-04 | 2021-11-02 | Salesforce.Com, Inc. | Autobuild log anomaly detection methods and systems |
US11934403B2 (en) | 2020-05-18 | 2024-03-19 | Salesforce, Inc. | Generating training data for natural language search systems |
US11164118B1 (en) | 2020-05-21 | 2021-11-02 | Salesforce.Com, Inc. | Generating work plans which include work steps when creating new work orders |
US11182719B1 (en) | 2020-05-21 | 2021-11-23 | Salesforce.Com, Inc. | Associating executable actions with work steps in work plans generated when creating work orders |
US11474793B2 (en) | 2020-05-22 | 2022-10-18 | Salesforce.Com, Inc. | Polymorphic application architecture |
US11113459B1 (en) | 2020-05-22 | 2021-09-07 | Salesforce.Com, Inc. | Dynamic guidance engine for software customization systems |
US11294648B2 (en) | 2020-05-22 | 2022-04-05 | Salesforce.Com, Inc. | Application development architecture for mobile applications |
US11556461B2 (en) | 2020-06-16 | 2023-01-17 | Salesforce.Com, Inc. | Middleware for transparent user interface testing |
US11494509B2 (en) | 2020-06-19 | 2022-11-08 | Salesforce.Com, Inc. | Controlling just in time access to a cluster |
US11526528B2 (en) | 2020-07-07 | 2022-12-13 | Salesforce.Com, Inc. | Techniques and architectures for providing atomic transactions across multiple data sources |
US11762656B2 (en) | 2020-07-13 | 2023-09-19 | Salesforce, Inc. | Service fabrication tool |
US11522686B2 (en) | 2020-07-16 | 2022-12-06 | Salesforce, Inc. | Securing data using key agreement |
US11392419B2 (en) | 2020-07-16 | 2022-07-19 | Salesforce.Com, Inc. | Cloud agnostic workload identity |
US11368292B2 (en) | 2020-07-16 | 2022-06-21 | Salesforce.Com, Inc. | Securing data with symmetric keys generated using inaccessible private keys |
US11194774B1 (en) | 2020-07-20 | 2021-12-07 | Salesforce.Com, Inc. | Systems and methods for logically copying data from a source database to one or more target databases |
US11314767B2 (en) | 2020-07-30 | 2022-04-26 | Salesforce.Com, Inc. | Techniques and architectures for managing cascading mutations in an environment having a data lake |
US11586643B2 (en) | 2020-08-11 | 2023-02-21 | Salesforce.Com, Inc. | Enabling dynamic data capture with database objects |
US11567945B1 (en) | 2020-08-27 | 2023-01-31 | Pegasystems Inc. | Customized digital content generation systems and methods |
US11159625B1 (en) | 2020-09-04 | 2021-10-26 | Salesforce.Com, Inc. | Efficiently distributing connections to service instances that stream multi-tenant data |
US11582252B2 (en) | 2020-09-11 | 2023-02-14 | Salesforce.Com, Inc. | Efficient monitoring of network activity in a cloud computing environment |
US11477273B2 (en) | 2020-09-11 | 2022-10-18 | Salesforce.Com, Inc. | Feedback control based load balancing for containerized workloads |
US11907385B2 (en) | 2020-09-18 | 2024-02-20 | Salesforce, Inc. | Process flow granular control and execution |
US11416382B2 (en) | 2020-09-18 | 2022-08-16 | Salesforce, Inc. | Change list-based snapshots of applications for development and testing |
US11460975B2 (en) | 2020-09-18 | 2022-10-04 | Salesforce, Inc. | Metric presentation within a flow builder |
US11379351B2 (en) | 2020-09-18 | 2022-07-05 | Salesforce, Inc. | Change list-based snapshots of applications for testing and development |
US11734237B2 (en) | 2020-10-09 | 2023-08-22 | Salesforce.Com, Inc. | Management of application of data actions to updated data objects in a data store |
US11658957B2 (en) | 2020-10-23 | 2023-05-23 | Salesforce.Com, Inc. | Methods and apparatuses for temporary session authentication and governor limits management |
US11275569B1 (en) | 2020-10-30 | 2022-03-15 | Salesforce.Com, Inc. | Techniques and architectures for providing continuous integration (CI) and/or continuous delivery (CD) in a data lake environment |
US11687523B2 (en) | 2020-11-25 | 2023-06-27 | Salesforce, Inc. | System and method for efficiently transferring data for offline use |
US11595309B2 (en) | 2020-11-30 | 2023-02-28 | Salesforce, Inc. | Source network address translation for unique sender identification |
US11675800B2 (en) | 2020-11-30 | 2023-06-13 | Salesforce, Inc. | Version control and execution on a mobile device |
US11467949B2 (en) | 2020-12-01 | 2022-10-11 | Salesforce.Com, Inc. | Techniques and architectures for providing an isolated runtime context in a shared environment |
US11429376B2 (en) * | 2020-12-07 | 2022-08-30 | Oracle International Corporation | Run-time modification of an application definition schema that controls the behavior of a software application |
US11520797B2 (en) | 2020-12-11 | 2022-12-06 | Salesforce, Inc. | Leveraging time-based comments on communications recordings |
US11328032B1 (en) | 2020-12-21 | 2022-05-10 | Salesforce.Com, Inc. | Systems and methods for presenting a demo for enabling a visual dialogue with a customer by single user tap actions |
US11924210B2 (en) | 2021-01-15 | 2024-03-05 | Salesforce, Inc. | Protected resource authorization using autogenerated aliases |
US11640348B2 (en) | 2021-01-22 | 2023-05-02 | Salesforce.Com, Inc. | Generating anomaly alerts for time series data |
US11740989B2 (en) | 2021-01-22 | 2023-08-29 | Salesforce, Inc. | Generating performance metrics from events derived from user interface logs |
US11449409B2 (en) | 2021-01-22 | 2022-09-20 | Salesforce.Com, Inc. | Schema inference and log data validation system |
US11741119B2 (en) | 2021-01-26 | 2023-08-29 | Salesforce, Inc. | Canonical data model for distributed data catalog and metadata exchange |
US11573682B2 (en) | 2021-01-27 | 2023-02-07 | Salesforce.Com, Inc. | System and method for selecting one out of a plurality of participants in a network-based video meeting |
US11630844B2 (en) | 2021-01-29 | 2023-04-18 | Salesforce.Com, Inc. | System and method for augmenting synced data across multiple systems to facilitate data cleansing |
US11330070B1 (en) | 2021-01-29 | 2022-05-10 | Salesforce.Com, Inc. | Containerized workflow engines executing metadata for user-defined applications |
US11853699B2 (en) | 2021-01-29 | 2023-12-26 | Salesforce.Com, Inc. | Synthetic crafting of training and test data for named entity recognition by utilizing a rule-based library |
US11728974B2 (en) | 2021-01-29 | 2023-08-15 | Salesforce, Inc. | Tenant-based database encryption |
US11509746B2 (en) | 2021-02-17 | 2022-11-22 | Salesforce.Com, Inc. | Distributing user requests to cloud computing systems across regions using a machine learning model |
US11520482B2 (en) | 2021-02-22 | 2022-12-06 | Salesforce.Com, Inc. | Navigating displayed graphical user interface panels using assigned keyboard shortcut key(s) |
US11797638B2 (en) | 2021-02-24 | 2023-10-24 | Salesforce.Com, Inc. | Aggregate component for parallel browser-initiated actions |
US11321422B1 (en) | 2021-03-09 | 2022-05-03 | Salesforce.Com, Inc. | User-configurable aggregate web components |
US11556608B2 (en) | 2021-03-22 | 2023-01-17 | Salesforce.Com, Inc. | Caching for single page web applications |
US11620305B2 (en) | 2021-03-25 | 2023-04-04 | Salesforce.Com, Inc | Ruleset engine for generating homogeneous data sets |
US11385876B1 (en) | 2021-04-01 | 2022-07-12 | Salesforce.Com, Inc. | Infrastructure control interface for database systems |
US11775519B2 (en) | 2021-04-08 | 2023-10-03 | Salesforce, Inc. | Optimizing indexes for accessing database tables |
US11520691B2 (en) | 2021-04-14 | 2022-12-06 | Salesforce.Com, Inc. | Test procedure systems and methods |
US11429257B1 (en) | 2021-04-15 | 2022-08-30 | Salesforce.Com, Inc. | Dynamically generated help based on derived hierarchical context |
US11929901B2 (en) | 2021-04-22 | 2024-03-12 | Salesforce, Inc. | Infrastructure-agnostic performance of computation sequences |
US11620124B2 (en) | 2021-04-23 | 2023-04-04 | Salesforce.Com, Inc. | System and method for flow runtime versioning |
US11636025B2 (en) | 2021-04-27 | 2023-04-25 | Salesforce, Inc. | Intelligent generation of automated user interface testing methods |
US11748243B2 (en) | 2021-04-27 | 2023-09-05 | Salesforce, Inc. | Intelligent generation of page objects for user interface testing |
US11487753B1 (en) | 2021-05-03 | 2022-11-01 | Salesforce, Inc. | Optimizing transaction times in distributed databases |
US11675653B2 (en) | 2021-05-11 | 2023-06-13 | Salesforce.Com, Inc. | Management and remediation of database issues |
US11507729B1 (en) | 2021-05-13 | 2022-11-22 | Salesforce, Inc. | Scoped containers using CSS custom properties and color pairs |
US11755546B2 (en) | 2021-05-21 | 2023-09-12 | Salesforce, Inc. | Attribute aware relationship-based access control on row and field levels in a relational database |
US11665268B2 (en) | 2021-07-30 | 2023-05-30 | Salesforce.Com, Inc. | Customization in standard application programming interfaces (APIs) provided by a cloud computing platform |
US11836072B2 (en) | 2021-08-23 | 2023-12-05 | Salesforce.Com, Inc. | Risk-based root cause identification methods and related autobuild systems |
US11681522B2 (en) | 2021-10-21 | 2023-06-20 | Salesforce, Inc. | Self-healing build pipelines for an application build process across distributed computer platforms |
US11442754B1 (en) | 2021-10-27 | 2022-09-13 | Salesforce, Inc. | Targeting system for web page components |
US11886458B2 (en) | 2021-11-05 | 2024-01-30 | Salesforce, Inc. | Configurable data transformation between different database systems |
US11755400B2 (en) | 2021-11-30 | 2023-09-12 | Salesforce, Inc. | Error detection and mitigation for software pull requests |
US11734265B1 (en) | 2022-03-08 | 2023-08-22 | Salesforce, Inc. | Automatic GraphQL data source field change handler |
US11934655B2 (en) | 2022-03-28 | 2024-03-19 | Salesforce, Inc. | Systems and methods for a log partitioner service |
US11893377B2 (en) | 2022-04-27 | 2024-02-06 | Salesforce, Inc. | Dependency-aware rules engine for delivering managed package upgrades |
US11874797B1 (en) | 2022-06-23 | 2024-01-16 | Salesforce, Inc. | Smart privilege escalation in a cloud platform |
US11750460B1 (en) | 2022-10-06 | 2023-09-05 | Salesforce, Inc. | Identifying duplicate entries in views of same and other network management interfaces |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4558413A (en) * | 1983-11-21 | 1985-12-10 | Xerox Corporation | Software version management system |
US4714996A (en) * | 1985-11-26 | 1987-12-22 | International Business Machines Corporation | Impact calculation for version management in a distributed information service |
GB2203573A (en) * | 1987-04-02 | 1988-10-19 | Ibm | Data processing network with upgrading of files |
US5155847A (en) * | 1988-08-03 | 1992-10-13 | Minicom Data Corporation | Method and apparatus for updating software at remote locations |
US5136707A (en) * | 1988-10-28 | 1992-08-04 | At&T Bell Laboratories | Reliable database administration arrangement |
JP3270102B2 (en) * | 1991-03-11 | 2002-04-02 | ヒューレット・パッカード・カンパニー | Licensing method and system |
DE69425198T2 (en) * | 1993-08-13 | 2001-03-15 | Toshiba Kawasaki Kk | Two way cable television system |
WO1995008809A2 (en) * | 1993-09-24 | 1995-03-30 | Oracle Corporation | Method and apparatus for data replication |
US5546539A (en) * | 1993-12-29 | 1996-08-13 | Intel Corporation | Method and system for updating files of a plurality of storage devices through propogation of files over a nework |
US5835911A (en) * | 1994-02-08 | 1998-11-10 | Fujitsu Limited | Software distribution and maintenance system and method |
US5586304A (en) * | 1994-09-08 | 1996-12-17 | Compaq Computer Corporation | Automatic computer upgrading |
US5978813A (en) * | 1995-09-25 | 1999-11-02 | International Business Machines Corporation | System for providing synchronization between a local area network and a distributing computer environment |
US5845077A (en) * | 1995-11-27 | 1998-12-01 | Microsoft Corporation | Method and system for identifying and obtaining computer software from a remote computer |
US5873096A (en) * | 1997-10-08 | 1999-02-16 | Siebel Systems, Inc. | Method of maintaining a network of partially replicated database system |
GB9623298D0 (en) * | 1996-11-08 | 1997-01-08 | Int Computers Ltd | Updating mechanism for software |
WO1998040804A2 (en) * | 1997-02-26 | 1998-09-17 | Siebel Systems, Inc. | Distributed relational database |
-
1998
- 1998-02-24 WO PCT/US1998/003572 patent/WO1998040805A2/en active Application Filing
- 1998-02-24 AU AU63367/98A patent/AU6336798A/en not_active Abandoned
-
1999
- 1999-08-17 US US09/375,427 patent/US6324693B1/en not_active Expired - Lifetime
-
2001
- 2001-11-27 US US09/992,813 patent/US20030009753A1/en not_active Abandoned
Cited By (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7584468B2 (en) * | 1999-05-10 | 2009-09-01 | Apple Inc. | Distributing and synchronizing objects |
US20050268307A1 (en) * | 1999-05-10 | 2005-12-01 | Apple Computer, Inc. | Distributing and synchronizing objects |
US9838474B2 (en) | 1999-05-10 | 2017-12-05 | Apple Inc. | Distributing and synchronizing objects |
US6789215B1 (en) * | 2000-04-21 | 2004-09-07 | Sprint Communications Company, L.P. | System and method for remediating a computer |
US7086050B2 (en) * | 2000-08-04 | 2006-08-01 | Mcafee, Inc. | Updating computer files |
US20020016959A1 (en) * | 2000-08-04 | 2002-02-07 | Networks Associates Technology, Inc. | Updating computer files |
US8848899B2 (en) | 2000-11-17 | 2014-09-30 | Qualcomm Incorporated | Operator network that routes customer care calls based on subscriber / device profile and CSR skill set |
US20080175372A1 (en) * | 2000-11-17 | 2008-07-24 | Jeffrey Brunet | Operator network that routes customer care calls based on subscriber / device profile and csr skill set |
US20030217031A1 (en) * | 2002-05-16 | 2003-11-20 | International Business Machines Corporation | Apparatus and method for validating a database record before applying journal data |
US6968349B2 (en) * | 2002-05-16 | 2005-11-22 | International Business Machines Corporation | Apparatus and method for validating a database record before applying journal data |
US8555273B1 (en) * | 2003-09-17 | 2013-10-08 | Palm. Inc. | Network for updating electronic devices |
US20050132351A1 (en) * | 2003-12-12 | 2005-06-16 | Randall Roderick K. | Updating electronic device software employing rollback |
US20110173598A1 (en) * | 2004-04-21 | 2011-07-14 | Chris Cassapakis | Updating an electronic device with update agent code |
US8578361B2 (en) | 2004-04-21 | 2013-11-05 | Palm, Inc. | Updating an electronic device with update agent code |
US7596585B2 (en) | 2004-11-03 | 2009-09-29 | Honeywell International Inc. | Object replication using information quality of service |
US20060106894A1 (en) * | 2004-11-03 | 2006-05-18 | Honeywell International Inc. | Object replication using information quality of service |
US20070180151A1 (en) * | 2005-09-20 | 2007-08-02 | Honeywell International Inc. | Model driven message processing |
US20070207800A1 (en) * | 2006-02-17 | 2007-09-06 | Daley Robert C | Diagnostics And Monitoring Services In A Mobile Network For A Mobile Device |
US8286127B2 (en) * | 2006-04-14 | 2012-10-09 | Apple Inc. | Mirrored file system |
US20100287526A1 (en) * | 2006-04-14 | 2010-11-11 | Apple Inc. | Mirrored file system |
US8893110B2 (en) | 2006-06-08 | 2014-11-18 | Qualcomm Incorporated | Device management in a network |
US9081638B2 (en) | 2006-07-27 | 2015-07-14 | Qualcomm Incorporated | User experience and dependency management in a mobile device |
US20080028395A1 (en) * | 2006-07-27 | 2008-01-31 | Giovanni Motta | User Experience And Dependency Management In A Mobile Device |
US8752044B2 (en) | 2006-07-27 | 2014-06-10 | Qualcomm Incorporated | User experience and dependency management in a mobile device |
US11347771B2 (en) * | 2007-11-28 | 2022-05-31 | International Business Machines Corporation | Content engine asynchronous upgrade framework |
US20090138523A1 (en) * | 2007-11-28 | 2009-05-28 | Wan-Chang Pi | Content engine asynchronous upgrade framework |
US20090248760A1 (en) * | 2008-03-27 | 2009-10-01 | Fujitsu Limited | Backup method of computer system |
US20100153351A1 (en) * | 2008-12-16 | 2010-06-17 | Yung Alex P | Techniques for real-time database processing |
US8965853B2 (en) * | 2010-04-09 | 2015-02-24 | Ca, Inc. | Distributed system having a shared central database |
US20120254214A1 (en) * | 2010-04-09 | 2012-10-04 | Computer Associates Think, Inc | Distributed system having a shared central database |
US20120036199A1 (en) * | 2010-08-09 | 2012-02-09 | Thomas Stephen Slee | Sharing Data on Mobile Devices |
US9977819B2 (en) * | 2010-08-09 | 2018-05-22 | Ianywhere Solutions, Inc. | Sharing data on mobile devices |
CN103140850A (en) * | 2010-08-09 | 2013-06-05 | 移动解决方案公司 | Sharing data on mobile devices |
US20130036412A1 (en) * | 2011-08-02 | 2013-02-07 | Roche Diagnostics Operations, Inc. | Software distribution amongst medical devices taking into account dependencies between devices |
US8893109B2 (en) * | 2011-08-02 | 2014-11-18 | Roche Diagnostics Operations, Inc. | Software distribution amongst medical devices taking into account dependencies between devices |
US9977671B2 (en) | 2015-07-20 | 2018-05-22 | Google Llc | Methods for multi-source configuration of mobile applications |
US10241783B2 (en) | 2015-07-20 | 2019-03-26 | Google Llc | Methods for multi-source configuration of mobile applications |
Also Published As
Publication number | Publication date |
---|---|
WO1998040805A9 (en) | 1999-05-06 |
US6324693B1 (en) | 2001-11-27 |
WO1998040805A3 (en) | 1999-02-25 |
AU6336798A (en) | 1998-09-29 |
WO1998040805A2 (en) | 1998-09-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6324693B1 (en) | Method of synchronizing independently distributed software and database schema | |
US7231407B2 (en) | Partially replicated distributed database with multiple levels of remote clients | |
US6604117B2 (en) | Method of maintaining a network of partially replicated database system | |
US6189011B1 (en) | Method of maintaining a network of partially replicated database system | |
US6092083A (en) | Database management system which synchronizes an enterprise server and a workgroup user client using a docking agent | |
US7076778B2 (en) | Method and apparatus for upgrading a software application in the presence of user modifications | |
US6216135B1 (en) | Method of determining visibility to a remote database client of a plurality of database transactions having variable visibility strengths | |
US6178425B1 (en) | Method of determining the visibility to a remote database client of a plurality of database transactions using simplified visibility rules | |
US6684438B2 (en) | Method of using cache to determine the visibility to a remote database client of a plurality of database transactions | |
EP1010096B1 (en) | Method of maintaining a network of partially replicated database system | |
WO1998040806A2 (en) | Method of determining the visibility to a remote database client of a plurality of database transactions |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MORGAN STANLEY & CO. INCORPORATED, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:LEGERITY, INC.;REEL/FRAME:011601/0539 Effective date: 20000804 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |