Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



KNS Feature

Implemented in KRAD



Ability to copy another business object by clicking a link from the lookup. Copies all the attributes except for the primary key, ver number, and object ID fields by default.
(Why can't we do this from a link on the inquiry page?) 


Different implementation will be needed, since object ID and version number are no longer required.

M2Upon copy, blanks out any fields determined to be "restricted" based on input from the document authorizer.No 
M3Ability to delete a business object. (Though usually no link is displayed to perform this operation.)No 
M4Ability to edit an existing business object.Yes 
M5Ability to pass in properties on the HTTP request to pre-populate fields on the document. If overrideKeys=field1,field2 not specified, then only parameters with the names of the primary key fields will be used.  
M6Calls into the Maintainable to populate any blank fields which have defaults after a New or Copy document is created.  
M7Automatically displays the left "Old" side when editing or copying a business object.  
M8In any document where the Old/New sections are both displayed, highlight (yellow asterisk in the KNS) fields which have been changed from their "old" values.  
M9Ability to block the creation of new objects of a given type at the data dictionary level. (allowsNewOrCopy)Yes 
M10Knowledge of the fields and collections present in sections (tabs) so that error messages will be displayed under the correct heading.Yes 
M11Auto-opening of tabs which have errors when redisplaying the document after a form submit which performs validation.Yes 

Security mechanism which required the registration of all properties displayed on the form. The standard form control tags pushed their field names into a session scope variable. Upon form re-posting, only attributes registered in this way would be posted back to the business object. This was done due to the way that Struts (and now Spring) auto-bind values based on dot-notation. Without this, it is possible to create custom form widgets in the browser and change internal properties of business objects which should have been non-editable by the end user.

(A call like: ${kfunc:registerEditableProperty(KualiForm, field.propertyName)} is used to perform this function from rowDisplay.tag)

The KualiMaintenanceForm also registers a number of properties which are not editable, but which will be present on the form. These are used to prevent the security system from blowing the page for these standard fields. That map is also used to prevent the values on the form from being updated in the objects upon posting of the form.

M13Rendering of the "* = required field" heading when the document was in an editable format. (Probably not needed due to dynamic feedback in KRAD.)No 

Display of maintenance document sections in collapsable tabs.

M15Ability to expand/collapse tabs one at a time or all at once.No 
M16Memory of the state of the tabs on a given document across page refreshes.No 
M17Ability to specify the default open/closed state of the document-specific tabs.Yes 
M18Ability to include additional non-standard sections via a DD-specified file. The file would be included via the <jsp:include> tag.  
M19Ability to configure help links in the section headers via the DD.  
M20Ability to hide sections conditionally via the presentation controller.  
M21Ability to make entire sections conditionally read-only via the presentation controller.  
M22Ability to include additional JS files in the page via DD configuration.  
M23(warning) documentOverview.tag/rowDisplay.tag : Detection of whether the screen is a maintenance document by checking if the Struts Form class == KualiMaintenanceForm.  
M24Ability to set the title of the tab sections via the DD.  
M25Ability to set an ID for sections for use by the presentation controller and document authorizer when setting sections as hidden or read only. If no ID is specified, the ID defaults to the tab's title. (This is not the HTML id used in the generated code.)  

Support for custom buttons on maintenance documents which only display on the "New" side and not when in read-only mode. They call back into the "refresh" method but with a custom action in one of the special URL-encoded fields. The custom action is manually inserted into the request parameter map passed to the Maintainable's processAfterPost() method.

M27Use of the control definitions in the business object DD files to render the fields.  
M28Recognizes properties which are sensitive when passed in for the "newWithExisting" action and assumes they are encrypted, decrypting them before passing them into the new business object. (Please don't support - we should never be passing sensitive information on URLs. If there is a need to do this, have it place the sensitive data in Session scope and have the passed value be some sort of GUID to retrieve it.) (There is also use of a special prefix in places to indicate that a value is encrypted: EncryptionService.ENCRYPTION_POST_PREFIX)  
M29Support for retrieving attachments which have been linked to properties on the business object itself. (I presume they have been linked to BLOB fields.)
There also seems to be support for attachment objects linked to collections within the BO. (See PersistableAttachment and PersistableAttachmentList)
M30Altering of behavior of the main Action when the generic docHandler method is used depending on the "command" passed (displayActionListView, displayDocSearchView, displaySuperUserView, displayHelpDeskActionListView, initiate)  
M31Special handling to support multiple value lookups and mapping of the properties from the business object being looked up into the child records actually referenced by the "global" document. This is handled via the fairly overloaded "refresh" method. MV lookups only return the OBJ_ID values, so the records need to be retrieved before the properties can be mapped. (question) How will this work in KRAD if the object being looked up does not implement the "GloballyUnique" interface?  
M32Support for collections within business objects, with base methods for handling the addition and deletion of lines from the collection.  

Special handling of the Struts populate command on the form to strip off the new/oldMaintainable prefix and push the resulting properties directly into the business objects. (Since the base function would to have been document.newMaintainableObject.boProperty.) This population is deferred to the maintainable's populateBusinessObject() method rather than using the Struts functions.

Now, the existing code applies the values to the "oldMaintainableObject" as well. This probably should not have been happening, as the old object should never be changed by UI code.

M34All incoming properties are handled as String objects. Data conversion errors are handled by storing the unconverted values in a "cachedValues" Map. This map is then used when re-displaying the page so that the data the user entered is not lost even though it may not be able to be stored in the data type on the business object. (E.g., letters in a KualiDecimal property.   
M35For lookups and inquiry buttons/links: Automatic passing of keys from related fields when the field is the last field in a multi-field foreign key. (E.g., retrieval and inclusion of the chartOfAccountsCode when performing a lookup on the accountNumber field.)  
M36Automatic setting of the primary key fields on the BO to read-only when the maintenance document is in edit mode (FieldUtils).  
M37Special case of above: Automatic setting of the principal name property to read only when the related principal ID field is part of the primary key.  
M38Automatic handling of field conversion values for building the quickfinders and direct inquiry buttons on attributes. Adds the necessary "document.newMaintainableObject." prefix.   

In maintenance document authorization checks, automatic stripping of the document/maintainable prefixes on property names to allow the permission definitions to only use the business object property name.

M40Automatic recognition of masked fields as sensitive. If so, it marks them as needing encryption when sent to the client and sets up their masked value for display.  
M41Support for specification of additional "onblur" functionality in the DD. (Assumes that any called functions exist in the standard libraries or are included in the additional script files also in the DD for the maintenance document.  
M42Ability to define a help URL on a per-field basis. (This should probably be retired in favor of KRAD popup help.)  
M43Ability to indicate that any property which is the code on a relationship for a BO class which implements KualiCode should display itself as a combination of Code + Name. (Used when document/field is in read-only mode.)  
M44Automatically clears out secure fields upon a BO copy operation.  
M45If a collection class under the main object implements the Inactivatable interface, then display, as part of the tab containing the collection) a show/hide inactive button.  
M46Skipped generating a required field error if the field was also marked as unconditionally read only. The assumption is that the field would be filled in by server-side code in these cases and not to inform the user since they could not do anything about it anyway.  
M47Stores contents of all maintenance documents in a single table. (KRNS_MAINT_DOC_T) It is stored as an XStream-serialized representation of the document's maintainables. There are a number of custom tags used to wrap the business objects. See MaintenanceDocumentBase.populateMaintainablesFromXmlDocumentContents()  
M48Ability for an application to use a custom base document class for maintenance documents.  
M49Ability to specify the Maintainable class for a given document in the DD.  
M50Upon populating the business object (called from the action), manually performed the resolution of principal name to principal ID for all registered Person relationships.  
M51Responsible for creating the UI components from the DD information and business object data.  

Provided customization hooks for documents for the following operations:

    • Creating New BO
    • Editing Existing BO
    • Copying Existing BO
    • Any form POST operation
    • Before adding a collection line
    • After adding a collection line
M52M53Ability to override any default values.  
M53M54Maintained special containers for the "add" lines for collections so that the data models did not have to have "fake/non-persistent" add line attributes.  
M54M55Handler for and recognition of references (related objects) which could have been affected by a user's returning from a lookup with a new value.  
M55M56Performed for force uppercase function for the document.  
M56M57Hook to prepare the business object as part of the document setup.  
M57M58Generation of the strings which would be stored to the KRNS_MAINT_LOCK_T table to prevent the editing of the same record on multiple documents.  
M58M59Hook to allow access to and manipulation of the KNS Section objects to make tweaks. The KFS OrgReviewRole used this function to, per data available only after the user entered it on the document, to hide or mark fields as read only. 

Probably should be reviewed within KFS to see what they are doing and whether it can be done within KRAD in a less hacky way.

Likely, this document would be better served by having multiple "views" and dynamic read-only/editable fields. Progressive disclosure would also work in this case.

M59M60Ability to specify (via method override) that the related document was editing an "Externalizable Business Object" - this essentially would shortcut/skip some of the behaviors which only worked when the object was a normal PersistableBusinessObject. (Only real purpose seems to be to avoid throwing errors if the object could not be loaded from the database.) Ideally - this should not be needed after the data module conversion, as the data providers would take care of this.
M60M61Hook to prepare the "old" business object after loading from the database. For non-database objects, this would be used to populate the object from whatever source was needed.  
 "Global" Maintenance Documents  
M61M62Supports a mass change form of maintenance document termed a "Global". These extend the base maintainable framework by using a business object which implements a special marker interface. This object is really a document-based class complete with document number and containing one or more lists of GlobalBusinessObjectDetail objects. This and the special maintainable (KualiGlobalMaintainableImpl) result in the special behavior. (Should probably choose some other MassChange or BulkUpdate)
M62M63Global documents provide a hook (though it must be implemented from scratch by any implementors) to add locks to the maintenance lock table for each object being edited. 

This is a point for improvement. We should have a default implementation which, since it should know what the detail object is, to call into the maintainable for that object and generate the individual locks.

This would however require a new API method to generate a single lock for a given business object. Can be culled from org.kuali.rice.krad.maintenance.MaintainableImpl.generateMaintenanceLocks()

M63Calls into the GlobalBusinessObject (the document) to build the list of maintained business objects to save or delete. 

We should have a more intelligent base implementation. At the moment, everything needs to be done custom each time. It seems that it would be easy to add a method to retrieve all the contained GlobalBusinessObjectDetail objects and then ask each of those for their business object to save.

Given that there are some hard-requirements for the implementation of the GlobalBusinessObject, we should provide a useful base class so the simple functions can be handled via configuration rather than code.

 NOTE: On the maintenance document collection used for the detail objects, you must specify the global detail class as the business object and the BO class being modified as the source class. Since any instance of the global detail object needs to have that class information, this is redundant and could be removed.  
 Business Rules  
M63M64Provides a base method to allow customization of the setup of convenience objects (and anything else which will be used by the various rule methods.) The base implementation just extracts them from the old and new maintainable objects  

The base rule class provides explicit hooks for adding functionality to the default validation operations shared by all maintenance documents. (The processCustomXxxxx methods) The base has hooks for the following operations:

    • save
    • route
    • approve
    • add collection line
M65M66Performs a set of global (base) validations for the document as a whole. These are always run and usually prevent the operation on the document if they fail. (doc description, filling out the PK)  
M66M67The base classes provide special support for linking errors to the correct form field path so that the error messages appear in the correct location. This may already be working in KRAD and the validation is much more dynamic. We just want to make sure that we preserve an easy way for rule implementors to attach their messages to the correct fields.
M67M68Upon document routing, performs a permission check via the document authorizer to ensure that the initiator can edit that particular business object.  
M68M69If the object is being inactivated, then checks for InactivationBlocking configuration referencing this class. If a blocking record is found, it stops the document submission. This function does not block the deletion of business objects and probably should. (It was created before the delete function was incorporated.)
 DD Properties  
M69M70Ability to control whether an BO can be deleted via maintenance document at the DD level. (I.e., disallow it regardless of permissions.)  
M70M71Allow for PK values to be preserved when copying a business object.  
M71M72Ability to control whether new BOs of a given type can be created via documents. (if not, you can only edit existing records.) We should consider moving this down to the BO DD files. This is really a property which affects the BO table, not any particular document which edits that object. Though, we may need it on the document as well.
M72M73Automatic detection, upon document submit, if there is already an existing document ENROUTE for the same business object.  
M73M74Ability to define a set of key fields used for detecting the above locking. (E.g., when the object has a user-visible unique key which is separate from the underlying primary key.) When not specified, the locking keys should default to the primary key.  
M74M75Ability to set the maintenance document base class. (Defaults to MaintenanceDocumentBase - but KFS does override this.)  
M75M76Ability to pre-process the HTTP request and manipulate the Struts form object directly rather than relying on the business object population. (org.kuali.rice.kns.web.derivedvaluesetter.DerivedValuesSetter) Not sure if this is still needed. I know that KFS uses this function a bit, but maybe there is a better way under KRAD.
M76M77Ability to specify a class which can ask questions prior to routing the document. (org.kuali.rice.kns.rule.PromptBeforeValidation) Again, this can probably be handled better in KRAD since we can use JavaScript. The KNS implementation had to work with JS turned off.
M77M78Ability to set a field as required (MaintainableFieldDefinition) - this was used to render the asterisk on the UI and perform DD validation when the document was submitted.  
M78M79Ability to set a field as "lookup-only", meaning that it could only by populated by use of a lookup - never entered directly. This was generally done when special processing was needed after entering a value. (E.g., to load other fields.) IMO - we should remove this capability. It's a PITA in places where you know the code. Example: Parent document type on the document type lookup. Why do I need to enter that when I know that I want "KFS" for the parent document?!?!?
M79M80Ability to specify a class (ValueFinder) which will obtain the default value for a field. The KNS version has a problem in that it is not aware of the document's state, and so can't make any decisions based on what is already on the document.
M80M81Ability to set a field as "unconditionally read only" so that not even permissions can make it editable. This also causes the UI components to simply not render the <input> tag for that field.  
M81M82Ability to note that a field (within a collection) should be read only after its been added. (Used to lock down collection PK fields after the user enters them.  
M82M83Ability to specify an alternate attribute to use for display purposes when the document is in read-only mode.  
M83M84Ability to specify an additional attribute for use during read-only display.  
M84M85On maintainable collections, to support multiple value lookup, you can specify what the source class is that you are looking up. (I.e., on the account global document, the detail object is AccountGlobalDetail - part of the document - but the source object is Account - the business object which gets referenced by that document class)  
M85M86Ability to control the existence of the "add" line via the collection definition.  
M86M87Ability to control whether to have a multiple value lookup.  
M87M88Ability to specify whether items can be deleted from the collection. (Default is to only allow deletion of newly added lines.)  
M88M89Ability to specify which field (singular) should be highlighted if there is a key violation between collection records.  
M89M90Ability to set a title for the summary line that appears at the top of each collection "row" (Applies when using the KNS-style old/new vertical alignment for collection rows.)  
M90M91Ability to set fields which will be included after the summary title. (Applies when using the KNS-style old/new vertical alignment for collection rows.)  
M91M92Ability to specify the list of fields which form the unique key within a collection.  
M92M93List data object attributes which should be reference checked for existence. These will be checked that they exist in the database and are active. You can (must?) also indicate which field you want the framework to highlight if the validation fails.  
M93M94Ability to configure workflow attribute information for the document, both for searching and for workflow node processing. The DataDictionaryQualifierResolver handles the workflow attributes.