Page Comparison

1)  Per SSP-1838 and SSP-1981, a new message template for the MAP Templates has been introduced to print templates.  This will not affect any existing message templates.  The message template definition exists in the Configuration Guide.

2)  Per SSP-1894, the Full Plan Message Template and Matrix Plan Message Templates have changed to consistently display contact information for both the owner and assigned coach.  Since implementers may have modified the message templates, the upgrade will ONLY update the message template definition IF no changes from the default have been made.  IF changes to the message template(s) have been made, the changes can be manually made in the SSP Admin Configuration.  The code snippets below details the portions of the templates that have changed:

Old

<p style="padding-left:20px;font-size:small;margin-top:30px;">
	<strong>If I have questions or concerns about my plan I will contact:</strong>
	</p>
	<p style="padding-left:20px;padding-left:20px;font-size:small">
		<strong>
	#if("$!contactName" != "") $!contactTitle $contactName #else $coachFullName #end</br>
	#if("$!contactPhone" != "") $contactPhone #else $coachPhone2 #end</br>
	#if("$!contactEmail" != "") $contactEmail #else $coachEmail #end
	</strong>
	</p>
------------------------------------------------------------------------------------------------
New

<p style="padding-left:20px;font-size:small;margin-top:30px;">
	<strong>If I have questions or concerns about my plan I will contact:</strong>
	</p>
	<strong>
	<p style="padding-left:20px">
	$!contactName</br>
	$!contactTitle</br>
	$!contactPhone</br>
	$!contactEmail
	</p>
		
	<p style="padding-left:20px">
	$!ownerFullName</br>
	$!ownerPhone</br>
	$!ownerEmail
	</p>
	</strong>
	</p>

Old

<b>If I have questions or concerns about my plan I will contact:
	</p>
	<p style="padding-left:20px">
	$!coachFullName</br>
	$!coachPhone2</br>
	$!coachEmail
	</p>
------------------------------------------------------------------------------------------------
New 

<b>If I have questions or concerns about my plan I will contact:
	</p>
	<p style="padding-left:20px">
	$!contactName</br>
	$!contactTitle</br>
	$!contactPhone</br>
	$!contactEmail
	</p>
		
	<p style="padding-left:20px">
	$!ownerFullName</br>
	$!ownerPhone</br>
	$!ownerEmail
	</p>

3)  Per SSP-1894, in addition to the default message template changes for MAP, the Velocity context variables $coachPhone1, $coachPhone2, $coachEmail, $coachFullname have been replaced with $ownerPhone, $ownerFullname, and $ownerEmail. The single phone number points to the owner's 'work_phone' (as opposed to home and cell phone with the previous variables). $student , the student 'person' object has been also added to this messages' scope.  The new variables should replace the existing variables in customized message templates

4)  Per SSP-1881, changes to the uPortal tables to harmonize the column size for user name were made.  The database changes will be made by the upgrade process UNLESS uPortal and SSP DO NOT share the same schema.  In the case where two different schemas are used, the SQL for updating the tabes must be run manually.

alter table up_person_dir alter column user_name type varchar(50);
alter table up_user alter column user_name type varchar(50);
alter table up_sso_ticket alter column user_name type varchar(50);
alter table up_raw_events alter column user_name type varchar(50);

alter table up_person_dir alter column user_name  nvarchar(50);
alter table up_user alter column user_name  nvarchar(50);
alter table up_sso_ticket alter column user_name  nvarchar(50);
alter table up_raw_events alter column user_name type nvarchar(50);

5)  Per SSP-1888, the uPortal build-time configuration options previously defined in <env>.properties (commonly local.properties) have been moved to a new file that is available during run-time.  Most importantly, configuration changes can be executed by restarting the application with no requirement to build.  This accounts for the most common build options.  The new file name and location are <SSP_CONFIGDIR>/ssp-platform-config.properties.  To ensure the latest configuration options are included in the local file, review the latest ssp-platform-config.properties at ./uportal-war/src/main/resources/properties/ssp-platform-config.default.properties. 

For future uPortal builds involving a database initialization ant target (initportal, initdb), you need to specify SSP_CONFIGDIR if it isn't already specified as an env var.

• E.g on *nix.... $> SSP_CONFIGDIR=/opt/ssp/sspconfig ant -Dmaven.test.skip=true clean initdb