Hi,
Is there a way to set security within Workflow where a can open and execute a workflow but not be able to edit , publish or delete that workflow?
Thanks.
If you make the workflow a Business Process, then a user can start the workflow.
Craig is right on his response. Making the workflow a business process will allow a user to kick of a workflow from the repository or to be kicked off by a form.
If the workflow is associated with the repository, make sure to setup security to the business process, if only certain users should be able to run the WF.
If the workflow is not associated with the repository, you can give access to a form to trigger the workflow to run after a submission.
Hi,
Thanks for your reply.
I guess I was not clear in my original request. We execute workflows from Workflow Designer for support purposes where a particular workflow, whether on a schedule or rule, has failed to execute successfully. Not all of these workflows run against a document such that we can create a business process and run them from the repository.
Having said this, the Forms idea is possibly one that could work, where we could list all the workflows and run them from there, mimicking Workflow Designer for executing purposes.
Using forms to select which WFs to run would be the only way to add security so that the workflow itself cannot be edited.
Workflow security rights do not cover this scenario. A user is either an editor (who can modify and run the workflow) or a viewer (who can view it but not run it.
Craig and Angela's solution is still the right way to go. If the workflow does not run on a document, then it wouldn't matter what what document is selected in the repository when the user triggers the Laserfiche business process. And Laserfiche business process security lets you further specify this users are allowed to start it.
Thank you for confirming. Much appreciated.
Forms or BP maybe the way to go, or perhaps use Workflow API?
Workflow API is subject to Workflow access rights, so that's not an option. I would go the route of Laserfiche business processes because that will preserve info on who stated the workflow if you ever need for troubleshooting.
OK thank you!