Page Comparison

...

• To upgrade from 2.0.X follow the upgrade instructions for BOTH the 2.1 and 2.2 Release Notes after deploying the 2.3 code
• To upgrade from 2.1.X follow the upgrade instructions for the 2.2 Release Notes after deploying the 2.3 code
• SSP-2303 addresses a bug identified in SSP where by a MAP plan/template term notes were duplicated in the system for each edit.  The application has been patched in v2.3.0, and a cleanup script was included to remove the duplicate rows.  In some cases, logic was required to determine the desired, unique row.  SSP will eliminate semantically duplicate rows in map_term_note in an attempt to winnow that dataset down to at most one row per plan_id\template_id+term_code. In general, because of the way the original bug worked, it's possible to figure out which note to keep by selecting the least frequently occurring note state per plan_id\template_id+term_code. But in the case of ties, the app will first attempt to find a unique result by only preserving records with the most recent created_date and, as a last resort, by making a truly arbitrary choice based on sorting by record id. Because this can potentially result in selection of a note state end users do not expect, and because the fixup is destructive in general, the first step in the fixup is to take a backup of the map_term_note table. That backup table is named map_term_note_SSP_2303_bak. The expectation is that administrators can query that table for historical map_term_note records in the event users report unexpected template state following an upgrade.
• • There is no way to turn the fixup off via configuration. In general, it makes no sense to do so because the UI will make similarly arbitrary decisions (as it did prior to the bug fix), those decisions will just be delayed until the next time a given template is saved.In the event the fixup must absolutely be disabled, comment out this line in masterChangeLog.xml:
    • <include file="org/jasig/ssp/database/changesets/000116.xml" />

• A change to the MAP Plan Full Printout was made to fix the Financial Aid Information option when printing or emailing the plan.

    SSP-2218 contains all of the details with the following steps to correct the template 
  
• Deploy the latest code.  When SSP starts, the SSP portlet will likely not start, the following SQL needs to be executed.
SQL to delete a change request that will be made manually below
delete from databasechangelog where

 If you are upgrading from but not through SSP 2.2.x, you will need to manually update the databasechangelog table, else SSP will fail to start up. The error message will resemble the following:

No Format
Caused by: liquibase.exception.ValidationFailedException: Validation Failed: 1 change sets check sum org/jasig/ssp/database/changesets/000087.xml::Update Full Map Printout for SSP-1894::tony.arland is now: 3:2ea129e39b757f33ecf3d107c8111ac9

 SSP-2218 contains all of the details for working around this problem (again, this should only be required if your currently deployed version is in the 2.2.x series): 

• Run the following SQL against the SSP database:
  • delete from databasechangelog where filename = 'org/jasig/ssp/database/changesets/000087.xml' and id = 'Update Full Map Printout for SSP-1894'
• Message Check to make sure the message template change was applied:
  • In the SSP
  administration
  • UI, navigate to Admin -> System Configuration
  ,
  • -> Message Templates
  edit the
  • -> Select 'MAP Plan Full Printout
  .
  • ' -> Click 'Edit'
  • Find
  this
  • the following section and replace the first line with 
  • #if($includeFinancialAidInformation)
 

Code Block

#if($includeHeaderFooter) <div style="width: 980px"> <div style="left:10px;margin-top:30px"> <p style="text-align:left; color:#000000;"> <strong>Attempted Hours - </strong> $!attemptedHours </p> <p style="text-align:left; color:#000000;"> <strong>Completed Hours - </strong> $!completedHours </p> <p style="text-align:left; color:#000000;"> <strong>Current Completion Rate - </strong> $!completionRage </p> <p style="text-align:left; color:#000000;text-indent:15px;"> <strong>Number of hours needed to earn 67% completion rate - </strong> $!neededFor67PercentCompletion </p> <p style="text-align:left; color:#000000;"> <strong>Financial Aid Cum GPA - </strong> $!financialAidGpa </p> <p style="text-align:left; color:#000000;text-indent:15px;"> <strong>Number of needed to earn a 2.0 Cum GPA with all B - </strong> $!hoursNeededB </p> </div>

• New installations of 2.3.0 are not required to make any additional change

...

...