The present page serves as an overview for the topic. All available documents for the topic can be found here.
Generally, the logical representation of an entity of the real world. From a developer's perspective, a business object (a.k.a. "domain object") represents a logic entity in a given domain, including attributes, relationships, business rules/logic, policies and constraints.
The business object layer provides an explicit business-oriented domain model as an API. In a picture that shows the typical architecture layers of a business application, it can be located on top of the persistence layer (or data layer), and below the application layer that forms the actual application from a reusable domain layer - the business object layer.
It forms a new level of abstraction over the persistent state of objects. It comes with concepts to change and extend the behavior of business objects without breaking the cartridge API barrier. It hides the underlying internal implementation, which can still be based on the existing ORM model, or on any other back end. It also provides a more object-oriented view on the available business functionality, which, for example, makes user interface development much easier.
|Title||Product Version||Product To Version|
|Concept - Business Objects (valid to 7.10)|
|Concept - Object Validation|
|Cookbook - Business Objects (valid to 7.10)|
|Cookbook - Object Validation|
|Guide - Business Objects|
|Reference - Type Codes|
|Support Article - Access Privileges and Permissions||7.6|
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.