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

Question

Question

_initiated_time out of sync in forms business process?

asked on July 11, 2017 Show version history

Hello, 

We are using Forms 9.2 and are running into a problem with saving forms to the repository to be picked up by our workflows. We have a business process that has several steps where we save a form to a repository. Each time we are saving a form to the repository, we are including /dataset/_initiated_time as part of the folder path. 

 

Oddly, every now and then, the first form in the process will save for a given datetimestamp; but then the subsequent forms save with a datetimestamp one second later even though we are using the "_initiated_time" variable consistently within the business process.

This obviously causes issues on the workflow end since the workflow looks for that original datetimestamp for all forms needed in the workflow. So it finds the first form; but then doesn't see the subsequent ones (in a wait activity).

 

I've tried to dig into the backend LFForms database for clues; and have only found the _initiated_time value for the datetimestamp  (which we store in cf_bp_main_instances.start_date) that is one second later in the cf_bp_main_instances table. I haven't found that original datetimestamp anywhere yet in the LFForms db.

 

Is this some type of bug in Forms for 9.2?

 

Thanks,

Julie

0 0

Replies

replied on July 12, 2017

Hi Julie,

I was not able to reproduce the issue in Forms 9.2. I tried a process like this and used initiated time in both save to repository services, and the time was consistent:

Can you open a support case and provide the process to us so we can see whether we can reproduce the issue?

0 0
replied on July 12, 2017

Hi,

It doesn't happen the majority of the time, so reproducing I guess will be tricky. I was hoping there was some fix or something I could update. How do you go about opening a support case?

 

Thanks,

Julie

0 0
replied on July 12, 2017

This is not a known issue so we need to first find the cause of the issue. Please contact your VAR for opening a support case.

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

Sign in to reply to this post.