Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

7
Replies
853
Views
ParidhiS Member since 2015 2 posts
Mphasis
Posted: Jan 25, 2018
Last activity: Sep 13, 2018
Closed
Solved

Using Field level auditing wizard for date property, in history it shows in GMT, how to use dateformat

Hi,

I am using field level auditing wizard for one of the date property, In the history it shows the date in GMT. How can I format the date and where exactly.

e.g

If I am choosing a date 1/26/2018

it is printing :

Data field EndeIstTechnicalDate manually changed from null to '20180125T230000.000 GMT'

***Edited by Moderator Marissa to update categories***

To see attachments, please log in.
Low-Code App Development
User Experience

Posted: 7 years ago

I would try to reverse engineer the history table to understand what, if any, rules are available to customize. You may be able to apply a datetime control or other formatting options, depending on what you find.

To see attachments, please log in.
Posted: 6 years ago

Hi,

We had a similar issue, where I applied the pxDateTime control to the parameter of a field value.  While the format displays in the proper locale's structure (dd/MM/yyyy hh:mm:ss) instead of the ugly Java GMT timestamp, it is not converting to the right TIME ZONE first.

So using example timestamp: '20180125T010100.000 GMT' passed in as a parameter to a field value, would display as '25/01/2018 01:01:00 AM", which is an acceptable structure, but I expect it to display in Eastern Standard Time, which actually changes the calendar date since it is 5 hours behind, so it should actually show 24/01/2018 08:01:00 PM".

What is strange is that the exact same control, used in any other UI section, displays my expected format in the proper time zone.  Just not in the parameters of field values.

Suggestions?

 

To see attachments, please log in.
Posted: 6 years ago

Used the below control to address the issue. Comments appreciated on how to further improve this control to remove hard coded values:

<%
ClipboardProperty curProp = tools.getActive();
String propvalue = tools.getActiveValue();
 
boolean value = pega_rules_string.contains(propvalue,"GMT");
 
 
if (value==true && curProp.size() == 23) 
 
  {
String sDatetime="";
String type = tools.getParamValue("DateTimeFormat");
String strTimeZone = tools.findPage("pxRequestor").getString(".pyUseTimeZone");
 
sDatetime = PRDateFormat.format(null, strTimeZone, PRDateFormat.DEFAULT_DATETIME_DEFAULT, curProp.toDate()); 
 
tools.putSaveValue("result",sDatetime); 
    }
else {
tools.putSaveValue("result",tools.getActiveValue()); 
      }
%>
<pega:reference name="$save(result)" />

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice