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

Question

Question

Trouble with Setting a Business Process Variable - Stuck in Processing, Had Been Working

asked on November 10, 2021

I have a process which I have been testing and it has been working perfectly.  Yesterday, when I uploaded the existing cases into my new form process, I found that all entries are failing to complete the first workflow step.  I cleared all the imported records and attempted to start the process with a manual form submission and that is also now failing. I discovered the failures started sometime on Monday afternoon.

This is the step which is not working along with the workflow which it is calling (neither is complex).  I KNOW that everything would say I must have changed something somewhere, but if I did, it was purely unintentional and I wasn't actually working on the process at all that day, so I am lost.  No error messages, the task just stays in a perpetual processing state.



0 0

Replies

replied on November 10, 2021

I just had this same issue this morning on our Laserfiche 11 test environment using a workflow activity that contains a "Set Business Process Variables". The workflow completes according to Workflow Logs, but the signal to "release" the workflow activity in forms never makes it back so it remains "In Progress". 

I came to the forum here to see if this is a known issue or bug.. I'll report back here if I find a workaround or solution.

0 0
replied on November 10, 2021

@████████

I was able to resolve the issue at my end by removing any variables under [Starting Variable Values] that were being set to blank using %(DB.NULL). Not sure why, but it looks like that special variable causes the Set Business Process Variables to hang. You may want to also try removing references to system variables, and use Tokens only. Or, alternatively, bridge a system variable to a token and then use the token instead. 

Hope this helps!

0 0
replied on November 10, 2021

That is part of what is so frustrating.  I only have the ONE variable that I am even working with.  I will try to use a token again, but I am very certain I did try that earlier today.  I'll give it another shot though.

0 0
replied on November 10, 2021

Yeah I noticed that in your original screenshot which is why I mentioned trying to bridge it using a token, in case it was an issue/bug setting special/system variables directly using the Set Business Process Variables activity.

Let me know if you need an example of how to bridge a variable using a token and I can post a screenshot

Regardless, best of luck, hope you get it working!

0 0
replied on November 11, 2021

I have had that a few times.  Its been an ongoing random thing since before 11.  I would start a support case.  We have had it in the past and were given an extensive SQL script to run where we had to enter the instance ID and it went and updated all the forms variables to get it to update correctly.  Not sure if that is still done but it was the only want to continue a pretty extensive process.

0 0
replied on November 11, 2021

Kris, I am not sure what you mean by bridging unless you mean creating a token that is populated with the submission ID from the input parameters of the form.  Then using the token to update the business process variables.  I have already tried that.  Actually, on every workflow log and in every attempted means of updating the variable, the output is logged as the accurate number.
 

Chris, I have a support call at 1 today.  This has just been blowing my mind.

0 0
replied on November 11, 2021

Hi Christa, yep, that's bridging. Sorry to hear it didn't work. 

Please do report back what you hear from LF - I'd be interested to know if it is a bug or there is a workaround just in case I come across it happening again. 

Good luck!

0 0
replied on November 11, 2021

Well, whatever I am dealing with is bigger than just my form.  A bit ago I created a whole new form (2 fields) and created a new workflow to update the business process variables.  I cannot update the process variables through a created token, hard coded value, system variable or any other means.  They are also suspending.  However, in all cases, the value is showing accurately in the workflow log.  Heh.  I even made a sql table with only a PK and entry value where i can write a unique name to the table then query for the PK of that entry to plug that in as a sequential ID.  STILL no dice on any of it.

0 0
replied on October 31, 2022 Show version history

Hello All,

I am facing the same issues that "Set Business Process Variables" activity could not able to set forms variables at first time but when we call the same workflow it is run as expected.

Can you please provide me some help for the same.

Thanks,

Pratik

 

 

Workflow.png
Process Diagram.png
Workflow.png (28.46 KB)
0 0
replied on October 31, 2022

Pratik,

This is STILL an ongoing case with LF support.  It has been open for several months now.  The last I heard, they think it might be a certificate issue on the LF Forms or Workflow server which is preventing workflow from communication into LF Forms as a security measure.  I haven't heard anything further and that was several weeks ago.

I know my IT department is working on getting updates in place or at least they were.  If/when I get resolution, I will let you know!

Christa

0 0
replied on November 1, 2022

yes still I am waiting for answers from support team.

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

Sign in to reply to this post.