This page tracks major impacting changes post 2.0 release. Things such as database or package name changes for example. This page will serve as a holding pen for information on those changes.
KULRICE-6730 - Remove getBusinessRulesClass from MaintenanceDocumentDictionaryServiceImpl and TransactionalDocumentDictionaryServiceImpl
The following method has been removed from org.kuali.rice.kns.service.MaintenanceDocumentDictionaryService and org.kuali.rice.kns.service.impl.MaintenanceDocumentDictionaryServiceImpl
public Class<? extends BusinessRule> getBusinessRulesClass(MaintenanceDocument document);
The following method has been removed from org.kuali.rice.kns.service.TransactionalDocumentDictionaryService and org.kuali.rice.kns.service.impl.TransactionalDocumentDictionaryServiceImpl
public Class<? extends BusinessRule> getBusinessRulesClass(TransactionDocument document);
To apply this change, run the SQL in scripts/upgrades/2.0.0 to 2.1/db-updates/2012-02-27.sql (for Oracle) or scripts/upgrades/2.0.0 to 2.1/db-updates/mysql-2012-02-27.sql (for MySQL).
To apply this change, run the SQL in scripts/upgrades/2.0.0 to 2.1/db-updates/2012-03-05.sql (for Oracle) or scripts/upgrades/2.0.0 to 2.1/db-updates/mysql-2012-03-05.sql (for MySQL).
To apply this change, run the SQL in scripts/upgrades/2.0.0 to 2.1/db-updates/2012-03-13.sql (for Oracle) or scripts/upgrades/2.0.0 to 2.1/db-updates/mysql-2012-03-13.sql (for MySQL).
To apply this change, run the SQL in scripts/upgrades/2.0.0 to 2.1/db-updates/2012-04-04.sql (for Oracle) or scripts/upgrades/2.0.0 to 2.1/db-updates/mysql-2012-04-04.sql (for MySQL).
To apply this change, run the following SQL scripts for Oracle:
or the following SQL scripts for MySQL:
To apply this change, run the SQL in scripts/upgrades/2.0.0 to 2.1/db-updates/2012-04-16b.sql (for Oracle) or scripts/upgrades/2.0.0 to 2.1/db-updates/mysql-2012-04-16b.sql (for MySQL).
To apply this change, run the SQL in scripts/upgrades/2.0.0 to 2.1/db-updates/2012-04-16.sql (for Oracle) or scripts/upgrades/2.0.0 to 2.1/db-updates/mysql-2012-04-16.sql (for MySQL).
To apply this change, run the SQL in scripts/upgrades/2.0.0 to 2.1/db-updates/2012-04-25.sql (for Oracle) or scripts/upgrades/2.0.0 to 2.1/db-updates/mysql-2012-04-25.sql (for MySQL).
In some cases it may be desirable to only use the KNS without KRAD. For example if you're timelines push a conversion to KRAD out into the future, you may see some benefits with startup performance and with memory usage.
You can override the kradApplicationModuleConfiguration bean to not include any of the files in the UIF folder. That is, you only need to include these files:
<property name="dataDictionaryPackages"> <list> <value>classpath:org/kuali/rice/krad/bo/datadictionary/AdHocRoutePerson.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/AdHocRouteWorkgroup.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/Attachment.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/AttributeReferenceDummy.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/AttributeReferenceElements.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/BusinessObjectAttributeEntry.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/DataDictionaryBaseTypes.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/DocumentHeader.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/Note.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/NoteType.xml</value> <value>classpath:org/kuali/rice/krad/bo/datadictionary/PessimisticLock.xml</value> </list> </property>
Likewise, this can be done for the ‘baselinePackages’ property on the dataDictionaryService bean.
The help URL on the document and lookup level has been removed from the KEW document type. This means the "Help Definition URL" and the "Document Search Help URL" on the "Document Type" are depreciated and don't serve any function anymore. Instead the help URL are defined on the UIF-View level either within the data dictionary or the system parameters.
The following changes impact KRAD UIF configuration (XML). Mostly these should be covered by the Bean/CSS conversion script documented below.
Previously the component title property was be used for various purposes. For example on Containers the title was used as a shorthand for setting header.headerText. The title property should be getting passed to the template and used to populate the title attribute on the corresponding tag (for example on a group this would be the div). Therefore the change was made to pass this through and add to the tags. The container property 'headerText' was added as a shorthand for setting the header.headerText property. The bean conversion script converts title to headerText. However it must be used with care since this should only be converted on containers (view and group), and not other components (like image or link).
In 2.0, the Inquiry and DirectInquiry were separate widgets with separate properties on InputField. Therefore, when both were required both had to be configured with similar properties. This caused duplicate configuration. In 2.2, the DirectInquiry widget has been removed and the Inquiry widget supports rendering the direct inquiry when the field is not read-only. The direct inquiry behavior can be disabled with the Inquiry property enableDirectInquiry.
Any configuration referencing fieldDirectInquiry will need to be converted to the property named inquiry. Note if the standard inquiry and direct inquiry were both configured for a field, the direct inquiry can simply be dropped. If you were disabling the direct inquiry by fieldDirectInquiry.render="false", this can be changed to inquiry.enableDirectInquiry. The bean conversion script makes this change.
The process for adding growl messages server side has been modified. In 2.0, a growl was shown for each message in the GlobalVariables.getMessageMap() that was of type Info. The MessageMap has been enhanced to support a new growl type. For adding growls you now should call one of the following methods: