Versions Compared

Old Version 17

changes.mady.by.user Daniel McCallum

Saved on

compared with

New Version 18

changes.mady.by.user Daniel McCallum

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add SSP_CONFIGDIR=/path/to/ssp/config to risk indicator data-import

...

4 - Import Permissions for Watch Student Feature

After the SSP-Platform source has been pulled into the local repository, the following import will add the appropriate permissions for the Coach and Manager roles to enable the Watch Student feature.

Code Block
SSP_CONFIGDIR=</path/to/your/config/dir> ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-6-0/SSP-770 data-import

 

5 - Import Permissions for Bulk Action Features

After the SSP-Platform source has been pulled into the local repository, the following import will add the appropriate permissions for the Coach, Manager and Administrator roles to execute Bulk Actions from the Caseload and Search Results

Code Block
SSP_CONFIGDIR=</path/to/your/config/dir> ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-6-0/SSP-2086 data-import

 

6 - New permissions and functionality were created to remove the Main Tool from individual users or groups/role (added in v2.5.2)

The intent of this feature is to remove the display of protected information from users who should not have access.  For example, the application can be configured such that faculty members who do not need to view academic history for any student will not have the Main Tool available in the UI.  Instructions to manage the permissions are described in the User Guide. Before you'll be able to manage those permissions, though, you need to run the following command from within your SSP-Platform source code checkout (only necessary for an upgrade; fresh installs will execute this file automatically):

Code Block
titleImport New Permissions
SSP_CONFIGDIR=</path/to/your/config/dir> ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-5-2/SSP-2631 data-import

7 - New permissions and functionality to display Student Risk Indicators on the Main Tool (added in v2.6.0)

IMPORTANT- this only applies to situations where individual permissions need to be assigned to a group/user.  By default, the indicators are accessible by any group/user with PERSON_READ.  The intent of this feature is to display student risk factors based on data loaded into the external database table.  SSP will display the indicators defined a active in administration.  Before you'll be able to manage those permissions, though, you need to run the following command from within your SSP-Platform source code checkout (only necessary for an upgrade; fresh installs will execute this file automatically):

Code Block
titleImport New Permissions
SSP_CONFIGDIR=/path/to/ssp/config  ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-6-0/SSP-2898 data-import
SSP_CONFIGDIR=/path/to/ssp/config  ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-6-0/SSP-2899 data-import

8 -  SSP Platform Database Pool Configuration Options

The database pool configuration options were externalized into the ssp-platform-config.properties files.  All of configuration values were previously included in the source files: datasourceContext.xml and/or rdbm.properties.  Generally, the values were changed to increase the value of environment.build.portaldb.max.active.  Any implementer may wish to back out that change and re-apply it in $SSP_CONFIGDIR/ssp-platform-config.properties. Otherwise, deployers should not be affected by the externalization as all default values were defined in the default configuration.

SSP v2.6.0 JIRA Issues

...