SSP v2.3.0 General Release Announcement

Changelog Summary

TBD TBD TBD

Fresh Installation Instructions

See SSP v2.3.0 Installation Instructions

Upgrade Instructions

By definition, these instructions cannot provide comprehensive advice for all the situations you may encounter when upgrading source code forks, and they should be understand as a best-effort attempt at a generic recipe for working through any given upgrade, with pointers on known issues and "gotchas" mixed in.

In many cases, a systems administrator with relatively limited SSP-specific experience can successfully execute an upgrade. But again, because upgrading a source code fork almost always involves making decisions about what does and doesn't constitute a valid local change that should be carried forward into the upgraded source code, it may be necessary to involve a developer or technical staff already familiar with SSP internals.

The SSP team strongly recommends a multi-stage process for upgrading institutional SSP installations. Start by attempting the upgrade locally, even in the absence of a complete copy of UAT or production databases. Work out the obvious problems there, then move to your shared QA/Test/UAT/Dev environment and attempt a deployment. You'll usually want to refresh the database in that environment from a recent production backup, if possible, before attempting the deployment. Once everything has been tested successfully in that environment, you should have a very good idea of the exact steps you'll need to reproduce to execute the deployment in production. 

SSP Source Code Upgrade

If your deployment is not derived from a fork of the SSP source code project, skip this section and go to SSP-Platform Source Code Upgrade below.

TBD TBD TBD

SSP-Platform Source Code Upgrade

TBD TBD TBD

Additional Upgrade Steps

For implementers with an existing installation of 2.0.X, 2.1.X or 2.2 the changes described below should be executed after the release is built during the upgrade process. 

• 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
• 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 id = 'Update Full Map Printout for SSP-1894'
  • Message template change: In SSP administration, System Configuration, Message Templates edit the MAP Plan Full Printout.
  • Find this section and replace the first line with 
    • #if($includeFinancialAidInformation)
      

   

      #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

v2.3.0 JIRA Issues

Bugs

Improvements and New Features

Task