Abstract: The present disclosure involves systems, software, and computer implemented methods for creating an extension field across system tenants in a customer landscape. One example method includes receiving a request to add an extension field to an entity used in a customer landscape. Entity-using system tenants that use the entity are determined. Event-pairing information is provided to each entity-using system tenant to enable receiving of extension field events. Field attribute values for a set of field attributes for the extension field are received. A field creation event is generated that instructs a system tenant receiving the field creation event to create a local field that has a target state of the extension field in that system tenant. The field creation event is sent to each entity-using system tenant.

Abstract: In an example embodiment, a technique is disclosed to describe generic capabilities in the ORD standard. In addition, this new ORD resource type may be explicitly supported by a Central ORD aggregator (or Central Management Plane), which can be used to discover and retrieve the information centrally. Having a central metadata service also eliminates the need for many point-to-point integrations.

Abstract: The present disclosure involves systems, software, and computer implemented methods for creating an extension field across system tenants in a customer landscape. One example method includes receiving a request to add an extension field to an entity used in a customer landscape. Entity-using system tenants that use the entity are determined. Event-pairing information is provided to each entity-using system tenant to enable receiving of extension field events. Field attribute values for a set of field attributes for the extension field are received. A field creation event is generated that instructs a system tenant receiving the field creation event to create a local field that has a target state of the extension field in that system tenant. The field creation event is sent to each entity-using system tenant.

Abstract: Disclosed herein are system, method, and computer program product embodiments for using design-time metadata to dynamically determine properties and actions for user-interface elements. By dynamically determining the properties and actions using the design-time metadata, a design-time tool may remain generic and need not include actual change handlers to process the actions and change the properties. By maintaining its agnosticism, a design-time tool may incorporate any changes to an overarching application framework without requiring code updates to the design-time tool itself.