Abstract: Some embodiments of the present invention include a method for performing data assessment. The method includes receiving, by a first server computing system, a request to assess first data stored in a storage device associated with a second server computing system, the request including one or more rules indicating how the first data is to be assessed; performing, by the first server computing system, an assessment of the first data based on the one or more rules and based on a data source associated with the first server computing system, the data source including data provided by one or more data providers, the assessment of the first data including assessing outdated information and missing information based on the data source; and providing, by the first server computing system, an assessment result from the assessment of the first data and an option to engage in an enrichment of the first data based on the assessment result and the data source.

Abstract: A computing system may create a database schema representing tables for data assessment, organization identification (ID), rule ID, data source ID, and data assessment ID. The data assessment table may include a first field representing an organization ID, a second field representing a rule ID, a third field representing a data source ID, wherein the fields correspond to a records in the organization ID table, rule ID table and data source ID table, respectively. The data assessment table may also include a fourth field representing a match status indicating whether a record in data assessment ID table matches a record of a data source associated with the third field, a fifth field representing a data assessment record ID and corresponding to a record in data assessment record ID table, and a sixth field configured as a column family and representing a field of the business object.

Abstract: Some embodiments of the present invention include a method for controlling requests to be transmitted to a server computing system. The method generating, by a first requester, a request to be transmitted to a first server computing system, the first requester being part of a first group of requesters, each of the requesters in the first group of requesters is configured to access an indicator to determine whether the first server computing system is ready to receive its request, the indicator being set or reset at least based on a response received from the first server computing system, the indicator stored in a memory device associated with a second server computing system; and based on the indicator indicating that the first server computing system is not ready, delaying from transmitting, by the first requester, the request to the first server computing system.

Abstract: Some embodiments of the present invention include a method for merging nodes in hierarchies and include receiving, by a database system, a request to merge a first node in a first hierarchy of a plurality of nodes into a second node, the first node in the first hierarchy having child nodes; determining, by the database system, whether the merge request violates each of a plurality of constraints, the plurality of constraints comprising circular dependency of nodes, deleted node and ordering of nodes; and re-parenting, by the database system, in response to a determination that the merge request does not violate each of the plurality of constraints, the child nodes of the first node in the first hierarchy of nodes to the second node in response to the merging of the first node into the second node.

Abstract: The method includes generating a first graphical representation of a first group of records, including a root node associated with a first representative record of a duplicate record in the first group, the first graphical representation associated with a rank corresponding to a height of the first graphical representation. The method further includes forming a map to reflect the first graphical representation and first representative record. A second graphical representation of a second group of records is generated including a root node associated with a second representative record in the second group. The method compares each of the records in the second group of records with the map to determine if there is a sharing of a duplicate record in the second group with the first group. The first and second graphical representations are merged based on the second group of records sharing a duplicate record with the first group.

Abstract: Some embodiments of the present invention include a method for determining duplicate records in multiple objects and may include combining records associated with a first object with records associated with a second object to generate a third object, wherein the first object is related to the second object; performing de-duplication on the third object to generate a combined group of duplicate sets; and from the combined group of duplicate sets, identifying at least one duplicate set associated with both the first object and the second object based on the duplicate set having at least one record associated with the first object and at least one record associated with the second object.

Abstract: Some embodiments of the present invention include a method for identifying duplicate records from a group of records in a database system.

Abstract: Some embodiments of the present invention include a system and method for removing duplicate records from a group of records in a database system. The method includes generating a first cluster of records from the group of records, generating a second cluster of records from the group of records, identifying sets of duplicate records in the first cluster of records, and identifying sets of duplicate records in the second cluster of records. The method also includes merging at least two sets of duplicate records associated with both the first cluster and the second cluster of records to form a merged set of duplicate records. The merging is performed based on the at least two sets of duplicate records having a common record. Duplicate records in the group of records may then be removed by removing duplicate records from the merged set of duplicate records.

Abstract: Matching objects using keys based on match rules is described. A system generates a match rule key based on a match rule, wherein the match rule specifies whether two objects match. The system creates candidate keys by applying the match rule key to data objects. The system creates a probe key by applying the match rule key to a probe object. The system determines whether the probe key matches a candidate key. The system determines whether the probe object matches a candidate object based on applying the match rule to the probe object and the candidate object if the probe key matches the candidate key corresponding to the candidate object. The system identifies the probe object and the candidate object as matching based on the match rule if the probe object matches the candidate object.

Abstract: Some embodiments of the present invention include a method for identifying match candidates in a database object and may include generating, by a database system, a match key associated with a lookup field of a database object. The method may further include activating, by the database system, a matching rule associated with the match key, and receiving, by the database system, a request to search for duplicate candidates in the database object. The request may include an input entity. The duplicate candidates in the database object may be identified by using the input entity and the matching rule.

Abstract: Matching objects using keys based on match rules is described. A system generates a match rule key based on a match rule, wherein the match rule specifies whether two objects match. The system creates candidate keys by applying the match rule key to data objects. The system creates a probe key by applying the match rule key to a probe object. The system determines whether the probe key matches a candidate key. The system determines whether the probe object matches a candidate object based on applying the match rule to the probe object and the candidate object if the probe key matches the candidate key corresponding to the candidate object. The system identifies the probe object and the candidate object as matching based on the match rule if the probe object matches the candidate object.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for conditionally enabling an installation aspect. In one embodiment, code to be installed within a multi-tenant on-demand database system is identified. Additionally, a feature required to install the code is identified, where the feature includes data that is required to be accessed by the code when the code is installed and run within the multi-tenant on-demand database system. Further, the feature is conditionally enabled, based on one or more criteria.

Abstract: Methods and systems for presenting different versions of an application are described. In one example, a selection of a version of application code is received. Such a selection may include a simultaneous selection of all versions. Information about the selected version is retrieved. A description of features contained within the selected version is presented and then a version summary for each listed feature is displayed, together with the description of features, to indicate the versions of the application code that contain the respective feature.

Abstract: Systems and methods for installing and upgrading application packages to an application platform include mechanisms for allowing subscribers to make changes to components contained in managed installed packages, while allowing for upgrades of such components. The mechanisms give the subscriber the choice of using developer provided components (the ones that belong to the original package), or creating their own. This also allows developers to package the components, knowing that subscribers won't be limited to using only what's packaged, but rather will be able to make changes if they wish. Information about multiple versions of the same installed managed component is stored and managed with different ownership (e.g., one version belongs to a developer, the other to the subscriber) while in the context of a subscriber organization.

Abstract: Methods and systems for presenting different versions of an application are described. In one example, a selection of a version of application code is received. Such a selection may include a simultaneous selection of all versions. Information about the selected version is retrieved. A description of features contained within the selected version is presented and then a version summary for each listed feature is displayed, together with the description of features, to indicate the versions of the application code that contain the respective feature.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for conditionally enabling an installation aspect. These mechanisms and methods for conditionally enabling an installation aspect can enable an improved determination of boundaries associated with the code, improved communication between code developers and users, improved security and access restriction, etc.