[KULRICE-13147] Inefficiencies in view lifecycle and rendering Created: 25/Aug/14  Updated: 24/Sep/14  Resolved: 08/Sep/14

Status: Closed
Project: Kuali Rice Development
Component/s: Development, User Experience (UX)
Affects Version/s: None
Fix Version/s: 2.5
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Critical
Reporter: Jerry Neal (Inactive) Assignee: Jerry Neal (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Performance
Rice Module:
Application Requirement:
Sprint: UXI 2.5.0-m7 Sprint 1
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:
Story Points: 1


There are a few places in the view lifecycle where we are doing more than we need to which impacts performance.

The first is we rebuild the dialogs groups for each page change, even though they are only rendered on full view refreshes.

The second is we render the top group, breadcrumbs, and view header on twice on full view loads (update logic in pageGroup.ftl). On a full view refresh we don't need to render the updates in pageGroup.ftl.

Generated at Sat Jun 19 13:52:01 CDT 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.