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

Question

Question

invoke business process values doesn't use starting form setup

asked on September 12, 2024

I have a process where I am trying to use one form to invoke many of another form.  On the starting form that is being invoked, there's only two fields that need to be input, but there's a significant amount of setup happening in the background based on those two fields, including setting default values, calculations, and database lookups.  

When I invoke the business process, only the values that were input into the variables show up in the invoked form, none of the starting form's setup comes through. Do I have to mirror all the data setup that happens in the starting form using workflow tokens/variables?  Is there a way to invoke the form to get all the starting form set up pieces without going through duplicative effort?

 

Any insight is appreciated.

 

On Prem Laserfiche Forms 11.0.2311.50553

On Prem Workflow Designer 11.0.2206.826

0 0

Answer

SELECTED ANSWER
replied on September 12, 2024 Show version history

You will need to setup the Starting Variable Values if you want to pass those values to the invoked form. I usually proceed the Invoke Business Process activity with a Retrieve Business Process Variables activity and grab the variables I need.

3 0
replied on September 12, 2024 Show version history

As Craig points out, things like calculations, lookups, JavaScript, etc., are basically client-side functions of the form meaning they need a browser session to run.

If you want the data in from the start, I frequently do the same as Craig, or for data I can safely get later I'll add lookups and calculations to that first user task.

Another tip is to make use of the NULL format for tokens if you need to set a truly null value instead of an empty string.

%(Token#NULL#)

Token Formatting--Empty Tokens (laserfiche.com)

It's not always relevant, but there can be a difference in behavior between NULL and empty/blank when it comes to things like default values set on the next form.

0 0
replied on September 12, 2024

This is what I expected , but I'm a bit disappointed that I can't mimic the client side functionality with workflow.  The lack of that ability makes the Invoke Business Process function quite limited.

Unfortunately, I've built a rather large form, and prefilling the first form isn't possible.  I'm dealing with a list of dozens or hundreds, each needing a hundred populated values or so.

The NULL token tip is on point, I've run into that a few times, never figured out how to solve it. 

I'll probably just send an email with a parameterized url instead of invoking the form, if I can get business to approve the methodology.

Thanks for the input!

0 0

Replies

replied on September 12, 2024

Are you immediately saving to the repository, or is the invoked form going to a user task first?

0 0
replied on September 12, 2024

It goes to a user task.

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

Sign in to reply to this post.