Details
-
Type:
Bug Fix
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 2.2.1
-
Component/s: User Interface
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Similar issues:
KULRICE-10597Library - Stacked Layout Manager: Delete button rendered as link KULRICE-11997Travel Account Inquiry with Collections not rendering KULRICE-7489RichTable widget for collections does not display the paging buttons KULRICE-12670Input field not rendering on collection add line item KULRICE-11179Radio Buttons in Lookup Criteria not rendered nicely anymore KULRICE-12419 action buttons vanish for visible items in stacked collection with ajax disclosures KULRICE-7490Highlight collection when hovering on add button KULRICE-11408Kitchen sink rendering error KULRICE-10600Libary - Stacked Layout Manager: Sub Collection expands bejond visible area to the right KULRICE-13774Fill AFT Gap: Kitchen Sink: Collections -
Rice Module:KRAD
-
KRAD Feature Area:Authorization and Presentation
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
-
Include in Release Notes?:Yes
Description
In Rice 2.2.1, "stacked" collection elements in KRAD are no longer displaying add/delete buttons by default. This problem is clearly visible on the sample KRAD collection-displaying views in Kuali test drive.
I noticed a recent addition to the StackedLayoutManager class that could be causing the problem. On lines 201 and 202, if the layout manager is not configured to place actions in the line items group, the actions are instead placed in the line group's footer but then its renderFooter flag is set to false. When testing locally, I can work around the problem by commenting out the line that sets the line group's renderFooter flag to false.