Well a class join, defined in a report is really as a definition tied to that one report and therefore not reusable in other reports. Association rules on the other hand are seperate rules which can be reused throughout all reports in your pega environment. Take a look at some of the Association rules pega provides out of the box.
I understand that Association is a rule and is an instance of Rule-Obj-Association and it can be reused in other reports.
But, it also uses the class join feature to define a relationship between two classes based on matching values in pairs of properties.
My question is bit specific now.
When to use Class Join and and when Association in a report? Can you please give one example of Association rule used in Report Definition?
Why shall I create an Association Rule if a relationship between multiple classes can be achieved through Class Join feature in report definition only?Moreover, extra rule increases our task of maintainability.
If you can reuse such relationship in multiple RD - you should consider use of Association Rule. It will increase maintainability. Especially in situations when RD rule is delegated to business users that have no idea about classes, joins etc, but know about business terms like Association