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

Question

Question

Process in Laserfiche Forms - Email to Different Users based off of Different Variable

asked on December 18, 2019

Please see screenshot of attached process.

We're having a bit of an issue with early terminations in the process attached. I've recently added the "save to repository" step in hopes that it won't terminate immediately. I know that we have a lot going on here; Does anyone have any suggestions or advice on how to better this? We are just getting started as Laserfiche Forms users and aren't sure if there are proper or standardized ways of making more efficient processes in Forms.

LaserficheProcess.PNG
0 0

Answer

SELECTED ANSWER
replied on December 18, 2019

The default really depends on how your process flows. Sometimes I have an entirely separate default path when I don't want either thing to happen if the values aren't what I expect, but in other cases you might default to the more "common" answer.

It all depends on what could "go wrong" if it defaults to one path or the other. I usually go with the "least destructive" path, for example, defaulting to a rejection path rather than approving something just because it had an unexpected value.

1 0

Replies

replied on December 18, 2019

We would probably need some more details about why the process is terminating. If you go into the instance monitoring, highlight the terminated instance, then click the little clipboard icon near the top right it should give you the actual error message so you can determine what needs to be fixed.

My first suggestion would be to always have a "default" path on your gateways. One of the most common reason for errors in a process design like this is that no valid path could be identified. By setting a default outflow path you ensure that kind of situation will not occur.

For example,

If I have the following outflow paths:

  • If Field1="Yes"
  • If Field2="No"

 

And for whatever reason the process comes through with a value of "Maybe" then it will terminate because it has nowhere to go in the gateway.

Ideally, you should always have at least one default path so that won't happen. You could either add a third branch with a default path that does something entirely different, or just decide which path you'd prefer be taken in an "unexpected" situation and set that as the default.

For example,

  • If Field1="Yes"
  • Default (i.e., any value other than "Yes")
0 0
replied on December 18, 2019

Thank you Jason!

I was looking over the Logic that I put in and made a change- Previously, the "No" section had "or" instead of "and". We are testing it currently!

 

Should the most common answer be the Default?

InkedNotificationProcess.jpg
0 0
SELECTED ANSWER
replied on December 18, 2019

The default really depends on how your process flows. Sometimes I have an entirely separate default path when I don't want either thing to happen if the values aren't what I expect, but in other cases you might default to the more "common" answer.

It all depends on what could "go wrong" if it defaults to one path or the other. I usually go with the "least destructive" path, for example, defaulting to a rejection path rather than approving something just because it had an unexpected value.

1 0
replied on December 18, 2019

Perfect!

The logic was incorrect as well; I believe we're going to opt to putting the "no" as default. Thank you again for your help!!

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

Sign in to reply to this post.