Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
docs:2000_concepts:0200_basics:0600_business_object_groups [2022/09/13 18:15] – external edit 127.0.0.1docs:2000_concepts:0200_basics:0600_business_object_groups [2025/06/12 02:09] (current) – Rename to AwareIM aware_support3
Line 1: Line 1:
 +{{tag>business_object_group business_object concepts}}
 [<10>] [<10>]
 ====== Business Object Groups ====== ====== Business Object Groups ======
  
-//Business object groups// in **//Aware IM//** offer you a simple and convenient way to handle similar yet different data. +//Business object groups// in //**AwareIM**// offer you a simple and convenient way to handle similar yet different data. 
  
 Let us consider an application that registers client communication history, such as meetings, phone calls, letters, e-mails, etc. A summary of the history should be presented as a chronological list on the client form. The user should be able to see full details of any list item on a separate form. Let us consider an application that registers client communication history, such as meetings, phone calls, letters, e-mails, etc. A summary of the history should be presented as a chronological list on the client form. The user should be able to see full details of any list item on a separate form.
Line 12: Line 13:
 Another way of going about it could be to create separate business objects for different communication types, like ''Outgoing Emails'', ''Incoming Emails'', ''Outgoing Letters'', etc. Each of these objects would have its own data form. The trouble with separate objects is that it would be very difficult (if not impossible) to show records from separate objects in a single chronologically sorted list, say on a client form, or do a search across multiple objects. Another way of going about it could be to create separate business objects for different communication types, like ''Outgoing Emails'', ''Incoming Emails'', ''Outgoing Letters'', etc. Each of these objects would have its own data form. The trouble with separate objects is that it would be very difficult (if not impossible) to show records from separate objects in a single chronologically sorted list, say on a client form, or do a search across multiple objects.
  
-With the solution that //**Aware IM**// offers you would create separate business objects for different communication types, like ''OutgoingEmail'', ''IncomingEmail'', ''OutgoingLetter'', then create a business object group, say, called ''Communication'', and include all the specific objects as its members. This is all it takes.+With the solution that //**AwareIM**// offers you would create separate business objects for different communication types, like ''OutgoingEmail'', ''IncomingEmail'', ''OutgoingLetter'', then create a business object group, say, called ''Communication'', and include all the specific objects as its members. This is all it takes.
  
 Each member of a group usually contains attributes common to all other members. In the example above the common attributes would be the date when the communication was sent or received and the state of the communication. Each member would also have some specific attributes not found in other group members, for example, telephone number for telephone communication; e-mail address for e-mail communication etc. Each member of a group usually contains attributes common to all other members. In the example above the common attributes would be the date when the communication was sent or received and the state of the communication. Each member would also have some specific attributes not found in other group members, for example, telephone number for telephone communication; e-mail address for e-mail communication etc.
  • Last modified: 2022/09/13 18:15