Hello
I read in documenation that (( Generic Start Event , This generic start event lets a user start the process manually ))
How to start process only in Business process without any relation to workflow ( ignore workflow)
give example ?
regard
Hello
I read in documenation that (( Generic Start Event , This generic start event lets a user start the process manually ))
How to start process only in Business process without any relation to workflow ( ignore workflow)
give example ?
regard
Hello Christopher
Thank you very much for this explanation
Every thing now is clear
I think ( my opinion ) , this way of restart process manually is not easy for end user to remmber
Most cases , process start relate with eForm or Timer for example
Regard
Maybe it is different in cloud versus on prem - but in my on prem environment, the users can still start those from the “Start Process” menu, just like they can with processes that use the Message Start Event. It just starts the process instead of providing a form to submit before it starts.
This is especially useful if I need to run a workflow or other activity prior to providing form tasks back to the user.
Hello Matthew
Thank you for this explination
I have cloud only
Can you put images show me this point in prem.
Regard
I don't know how much on prem and cloud differ, but on prem, we have this Start Process menu that includes every published process that the user has permissions to.
It also includes ones who have a regular start event instead of a Message start event.
The only thing the user sees that is different, is when they click the Start button for the process.
They will get a warning message that the process does not require a form submission and will be started immediately.
Since most of our processes do not work this way, we made sure the staff who use the couple that are set-up to be started this way were trained to understand the difference and what this message meant.
Thanks Matthew
Hi Omar,
I believe that Generic Start Events can only start Business Processes manually :
There's some additional documentation here: https://doc.laserfiche.com/laserfiche.documentation/en-us/Subsystems/ProcessAutomation/Content/Forms-Current/Building-a-Process.htm
Otherwise:
Message Start Events can kick off Business Processes by a form (found in Submit Forms)
Timer Start Events can kick off Business Processes on a certain schedule
Error Start Events can kick off Business Processes by Error code
(Global) Starting Events in the Process Automation picker can invoke Workflows, and Workflows can invoke Business Processes. That's where the confusion may be.
Hope that helps.
Hello
Thank you for your replay , but following point to explain my case clearly
1- Iam focusing on Business process only
2- I download sample ( Building Inspection ) , from Solution Templates \ Facilities Management
3- This process has first element is ( Start Event )
4- After publish it , I return back to my repository ( Folder structure)
5- How to start this process , since there is no eForm to fill at beginning
I try to check in all documentation , but there is no any clear answer about this point ( Business process only)
Regard
Thanks for specifying the template. The only way to start this Business Process is to use the Play Button:
If you press Play, the process will begin with the Form:
This is only possible to start for Users that have the privileges to design Business Processes.
** You can edit this so that it starts with the Form: **
Make sure you delete the "Start Event" and "Building Inspector" User Task and then edit the "Details" accordingly:
Enable the process (Process Status), determine who can start the form (maybe allow specific users and just allow yourself to test).
Now, any user you grant access to can start the Form:
You will have to make more modifications to this process to get the form to save to your repository and act appropriately, but hopefully this gives you a good starting point to test.
Usually the easiest way to test is to assign User tasks to the "Process Initiator", which will just bounce the tasks back to whoever starts the form. (If you specify the Users to only you, it will bounce back to you)