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
2000_concepts:0200_basics:0600_business_object_groups [2026/08/13 00:50] – ↷ Page moved from docs:2000_concepts:0200_basics:0600_business_object_groups to 2000_concepts:0200_basics:0600_business_object_groups localdev2000_concepts:0200_basics:0600_business_object_groups [2026/08/13 00:55] (current) – ↷ Links adapted because of a move operation localdev
Line 17: Line 17:
 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.
  
-Business object groups are treated in the same way as regular business objects - they can be used in business rules, queries, document templates, and they also appear in the list of available attribute types. So, we would simply add a [[docs:2000_concepts:0200_basics:0400_reference_attributes|multiple reference attribute]] ''ContactHistory'' of type ''Communication'' to ''Client'' to display a list of communication records on the client form. When the user clicks on an item in the list, a form for the specific record will be automatically shown to the user. +Business object groups are treated in the same way as regular business objects - they can be used in business rules, queries, document templates, and they also appear in the list of available attribute types. So, we would simply add a [[2000_concepts:0200_basics:0400_reference_attributes|multiple reference attribute]] ''ContactHistory'' of type ''Communication'' to ''Client'' to display a list of communication records on the client form. When the user clicks on an item in the list, a form for the specific record will be automatically shown to the user. 
  
 Business object groups are useful in the following scenarios: Business object groups are useful in the following scenarios:
  
-  - 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:2000_concepts:0600_data_retrieval|Data Retrieval]]. +  - 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 [[2000_concepts:0600_data_retrieval|Data Retrieval]]. 
   - Business object groups can be referred to by reference attributes as shown in the above example – the ''ContactHistory'' attribute on the ''Client'' object refers to a group rather than to a particular object.   - Business object groups can be referred to by reference attributes as shown in the above example – the ''ContactHistory'' attribute on the ''Client'' object refers to a group rather than to a particular object.
   - 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:<code aim>FIND Communication WHERE Communication.SentDate = CURRENT_DATE   - 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:<code aim>FIND Communication WHERE Communication.SentDate = CURRENT_DATE
Line 29: Line 29:
 Here the second rule would set the value of the state attribute of any communication object found by a query irrespective of its type. Here the second rule would set the value of the state attribute of any communication object found by a query irrespective of its type.
  
-<callout type="tip" icon="true" title="tip">If business rules attached to different members of a group are exactly the same it is better to use group names in the rules rather than names of a particular group member. In this case changes made to a rule attached to one member will be automatically transferred to the equivalent rules attached to other members – see also [[docs:2500_config_apps:0800_add_edit_rules|Adding/Editing Rules]].</callout>+<callout type="tip" icon="true" title="tip">If business rules attached to different members of a group are exactly the same it is better to use group names in the rules rather than names of a particular group member. In this case changes made to a rule attached to one member will be automatically transferred to the equivalent rules attached to other members – see also [[2500_config_apps:0800_add_edit_rules|Adding/Editing Rules]].</callout>
  
-Configuration of business object groups is explained in the [[docs:2500_config_apps:1000_add_edit_bogs|Adding/Editing Business Object Groups]] section.+Configuration of business object groups is explained in the [[2500_config_apps:1000_add_edit_bogs|Adding/Editing Business Object Groups]] section.