Details
-
Type:
Task
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 2.2
-
Fix Version/s: Backlog
-
Component/s: Development, Roadmap, User Experience (UX)
-
Security Level: Public (Public: Anyone can view)
-
Labels:
-
Similar issues:
KULRICE-10396 Extending a bean that has ids on inner beans causes issues, need to define id on inner beans with component id property KULRICE-6831Inner scroll bar on firefox KULRICE-7639Edit, Copy, or View Agenda in sampleapp yields stacktrace KULRICE-2998Recreate the KIM views in the Rice database KULRICE-3339Facilitate KEW method for using Principal Id in an Inner Application Role (see NetworkIdRoleAttribute class) KULRICE-13147Inefficiencies in view lifecycle and rendering KULRICE-5981Breadcrumbs with single page views KULRICE-7873Optionally supress the view in breadcrumbs KULRICE-8556Progressive disclosure of group/fields within a checkbox or radio group - verify functionality KULRICE-6383Refactor view template -
Epic Link:
-
Rice Module:KRAD
-
KRAD Feature Area:Document
-
Application Requirement:KS
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
"The InnerView component allows a page or a component from another view to be rendered with the view that contains the component. This is useful for the following reasons:
1. Content that is reused across many pages can be built in one view and reused. Prevents from having to include the data and controller methods for each view that needs it.
2. Creation of views can be broken into multiple efforts of form/controllers/view. Valuable for team work.Note there is a restriction that the inner view have the same theme as the parent view. That is the same set of CSS and JavaScript files. If the inner view contains additional CSS or JavaScript files they will be ignored, which might cause the view to malfunction."
