How to ensure CA PPM Jaspersoft Domain Dates to handle all timezone?

Document ID : KB000010060
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

How to ensure CA PPM Jaspersoft Domain Dates to handle all timezone? 

Background:

Out of the box domain based attributes allow date format to be set to mm/dd/yyyy format. However a simple custom domain based attribute does have only mm/dd/yy as an option on reports as well as in the domain designer. 

Environment:
CA PPM 14.2 and above
Instructions:

This is normal behavior, all the OOTB domains' business dates have been manually modified to a different datatype, java.util.Date.

This was done not only for format purposes but also to ensure proper timezone handling.

 

When you create your own domain this doesn't happen. To workaround this, please try the following:

 

  1. Export your custom domain by going to JS Console - Domains - View List - right-click - Export - save it as zip file
  2. Open the zip file and navigate to find the Domain_files, it should look similar to this: resources\organizations\CA\MyFolder\New_Domain_files\
  1. Open the file inside schema.xml.data with a Text Editor
  2. Find the business date fields you need to reset and set them to java.util.Date instead of java.sql.Timestamp

Here is an example:

1.png

Important! Do not set any system dates, only the business dates in CA PPM. Internal dates should remain as timestamp. (Example dw_updated_date should be a timestamp) 

  1. Save and Import the domain back to Jaspersoft via CA PPM Advance reporting