Hi all,
I'm hoping I can get help. I'm having trouble getting on-prem forms to display in the cloud.
I have some forms that are scheduled to start every day through a workflow.
The forms that start with Start Event are not available to be started like on-prem. The forms that start with a Message Start Event display in the Submit Forms homepage (https://app.laserfiche.com/forms/)
In the cloud, the Access Rights window is gone. From what I read in the post, we are supposed to create a project, add members and the business processes needed. I have done this and tested it with a coworker who has the Viewer role and a Participant license. It doesn't show up. In the post I referenced, a user asks a year ago if only full users can effectively start forms inside a project, but never got an acknowledgement or reply.
To elaborate more on why some forms HAVE to start with the Start Event is due to the due date/time having no actual impact in the business process's workflow(Unless this has changed). So, I had to create a workflow that runs a timer till 11:59pm, then a Signal Throw Event will be sent if data wasn't entered. A Boundary Signal Event will catch it and then interrupts the activity. this allows the form to go to the next step. This also allows at most two instances to exist for a daily form: yesterday's and today's.
So, my question is how can I get forms that do not have a Message Start Event to show up in LF Cloud's Forms? If it is not possible, what are some workarounds?
Question
Question
LF Cloud: Allow BPs with Start Events to be started by users
Replies
Hi Kevin,
Sorry, if I didn't explain it well. I will try to elaborate on it more. I have a workflow that is scheduled to start every day at midnight. The workflow invokes business processes by assigning values to the forms. One of the values is used to assign the BP to a team based on variables inside a User Task. The other value is the equipment ID or serial number.
The business processes that are started every day look similar to this:
I use the Start Event so I can get the form, inside the Daily Check (User Task), to be assigned to the correct team each day. Our daily forms can be entered at most, twice. For example, an equipment failed the first check, so we have to log and save the failed form. Then, we have to start the business process and do a retry. On-prem, our Participant licensed users can start the business process without issue by going to the Start Process tab and clicking Start. On the cloud, I cannot get the forms to be available to start if they have the Start Event first instead of the Message Start Event.
With Start Event, I can also start a Signal Catch Event the moment the BP is started. This is helpful as I also start a workflow that helps set a deadline no matter if it is started by workflow or user.
This is the Deadline Workflow:
I had to create and use this workflow as the Due Date in the User Task, doesn't actually interrupt the the task and proceed it to the next step in the workflow. Instances of the BP will start to accumulate. Also, because it's a daily form, being dependent on end users to do things on time causes more problems. So I have the BP to have at most two instances of an equipment or SN's form: yesterday's(for review) and today's. On-prem, staff do have the option to start the forms, but because I have automated the forms to auto-populate into their Team Tasks, we don't run into duplicates and I have logic that checks it as well.
I hope this explanation helps and if there is constructive feedback on how to do what I want, but in a different way, I am happy to learn. 
Hi Jasciel,
Can you go into more detail about the reason you have to use a Start Event in this Forms Process? I wasn't quite following the reasons why you had to use one, instead of Message Start event if you wanted the start to be manual, or a timer start event if it should be automatically started every day.
-Kevin