Release 13.3 Updates › Documentation Changes

Documentation Changes

The CA Clarity PPM documentation has been improved with these changes to help you find information faster.

• CA Answer Bar. Quickly find the CA Clarity PPM information you need using the CA Answer Bar (https://enable.ca.com/answers/us/CA-Clarity-PPM). Find the latest “how to” scenario content, discover great insights from CA Support, and more. You’ll spend less time searching and more time focused on getting your job done. Technical content is available for CA Clarity PPM 13.0 and above.
• CA Clarity PPM Cookbook. Select CA Clarity PPM technical content is available on the mobile device platform Flipboard. Watch this video and use the cookbook today. Happy flipping!
  • To add the CA Clarity PPM Cookbook to your RSS feed folder, add this URL: http://cookbooks.ca.com/cacppm/?feed=rss2
  • To view the CA Clarity PPM Cookbook in your browser, rather than the mobile app, access this URL: https://flipboard.com/section/ca-clarity-ppm-cookbook-bgk99n
• Online Help Bookshelf. To help simplify and improve how you find content, the bookshelf available from the product only includes the product documentation. Additional information such as release notes, green books, KB articles, social media, and so forth is available in the On Premise and On Demand bookshelves on CA Support Online.
• New Portfolio Management Scenarios Guide. Provides “how to” scenario content the Portfolio Manager needs.
• New Portlet Reference Guide. Provides a list and details for all out-of-the-box portlets and PMO Accelerator portlets.
• Accelerator, Add-in, and Connector Guides. To help improve how you find content, the release notes for the accelerators, add-ins, and connectors are now found in their associated product guide.
• Basics User Guide and Personalizing CA Clarity User Guide. To help improve how you find content, the content in the Personalizing CA Clarity User Guide is now found in the Basics User Guide.
• Access Rights Reference Guide. To help improve how you find content, the access rights for all the guides are now found in the Access Rights Reference Guide. They are no longer included in the individual guides.
• XML Open Gateway Developer Guide. The element syntax IsComplete and completed were recognized as deprecated forms and are replaced by complete. For example, when true, the optional complete element for the OBSAssocs element indicates that any OBS associations represent a complete replacement as a set. When the value is false, the operation inserts and/or updates any existing OBS associations. Sample content including sample .xsd files may continue to show the old forms. The documentation reflects this recognition of a single standard in topics that include the complete element with the following note:

  Note: Complete replaces deprecated forms completed and IsComplete.

Financial Management

This section provides Financial Management enhancements for Release 13.3.

Inactive Resources in Cost Plan Population

Starting with Release 13.3. information for both active and inactive resources appears in cost plan detail and is used for the rate calculation. The values for resource attributes are pulled for the rate calculation regardless of the active status if the attributes are specified in the resource profile.

For example, if the transaction class is defined for a resource, the resource transaction class appears in the cost plan. The transaction class is used to pull the rate from the rate matrix. Setting the resource to inactive on the general properties page or the financial properties page does not change this behavior.

If a resource has no defined transaction class but the resource has project allocation, ETC, or actuals, the rate is pulled from the rate matrix. The active status does not change this behavior.

Upgrade Action: None

Open Workbench

This section provides Open Workbench enhancements for Release 13.3.

Java Runtime Environment for Open Workbench

Starting with Release 13.3, CA Clarity PPM provides a specific Java Runtime Environment (JRE) for use by Open Workbench (OWB). The JRE is copied to the hard drive in the OWB installation directory on the end-user workstation. The JRE is used specifically for OWB and is independent of the JRE used for the Windows workstation.

OWB uses only the internal JRE version that is provided which we certify to be compatible. This approach eliminates issues that arise when the workstation Windows installation of the JRE is not the correct version or the JRE is missing. An IT department no longer has to update a JRE version when deploying OWB.