This article covers grouping fields into fieldsets, adding conditions, and attaching fieldsets to activities so the fields appear on jobs. It also explains how to change a field's settings for one fieldset or one activity without affecting anywhere else.
Build a Fieldset
- Open Field Sets and select New.
- Enter a Name and description.
- Add fields in any of these ways:
- Add new field to create a field here.
- Add existing field to reuse a field that's already set up.
- Add nested set to include another fieldset.
- Expand a field to review its settings and conditions.
- Select Reorder fields ⇅ to arrange them, and save the order.
- Select Preview fields to check how the fieldset looks.
- Select Save.
A fieldset needs at least one field or nested fieldset. Fields you create inside a fieldset become reusable fields once you save. Your changes only take effect when you select Save.
Attach Fieldsets to an Activity
Fields only appear on jobs once their fieldset is attached to the job's activity.
- In your hub, open Activities and create or edit an activity.
- Select Attach Field Set.
- Search for and expand fieldsets to check their contents. Select one or more, then choose Attach selected.
- Use the move-up and move-down controls to set the order.
- Select Preview fields to check the fields..
- Save the activity.
To edit a fieldset from here, select Open field set →. Your changes apply everywhere the fieldset is used. Remove field set on the activity page detaches it from this activity only.
Add a condition to show a Field
Use a condition when a follow-up question should only appear for a certain answer. For example, show Tank size only when Job scope is Tank delivery.
- In the fieldset, expand the field that should appear conditionally.
- Open Conditions.
- Under Show this field if, select Add condition.
- Choose the source Field and the answer Value.
- Preview the result and save the fieldset.
If you add more than one condition, the field appears when any of them is met. When you change a condition, select the new value to finish the change. Otherwise the old condition stays.
Nest a Fieldset
Nest a fieldset when several fieldsets need the same group of fields, such as contact details. Select Add nested set and choose the fieldset.
A nested fieldset stays shared, so it isn't copied. To change its fields, open it in the new window. Your changes apply everywhere it's nested.
Nesting goes one level deep, so you can't nest a fieldset that already contains a nested fieldset. Removing a nested fieldset only removes it from this fieldset.
Choose where to change a Field's settings
A reused field doesn't have to behave the same everywhere. Make each change at the narrowest level that does what you need.
| You want to change | Where to do it | Affects |
|---|---|---|
| A field's label, or whether it's sortable | Fields | Everywhere the field is used |
| A field's default settings | Fields | Every fieldset that hasn't overridden that setting |
| A field's settings in one fieldset | Field Sets | Every activity that uses that fieldset |
| A field's options in one activity | Activity Option list overrides | That activity only |
| A shared set of options | Option Lists | Every field and activity using the list |
If an option list is overridden in both a fieldset and an activity, the activity's override wins. When you save something that's used in more than one place, you'll see a warning first.
Field defaults
The settings you choose for a field in Fields are its defaults. Every fieldset that uses the field starts with them. If you change a default later, fieldsets that kept it pick up the change, and fieldsets that overrode that setting keep their own value.
In a Fieldset
Expand the field in the fieldset and change any of these: Required, Default value, Clear value on clone, Remember user's previous response, option lists, and type-specific settings such as minimum and maximum values. The label and key can't be changed here.
To go back to the field's original settings, use the reset control ↻.
In an activity
Option lists are the only setting you can change per activity.
- On the activity, expand the attached fieldset.
- Open Option list overrides.
- Use Override with to choose another option list, or create one.
- Preview and save the activity.
To go back, select Use field set default.
Troubleshooting
| Problem | What to check |
|---|---|
| A field isn't showing on jobs | Make sure its fieldset is attached to the job's activity and the activity is saved. |
| A change isn't showing on an existing job | Existing jobs keep the fields they were created with. When a newer version of fields is available, the job shows New fields available. Selecting Update replaces its fields and answers, so review the existing answers first. |
| A field can't be used as a condition source | Lists, groups, record selectors and display fields can't be sources for condition. |
| I can't remove a field from a fieldset | Another field's condition depends on it. Remove that condition first. |
| The option list override is disabled | Overrides aren't available for Grouped Dropdown fields or fields that conditions depend on. |
| A field/fieldset/option list can't be archived | It's still in use. Check where it's used, remove it from each place, then archive it. Remove a field from its active fieldsets. Detach a fieldset from its activities and any fieldsets it's nested in. Remove an option list from its fields and activity overrides. |
| My changes aren't showing | Select Save. A preview or unsaved field or fieldset isn't published. |
Related articles
- Custom fields overview: the building blocks and how setup works.
- Create fields and option lists: field types, settings and option lists.
Have questions? Contact us at support@ironsight.app and we’ll help you out.