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

Question

Question

LF Form %(bp_start_date) token showing wrong....

Workflow Laserfiche Forms Version 9 Business Processes
Updated October 23, 2014
asked on October 21, 2014

I have a form that when finished with the process, initiates a WF. This workflow processes the stored files and uploads some of the information of the form to an external DB for use elsewhere.

 

For tracking purposes, we want to keep track of when the initial form was submitted, but when I track tokens, we find that the time is 4 hours ahead of the actual time it is supposed to be. We noticed this after testing the solution and finding the time to be off when it was sent to the DB. The token %(bp_start_date) is saying 8:05:07 PM, the %(bp_start_date_utc) is saying 12:05:07 AM, but the actual time it should have is 4:05:07 PM. The servers for the Forms Service, SQL DB, and Workflow Server are all configured with the proper times, so I do not know why this is happening.

 

Please note: I have removed the date from the values I am indicating for these tokens to save space and avoid confusion. The UTC date was indicating a day forward from the current date since it went past 12 AM

0 0

Answer

SELECTED ANSWER
replied on October 23, 2014

It appears the start date token from the original submission always is accurate. I have added a Retrieve Laserfiche Content activity to my workflow that takes in that information so this is my solution for now.

0 0

Replies

replied on October 21, 2014

Are the Forms Server and the Workflow Server in the same timezone (EDT i assume given the offset from UTC)?

0 0
replied on October 21, 2014

Yes, they are both set for the same time zone. The %(starting_datetime) token for the workflow is showing 4:05:12 PM in this instance, which would be accurate for when this workflow began. 

 

For %(submission_timestamps_utc) and %(submissions_timestamps), they both are saying 8:05:07 PM (in this test instance, we only had 1 step to the process, a simple submission, so the start and end time are identical, as well as the time of start and the time of the latest submission. This is not always going to be the case though, so these tokens are only being pointed out for being odd and not expected).

0 0
View 4 previous replies
replied on October 21, 2014

It looks like a conversion bug on the Workflow Server. We'll look into it some more.

0 0
replied on October 21, 2014

How should we fix this then? or even correct it for now?

0 0
replied on October 21, 2014

For now, you could run the token through a Date Token Calculator and subtract 4 hours.

0 0
replied on October 21, 2014

What tokens might I use to test and then calculate the offset, so that I can make it a conditional sequence for the calculations to be performed, this way once the fix is made I do not need to immediately reverse this customization?

0 0
replied on October 21, 2014

Does the Forms process call into Workflow immediately after starting? I'd check if the hour in the start time is 4 hours off from the hour in the %Time) token since the 2 times should be within a few seconds of each other.

0 0
replied on October 21, 2014

it runs at the end, which means if the process only has 1 submission, that works, but what about if their are two submissions, one which is a few days later? that is something that can happen in the process modeler. 

0 0
replied on October 22, 2014

Any further recommendations? 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...