You are viewing limited content. For full access, please sign in.

Question

Question

Task due date format issue

asked on August 2, 2016

Hello, Based in Australia we use dd/MM/yyyy so i have gone through the process of regional setting etc to make sure throughout processes this is realised. Yesterday I struck an issue when using the task due date set from the task start date. i.e task start is 02/09/2016 (2nd august 2016) the due date 24 hrs later comes up in the task as due 09/02/2016 (9th Feb 2016) . any thoughts?

thanks

Grant

Capture.PNG
Capture.PNG (4.08 KB)
0 0

Answer

SELECTED ANSWER
replied on August 8, 2016

Hello Rui, we updated from 10 to 10.1 and now fixed. Thanks for your assistance

0 0

Replies

replied on August 3, 2016

Hi Grant,

You may have checked this already, but I've run into this with browser settings having US English as the default or top option: "Settings - Advanced - Language and input settings" in Chrome, and "Options - Content - Languages" in Firefox.

Cheers,

Mike

1 0
replied on August 5, 2016

Hi Grant,

I tried changing server region and browser display language to English(Australia), and changing routing service configure date/time format to "dd/MM/yyyy", but I can't reproduce the issue. The due date is correct:

Is there any other setting you've made? 

0 0
replied on August 5, 2016

Hi Rui, thanks for replying , no we are not getting that outcome , we have lodged a ticket as we have gone through all the settings described , it sets the task at correct date but due date is an issue . I.e task start date is 05/08/2016 if you set due date + 1 it comes up as 09/05/2016? So it interprets 05/08 as 8th may 

0 0
replied on August 5, 2016

We checked service accounts/ sql settings 

workflow/forms/lf server 

all have our region. We set the config file in routing service . 

0 0
replied on August 8, 2016

I tried again with updating the region of sql server, but still could not reproduce the issue.

Could you please open a support case on this issue? Thanks.

0 0
SELECTED ANSWER
replied on August 8, 2016

Hello Rui, we updated from 10 to 10.1 and now fixed. Thanks for your assistance

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.