Known issues

This section displays known issues and limitations when working with PPM. For convenience, the known issues are grouped according to product modules.

Known issues

The following table lists some known issues when working with PPM and possible solutions.

Issue Description
Auto-fill allocations in Weekly View not working from first cell

Applicable to 25.3 only. In Resource Allocation Management > Weekly View, when you use Shift + click to copy a cell's value to multiple cells on the same line, auto-fill does not work if you start with the first column.

Workaround: Copy and paste manually, or start auto-fill with a different column.

Layout tab in Request Type Settings page truncated

Applicable to 25.2 only. The Layout tab of the Request Type Settings page is truncated, causing some elements in the Advanced Fields section to be hidden or not fully visible.

Workaround: Collapse the Basic Fields section to view and access the hidden elements in the Advanced Fields section. Alternatively, reduce the browser zoom level to display the entire tab.

Blank page after reloading scenarios using Board View with content deleted in portfolio

Applicable to 25.2 only. In what-if scenarios using the Board View content view widget, after a content is deleted from the associated portfolio, clicking the Reload button in the scenario details page causes the page to go blank.

Workaround: Refresh the page to load the content.

Missing divider lines in table headers Applicable to 25.2 only. Some table headers in the table component are missing dividing lines, affecting visual separation between columns.
Menu items truncated in classic menu

Applicable to 25.2 only. In the classic menu, some menu items are truncated and not fully visible.

Workaround: Reduce the browser zoom level to display all menu items.

Error when reordering pages in My Links using classic menu style Applicable to 25.2 only. An error occurs when you adjust the page sequence in the My Links list while using the classic menu style.
Error with SQL rule on request type due to regional language setting conflict

An error may occur when a user with a specific regional language variant opens a request that has an SQL rule defined for field-level security. This issue may not happen to users with a different variant of the same language. The behavior is due to how Oracle interprets different regional language options, even when they appear to represent the same language. These options result in different parameters being passed to Oracle, which can cause inconsistent behavior.

Workaround: To prevent this issue, set the same regional settings for all users.

Action buttons disappear on Project Details page

On the Project Details page, the Save and other action buttons disappear when the project name is excessively long.

Resolution: A hotfix is available. Contact support to obtain the hotfix.

APIs do not support unlimited rich text length

When the ALLOW_NO_SIZE_LIMIT_RICH_TEXT_FIELD parameter is set to true, rich text fields have no character limit. However, the following APIs do not currently support this functionality and still enforce a maximum character limit of 4000:

  • post/dm/reqeusts

  • put/dem/requests/{reqId}

If the submitted rich text exceeds this limit, the API request may fail.

Upgrade to version 25.1

Applicable for PPM using Oracle. When upgrading PPM to 25.1, if you upgrade the code file system first and then upgrade the database, an error occurs. PPM using PostgreSQL is not affected.

Workaround: Upgrade the database first, then the file system, or upgrade the file system and database together.

Regional settings language option not saved correctly

Applicable to 25.1 only. On instances using OpenJDK17 as the JAVA_HOME, if you select language options with multiple parameters from the Regional Settings page, the selected option is changed after saving. For example, Chinese (Simplified, China) is saved as Chinese (China).

Workaround: Manually reselect the correct option and save again.

Portlets fail to load when the data source column contains "?"

Applicable to 25.1 only. When a portlet data source column contains a "?", the portlet fails to load data.

Resolution: A hotfix is available. Contact support to obtain the hotfix.

Menu display issues

Applicable to 24.4 only. After upgrade to version 24.4, the new SideNav menu is enabled by default. However, you can switch back to the legacy TopNav menu by turning off the SideNav Menu feature toggle. Please note that when reverting to the TopNav menu, the display of the menu and the masthead may appear misaligned or disorganized.

Workaround:

  1. From the legacy menu, click the Administration button in the masthead.
  2. From the Administration menu, click System Appearance Customization > Theme Customization.
  3. Go to the Logo area and click Restore to Default.
Browse Project Types menu removed in 24.4

Applicable to 24.4 only. After upgrading to version 24.4, the Browse Project Types menu is not available for users who had access in version 24.3 and earlier. If you added this menu to the My Links list or saved the URL, you can still access the page directly.

Workaround: To view a specific project type's details, open a project of that type, go to Project Settings, and then click the project type link to open its details page.

FX Rate Update background service stuck

Applicable to 24.3 and 24.4. The FX Rate Update background service intermittently stops processing, leading to delays or failure in updating foreign exchange rates.

Login issues on a multilingual interface

Applicable to 24.1 only.After upgrading a PPM instance with a multilingual interface to version 24.1, the login page is locked after selecting a session language, preventing further progression.

Resolution: A hotfix is available. Contact support to obtain the hot fix.

For more information, see this article: KM000026809.

Error after login

Applicable to 24.1 only. After upgrading PPM to version 24.1, the following error may appear after login: "An unknown error has occurred".

Resolution: A hotfix is available. Contact support to obtain the hot fix.

For more information, see this article: KM000026984.

Excel reports

Applicable to 24.1 only. After the upgrade to version 24.1, a problem is encountered when generating Excel reports or generating data. The issue arises when utilizing an Excel template file that references database fields with non-lowercase names, for example, use PROJECT_NAME instead of project_name.

Resolution: A hotfix is available. Contact support to obtain the hot fix.

For more information, see this article: KM000027122.

Time sheet notifications

Applicable to 24.1 only. Fail to send time sheet notifications in PPM upgraded from earlier versions to 2023 and later versions.

Workaround:

  1. Stop all PPM nodes.
  2. Run the following update statement and then commit.

    Copy code
    update knta_services_nls
    set job_class = 'com.kintana.core.server.scheduler.EmailNotificationJob'
    where reference_code='_NOTIFICATION_SERVICE';
  3. Start all PPM nodes.
Oracle Database version 12.1

Applicable to 24.1 only. If you use Oracle Database version 12.1 with PPM 23.3 and later versions, PPM would fail to start.

Workaround: Before starting the PPM sever, copy the V1.27__alter_configuration_table.sql file to the <PPM_Home>/server/_common/deploy/pvo.war/WEB-INF/classes/db/oracle/migration directory.

Note: If you upgrade PPM from 23.3 to 23.4, 23.3 to 24.1, or 23.4 to 24.1, you need to copy the V1.27__alter_configuration_table.sql file each time after the upgrade.

Filter mapping in drilldown portlets

Applicable to 23.4 and 24.1. Drilldown portlets with filter mapping fields do not work, failing to resolve filter tokens and generating an error: "This drill-down cannot be displayed because one or more required preferences are missing. Please contact your dashboard administrator."

Resolution: A hotfix is available. Contact support to obtain the hot fix.

For more information, see this article: KM000027123.

Self-service portlets display no data on project and portfolio overviews

Applicable to 24.2 only. Self-service portlets configured with the grid view type fail to display any data on project and portfolio overviews.

Toggle to disable a personal landing page becomes invisible

Applicable to 24.2 only. The toggle to disable a personal landing page becomes invisible after setting the page as your personal desktop landing page. Despite its invisibility, the toggle remains functional.

Workaround: To stop using a page as a personal landing page, in the top menu, hover over the area to the right of the Add to My Links icon until the "Stop using this page as your personal landing page" tooltip appears, and then click to disable it.

Email notifications are not sent in JDK 11 environments

Applicable to 24.1 only. Email notifications are not sent in instances using JDK 11.

This impacts instances upgraded to version 24.1. Fresh install of version 24.1 and instances using other JDK versions are not affected.

Resolution: Remove the javax.mail.jar file in the lib/jboss/boot/ directory and then restart the server.

Note:

When this issue is resolved, all the pending email notifications will be sent out.

  • To check the number of pending email notifications, run the following SQL query:

    Copy code
    SELECT count(*)
      FROM knta_notif_txn_parents p
    where p.notification_sent_flag = 'N'
       and p.interval_id = 3
    order by p.notif_txn_parent_id asc
  • To stop sending these notifications, set the sent flag to Y:

    Copy code
    update knta_notif_txn_parents p set p.notification_sent_flag = 'Y'

    The Notification Cleanup Service automatically deletes these notifications after 7 days. This timeframe can be adjusted using the NOTIFICATIONS_CLEANUP_PERIOD server parameter.

Advanced Filter option not function on portlet Edit Preferences page

Applicable to 24.3 only. The Advanced Filter option does not function on the Edit Preferences page for Java portlets of the Requests category.

Resolution: A hotfix is available. Contact support to obtain the hot fix.

Self-service portlets fail to display when date fields contain null values

Applicable to 24.3 only. Date fields containing null values cause Self-service portlets to fail to display any data.

Resolution: A hotfix is available. Contact support to obtain the hot fix.

Adjacent fields are hidden in multi-select list fields Applicable to 24.3 only. Enabling the Use New Drop-Down and Auto-Complete Lists feature causes adjacent fields to become hidden or not render correctly after selecting multiple values in multi-select fields.

Limitations

The following table lists the limitations for working with PPM.

Limitation Description
Portlets with required filters have values missing when exported

Applicable to 24.3 only. When exporting a drill-down page with multiple portlets to PDF, portlets that have required filter fields may have their values missing in the exported PDF.

Workaround: To export such portlets without error, display each portlet in the maximized view and then export the portlets individually.

ALM Octane integration Applicable to 24.3 only. Unable to import effort from ALM Octane to PPM time sheets.

Bullet and numbered list formatting unavailable in staffing profile notes

Applicable to 24.2 and 24.3. When rich text format is enabled for notes, bullet and numbered list formatting is unavailable in staffing profile notes.

ALM integration

Applicable to 24.1 only. Unable to connect to SSO ALM HTTPS server for ALM integration.
Export the Analyze Assignment Load portlet If you export Analyze Assignment Load portlet data to Excel and select the following two options: display Total Assignment Values for Actual Effort, and include detailed data, the details from packages, programs, and miscellaneous are not exported to Excel, while their actual efforts are included in Actual Total Assignment.
Export Dashboard landing page If you click the product icon to go to the Dashboard landing page, and before you export the page to PDF, your landing page has already been changed, the PDF will display the contents of the new landing page instead of the page you want to export.
Create Staffing Profile Baseline dialog box goes outside screen

When creating a baseline for a staffing profile from the project summary page, if the page is long and you scroll the page to the very bottom to click the Baseline button, the Create Staffing Profile Baseline dialog box might be displayed beyond the screen. You can move this dialog box to the desired place on screen so that you can create the staffing profile baseline.

This issue occurs in the Chrome and Edge browsers.

Turkish locale

Fail to install PPM on the operating systems with the Turkish locale.