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

Question

Question

Forms - Timer Catch on user task - retain lookup values if timer runs

asked on July 19, 2024 Show version history

Hello,

I have a Forms process where a user submits a form initially, and then a subsequent user task that gets assigned to someone else has a series of fields that are filled by lookup rules and calculations. This user task has a timer catch on it, where if the task isn't completed within a certain amount of time, it just skips this user task and moves on to the next step. This all works fine.

However, the form fields populated by the lookup rules contain data that gets written to a SQL table for reporting later. If the timer catch event runs and the user task isn't completed by the user, the these form fields are empty. Which makes sense to me - they wouldn't populate unless the form was opened and the fields were given the opportunity to populate.

There is no input required by the user at this step - the lookups and calculations populate based on the data filled out by the user who started the process. I'm thinking I need to have these same lookups occur on the starting form and just hide these fields from the initial user - that way the form is submitted with those values so I have them if the next user task expires and doesn't get completed. Is that the best method for something like this?

Thanks!

0 0

Answer

SELECTED ANSWER
replied on July 19, 2024

Jacob, for me it would depend on the data that is being returned by the lookups. If the data is sensitive, you may not want that data to be pulled back during the starting form since it could be accessed using Dev Tools once the lookups have completed. If that is the case, you could kick off a Laserfiche Workflow that performs the lookups for you and then sends the values back to Forms instance so they are populated.

If you aren't working with sensitive data, then adding the lookups to the starting form should work.

2 0
replied on July 19, 2024

Makes sense. The data isn't necessarily sensitive - it's just that the first submitter doesn't need to see it/scroll past it. I think I have this working. 

Thanks for the input!

0 0

Replies

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

Sign in to reply to this post.