Gap Analysis - Lookup

Data Dictionary configured ordered list of lookup (criteria) fields

Configure a Uif-LookupView

LCF1 LCF2 LCF3

Ability to arrange criteria into multiple columns by DD configuration.

Set the layoutManager.numberOfColumns property on the criteriaGroup of the Uif-LookupView

Automatic inclusion of criteria for the "active" attribute when the BO class implements the Inactivateable interface

Automatic child lookups on criteria based on DD/Persistence layer relationships

Ability to suppress child lookups on criteria via DD configuration. (E.g., used to suppress the lookup on the PK field of the business object currently being looked up. It would be nice if this condition were detected automatically to make configuration simpler.)

PK field on same BO does not show quickfinder automatically
 To suppress other fields just set p:quickfinder.render="false" on Uif-LookupCriteriaInputField

Ability to set default values via DD on lookup criteria.  (Both as string literal and via a ValueFinder class.)

Set the defaultValue param on the Uif-LookupCriteriaInputField of the Uif-LookupView

Quickfinder Disabled

(see Travel Account Number)

Automatic inclusion of a "blank" value in select-list lookup criteria if one did not exist after the ValuesFinder is used.

Automatic conversion of attributes with a checkbox definition into a set of 3 radio buttons.

Support for the special lookup operators ( |, <, >, .., etc...)

Lookup Operators

Specification of a lookup title. (Nice to have: auto generate this by creating name from the conversion of the business object name)

Use headerText property on Uif-LookupView. Does not do auto generation.

Specification of additional HTML to display in the header section (called "menubar" or "supplementalMenuBar") (Not used by KFS)

The page.header groups support Uif components.

Specification of additional buttons to display with the standard lookup buttons.  Can specify a strings for the remainder of the HTTP URL and the SRC attribute for the button's image.

The criteriaGroup.footer can be extended or replaced with Uif components.

Ability to clear all input values via button.

Ability to cancel the lookup and return to the calling page.  (Presently via the backLocation URL parameter.)

Via close button on light box.

Ability to hide the entire search criteria section by passing "searchCriteriaEnabled=true" on the URL.  (Not in use by KFS)

Uif: renderLookupCriteria property
URL: &renderLookupCriteria=false

Ability to configure on the BO DD file that the search buttons (Search/Clear Values/Cancel) be hidden. Presumably, this would be used by places which also force the search to run automatically.)

Uif: renderCriteriaActions

Ability to make the search fire off automatically. (Presently, this may require the URL to be altered upon the lookup to use the "search" methodToCall. It might be nice to be able to configure a default for this in the DD and then allow a more explicit override when starting the lookup.)

Can be configured by adding to url methodToCall=search (same as KNS). No DD property to set.

Validation of search criteria.  Present default implementation will only validate criteria specified in the list in the DD.  It will not validation other items in the map even though they may be used by the later lookup code.  (And may, in fact, be attributes of the business object for which there could be type validation.)  Only appears to validate them for required status and use of the search operators on non-supported data types.

In KNS and KRAD the required criteria is not inherited from the attribute definition

Ability to specify in the DD that a field should always be treated literally, even if search operators are present. If a user specifies a value in such a field, an information message is returned.

Uif: disableWildcardsAndOperators

Ability to define, on the source attribute in the DD which will generate a lookup (quickfinder), a set of lookup parameters. (A mapping between attribute names on the source object and the lookup object which will be pre-populated on the lookup.)

Adding a quickfinder to the LookupCriteriaField

Auto-generation of lookup (quickfinder) parameters (when not explicitly given) based on the key field relationships known to the system. (DD or persistence layer)

Ability to pass in default values when initially displaying the lookup by passing propertyName=value pairs on the URL.

LCF10

Ability to set any given field (via DD) to trigger a page submit and reload upon changing its value and tabbing out. (triggerOnChange)

Ability to program into the Lookupable a javascript string which would be run upon load of the lookup page. (Presently only used by the document search lookup.)

Add onLoadScript on the Uif-LookupView

Includes hidden form fields for read-only input criteria so it gets passed to the lookup properly. (As opposed to documents, where the field is maintained in the session so that an HTTP POST hack can not change the value.)

Hitting enter in any text field submits the lookup.

Needs to moved into the framework.
KULRICE-10902

Will display field icons (lookup/direct inquiry) even if the field is labeled as read-only. Seems strange. There is code which explicitly allows it when in "isLookup" mode.

Will display field on lookup criteria even if there is no attribute definition defined. (It then shows up as an unadorned text field with no label.) If we are going to allow this, then we should make some attempt to label the field, even with just the property name to help the developer troubleshoot.

Data dictionary configured ordered list of result fields

Configured through Uif-LookupView resultFields property

LRF1 LRF2

Automatic inquiry links on lookup results

KULRICE-10466

ResultsField - InputField - inquiry.render=true 
See ViewHelperServiceImpl:buildInquiryLink

Ability to suppress inquiry links in lookup results via DD configuration

Configure through UifLookupView::resultsFields - field.inquiry.render=false

Ability to configure lookup result limits globally by system parameter.

Based on RESULT_LIMIT system parameter. Ticket (KULRICE-9034) created to add new KR-KRAD namespace system parameter to prevent configuration issues between KNS from KRAD.

Ability to configure lookup result limits per client application by system parameter.

KULRICE-10453

Handled in KULRICE-5804.  Needs new namespace in KULRICE-9034.

Ability to configure lookup result limits by module by system parameter.

Retired.  Not used in KNS

Ability to configure lookup result limits by business object by system parameter.

Uses KRAD specific* RESULTS_LIMIT and MULTIPLE_VALUE_RESULTS_LIMIT parameters.
(* via KR-KRAD namespace)

Paging of lookup results.

Handled by default as LookupResultsCollection is based on Uif-PagedRichTable

Ability to configure page size for results globally by system parameter.

KULRICE-9086

Added KULRICE-9086 to deal with adding MULTIPLE_VALUE_RESULTS_PER_PAGE system parameter to KR-KRAD namespace

Ability to configure page size for results per client application by system parameter.

KULRICE-9086

Added KULRICE-9086 to deal with adding MULTIPLE_VALUE_RESULTS_PER_PAGE system parameter to KR-KRAD namespace

Ability to configure page size for results by module by system parameter.

Retired. Not used in KNS

Ability to configure page size for results by business object by system parameter.

Can be done in XML. Do implementers really need to change this?

System parameter-based maximum result column display length

KULRICE-9109

Can be controlled from the p:size parameter.  However, may want to find way to incorporate RESULTS_DEFAULT_MAX_COLUMN_LENGTH system property.

Automatic detection of whether the lookup is being used from within another function or from the portal/menu pages
(The KNS implementation is a complete hack.  We need a better (more explicit) way to control this.

renderMaintenanceLinks

Ability to customize the "actions" available on the left of the lookup results.
(This requires custom code now which has awareness of HTML and the KNS structure - should work out a better way which is more output-independent.)

 KULRICE-10663

Client application can override and merge a list of action components into Uif-LookupView-ResultActions.  JIRA to allow any component.

Vertically stacked actions

Actions with link group

Permission, workflow, and DD-based control of the appearance of the standard "edit", "copy", and "delete" links.

• If no workflow document exists, the edit/copy links will not be shown.
• If the DD <allowsNewOrCopy> is false, the Copy link will not be shown.  (Checked via the presentation controller class - which allows another customization hook for this check.)
• The KNS checks the BO Authorizer Service canCreate() method to see whether the user can create objects of the given class. (Checks the KR-NS / Create / Maintain Record(s) permission for against the current object.)
• The KNS checks the BO Authorizer Service canMaintain() method to see whether the user can edit the current record.  (Checks the KR-NS / Create / Maintain Record(s) permission for against the current object.)
• The KNS checks the BO Authorizer Service canMaintain() method to see whether the user can delete the current record.  (Checks the KR-NS / Create / Maintain Record(s) permission for against the current object.)
• Verifies in the DD whether this type of object can be deleted.  (NOTE: this check should be moved first, since it's usually false and *muuuuch* cheaper to perform than the KIM check done just above it.)

DD allowsNewOrCopy is handled by allowsMaintenanceNewOrCopyAction
Links in the Uif-LookupViewResultsActions include a ViewHelper.allowsMaintenance*Action to edit/copy/delete.

Configure a set of default sort fields in the DD. Multiple sort field could be specified, although the ascending/descending property could only be applied to the definition as a whole.

KNS:SortDefinition
KRAD:defaultSortAttributeNames

Automatic recognition of when the primary key fields were all filled out and display of a message to that effect.

KULRICE-10493

KNS: Lookup.jsp searchUsingOnlyPrimaryKeys
KULRICE-5391

Ability to define, on the source attribute in the DD which will generate a lookup, a set of field conversions. (A mapping between attribute names on the lookup object to the source object which will be populated on the source object when the user clicks the return value link on a row.)

KNS: FieldUtils.populateFieldsFromBusinessObject

Auto-generation of field conversions (when not explicitly given) based on the key field relationships known to the system. (DD or persistence layer)

KNS: FieldUtils.populateFieldsFromBusinessObject

Automatic translation of code fields which have, as a related class, a business object which extends KualiCode. In these cases, it adds the referenced business object's "name" property and includes that in the display of the column. (via the additionalDisplayPropertyName property)

KNS: FieldUtils.populateFieldsFromBusinessObject; KRAD: View.setTranslateCdoesOnReadOnlyDisplay

Storage of the search results in the session backed by a table.  (Table may only be used for multiple value lookups...)  Clicking on the search button again clears the prior session cache...of *all* lookups in the user's session, not just the current one.

for multi value, done differently

Jerry conversion: was disccusions related to the rewrite and how to store this data.  See: 

Display of the actual number of results when results are truncated.  (This is done by running the lookup with a COUNT(*) instead of the field list.)

Jerry: should the samples show  that there are actually 7 records in the database?  KNS doesn't seem to do that either.

Value is tracked through the resultSetCount and can be accessed, however there is no message to display (other than datatables sInfo)
KULRICE-5391

Ability to designate certain columns as to be totaled. These must be numeric columns and the result is formatted as currency. The totals are displayed at the bottom of the report. The totaling of the values is a feature provided by the DisplayTag library.

no formatting support for client option
Does serverside formatting work?

See Uif-ColumnCalculationInfo

Ability to sort results by clicking on header. Clicking a 2nd time reverses the sort. Sort is somewhat data type sensitive, but may (in KNS) depend on the detected datatype in the first row.

See Uif-PagedRichTable.templateOptions.sortableColumns

Ability to specify a Spring-configured bean to override the default lookup behavior.
(This should be simplified - does anyone remember why we have a Lookupable *and* and LookupableHelperService?)

Uif-LookupView can be overridden to customize default behavior.  Via the viewHelperServiceClass the LookupableImpl can be customized as well.

Permission check (Look Up Records) on the use of the lookup as a whole.

The LookupView AuthorizerBase class has a method "canOpenView" which looks at the user and their permissions and determines whether they can use lookup as a whole.

Checks if the user has the Initiate permission on the maintenance document (via the document authorizer class) related to the business object on the lookup and suppresses the entire action column if so.

KULRICE-8571 /  KULRICE-10524 hide action column if not actions are available to user

Permission, workflow, and DD-based control of the appearance of the create new link in the upper left.

LookupableImpl method buildMaintenanceActionLink is the method that generates the action link of the "New" button, maintenanceMethodToCall argument with value of "start" is used to generate the new link by default, the method could be overridden.

In KRAD, workflow check is done by the allowsMaintenanceNewOrCopyAction, which checks to see if the data object has an associated maintenance document defined for it

Ability to override the behavior and contents of the create new link in the Lookupable.

Lookupable has "allowsMaintenanceNewOrCopyAction", not sure if this is actually being used, but overriding the method seems like it would work, also the buildMaintenanceActionLink is public and could be overridden to modify behavior

Ability to open multiple inquiries from the lookup into separate windows.
(Really more of a browser feature, but something that power-users would be quite upset if they could not do.  Use case: load up a number of accounts in a lookup, then open the inquiries in separate windows and/or tabs for comparison.)

KULRICE-10915

UXI Prioritized

By default inquiries are opened in lightboxes.  User can open the inquiry in a new tap/windows via the right click context menu (or "Ctrl"-click)

Ability to export lookup results to CSV, Excel, or XML format.

Ability to customize the XML export format.  (As done by KEW for document types.)

Automatic display of help link (sourced from the DD) for the document or business object being queried.

KULRICE-9252

KFS (in 3 places) sub-classes the KualiLookupAction class to completely customize the lookup function, criteria, and results sections.

One of these subclasses seems to be for KFS multivalue lookup customization, this might go away as part of the upgrade to KRAD. Should be able to override LookupableImpl, LookupController, etc to customize

KFS (in more than 3 places) sub-classes the LookupForm class as part of the above.

are there specific samples.

The formClass property on Uif-LookupView could be set to point at a customized LookupForm that extends the original

Lookups first post back to the original page to save their values before redirecting on to the lookup action/controller.  This was necessary since we could not employ JavaScript originally.  Lots of the code in KualiAction.performLookup() relates to parsing out these "special" values.  If lookups always happen in a lightbox now, much of that complexity could go away.

KULRICE-9107 This functionality was determined to be unnecessary for KRAD implementation of multivalue lookups.

Ability for the document to specify that, upon returning to the originating document, which reference objects should be refreshed as a result.  (I.e., so that the name of the object is displayed in a related field.)  This list of references is usually auto-generated by the relationship metadata.

need to verify jpa

KULRICE-5286

Business Object Class

No - but sets it on the helper service as well.

set/getBusinessObjectClass have been renamed to set/getDataObjectClass.  Since now all data objects are supported the requirement that the object is a BussinessObject has been removed.  The rename of these methods reflect this change. The data object is usually specified via the dataObjectClassName property of the extended Uif-LookupView bean.

Result set columns

Yes

getColumns has been removed.  The result columns are now specified via the Uif-LookupView (see resultFields property).

KFS

KC

Lookup with Conditional Results

Lookup with Conditional Results Based on Criteria

Conversion script should check for usage of this method and write out a message

Search Parameter Validation

Yes

validateSearchParameters takes the LookupForm as an additional parameter and returns a boolean value indicating that no validation error message has occurred (true = no error).  Warning and informational messages do not affect this return indicator.  A ValidationException is no longer thrown.

Returning Search Results

Yes

getSearchResults takes the LookupForm and indicator for bounded/unbounded search as additional parameters.  getSearchResultsUnbounded has been removed.

Clearing search criteria

Yes

Yes, but...

performClear takes the searchCriteria map as an additional parameter since it is no longer stored in the Lookupable.  The searchCriteria map is returned after clearing the criteria and setting their default values.
Special handling for secure field and default value formatting has not been implemented. Is this needed?

Getting return URL (E.g., when used from quickfinder)

Yes

getReturnUrl has been renamed to buildReturnUrlForResult which accepts the LinkField that returns the result from the lookup and the model.

Create New HTML

(Renders image and URL. Asks the LookupableHelperService if it should display the link.)

Partially

currently renders as link

can be customized by overriding the appropriate header group

Lookup Menu Bar

(Pulled from DD for the business object)

No

 KULRICE-5388

configured via Uif

Supplemental Menu Bar

Yes

configured via Uif

Input Criteria Row Objects

Yes

see getRows in conversion guide

Lookup Display Title

Yes

getTitle has been removed.  The title is now specified via the Uif-LookupView (see headerText property).

Return Location

(Usually passed in)

Yes

getReturnLocation() has been removed. The return location is now stored on the form. Use LookupForm.getReturnLocation().

Return keys

(List of property names from the looked up object which will be returned to the calling page.)

Yes (pulls from PK list for BO)

getReturnKeys() takes the LookupView, LookupForm and the data object as an additional parameter.

Source image for a single extra button

(Pulled from DD)

No

getExtraButtonSource() has been removed.  Buttons are configured via Uif-LookupCriteriaGroup (see footer property). 

Additional URL parameters passed for the extra button

(Pulled from DD)

No

getExtraButtonParams() has been removed.  Buttons are configured via Uif-LookupCriteriaGroup (see footer property).

Default sort columns

Yes

getDefaultSortColumns() has been removed.  Sort columns are configured via Uif-LookupView (see defaultSortAttributeNames property).

"check for additional fields"

(Allows the lookupable to determine if there are fields in the HTTP request parameters which should be set on the input criteria. (Once this returns true, they are mapped by the property name.))

Yes

KULRICE-9082

&lookupCriteria[code]=us

docFormKey

(Used to separate multiple lookups within the user's session)

Yes

set/getDocFormKey() has been removed.  The document form key is stored on the form.  Use LookupForm.getFormKey().

field conversions

Yes

setFieldConversions() has been removed. The field conversion is specified via Uif (see quickfinder.fieldConversions property).

Read-only fields list

Yes

setReadOnlyFieldsList() has been removed.  Read only criteria fields are specified via Uif (see readOnly property).

Support for a "customLookupAction" when returning from a child quickfinder

Yes

KULRICE-9072

see performCustomAction() in conversion guide

Handling fields which need to be encrypted when transmitted

Yes

KULRICE-9076

No special conversion needed.  Data dictionary configuration is the same.
Data is encrypted for passing from Lookup back via URL and field is properly masked with the exception of the issue in the jira.

Performs conditional logic (based on current search values or other parameters) to override field hidden, read-only, and required attributes previously set.

(Everything with a "Yes" above)

see above

allowsMaintenanceNewOrCopyAction

default checks BO Authorization service.canCreate()

moved to LookupableImpl

allowsMaintenanceEditAction

default checks BO Authorization service.canMaintain()

moved to LookupableImpl

allowsMaintenanceDeleteAction

default checks BO Authorization service.canMaintain() and if the DD allows deletion of this type

moved to LookupableImpl

maintenance URL

BADLY NAMED: the URL is not returned by this method - it only sets the anchor title for accessibility

The anchor title is set as part of the LookupableImpl.buildMaintenanceActionLink

Action URLs

Returns HTML which forms the links in the Actions column of a lookup.

The URL is created in LookupableImpl.buildMaintenanceActionLink

Obtaining the max length for a column

Checks DD then the system parameter table if not set

Retrieval of search results

There are a number of methods and it's not obvious which one you should override. (E.g., getSearchResults() or getSearchResultsHelper())

Moved to LookupableImpl. Method signature changed, includes search criteria and unbounded indicator

Delegation of external business object lookups to their module service.

(see LookupableImpl.getSearchResults)

In-memory joining to external business objects by running the query against the EBO first and then using the results to filter the "normal" lookup.

(see LookupableImpl.getSearchResults)

Pass-through of the collection property name so that, upon return, the values can be added/processed properly.

Passed as a parameter back to the LookupController, the parameter value is lookupCollectionName, the xml property in the DD used to define this is collectionObjectClass

Tracking of selected items by the objectId property values.

Selected items are tracked successfully (for the most part) not sure if this is using objectId or another property value.

Maintenance of selected items in a KRNS database table (and retaining selected values when page changes.)

KULRICE-10302

KULRICE-10302

No longer necessary to maintain a KRNS table for results. However selected values are not currently saved when the lightbox changes to a different page in the result set, or if a lightbox is not used for the lookup, when a different page of the result set is displayed.

Additional control buttons to allow selection of all items on a "page" or all items in the resultset.

KULRICE-10534 KULRICE-10535

UXI Prioritized

Buttons include: "Select all from all pages" "deselect all from all pages" select all from this page" "deselect all from this page"

Currently being reworked.

In KRAD these buttons are found as part of a drop-down menu on a multivalue lookup.

The multivalue lookup action buttons in the KNS were provided by the displayMultipleValueLookupResults.tag file and were automatically included on any multivalue lookup. In KRAD this functionality has been moved into the component Uif-SelectCollectionItemField which is included by default on multivalue lookups.

Separate "per-page" size for multiple value lookups defined by system parameter. Not configurable by business object.

 KULRICE-9086

LookupView seems to have necessary additional parameter (multipleValuesSelectResultSetLimit), but it doesn't appear that this parameter is initialized by the system, or that there is a corresponding system parameter to store configurable values

Authorization checks on lookup results and individual records.

AttributeDefinition security masking

Passes a custom "refreshCaller" to the source page to tell it to pull the selected objects.

refreshCaller and refreshCallerType are passed back to the LookupController from the form, refreshCallerType is MULTI_VALUE_LOOKUP for the usage of this functionality

Support for multiple value lookups for EBOs.

KULRICE-10350

see LookupableImpl.getSearchResults. If the dataObjectClass is an EBO then the responsible module service is called to get the results.

<property name="collectionLookup">
<bean parent="Uif-CollectionQuickFinder"
p:dataObjectClassName="org.kuali.rice.location.framework.campus.CampusEbo"
p:fieldConversions="name:field1,shortName:field2,code:field3"/>
</property>
<property name="items">
<list>
<bean parent="Uif-InputField" p:label="Field 1" p:propertyName="field1"/>
<bean parent="Uif-InputField" p:label="Field 2" p:propertyName="field2"/>
<bean parent="Uif-InputField" p:label="Field 3" p:propertyName="field3"/>
<bean parent="Uif-InputField" p:label="Field 4" p:propertyName="field4"/>
</list>
</property>

org.kuali.rice.kns.datadictionary.LookupDefinition

org.kuali.rice.krad.datadictionary.SortDefinition

org.kuali.rice.krad.datadictionary.HelpDefinition

Contained a parameter PK which would contain the help URL.

org.kuali.rice.kns.datadictionary.FieldDefinition

rowDisplay.tag

Handles the display of the criteria section of Lookups (and KNS Inquiries and maintenance documents)

KualiLookup.jsp

org.kuali.rice.kns.util.FieldUtils

Class which was necessary once upon a time for compensating for limitations in the allowed technologies which we no longer have.

org.kuali.rice.kns.lookup.KualiLookupableImpl

org.kuali.rice.kns.lookup.AbstractLookupableHelperServiceImpl

org.kuali.rice.kns.lookup.KualiLookupableHelperServiceImpl

org.kuali.rice.kns.lookup.LookupUtils

(Most likely, this class should be removed and the functions moved into the abstract lookup helper class.  There is already duplication between those classes.)  Some is only used from the LookupForm - and so could be moved into the Model class under SpringMVC

org.kuali.rice.krad.service.impl.LookupServiceImpl

org.kuali.rice.kns.lookup.LookupResultsService

Can be removed.  This interface is no longer implemented anywhere.

org.kuali.rice.kns.web.struts.form.LookupForm

org.kuali.rice.kns.web.struts.action.KualiLookupAction

org.kuali.rice.kns.web.ui.Column

org.kuali.rice.kns.web.ui.Row

org.kuali.rice.kns.web.ui.Field

org.kuali.rice.krad.lookup.CollectionIncomplete

org.kuali.rice.kns.lookup.LookupableHelperService

org.kuali.rice.kns.lookup.MultipleValueLookupMetadata

org.kuali.kfs.gl.web.struts.BalanceInquiryLookupAction

org.kuali.kfs.gl.web.struts.BalanceInquiryLookupForm

org.kuali.kfs.sys.service.impl.SegmentedLookupResultsServiceImpl

(Used to handle large multiple value lookups - saves Base64 encoded version of entire result set to KRNS_LOOKUP_RSLT_T.) LookupResultsService is only used by multiple value lookup in Rice. In any other situation, this class will not be used. We probably want to fold this into the Lookupable if that makes sense.

org.kuali.rice.kns.lookup.LookupResultsService

This service is the one responsible for persisting and retrieving search results performed on a separate request.

org.kuali.rice.kns.maintenance.KualiMaintainableImpl

Contains a addMultipleValueLookupResults method which is used to push the values into the BO on the document and can be customized.

LookupableHelperService

Excluding a specific value to make sure it was never returned in the result list.

LookupableHelperService

Customization of the search criteria before handing off to the baseline getSearchResults() method.

LookupableHelperService

Altering the label on the Edit link in the actions column.

LookupableHelperService

Filtering results which could not be filtered by the LookupService.

LookupableHelperService

Adding messages/errors to the top of the criteria section.  (via KNSGlobalVariables.getMessageList())

LookupableHelperService

Override of the inquiry link on result fields.

LookupableHelperService

Doing just about anything imaginable to the "Actions" column contents.  (It would be good to have a more declarative way to create these links.)

LookupableHelperService

Merging two lookups into a single list.

LookupableHelperService

Custom validation of search parameters.

LookupableHelperService

Control the check the newOrCopy action.

Action (not lookup action)

performLookup() - override the path for the action forward to customize and send to a different Controller based on the BO Class.

LookupAction

Provide infrastructure for complete rewrite of query logic and display.  (KFS Balance Inquiries - really Lookups)  This is the "segmented" feature.

LookupForm

Addition of attributes which need to be persisted in the session for special lookups.  This works with the item below.  If we can have the Lookupable class stored in the session instead, then we can remove all customization of KualiLookupAction and LookupForm.

LookupForm

Manipulation of the field values which will be passed to the lookup based on the HTTP request parameters.  (Generally, it looks like this should *not* have been done, as they duplicated a large chunk of the code from the base class' populate() method.  Most likely, all the logic in the forms can be moved into the lookupable.

Ability to specify separate control definitions for different purposes of fields. Presently, we have a problem in cases that we want to use a select control definition in most cases. But, we can't use that on the document (since we are setting up the values there.) And, we may want to not use it on lookups, as that prevents us from using the special lookup syntax.

Validation during DD parsing that the field definitions given have associated attribute metadata. In KNS 2.1.2, you can reference attributes on the BO which do not have AttributeDefinition data, causing the field to have no label and defaulting to a 10-wide text control. Either we should make this more intelligent or throw an error during startup.

If the user will not have the necessary permission to perform a lookup from a document or other lookup, then we should not display the quickfinder.

DON'T make the display of the maintenance links dependent on the back location containing portal.do.  This makes it harder to get standard behavior when linking from outside of the main application.

Open up LOOKUP_READONLY fields to data entry. (Parent document type on document type lookup.) You should not have to search for a value to use on a lookup if you already know the value.

In the redesign, there is probably no reason that we can not fold multi-value lookup into the main lookup form. It duplicates a lot of the base features anyway. If we design with this in mind (rather than tacking it on afterwards as was done originally.)

(KC) Ability to specify whether lookup criteria should be handled in a case-sensitive or insensitive manner.