- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-08-2016 03:36 AM
In the Service portal when you open a change as an end user, we want to display the field "Planned start date".
There is no issue to display the field in the widget suming up the change, but the valu showing is incorrect.
If the Planned start date is 4 days ago it all show correct
If I change the Planned start date to be 4 days in the future it display the value "just now" which is totally wrong
As you can see the planned start date is 2016-09-12 12:36:56 but the displayed value is transformed into "just now" which is wrong.
Any idea how this can be changed? Seems like there are some automatic function that display all date/time fields as "just now" when they are in the future.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2016 01:14 AM
I raised a ticket to HI on this and their reply is that it's by design.
In my opinion this is a bad design since we can't customize the portal the way we want.
If the creation date would be in the future you have other issues in your instane you need to take care of, not write correcting code for the portal to solve bad data. You should always correct whatever is wrong, not write a new solution and keep the incorrect behaviour.
"Even though in the back-end we can set the data to be in the future, this was a design decision in the service portal in order to avoid showing potentially bad data with future dates, as it doesn't make sense for a Change Request's creation date to be in the future, so the assumption is that the data is wrong. You also still have "planned start date" for future dates."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2016 01:14 AM
I raised a ticket to HI on this and their reply is that it's by design.
In my opinion this is a bad design since we can't customize the portal the way we want.
If the creation date would be in the future you have other issues in your instane you need to take care of, not write correcting code for the portal to solve bad data. You should always correct whatever is wrong, not write a new solution and keep the incorrect behaviour.
"Even though in the back-end we can set the data to be in the future, this was a design decision in the service portal in order to avoid showing potentially bad data with future dates, as it doesn't make sense for a Change Request's creation date to be in the future, so the assumption is that the data is wrong. You also still have "planned start date" for future dates."

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2016 03:10 AM
Ok I got it. Thanks for the clarification.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-20-2017 11:40 PM
Hi Fredrik,
I also have the same requirement to show Date/Time on the portal widgets. Is there any settings or config we can do? OR we need to change all the OOB widgets to custom ones for this small requirement.
Thanks
Rohit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-21-2017 12:03 AM
I haven't seen any configuration for this but haven't looked for it either so they might have changed something.
Otherwise you'll have to manually update all the widgets to show something else.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2017 11:10 AM
Hi , did you end up manually updating the widget? I am encountering the same behavior on another table.