SCALABLE AND DISTRIBUTED BUSINESS OBJECT CONFIGURATION PROPERTIES
According to some embodiments, a method and an apparatus of defining a business object comprises receiving a business object type and a business object sub-type associated with the business object type. A business object based on the business object type and the business object sub-type is defined and the business object is saved.
1 . A method of defining a business object comprising:
receiving a business object type;
receiving a business object sub-type associated with the business object type;
defining, via a processor, a business object based on the business object type and the business object sub-type; and
saving the business object.
2 . The method of claim 1 , further comprising:
receiving a sub-sub type associated with the sub-type; and
defining, via the processor, the business object based on the business object type, the business object sub-type and the sub-sub type.
3 . The method of claim 2 , wherein prior to determining the business object, determining if more business object sub-types are received.
4 . The method of claim 1 , wherein saving comprises serializing the business object into name-value pairs that comprises the business object type and the business object sub-type.
5 . The method of claim 4 , further comprising:
editing the business object by de-serializing the saved business object; and
re-saving the edited business object by serializing the edited business object into name-value pairs.
6 . The method of claim 1 , further comprising:
rending the business object in a user interface where the rendered user interface comprises first attributes associated with the received business object type and second attributes associated with the received business object sub-type.
7 . The method of claim 1 , wherein a business object comprises a software object comprising attributes and functions that is modeled to describe an object.
8 . A non-transitory computer-readable medium comprising instructions that when executed by a processor perform a method of defining a business object, the method comprising:
receiving a business object type;
receiving a business object sub-type associated with the business object type;
defining, via a processor, a business object based on the business object type and the business object sub-type; and
saving the business object.
9 . The medium of claim 8 , further comprising:
receiving a sub-sub type associated with the sub-type; and
defining, via the processor, the business object based on the business object type, the business object sub-type and the sub-sub type.
10 . The medium of claim 9 , wherein prior to determining the business object, determining if more business object sub-types are received.
11 . The medium of claim 8 , wherein saving comprises serializing the business object into name-value pairs that when saved, comprise the business object type and the business object sub-type.
12 . The medium of claim 11 , further comprising:
editing the business object by de-serializing the saved business object properties; and
re-saving the edited business object by serializing the edited business object properties into name-value pairs.
13 . The medium of claim 8 , further comprising:
rending the business object in a user interface where the rendered user interface comprises first attributes associated with the received business object type and second attributes associated with the received business object sub-type.
14 . An apparatus comprising:
a processor; and
a non-transitory computer-readable medium comprising instructions that when executed by a processor perform a method of defining a business object, the method comprising:
receiving a business object type;
receiving a business object sub-type associated with the business object type;
defining, via the processor, a business object based on the business object type and the business object sub-type; and
saving the business object.
15 . The apparatus of claim 14 , wherein the method further comprises:
receiving a sub-sub type associated with the sub-type; and
defining, via the processor, the business object based on the business object type, the business object sub-type and the sub-sub type.
16 . The apparatus of claim 15 , wherein prior to determining the business object, determining if more business object sub-types are received.
17 . The apparatus of claim 14 , wherein saving comprises serializing the business object properties into name-value pairs that when saved, comprise the business object type and the business object sub-type.
18 . The apparatus of claim 17 , wherein the method further comprises:
editing the business object by de-serializing the saved business object properties; and
re-saving the edited business object by serializing the edited business object properties into name-value pairs.
19 . The apparatus of claim 14 , further comprising:
rending the business object in a user interface where the rendered user interface comprises first attributes associated with the received business object type and second attributes associated with the received business object sub-type.
20 . The apparatus of claim 14 , wherein a business object comprises a software object comprising attributes and functions that is modeled to describe an object.