...
Just as with lookups, we sometimes want the inquiry screen to work a bit differently than most vanilla inquiries. Any business object that is being seen on an Inquiry screen is wrapped in an implementation of org.kuali.ricekfs.kns.inquiry.Inquirable. There are two default implementations that can be extended: org.kuali.ricekfs.kns.inquiry.KualiInquirableImpl and its KFS extension, org.kuali.kfs.sys.businessobject.inquiry.KfsInquirableImpl. Most of the time, we'll discuss KualiInquirableImpl; KfsInquirableImpl adds interesting behavior to the functionality, but one with a smaller set of use cases.
...
Again, when overriding, one can write code to simply wait for specific attributes and otherwise defer to the inherited version of the method. There is also a helpful utility class, org.kuali.ricekfs.kns.util.UrlFactory that can be called like so:
...
getSections() takes in the business object that is the subject of the inquiry and returns a List of org.kuali.ricekfs.kns.web.ui.Section objects to be displayed about that object. Each Section object is, in turn, an amalgamation of org.kuali.ricekfs.kns.web.ui.Field objects which can be manipulated by the Inquirable. This is a lot of work and can often lead to situations where inquiry pages don't follow KFS standard practice. However, if there is a need for very fine grained control over how the inquiry page looks, this is the ultimate method to get that tweaking power.
...