Control field behaviour by area
Administrators can now control how custom fields behave depending on where users are working in Camphouse. This makes it possible to apply different rules in planning, production (limited release), and results, without duplicating fields or creating workarounds.
What’s new
You can now define conditional rules that control field behaviour based on the area of Camphouse the user is working in.
For each area, a field can be set as:
Required
Disabled
This allows the same field to behave differently depending on context.
Condition builder options
When creating or updating a conditional rule, you can base the condition on where the user is working.
You’ll see this listed as Entity type in the rule setup.
Entity type simply refers to the area of Camphouse where the rule should apply:
Media entry – Sheet view
Media result – Results
Production entry – Production Plan
Available operators:
Equals (=)
The behaviour applies only in the selected area.
Does not equal (≠)
The behaviour applies everywhere except the selected area.
Includes (∈)
Lets you select multiple areas. The behaviour applies in all selected areas.
Example: Require a field only in the Production Plan
This is just one example. Use this when a field should be mandatory in one area, but optional in others.
To set this up:
Open the field settings in Media types and fields and set Required to Required on condition.
In the condition builder, select Entity type.
Choose Production Plan.
Save the rule.
The field will now be required only when users are working in the Production Plan.
This update helps you:
Adapt field behaviour to different workflows
Reduce unnecessary friction for users
Improve data quality where it matters most
By tailoring field rules to where users are working, you give clearer guidance and a smoother experience across planning, production, and results.
Keep Growing with Camphouse
🎓 Camphouse Academy – tutorials & courses
💬 Support – send us a message, we’ll reply as soon as possible