Home » Blog » Cumulative Update 3 (CU3) for UMT Project Essentials 2012

Cumulative Update 3 (CU3) for UMT Project Essentials 2012

We are pleased to announce the release of the UMT Project Essentials 2012 Cumulative Update 3 (CU3). This includes a number of fixes, therefore UMT strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production.

Here’s the list of fixes and improvements included:

  • Administration
    • The Queue Details page now correctly displays details about affected items for standard update operations
    • Addressed issues with the Financial Structure definition page around renaming or moving Financial Nodes
    • Added a new Global Setting labeled Persist display settings that can be used to turn off the end-user persistence of the last used Granularity and Detail Level
  • Schedule and Resource Plan integration
    • Addressed issues with synchronizing Resource Plan information for durations greater than 9 years
    • Improved reliability of the synchronization algorithms for Forecast when removing values from the last period in the Resource Plan
    • Updated synchronization functions to correctly account for generic resources of type Cost
    • Significant usability improvements in reducing the number of steps required for synchronizing Project Plan data to the financial structure by adding a Use Global Mappings checkbox. If Use Global Mappings is checked, the latest financial node and allocation center global mappings will be used in the synchronization process. If the setting is unchecked, custom mappings can be defined for each resource assignment. In case the global or custom mappings change, values will be updated after the next synchronization
  • API and Programmability
    • Improved parameter validation for the UpdateValues method
    • Updated WSDLs to include the ReadPeriodList method
  • Reporting
    • Data for Custom Snapshots is now included in the Reporting database
    • Updated the name of custom Change Requests from Manually Created Change Request to the actual name
  • Data Import
    • Improved reliability by skipping invalid projects (deleted from the Draft database but available in the Published database) and continuing with the remaining projects rather than failing the entire import session
    • Fixed issue with end date for a project being incorrectly set via data import to the previous day
  • Upgrade
    • Addressed issues with mapped date Custom Fields showing a timestamp (hh:mm) after upgrade to UMT Project Essentials 2012
    • Improved validation for rows not matching the column headers, and set default qualifier to double-quotes (“)
  • Performance and Reliability
    • Improved performance for Reporting Database updates when lookup tables are changed, by processing only the affected projects and currencies
    • Significantly improved performance and responsiveness for scenarios where a Cost Node is deleted on a site with a large number of projects and significant volumes of financial information
    • Improved reliability of mapping Relationships to Lookup Tables when using the Bulk Import solution starter or the Delete Enterprise Projects functionality
    • Resolved timeout issue when using the Close and Create Financial Status Periods page with large numbers of projects
    • Addressed error on deleting a Node from and Enterprise Financial Type when no financial Start and End dates were defined
    • Resolved memory leaks when using the Actuals web part with Budget fields visible
    • Addressed reliability issues with Queue items getting stuck when specific jobs are running for more than 60 minutes
    • Addressed issues with empty periods (null) not being overwritten when using the Copy Actuals To Forecast transition
    • Improved reliability of the Retry action for long-running in-progress and completed Queue items
    • Significantly improved performance and reliability for the item swapper control
    • Addressed performance issue when building a reporting cube on an instance with a large number of users defined
    • Addressed reliability issues when bulk-restarting workflows for a large number of projects
    • Addressed reliability issues with deleting cost centers while a Cost Center Template Update Queue job is waiting or running
  • Other
    • Fixed errors on updating Custom Field mappings and Relationships when users didn’t have the Manage Enterprise Custom Fields permission. The permission is no longer required for these operations
    • Addressed issue with individual accounts not being visible as Change Request approvers if the current user did not have the Manage User and Groups permission
    • Improved usability on creating a Change Request by no longer closing the dialog on Save and allowing for a 1-step submission
    • Addressed issue on importing settings for Enterprise Financial Types
    • Added an explicit strong warning when changing the Calendar Type under Global Options
    • Values for some nodes from past or read-only financial periods are no longer overwritten with null when values are added to specific cost levels for editable periods
    • Project Names are no longer trimmed to 50 characters for reporting (kept at 255 characters)
    • Export to Excel no longer fails for projects with long names (more than 50 characters)
    • Improved end-user messages when the financial timeline is changed for a project in execution, including steps for addressing the issue
    • Fixed issue with financial data aggregation when names of projects used in the aggregation included commas (,)

To download, visit www.umt360 and log into the partner/customer portal.

Visit the version history page for version details.