Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.2
-
Component/s: Sample Apps
-
Labels:None
-
Environment:All
Description
We should create a new tutorial that demonstrates common master-detail scenarios using the ICEfaces components.
Suggestions for contents include:
1. dataTable with rowSelector to select "master" record.
2. detail form updates with selected record details.
3. user edits, optionally saves detail rows
4. user selects a different "master" record from dataTable.
Alternate scenarios:
- A different component is used for the master list (selectOneMenu, etc.).
- Both master and detail within the same form and also in separate forms
- Handling of "dirty" (unsaved) edits on the detail form when the user selects an alternate "master" record to view:
A - Ignore entered changes and display new master detail.
B - Save entered changes prior to switching to new master detail (abort change if validation fails)
C - Prompt the user to save any unsaved changes prior to displaying new master detail (abort change if validation fails)
Suggestions for contents include:
1. dataTable with rowSelector to select "master" record.
2. detail form updates with selected record details.
3. user edits, optionally saves detail rows
4. user selects a different "master" record from dataTable.
Alternate scenarios:
- A different component is used for the master list (selectOneMenu, etc.).
- Both master and detail within the same form and also in separate forms
- Handling of "dirty" (unsaved) edits on the detail form when the user selects an alternate "master" record to view:
A - Ignore entered changes and display new master detail.
B - Save entered changes prior to switching to new master detail (abort change if validation fails)
C - Prompt the user to save any unsaved changes prior to displaying new master detail (abort change if validation fails)
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion