Skip to main content

Custom fields

In briefCustom fields are your own metadata fields for jobs. An administrator defines each field once for the whole organization — its name, input type, default and whether it is required — and its value is then set job by job in the job editor.

WhereAdministration › Custom Fields for the definitions; New Custom Field adds one. Values are set in the Custom Fields section of the job editor, in both the Workflow View and the Process View.

When

  • You want every job to carry information Continuum has no field for, such as an owner or a cost centre.
  • You want a value to be mandatory on every job definition.
  • You need to correct a custom-field value on a run that is already under way.

How

  1. Open Administration › Custom Fields and select New Custom Field.
  2. Give it a Name and an Input Type; for Select, enter its Options.
  3. Set Required field, Default Value and Display Order as needed, and save.
  4. Set each job's value in the job editor's Custom Fields section. The full walkthrough is Manage custom fields.
Notes
  • Custom fields apply to jobs only today.
  • A Default Value is written onto every job that has no value for the field when its workflow is saved or imported, and the Workflow View job editor names it in a hint under the empty field. A field you clear stays empty.
  • Required field is enforced when you save a new job or clear the value, and a usable default satisfies it. Jobs saved before a field became required still save without it. On a built job instance it is enforced only for a field the instance was built with.
  • Push Changes to Workflow carries custom fields field by field, so a field the instance never had keeps its workflow value.
  • A save or import that removes a value for a deleted or unknown field says so: the workflow editor shows a warning after the commit, and the API response carries a removedCustomFields list.
  • A job instance that holds a value for a deleted field can still be edited while that value is sent back unchanged.
Watch out
  • A Select field cannot be saved without at least one option.
  • A default that does not fit its Input Type, or a Select default that is not one of its options, is refused when you save the field.
  • Changing a field's type or options leaves job values that no longer fit in place. A workflow still saves while those values are untouched; changing one to another value that does not fit is refused.
  • The Process View job editor lists only the first 100 definitions, so a set larger than that is not fully shown on a built job instance.