SSP v2.1 general release announcement
Last paragraph of
Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Remove unused permissions with SQL
- delete from up_permission where activity in ('PERSON_TEST_READ','PERSON_TRANSCRIPT_READ');
- delete from up_permission_activity where activity_fname in ('PERSON_TEST_READ','PERSON_TRANSCRIPT_READ');
Add new persmissions for configurable Confidentiality Levels
- ant -Dmaven.test.skip=true -Ddir=platform-war/src/main/data/ssp_entities/patches-SSP2-1-0/SSP-1466
Add new bulk reassign permission for the Caseload Reassignment tool
- ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-1-0/SSP-1762 data-import
Add SSP adminsitrators to the uPortal administrators group
- ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/group_membership/Portal_Administrators.group-membership.xml
Correct the DATA_ENGLISH_SECOND_LANGAGE permission * Applies to 2.0.1 also*
- update up_permission set activity = 'DATA_ENGLISH_SECOND_LANGUAGE' where activity = 'DATA_ENGLISH_SECOND_LANGAGE'
- update up_permission_activity set activity_fname = 'DATA_ENGLISH_SECOND_LANGUAGE', activity_name = 'DATA_ENGLISH_SECOND_LANGUAGE' where activity_fname = 'DATA_ENGLISH_SECOND_LANGAGE'
New Confidentiality Levels
- define approach for generic levels
- define access by users when creating/editing an entity
- any new generic CL defined should be added to oauth perms to access the new CLs
v2.1 JIRA Issues