When you're using CityGrows to create a complex workflow, there are times when there are whole workflows that may be conditionally or always required. They're too complex to have as conditional steps, or require a specific output document that's separate from your main document. These situations are a good use of the Subprocess feature.
Here's a video overview of how it works:
Here are some common use cases for subprocesses:
Building permit may require separate plumbing permit
Zoning application may require public hearing for some projects
Business license may require separate liquor license
Here are some step by step screen shots:
First, set up two workflows, one each for the main and one for the subprocess.
From the main process edit screen, select Power-Ups / Subprocesses
You'll select a specific workflow that will be the subprocess (both workflows must be on the same Team). You may select whether or not the applicant can link a process they've already started/ completed (if Allow link existing is set to on, they are able to). You'll also select whether the subprocess is always or conditionally required. The conditional setup works the same way as our Logic configuration.
When you hit save, the two workflows will be linked.
Here's an example of how the required Subprocess will appear to an applicant (in this view, the green check in the Additional Requirements section indicates the subprocess has been completed. The Additional Document Upload workflow is a subprocess of the main Sample license for subprocess demonstration workflow in the example below.