When you right click on the class and click on 'view inheritence', you will be able to see the inheritence of that class.
So during rule resolution, prpc resolves to find a rule by class first (where it preferes pattern inheritence at first, and later goes to directed inheritence)
So in the screenshot, it tries to find rule in PegaSampe-SupportRequest, if it doesn't find any related rule, it searches in PegaSample(pattern inheritence of the class), else it will try to find in Work-Cover- and so on.
Here Work-Cover- is the directed inheritence of the above class.It is mentioned in the class rule form as below.
Class inheritance is the method by which a child class can use all of the rules defined for a parent class. The Pega 7 Platform supports two types of class inheritance: directed inheritance and pattern inheritance.
Both types of class inheritance allow rules of ancestor classes to be inherited. However, class inheritance does not apply to external classes, even if the class name contains a dash character.
Directed inheritance is the method by which a class inherits characteristics directly from a specified parent class, regardless of any defined pattern inheritance.
For example, the PegaSample-CustomerRequest class (part of the PegaSample sample application) employs directed inheritance, and its directed parent class is Work-Cover-DupByCus. Based on pattern inheritance, the parent class is Work-Object-.
Pattern inheritance is an optional method by which a class inherits characteristics from other classes based on the parsing of class names and inheriting from classes it resembles in name.
The system determines the name of the parent class based on an initial portion or substring of the name of the class. You can set up pattern inheritance for a class in the Rule-Obj-Class rule, and pattern inheritance affects the first steps in the rule resolution algorithm.