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

Question

Question

Can forms processes be halted?

asked on May 21, 2018

Hi All,

 

Was wondering if this can be achieved within Forms?

We have a client requirement where the main form (Process) kick starts new processes via LF Workflow based on selections. We would like to know if it is possible to have a HALT option on all processes? As in, it is possible for a user to HALT the process? which will then halt all other processes initially created until further notice? 

 

If so, how can this be achieved? 

 

Thank you

Ziad

 

 

0 0

Replies

replied on May 23, 2018

Can you use a catch/throw activity in Forms? I do something similar where I have a branch of the process continually loop every x days and run a workflow to check the status elsewhere. If the status is changed then a variable is populated in the form by workflow. That variable will determine how an Exclusive Gateway flows. If the variable is set and the path changes, a throw event occurs which is caught at the current step and ends it. This means you need a catch on every step.

Hope this helps.

0 0
replied on May 23, 2018

Thanks Chris, 

 

I believe what you have added here will be very helpful for us to try achieve what we are after with a few other things we are trying to do in the background of the SQL DB's. 

 

Thanks again for your assistance, 

Ziad

1 0
replied on May 23, 2018

Hi Ziad,

 

Let me rephrase what you want first, could you confirm I am understanding you correctly?

 

You have a process, let's call it P1, which is started by a form (Message Start Event), and inside the process there is at least one Workflow service. Inside the workflow, it will start other forms processes, let's call them as a group P2-Pn. 

You want to :

1. stop the initial process instance you started of P1.

2. stop the process instances started by P1's workflow services of P2-Pn.

 

If so, probably the below steps could help you achieve it. But be aware that once a process instance is cancelled, it cannot be resumed. I assume you use Forms 10.3, let me know if this is not the case.

1. first we will stop the instance from P1:

      (1) go to the monitoring page of P1 through the icon in process diagram of P1.

     (2) select the running instance you would like to stop, and click on the stop button to stop it.

2. Second step is to stop the instances started by workflow in P1.

(1) go to Reports tab, on Custom Reports, click on Create New, click Table, select all the processes that could be triggered by the workflow services in P1. Then click Select.

(2) on the configuration page, click on Filters, then add the status to be running (I added the inprogress with suspended tasks, if you only want to stop the running instances, remove the second one), and the click set filters. Finally click on Create.

(3) on the generated instances report, do the same as (2) from step 1: select the instances, and stop them.

 

The risk from this method is : from P2-Pn, if you have other process excluding P1 which also contains a workflow service who starts one of the processes in P2-Pn, you will also stop these instances. This method is just to group all the instances you want and stop them with bulk actions.

 

0 0
replied on May 23, 2018

Thanks Ming, 

 

We were wondering if it would be possible for this to be done based on a metadata entry change within Laserfiche. 

 

As in, more automated then for the user to find the processes and halt them. 

We have started testing with SQL databases within the processes based on its ID, something in the lines of:

 

  1. Fill out initial “Whole Job” Form
  2. This kicks off a workflow to start a business process and also saves a hidden copy to the repository
  3. The form saved to repository has 4 metadata fields

 

  • Status (In Progress = 1, On Hold = 2, Contractor Alerted = 3, Resume = 4)
  • Contractor Email Address
  • Due Date
  • Address

 

  1. When Initial form is updated inside of Forms  and “Halt Jobs / On Hold” is selected, run a workflow which updates the metadata for the hidden forms in repository (this is by using the LF SQL tables) which is based on the address and confirms the status is set to 1.
  2. Create a workflow which is triggered by Metadata change on this hidden folder (containing the work orders) – Workflow checks if Status = 2 (On Hold), if so, sends an email to email address retrieved from the metadata and then set’s the status to 3.

 

Hope this helps, 

 

Thank you

Ziad

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

Sign in to reply to this post.