Abstract:
Systems and methods are provided for alternative change processes for changes to data objects. A change to a data object is recorded, wherein the change is submitted to a first change process. The first change process is disabled. A second change process is asynchronously executed to process the change to the data object.
Abstract:
Systems and methods are provided for data object change history. A first data object and a second data object are retrieved, wherein the first data object includes an identifier, a field name, a first value, and a first date, and wherein the second data object includes the identifier, the field name, a second value, and a second date. A history object is stored, wherein the history object comprises the identifier, the field name, the first value, the first date, and the second date. The history object is output in response to a query which specifies the identifier, the field name, and a query date within a range of the first date and the second date.
Abstract:
The efficiency and versatility for the implementation of formulas in an on-demand database is improved. Formulas are categorized. Based at least partly on the categorization, formulas are evaluated synchronously or asynchronously. An asynchronous evaluation may be performed if a certain set of criteria is not satisfied. Asynchronous evaluations may be performed using a queue. During an asynchronous update of an object, a counter field and/or an estimate field may be used respectively for indicating the consistency of values of the object and a time when the values were consistent. The versatility of formulas is enhanced by using a formula to create a default value for a custom field when it is created and to determine whether an action is to be performed, and is enhanced by having an action define when a formula is to be updated.
Abstract:
In accordance with disclosed embodiments, there are provided methods, systems, and apparatuses for creating a data silo and testing with a data silo including, for example, initiating a test sequence against a production database within the host organization, in which the test sequence specifies: a) new data for insertion into the production database during the test sequence, and b) one or more test queries against the production database during the test sequence; performing a database transaction to insert the new data into the production database without committing the new data to the production database; recording names of one or more objects corresponding to the inserted new data, the one or more objects created as part of the transaction to insert the new data into the production database within a transaction entity object map; modifying the one or more test queries specified by the test sequence to no longer query against the production database by substituting the one or more test queries with references to the names of the one or more objects in operating memory separate from information stored within the production database; and executing the one or more modified test queries. Other related embodiments are disclosed.