Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:2000_concepts:0200_basics:0600_business_object_groups [2022/08/31 05:06] – [Business Object Groups] administrator | docs: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 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**// |
| 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 '' | Another way of going about it could be to create separate business objects for different communication types, like '' | ||
| - | With the solution that //**Aware IM**// offers you would create separate business objects for different communication types, like '' | + | With the solution that //**AwareIM**// offers you would create separate business objects for different communication types, like '' |
| 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; | 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; | ||
| Line 22: | Line 23: | ||
| - Business object groups can be used in queries to search the system for objects of different types based on the criteria that use common attributes of the group – see [[docs: | - Business object groups can be used in queries to search the system for objects of different types based on the criteria that use common attributes of the group – see [[docs: | ||
| - Business object groups can be referred to by reference attributes as shown in the above example – the '' | - Business object groups can be referred to by reference attributes as shown in the above example – the '' | ||
| - | - Business object groups can be used in business rules – again in this case rules may only use common attributes of the group. For example consider the following rules:< | + | - Business object groups can be used in business rules – again in this case rules may only use common attributes of the group. For example consider the following rules:< |
| - | | + | |
| - | Communication.State = ' | + | |