Abstract: A system for model validation comprises an input interface, a model builder, a model validator, a model committer, and an attachment point. The input interface is for receiving a set of input data, wherein a first input data of the set of input data is associated with a first model level validation and a first attachment point. The model builder is for determining a model that is used to update a database based at least in part on the set of input data. The model validator is for determining whether the model is valid using model validations, wherein the model validations include the first model level validation. The model committer is for committing the model in the event the model is valid. The attachment point determiner is for determining a failure associated attachment point in the event the model is not valid, wherein the failure associated attachment point comprises the first attachment point in the event that the first model level validation failed.

Abstract: A system for executing an embedded intelligence process comprises an interface and a processor. The interface is for receiving an input object for a process associated with an embedded intelligence applet. The processor is for searching a database for a set of objects. The set of objects is based at least in part on the input object. The processor is for determining display information for the embedded intelligence applet based at least in part on the set of objects.

Abstract: A system for configuration of embedded intelligence comprises a processor and a memory. The processor is configured to associate a prompt of an embedded intelligence applet with an exposed field of a process. The memory is coupled to the processor and is configured to provide the processor with instructions. The memory is configured to store the process definition.

Abstract: A system for executing an embedded intelligence process comprises an interface and a processor. The interface is for receiving an input object for a process associated with an embedded intelligence applet. The processor is for searching a database for a set of objects. The set of objects is based at least in part on the input object. The processor is for determining display information for the embedded intelligence applet based at least in part on the set of objects.

Abstract: A system for executing an embedded intelligence process comprises an interface and a processor. The interface is for receiving an input object for a business process associated with an embedded intelligence applet. The processor is for searching a database for a set of objects. The set of objects is based at least in part on the input object. The processor is for determining display information for the embedded intelligence applet based at least in part on the set of objects.

Abstract: A system for configuration of embedded intelligence comprises a processor and a memory. The processor is configured to associate a prompt of an embedded intelligence applet with an exposed field of a process. The memory is coupled to the processor and is configured to provide the processor with instructions. The memory is configured to store the process definition.

Abstract: A system for configuration of embedded intelligence comprises a processor and a memory. The processor is configured to associate a prompt of an embedded intelligence applet with an exposed field of a business process. The memory is coupled to the processor and is configured to provide the processor with instructions. The memory is configured to store the business process definition.

Abstract: A method for synchronizing a mobile device with a central computer system is provided. The method includes coupling the mobile device to an application server of the central computer system over a network, defining a sync list that includes a candidate object type for distribution, synchronizing a relevant object of the candidate object type to the mobile device, determining a referenced object type from the relevant object type, and synchronizing a referenced object of the referenced object type to the mobile device. The sync list can be defined from meta-data that associates a user of the mobile device with one or more candidate object types, where the candidate object types serve as a starting point for the distribution process. Referenced object types can be determined from the relevant object types through additional meta-data.

Abstract: A method for synchronizing a mobile device with a central computer system is provided. The method includes coupling the mobile device to an application server of the central computer system over a network, defining a sync list that includes a candidate object type for distribution, synchronizing a relevant object of the candidate object type to the mobile device, determining a referenced object type from the relevant object type, and synchronizing a referenced object of the referenced object type to the mobile device. The sync list can be defined from meta-data that associates a user of the mobile device with one or more candidate object types, where the candidate object types serve as a starting point for the distribution process. Referenced object types can be determined from the relevant object types through additional meta-data.

Abstract: Objects in a master database and objects in a replicated database are synchronized using identifiers and version stamps of the objects. Each object has a unique identifier and a version stamp that is incremented when the object is updated at the master database. A synchronization server uses the identifiers and version stamps of objects to perform out-of-date detection and conflict detection. The synchronization server resolves update conflicts according to rules.

Abstract: A method for synchronizing a mobile device with a central computer system is provided. The method includes coupling the mobile device to an application server of the central computer system over a network, defining a sync list that includes a candidate object type for distribution, synchronizing a relevant object of the candidate object type to the mobile device, determining a referenced object type from the relevant object type, and synchronizing a referenced object of the referenced object type to the mobile device. The sync list can be defined from meta-data that associates a user of the mobile device with one or more candidate object types, where the candidate object types serve as a starting point for the distribution process. Referenced object types can be determined from the relevant object types through additional meta-data.

Abstract: A method for synchronizing a mobile device with a central computer system is provided. The method includes coupling the mobile device to an application server of the central computer system over a network, defining a sync list that includes a candidate object type for distribution, synchronizing a relevant object of the candidate object type to the mobile device, determining a referenced object type from the relevant object type, and synchronizing a referenced object of the referenced object type to the mobile device. The sync list can be defined from meta-data that associates a user of the mobile device with one or more candidate object types, where the candidate object types serve as a starting point for the distribution process. Referenced object types can be determined from the relevant object types through additional meta-data.

Abstract: A method for synchronizing a mobile device with a central computer system is provided. The method includes coupling the mobile device to an application server of the central computer system over a network, defining a sync list that includes a candidate object type for distribution, synchronizing a relevant object of the candidate object type to the mobile device, determining a referenced object type from the relevant object type, and synchronizing a referenced object of the referenced object type to the mobile device. The sync list can be defined from meta-data that associates a user of the mobile device with one or more candidate object types, where the candidate object types serve as a starting point for the distribution process. Referenced object types can be determined from the relevant object types through additional meta-data.

Abstract: Objects in a master database and objects in a replicated database are synchronized using identifiers and version stamps of the objects. Each object has a unique identifier and a version stamp that is incremented when the object is updated at the master database. A synchronization server uses the identifiers and version stamps of objects to perform out-of-date detection and conflict detection. The synchronization server resolves update conflicts according to rules.

Abstract: A method for synchronizing a mobile device with a central computer system is provided. The method includes coupling the mobile device to an application server of the central computer system over a network, defining a sync list that includes a candidate object type for distribution, synchronizing a relevant object of the candidate object type to the mobile device, determining a referenced object type from the relevant object type, and synchronizing a referenced object of the referenced object type to the mobile device. The sync list can be defined from meta-data that associates a user of the mobile device with one or more candidate object types, where the candidate object types serve as a starting point for the distribution process. Referenced object types can be determined from the relevant object types through additional meta-data.

Abstract: A method for synchronizing a mobile device with a central computer system is provided. The method includes coupling the mobile device to an application server of the central computer system over a network, defining a sync list that includes a candidate object type for distribution, synchronizing a relevant object of the candidate object type to the mobile device, determining a referenced object type from the relevant object type, and synchronizing a referenced object of the referenced object type to the mobile device. The sync list can be defined from meta-data that associates a user of the mobile device with one or more candidate object types, where the candidate object types serve as a starting point for the distribution process. Referenced object types can be determined from the relevant object types through additional meta-data.

Abstract: A method for operating a software application on a mobile device while not maintaining a real-time connection to a server includes using a server to pre-calculate relationship values between object instances stored in an object store on the mobile device, communicating the pre-calculated values to the mobile device for storage in the object store, and using the pre-calculated values to navigate between object instances while the mobile device is not in communication with the server.