Abstract: The subject disclosure relates to systems and methods for providing custom controls configuration. In one embodiment, a system comprises a custom controls component configured to receive view information associated with a default view of controls, and receive customized configuration information indicative of a customization of at least one aspect of the controls. The default view of controls is based on data and default configuration information, and the data and the default configuration information are represented via a data-driven programming language. The custom control component is also configured to generate a customized view of the controls based, at least, on the default view of the controls and the customized configuration information. The configuration information comprises metadata, and the customized view of the controls includes a modified view, help text, or a description of a field associated with the controls.

Abstract: Changes are managed in a multi-user database application environment. Proposed changes are collected, including changes to data, schema, and/or application descriptions. A user may specify foreign key relationships between items belonging to one or more of these categories. A view is produced showing the impact proposed changes would have on the environment if successfully committed. The user's proposed changes are ordered according to their dependencies, and submitted for committal together in a single transaction, subject to optimistic concurrency and consistency checks. For example, a proposed change to a data value may be inconsistent with a change which removed a data element containing the data value. The commitment operation may return identifiers and other return values, in addition to indicating whether the commitment was successful.

Abstract: The subject disclosure relates to systems and methods for providing custom controls configuration. In one embodiment, a system comprises a custom controls component configured to receive view information associated with a default view of controls, and receive customized configuration information indicative of a customization of at least one aspect of the controls. The default view of controls is based on data and default configuration information, and the data and the default configuration information are represented via a data-driven programming language. The custom control component is also configured to generate a customized view of the controls based, at least, on the default view of the controls and the customized configuration information. The configuration information comprises metadata, and the customized view of the controls includes a modified view, help text, or a description of a field associated with the controls.

Abstract: Changes are managed in a multi-user database application environment. Proposed changes are collected, including changes to data, schema, and/or application descriptions. A user may specify foreign key relationships between items belonging to one or more of these categories. A view is produced showing the impact proposed changes would have on the environment if successfully committed. The user's proposed changes are ordered according to their dependencies, and submitted for committal together in a single transaction, subject to optimistic concurrency and consistency checks. For example, a proposed change to a data value may be inconsistent with a change which removed a data element containing the data value. The commitment operation may return identifiers and other return values, in addition to indicating whether the commitment was successful.