What's Changed in PPM 9.54
This section highlights what's changed in 9.54 that requires your attention before the upgrade.
Sever configuration parameters
The following parameters behave differently in PPM 9.54.
Parameter | In 9.54 | Before 9.54 |
---|---|---|
ENABLE_MOBILITY_APPS |
|
|
**CONC_LOG_TRANSFER_PROTOCOL |
Valid values: FTP, SCP, SCP2JSch | Valid values: FTP, SCP |
Access Grants
The following out-of-the-box security groups include more access grants.
Security Group | Added Access Grants |
---|---|
(REFERENCE) PPM Administrator |
|
PPM All Access Grants |
|
Menu
If the availability of a menu item is controlled by a server parameter, when the PPM administrator changes the parameter value, the change is no longer immediately reflected on the menu. In order to make the change take effect on the menu, either of the following should be done:
- The currently logged-in users log out.
- The PPM administrator flushes the usermenu cache.
Example: The menu "Manage Global Strategic Themes" is only available when the PPM administrator enables the parameter ENABLE_STRATEGIC_THEMES
. If the administrator disables it, the menu does not disappear immediately. The menu disappears only after the currently logged-in users log out or the administrator flushes the usermenu cache.
PPM now has the following menu items controlled by server parameters.
Menu Label | Controlled by Parameter |
---|---|
Search Request Drafts | ALLOW_SAVE_REQUEST_DRAFT |
|
LOCK_TIMESHEET_ENABLED |
|
ENABLE_BUSINESS_OBJECTIVES |
View Connection Correlation | ENABLE_CONNECTION_CORRELATION |
Manage Global Strategic Themes (OPEN) | ENABLE_STRATEGIC_THEMES |
|
APM_ENABLED |
Exceptions | LOG_EXCEPTIONS_TO_DB |
Dashboard
Resource Pool List portlet
The portlet used to show disabled resource pools. In 9.54, it does not show disabled resource pools by default. That's because a new filter "Enabled Resource Pools Only" is added in the portlet preferences, and it is set to "Yes" by default.
PPM-Agile integration
PPM-JIRA request integration
If you already mapped a PPM field to JIRA's field "Priority" before 9.54, after the upgrade to 9.54, you should delete the field mapping and remap "Priority" with a PPM field.
Platform
Grant privilege of DBMS_CRYPTO
PPM 9.54 uses DBMS_CRYPTO.HASH to generate hash code for reference codes of entity types (such as request type, report type, and datasource). When PPM starts, it first checks whether the PPM schema has the privilege of executing DBMS_CRYPTO. If not, PPM cannot start with an error.
To grant privilege of DBMS_CRYPTO, ask your DBA to run the following command:
GRANT EXECUTE ON DBMS_CRYPTO to <ppm_schema>
JMS
JMS service changes for standalone PPM. Previously, JMS service opens in localhost. In 954, it changes to LOCAL_IP (defined by RMI_URL)
REST API
PPM 9.54 does validation check when you use REST APIs to do the following:
-
Submit a new time sheet
You cannot submit a time sheet if it includes a completed task, a task upon which your work is marked as 100%, or a task whose total hours is negative.
-
Update an existing time sheet
You cannot submit a time sheet if it includes a completed task, a task upon which your work is marked as 100%, or a task whose total hours is negative.
-
Get suggested work items
It does not return the following tasks:
- Your work on the tasks is marked as 100%
- The tasks are complete and time is no longer allowed to be logged on them, as specified by the parameter TM_CANNOT_ADD_ASSIGNMENT_COMPLETE_TASK.
Hotfix deployment
- kDeploy.sh supports new command-line options:
-f
,-nv
,-validate
, -debug
. -
Hotfix information is stored in new tables:
- PPM_HOTFIX_LIST : records hotfix general information and status
- PPM_HOTFIX_FILE_LIST : records hotfix files information
- PPM_HOTFIX_ACTION_AUDIT : records the operations for each hotfix, like deploy or un-deploy
- Hotfix deployment supports system file changes only. It does not support SQL changes.
For details, see kDeploy.sh.