Association node has the following properties:

General Properties:

Name:

Specifies the name which will identify the Association Node. The value of this property will be concatenated as a sufix in the object's name.  

Associated Records Expression:

Specifies the information that will be shown for each record of the transaction to associate. This property can be the value of an attribute (like this example), the concatenation of some attributes or the result of invoking some procedure. 

Associated Records Condition:

Specifies the condition to be added to the For Each used to load the reocord lists. 

Order List:

Specifies the mechanism that will be used for ordering the records that are displayed on each list (list of associated records and list of not associated attributes). The options for this property are 'User order clause', 'Order programmatically', 'False'. If this property is 'User order clause' the lists will be ordered by Associated Records Expression, so Associated Records Expression property must be an attribute. If this property is 'Order programmatically' the lists will be ordered by code (use this option if the AssociatedRecordsExpression is a composed expression and an order clause cannot be used). Finally, if this property is 'False' the list of associated and not associated records will not be ordered.

Properties Of Category Generation options:

Update Object:

Specifies the way in which the Association object will be updated after re applying the pattern. The alternatives are:

• Do not update:
  It won't update any of the association's elements (webForm, Events, Rules) when re applying the pattern. It is like the Association object was no more linked to the pattern, unlike the other objects of the instance.
   
• Create default:
  Each time we apply the pattern, the form will be created and the Rules and Events updated according to the pattern instance. The user code and the content inside user tables will remain intact after re applying it.
   
• Only events and rules:
  Each time we apply the pattern, the Rules and Events will be updated according to the pattern instance, but the Association form will not be created from the instance, it will remain as it was before.
   
• Overwrite:
  Each time we apply the pattern, the Rules, Events and the form will be overwritten. All the content inside user table and the user code will be cleaned.
   

Web User Experience:

Specifies the the web user experience of the Association object. The options for this property are 'Use model property', 'Smooth' or 'Previous versions compatible'. When the property has the value 'Use model property', it will take its real value from the property 'Web User Experience' of the actual version of the KB:

Base Web Form:

Specifies whether the base of the Web Form will be HTML or an Abstract Layout. Then, depending on the type of the tables inside the form, the Form may contain some HTML controls or Layout controls. The options of this property are: 'Use model property', 'Abstract layout' or 'HTML'. The value 'Use model property' will take its real value from the property 'Default Web Form Editor' of the actual version of the KB (Image above).

Example: Base Web Form 'Abstract Layout' with some HTML controls inside

Example: Base Web Form 'HTML' with some Layout controls inside

If you want to read more information about Association feature, follow this link: Association