Building Workflows Best Practices

Back to Best Practices

1. Keep workflows less than 10 Manual steps and connect workflows. This will make it easier if you need to update workflows and allows for more reusability of workflow components.

2. Use Sub-Processes and then one update will update everywhere it is used.

3. Use Reject (which stops workflow), Not Approved (which sends back to an early step with a message), or Approve.

4. Emails – can be configured to allow a reply to approve workflow.

5. All workflows should have an output document that is saved with the content as audit for process.

6. All IFS Development Workflows for use of Automated Testing can not have manual assignments

7. Versioning in Output Documents have caused issues with finding output docs, it has been best to disable this in both input and output documents

8. All files that get uploaded to a process needs to have a corresponding input document

9. All input and Output documents need to have a proper path designated for saving within the provided document repository

10. Triggers should be specific and functional and written in a way that allows for users and other development teams to utilize that function via 'copy' feature that ProcessMaker

11. Server Setup- see the ProcessMaker wiki for use of server sizing, but more importantly

    1. cron.php needs to be setup in a manner that allows the server to be performant as well as meets the requirements of the users/workflow

    2. env.ini needs to be properly configured, see the ProcessMaker wiki

    3. database drivers- log a ticket with ProcessMaker and get assistance to install