Events – Laserfiche Forms has three types of events: start events, intermediate events, and end events. Start events are the mechanism for starting a business process, intermediate events happen during a process, and end events stop a business process after it has finished running. Every process starts with one of the three types of start events.
This generic start event lets a user start the process manually, as opposed to starting it with a form submission. This lets you push content and forms to other users when you want to.
Message Start Event
Message start events start a process when a form is submitted. This is the most commonly used start event in Laserfiche Forms and is useful for capturing information that you can use in a business process. You can also use an HTTP POST request to complete a starting form.
Tip: Select Enable reCAPTCHA to protect your form from spam.
Timer Start Event
Timer start events start a process on a particular date or schedule. Timer start events are useful if you have a process that should automatically start at a certain time or on a certain schedule.
Timer Catch Event
A timer catch event helps adjust the amount of time before a process continues, an activity is escalated, or an alternate path is taken. You can use it as an independent event or attach the event to a user task or sub-process.
Signal Throw and Catch Event
A signal throw event can broadcast a signal that a signal catch event will listen for. Upon receiving the signal, the signal catch event can act on the signal. In BPMN, this is referred to as “throwing” and “catching” a signal.
Example: If a document is routed for review and approval using parallel routing to a manager as well as multiple users and the manager denies the approval, there is no need for the other users in the process to review. An email service task would be included in the routing for other parties notifying them that they no longer need to review and approve the form.
A signal throw event in a process flow broadcasts a signal. The signal catch event listens for the broadcast signal. When the signal is received, the process flow that starts from the signal catch event runs.
Error Start Event
Error start events start a process based on a custom error generated from an error end event. Error start events interrupt all activities in a process.
Error Catch Event
Error catch events can be attached to a sub –process to listen for custom errors generated by an error end event. The error catch event always interrupts the sub-process to which it is attached.
Error End Event
Error end events generate a custom error and then end the current process flow.