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

Question

Question

Laserfiche Forms Upgrade - Steps Missing From Workflow

asked on February 19, 2020

I have recently upgraded one of my test environments to Laserfiche Forms 10.3. After the upgrade, the subflow for my forms Workflow process renders steps off screen.

 

I validated the workflow. 

I republished the workflow.

I auto-spaced the workflow.

I ensured I ran the upgrade database option from the forms config website.

Even after all of this the workflow still renders with missing steps.

I'm posting this to reveal my solution to this problem.

0 0

Answer

SELECTED ANSWER
replied on February 19, 2020

So what finally resolved the issue?

 

TLDR;

the style_json field in the cf_bp_steps table had a negative X value. Change it to a positive value.

Long Winded Monologue

 

Over the last few years, I have spent extensive time digging through the database tables to gain a deeper understanding of how Laserfiche works. In this particular instance, this upfront work paid off for me.

 

Every workflow persists the details for workflow steps in the lfforms.dbo.cf_bp_steps table. The table maintains a field titled style_json. I observed after the upgrade the steps which were not being displayed all possessed a negative X coordinate value. I ran a manual update (I always recommend backing up and using checkpoints) to update the field for the records with a negative value to a positive value. After the update, I refreshed the GUI for the forms workflow and the missing steps were rendered on the screen. 

 

The following is an example of the query I executed:


begin tran sp1


update lfforms.dbo.cf_bp_steps
-- original value, notice the x value is negative
--set style_json = '{"x":-160,"y":424}'
-- use this value after upgrade
set style_json = '{"x":160,"y":500}'
where process_id = #
and step_id = #

-- dont forget to commit or rollback based on your results
rollback tran sp1
commit tran sp1

I hope this saves someone some trouble in the future.

 

Skip Cherniss

2 0

Replies

replied on February 19, 2020

Which version of Forms are you using before upgrade to Forms 10.3?

0 0
replied on February 20, 2020

9.3

0 0
replied on February 21, 2020

Hi,

 

We can reproduce the issue, and have filed bug 227293 for it. This bug will be fixed in next release.

 

Thanks

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

Sign in to reply to this post.