Skip to content
Hawzu Docs
API reference Go to app

Field Lifecycle

2 min read

Custom fields move through statuses as teams create, enable, disable, remove, and retire them.

Workspace and project fields have different lifecycle behavior.

Workspace Statuses

Section titled “Workspace Statuses”

Workspace fields can show:

  • Enabled: the field is active in the workspace catalog.
  • Deprecated: the field is retired across the workspace.

Deprecated workspace fields keep existing values visible for reference. They cannot be newly enabled in projects.

Project Statuses

Section titled “Project Statuses”

Project fields can show:

  • New: the workspace field is available but not yet enabled in the project.
  • Enabled: the field is active in the project.
  • Disabled: the field is hidden from normal use in the project.
  • Deprecated: the field is retired in the project.
  • Deprecated at workspace: the workspace field was retired globally.

Enable Field

Section titled “Enable Field”

Use Enable Field on a new or disabled project field to make it available for project configuration.

After enabling, configure views, required behavior, default value, and dropdown options where applicable.

Disable Field

Section titled “Disable Field”

Use Disable Field to hide a project field without removing its configuration.

Disabling is useful when a field may be needed again later or when a team wants to pause use before retiring it.

Remove Unused Fields

Section titled “Remove Unused Fields”

Remove deletes field configuration when it is safe to do so.

  • Unused workspace fields can be deleted from the workspace.
  • Unused project fields can be removed from the project.

Removing is permanent for the affected level.

Deprecate Used Fields

Section titled “Deprecate Used Fields”

When a field has usage, Remove retires it by deprecating it instead of deleting active history.

  • Used workspace fields are deprecated across the workspace.
  • Used project fields are deprecated for that project.

Deprecation keeps existing values visible for reference and prevents the field from being used for new data going forward.

Delete Confirmation

Section titled “Delete Confirmation”

When deleting is available, Hawzu asks for confirmation.

Deleting a workspace field removes the field from the workspace and permanently removes values saved in that field.

Removing a project field removes it from that project and permanently removes values saved in that field for project items.

Impact And Backfill

Section titled “Impact And Backfill”

Some changes add default values to existing items. Hawzu shows an impact summary when relevant.

If a project update requires background work, the details view can show a backfill status while existing data is updated.

Next Steps

Section titled “Next Steps”