Details
-
Type: New Feature
-
Status: Done/Fixed
-
Priority: Major
-
Resolution: Fixed/Completed
-
Affects Version/s: None
-
Fix Version/s: Quest-CM
-
Component/s: None
-
Labels:None
Description
This issue covers form rendering, validation, post-processing for new sections 13 and 14 as shown in the mockups:
http://www.questbridge.org/app_staging/cm/appl/cm_ranking.html
http://www.questbridge.org/app_staging/cm/appl/forward_appl.html
Update quest/sql/quest_data_cm.mysql
------------------------------------------------------
Create a new civicrm_option_group for "partner_ranking" with the option_value records for each rank. These should have labels as shown in the mockup. Option_value "values" should be integers, use 0 for Not Interested.
Forms
---------
Data for both these forms will be stored in the new class/table - Quest/PartnerRanking (quest_partner_ranking). There will be one row in the table for each student + partner college. The row will include columns for both the student's ranking and "forward application" boolean (yes/no).
The grid rows for both forms should be generated dynamically from active quest_partner records. For the Ranking form, only include partners where partner_type = 'College'. For the Forwarding form, use the partner_type enum (College, Scholarship) to group the partners for the 2 form sections. The "learn more" URLs are stored in quest_partner.url_learn.
NOTE: Forwarding mockup should be changed to reflect this - but just in case ... the forwarding form elements are a single checkbox (for TRUE). This replaces the original layout which used Yes/No radio buttons.
Validation
-------------
Ranking - User must select a value for EVERY partner ("Not Interested" - which should have a value of 0 - is a valid value).
Forward - No input required (user may check none, one or more partner forwarding boxes).
State Machine
-------------------
Add these new sections to state machine. Both must be completed (validated).