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

Question

Question

How do I get a form to save to a users folder

Forms How To
Updated September 24, 2019
asked on September 24, 2019

So I have a form that requires running input from the user of the form is there a way to have the formed saved to that particular users folder in LF until they have completed the form. More specifically the user has to update the form weekly and then is required to submit the form once the instance is closed typically 45 days after beginning the form.

0 0

Replies

replied on September 24, 2019

Are you talking about a Laserfiche Forms process, or just a form document in the repository? It sounds like you should just have a form task stay in their inbox until the instance is closed.

If you set it to loop back on itself, it will go back to their inbox whenever they make changes, and you can use a timer or signal event to end the task when it comes time to finish the instance.

0 0
replied on September 24, 2019

Unfortunately that won't work. As I have to have supervisors review what has been done on the form. Yes it is a LF form. So basically what will happen Is the worker will initiate the form and then when they update the form the supervisor would be notified in 5 day increments up to 45 days but the worker would need to have access to the form to be able to continue work on the form. At the completion of the assessment (form) the form would need to be saved to the repository. Does that make any more sense?

0 0
replied on September 24, 2019 • Show version history

It should still work if you set up a parallel gateway with each task and signal events.

Each time the form is updated, it would cancel the existing "assessment" task using a signal event and create a new one with the updated data.

Using this approach, there would always be a task for the submitter and a separate task for the approver to review the current state of the form.

For example,

  1. User submits a "starting" form
  2. Parallel gateway
    1. User task is assigned to Submitter
    2. User task is assigned to Approver
  3. Submitter submits an updated form (via the User Task)
    1. Signal Throw event is triggered
    2. Signal Catch event cancels Approver Task
  4. Parallel Gateway
    1. User task is assigned to Submitter
    2. User task is assigned to Approver
  5. Approver "approves" the form
    1. Signal Throw event is triggered
    2. Signal Catch event cancels Submitter Task
  6. End instance 

 

It's not impossible, but trying to go back and forth between Forms and the repository is going to be a lot more difficult than just keeping all the data entry and review/approval in Forms until the entire process is complete.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...