[KULRICE-7954] Create ToggleAction component Created: 22/Aug/12  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development, User Experience (UX)
Affects Version/s: 2.2.0-m4
Fix Version/s: Backlog
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: Jerry Neal (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
cloned from KULRICE-7953 Add support for ajax retrieval of dis... Closed
cloned to KULRICE-7955 Upgrade jQuery version from 1.7.2 to 1.8 Closed
Similar issues:
KULRICE-10105Remove initializing of ComponentSecurity objects for each component
KULRICE-13464Create AFT to test Component document in EXCEPTION route status
KULRICE-10533Create Smoke Tests for KRAD Component Library - Element Dropdown Menu
KULRICE-13476Create script to bulk load Component documents with pending Approval
KULRICE-10390New component for Application Header
KULRICE-9847Create group component whose parent element is a link
KULRICE-13601Fill AFT Gap: KRAD Library - Component Refresh
KULRICE-11981Create component library demo for enter key support
KULRICE-13540Create JMeter Doc Search for Component
KULRICE-12161Component waiting Acknowledge not persisted to DB
Epic Link: Components
Rice Module:
KRAD
KAI Review Status: Not Required
KTI Review Status: Not Required

 Description   

Create ToggleAction content element. Some design suggestions:

ToggleAction extends ContentElementBase

// defaults for both actions, unless overridden by action
methodToCall
actionLabel
preSubmitCall
additionalSubmitData // note merge this property if both default and in action
actionParameters // note merge this property if both default and in action

Action state1Action
Action state2Action
String initialState; // indicates which action to use initially by the integers 1 (state1Action), or 2 (state2Action)

Framework will add onclick script to handle the toggling of actions (both will be in DOM). The corresponding state for the action will be a data attribute on the element.

Also we need to deal with client side state syncing of the toggle state (for refreshes containing the action).



 Comments   
Comment by Jessica Coltrin (Inactive) [ 16/Oct/12 ]

moving non-blocker and non-critical m4 Jiras to 2.2-backlog

Generated at Tue Jun 02 21:08:44 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.