This article explains how to configure and use settings to automate creation of follow-up jobs from cultivation work order outputs. It complements the core cultivation jobs and work orders documentation.
Overview
Automating follow-up jobs streamlines repetitive cultivation workflows (e.g., Cutting → URC), reduces manual data entry, and enforces consistent job setup. By defining an association between an output activity and a default Follow Up Job Type Code plus schemes, the work order output line can pre-fill required values. Optionally, the system can auto-create the follow-up job upon posting.
Goal: When a work order for a selected activity is completed, the output line automatically defaults a Follow Up Job Type Code and related schemes so users only enter Output Qty and Bin, then create (or auto-create) the follow-up job.
Key Concepts
Cultivation Activity (Output): An activity whose completion generates an output line on a work order (e.g., Cutting).
Follow Up Job Type Code: The job type that should be created next (e.g., URC).
Related Schemes: Predefined Activity and Production schemes that standardize downstream job structure and steps.
Auto Create Follow Up (Boolean): Optional setting to automatically create the follow-up job when the output is posted.
Benefits
Consistency: Standardized follow-up jobs and schemes.
Speed: Fewer clicks and less data entry on output lines.
Compliance: Reduces risk of missed downstream steps.
Configuration
Use the following steps to enable automated follow-up jobs. Exact navigation labels may vary by environment; coordinate with your system administrator if you lack permissions.
Define Follow-Up Job Mappings
Create or open the configuration area for Cultivation Settings/Preferences.
Add a mapping that links:
• Activity (Output) → Follow Up Job Type Code (e.g., URC)
• Activity (Output) → Default Activity Scheme for the follow-up job
• Activity (Output) → Default Production Scheme for the follow-up job
Enable Auto-Create (Optional)
Set the boolean “Auto Create Follow Up” for each relevant activity mapping where immediate creation upon posting is desired (e.g., Cutting, New Moms).
If disabled, the system will prefill the output line and allow manual creation with Create Follow Up Job.
Permission and Defaults Review
Ensure users performing postings can view defaulted codes and schemes and have rights to create jobs.
Validate that scheme selections align with your SOPs to avoid mismatched tasks in downstream jobs.
How It Works (End-to-End)
Planner creates a work order for a mapped Activity (Output), e.g., Cutting.
On the output line, the system defaults the Follow Up Job Type Code and pre-populates the related Activity and Production schemes.
Technician enters Output Quantity and Bin Code.
If Auto Create Follow Up is OFF: Technician clicks Create Follow Up Job to generate the next job.
If Auto Create Follow Up is ON: Posting the output automatically creates the follow-up job using the defaulted values.
Configuration Examples
Activity (Output) | Follow Up Job Type Code | Default Schemes (Activity + Production) | Auto Create Follow Up |
|---|---|---|---|
Cutting | URC |
| Enabled |
New Moms | MOM |
| Disabled |
Operational Tips & Best Practices
Pilot first: Enable Auto Create Follow Up only for high-volume, predictable activities; expand after validating outcomes.
Audit defaults periodically: Review scheme applicability as strains, rooms, or SOPs evolve.
Use naming conventions: Keep Job Type Codes and schemes unambiguous for faster technician recognition.
Troubleshooting
Output line not defaulting: Verify mapping exists for the specific Activity (Output) and user has read access to schemes.
Follow-up job not created on post: Confirm Auto Create Follow Up is enabled for that activity and posting permissions are granted.
Wrong schemes selected: Update the mapping to the correct Activity/Production schemes and re-test.