Abstract: Techniques are described for expressing a constraint in a host language. A constraint can be defined in the host language as an event handler. The event handler can be registered to a built-in event associated with an object of the database that the constraint is intended to validate. When the object triggers the built-in event, the event handler is called to execute the constraint. Exemplary built-in events include onSave (trigger the event when the object is saved), onValidate (trigger the event when an explicit call to validate the object is detected), onInsert (trigger the event when the object is inserted), onUpdate (trigger the event when the object is updated), and onCheckBeforeSave (trigger the event when the object is checked prior to saving).

Abstract: A database language is extended to define constraints on a data model (e.g., entity-relationship model) rather than the concrete database. The constraints can be declarative (e.g., constraints that are defined using expressions of the database language) or programmatic (e.g., constraints that are defined as a stored procedure implemented in a domain specific language). By storing the constraints at a higher level than the database level, the constraints can be performed without changing the persistency of the database. Also disclosed are techniques for handling of constraints on partially loaded entities.

Abstract: Techniques are described for expressing a constraint in a host language. A constraint can be defined in the host language as an event handler. The event handler can be registered to a built-in event associated with an object of the database that the constraint is intended to validate. When the object triggers the built-in event, the event handler is called to execute the constraint. Exemplary built-in events include onSave (trigger the event when the object is saved), onValidate (trigger the event when an explicit call to validate the object is detected), onInsert (trigger the event when the object is inserted), onUpdate (trigger the event when the object is updated), and onCheckBeforeSave (trigger the event when the object is checked prior to saving).

Abstract: A database language is extended to define constraints on a data model (e.g., entity-relationship model) rather than the concrete database. The constraints can be declarative (e.g., constraints that are defined using expressions of the database language) or programmatic (e.g., constraints that are defined as a stored procedure implemented in a domain specific language). By storing the constraints at a higher level than the database level, the constraints can be performed without changing the persistency of the database. Also disclosed are techniques for handling of constraints on partially loaded entities.

Abstract: The present disclosure involves systems, software, and computer implemented methods for operating on type instances. One example method includes identifying a reference to a type instance during execution of a child control flow. The child control flow is associated with one or more ancestor control flows. One or more stack frames associated with the ancestor control flows are searched for a prior instantiation of the type instance. Access to the prior instantiation of the type instance in an identified stack frame associated with an identified ancestor control flow is provided in response to determining that the prior instantiation of the type instance exists in the identified stack frame. A new instance of the type instance is instantiated in a stack frame associated with the child control flow in response to determining that the prior instantiation of the type instance does not exist in the one or more stack frames.

Abstract: The present disclosure involves systems, software, and computer implemented methods for operating on type instances. One example method includes identifying a reference to a type instance during execution of a child control flow. The child control flow is associated with one or more ancestor control flows. One or more stack frames associated with the ancestor control flows are searched for a prior instantiation of the type instance. Access to the prior instantiation of the type instance in an identified stack frame associated with an identified ancestor control flow is provided in response to determining that the prior instantiation of the type instance exists in the identified stack frame. A new instance of the type instance is instantiated in a stack frame associated with the child control flow in response to determining that the prior instantiation of the type instance does not exist in the one or more stack frames.

Abstract: According to some embodiments, an employee identifier may be received from an employee of an enterprise via an employee device. Based on the employee identifier, a subset of customers associated with the employee may be determined, and business data for each customer in the subset of customers may be received from a remote business server. For each customer in the subset of customers, a display of a virtual plant on the employee device may be automatically facilitated, wherein the display of each plant is automatically modified based at least in part on the business data received for that customer. According to some embodiments, an interactive employee input associated with a first virtual plant is received via the employee device and the display of the first virtual plant may be further modified based on the interactive employee input.

Abstract: Systems, methods and techniques relating to managing execution of applications in a runtime environment are described. A described technique includes identifying logic for executing an application code, identifying a first portion of the application code associated with the identified logic and executed by a first runtime container, identifying a second portion of the application code associated with the identified logic, determining, based on a policy or a characteristic associated with the application code, a second runtime container to execute the second portion of the application code, and dispatching a request and the identified logic to the second runtime container for executing the second portion of the application code.

Abstract: A software component and method for constructing computer applications running on different runtime environments, which consume services provided in multiple protocols. Usage of the component and method is preferably done by a content professional and does not require programming knowledge for supporting the runtime environments or the protocols.

Abstract: A software component and method for constructing computer applications running on different runtime environments, which consume services provided in multiple protocols. Usage of the component and method is preferably done by a content professional and does not require programming knowledge for supporting the runtime environments or the protocols.