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

Question

Question

Workflow dates from forms cannot be parsed back into forms.

asked on June 17, 2018

Hi all,

 

A client of ours is filling out a Job date on an initial form. This form is then saved and the metadata captured into the repository for later use. 

 

The client will then mark the job as complete which kicks off a new workflow. This new workflow retrieves the original form data stored (from the initially saved metadata) and invokes a new business process using some of the data it retrieves.

 

The issue I'm having is when workflow attempts to fill the date variable out in the new form, it doesn't fill it out at all. When checking the workflow web designer, the error " Message:The value '30/06/2018' could not be parsed as a date.[Field=Date_of_Clean]"

 

Couple of information points:

 

  • Both date formats on both processes are set to dd/MM/yyyy
  • Region settings set to Australia on administrator and local system
  • Region settings set to Australia on google chrome.

 

I attempted to create a new field in the form which was set to MM/dd/yyyy and under it's advanced settings of the field, told it to = the other field variable (which was set to dd/MM/yyyy) 

This worked on the form itself and automatically converted the two fields, to show both formats. From this, I attempted to save the form to the repository and capture the new date field as MM/dd/yyyy in the metadata, however, this automatically converted the metadata to dd/MM/yyyy (even after changing the field format of the metadata to custom and changing it to display MM/dd/yyyy)

 

One other point to note, is in the workflow web designer, the dates shown for all activities (e.g. Workflow start date) display in MM/dd/yyyy.

 

Any help would be appreciated.

 

Windows Server 2012 

Forms Version 10.2.1.246.

0 0

Answer

SELECTED ANSWER
replied on June 18, 2018

What is the version of your Workflow Server? Does its service run as local system or some other user?

The Designer uses the Windows date format for the currently logged in user.

0 0
replied on June 18, 2018

Thanks Miruna,

 

The Service was running as the administrator account (which was set to the correct region etc) however, changing to the local system account seemed to fix the problem.

0 0

Replies

replied on June 18, 2018

Hi Shane,

What I have done in the past to make sure that this doesn't happen is format the metadata date token to "yyyy-MM-dd". Forms should pick it up and then convert it back to what the required display format is on the form.

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

Sign in to reply to this post.