Skip to main content

Object naming

In briefOpCon Continuum applies one character policy to the names you give almost every object: anything you can type, except control characters and leading or trailing whitespace. Each kind of object has its own length bounds, and six — workflows and schedule instances, environments, roles, agent pools, scripts and jobs — keep a rule of their own. A script name, for one, cannot contain spaces.

WhereThere is no naming screen: the rules are applied to the name field of whatever you are creating, renaming, copying or importing — a property, a calendar, a self service button, a workflow in the workflow editor, and so on. In an editor, a name the rules refuse is reported on that field.

When

  • A name you typed, pasted or imported is refused, and you need to know which rule it broke.
  • You are choosing names for objects other things will refer to by name.
  • You are editing an object whose name was stored under an older rule, and want to keep it.

For what a role, a schedule instance or a job may be named, the page that owns that object has the detail: Roles and permissions, Schedule instances and Versions and deployments.

How

  1. Type the name. Any character you can type is allowed except control characters, and the name must not start or end with a space. A script name cannot contain a space anywhere.
  2. Keep it within its object's length: 40 characters for a workflow, 255 for most other objects.
  3. For a workflow or schedule instance, leave out the characters its rule rejects.
  4. To keep a legacy name, leave the name field exactly as it is and save the other changes. A name you leave exactly as it was stored is exempt — including a workflow name over 40 characters.
Notes
  • Editors trim trailing spaces before they save, rather than reporting them.
  • A copy's suggested name is shortened to fit the object's length limit. A script's copy is suggested as <name>_Copy, since a script name cannot contain spaces.
  • Import holds names to the rule the matching editor applies.
  • A workflow's references to calendars, frequencies, thresholds, resources and tags are held by identity, and a save refreshes the name stored beside each one after a rename. A renamed threshold, resource, tag or calendar shows its new name in the editors, the build and exports straight away; an earlier version keeps the old name.
Watch out
  • Renaming an object does not update the things that refer to it by name, such as a property token or a deployment's frequency names.
  • Changing even one invisible character of a legacy name counts as a rename, and the full rule then applies.
  • A slash is valid in a workflow name but can be refused where the name travels to a legacy agent.
  • Deleting an object and creating a new one under its name does not move the old one's references to it; a workflow that required the deleted object is refused on its next save.