[CUI-132] Refactor KBA logic in the self-registration and profile views Created:
11/Dec/15 Updated: 04/Jan/16
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Open
Commons - UI
None
10.x
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Improvement
Eugenia Sergueeva
Unresolved
None
Not Specified
Issue Links:
Depends
depends on
None
Priority:
Assignee:
Votes:
Major
Unassigned
0
Not Specified
Not Specified
is required
by
OPENAM7693
OPENAM7719
KBA allow users to add the same
quest...
User shouldn't be allowed to
save/upd...
Closed
Open
Description
Both Self Registration and Profile View have KBA parts in them. On both views you can
add/edit/delete questions. Both views should have validation for minimum required questions
defined. Save/Update buttons should not be enabled when that requirement is not met. Also,
both views have additional generic validation (making sure fields are not left empty).
Currently, the KBA logic is not encapsulated and is duplicated in two places, which makes it
harder to improve, fix or maintain.
My suggestion would be to create a KBAView (or something similar), where the KBA
operations would be encapsulated, and there would be a single template responsible for drawing
KBA questions on UI. That view should then be included on both Profile and Self Registration
pages.
Comments
Comment by Eugenia Sergueeva [ 04/Jan/16 ]
should be addressed first.
Generated at Wed Feb 10 00:56:50 GMT 2016 using JIRA 6.3.9#6339sha1:46fa26140bf81c66e10e6f784903d4bfb1a521ae.