Object naming
- Synopsis
- Full Details
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
- 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.
- Keep it within its object's length: 40 characters for a workflow, 255 for most other objects.
- For a workflow or schedule instance, leave out the characters its rule rejects.
- 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.
- 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.
- 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.
Almost everything you create in OpCon Continuum has a name you choose. Those names follow one character policy across the platform, with per-object length bounds and a small number of deliberate exceptions.
Continuum previously enforced six different naming rules, which disagreed with each other: a name
containing a slash was valid for a workflow and rejected for a service request, and a property
called $TempFolder could be created directly but not imported. That is gone — a name is now
either valid or invalid, and the answer does not depend on which screen you are on.
- Characters and Length
- Exceptions
- Legacy Names
- Renaming and Replacing
- Import and Copy
- Troubleshooting
Characters and Length
The character policy
| Outcome | Rule |
|---|---|
| Allowed | Any character you can type — letters in any script, digits, spaces, /, \, (, ), $, @, ., ,, %, &, #, ', emoji. There is no allowlist. A script name is the one that cannot contain spaces — see the Exceptions tab. |
| Rejected | Control characters — the non-printing codes below a space, including tab, carriage return and newline, and the delete character. |
| Rejected | A blank name, or one that starts or ends with whitespace. |
That is the whole policy. A name that satisfies it and fits the length bounds below is accepted.
The editors trim what you type before saving, so trailing spaces are silently removed rather than reported as an error. The whitespace rule is what the API enforces for anything that submits a name directly.
Length bounds
The character policy is uniform; the length bounds are not.
| Object | Length |
|---|---|
| Service requests, scripts | 1–255 characters |
| Properties, tags, calendars, frequencies, thresholds, resources, Vision cards, notification groups, escalation policies, workspaces | 3–255 characters |
| Workflows, schedule instances | 1–40 characters — see the Exceptions tab |
| Environments | 1–100 characters — see the Exceptions tab |
| Roles | 3–23 characters — see the Exceptions tab |
255 is the ceiling everywhere except workflows, environments and roles.
Exceptions
Objects that keep their own rule
Six things are deliberately not governed by the policy in the Characters and Length tab alone, because each answers to a constraint outside Continuum's own naming.
| Object | Rule | Why |
|---|---|---|
| Workflows and the schedule instances inside them | 1–40 characters, and none of ' | ; % & < > ( ) [ ] { } , = ! \ " | The 40-character ceiling is a long-standing OpCon limit on workflow names, and the excluded characters carry meaning in schedule and event expressions. |
| Environments | 1–100 characters, must start with a letter or digit, and only letters, digits, _ and - after that | An environment name is an infrastructure identifier that appears in URLs and service discovery. |
| Roles | 3–23 characters, letters, digits, _ and - only, with no exemption for a name stored before the rule — see What a role can be named | A role's name is also its name in the Continuous identity system. |
| Agent pools | Up to 255 characters. A Universal Agent pool takes lowercase letters, digits and - only, starting with a letter or digit; a legacy agent group takes letters, digits, ., _ and - | Same reason — a pool name is an identifier, not a label. |
| Scripts | The character policy and 1–255 characters, and no spaces or other whitespace anywhere in the name. A name with one is refused with Script name cannot contain spaces. A name stored with a space before this rule is exempt while you leave it unchanged | A long-standing OpCon rule for script names. See Script library |
| Jobs | Up to 255 characters, and unique within the workflow ignoring case | Job names are checked when you create a version, alongside the rest of the workflow. No character policy applies. The same 255 holds in a running process, when you add a job to a workflow instance or edit one there; earlier builds refused a name over 40 characters there. |
Names that travel to a legacy LSAM over the relay are held to a stricter allowlist at that boundary, because the wire protocol is older than the policy. That check is deliberate and unchanged.
Legacy Names
Editing an object whose name predates the policy
Names created under earlier rules can contain things the current policy rejects — most commonly padding whitespace, or an interior tab. Such a name is exempt from validation as long as you do not change it. You can edit the object's other settings and save normally.
This matters more than it sounds. A name field that refuses to validate blocks the whole form, not just the name — so without the exemption you could not change a property's value, a script's content, or a service request's workspace without renaming the object first.
Renaming applies the full policy. Once you edit the name field at all, the new name is validated like any other, so a legacy name cannot be nudged — you either leave it exactly as it is or you give the object a compliant name.
The same exemption applies wherever a name arrives without being retyped: an object saved with the name it already has is not treated as a rename. The notification group editor is the one exception. It checks a group's name as though it were new, so a group whose stored name holds a character the policy rejects, such as an interior tab, has to be given a compliant name before that editor will save it. Padding alone does not stop it, because the editor checks the name with its padding trimmed.
Workflows are exempt the same way. A workflow whose stored name is longer than 40 characters, or
holds one of the characters the workflow rule rejects, saves from the workflow editor as long as its
name is left as it is. Change the name and the workflow rule applies in full, and the editor reports
the problem on the name field before you save — Name must be 40 characters or less, or
Name cannot contain: ' | ; % & < > ( ) [ ] { } , = ! \ ". Earlier builds checked the workflow rule on
every save that carried a name, and the editor always sends one, so a workflow holding such a name
— one imported before the 40-character check, for instance — could not be saved from the editor at
all.
Several things reference an object by name rather than by ID — a [[PROPERTY]]
token, and the frequency names stored in a
deployment. Renaming the object leaves those references pointing at a
name that no longer exists. Fix them in the same change, or leave a legacy name alone.
Renaming and Replacing
Renaming or replacing an object a workflow uses
A workflow refers to its calendars, frequencies, thresholds, resources and tags by the object's identity, with the name stored beside it, and so does a frequency that names a calendar. Every save checks each of these references against the objects in your tenant:
| The stored reference | What the save does |
|---|---|
| Names an object that still exists | Keeps it. If the object has been renamed, the stored name beside the identity is refreshed to the new one. |
| Names no object in this tenant at all — one carried in from another environment, for instance | Points it at the object here that has the stored name. |
| Names an object that has been deleted | Does not move it to a different object that has since taken the same name. A required reference refuses the save; an optional one is kept as stored. |
A renamed threshold, resource, tag or calendar shows its new name before any save. Wherever Continuum reads a stored workflow or frequency, it shows the current name of the object each reference identifies, so you do not have to re-save the workflow to see it:
- The workflow editor shows the new name on a job's Threshold or Resource dependency, on its tags, and in the workflow's Additional Holidays calendar.
- The frequency editor shows a renamed calendar's new name in its calendar fields.
- The build uses the new name, so a job instance's dependency message names the renamed threshold or resource. A deployment's transformation rules are applied after the names are refreshed, so a rule that sets a name for an environment still wins, and a rule that matches the old name by value no longer matches it.
- An automation export carries the new names.
The stored copy is updated the next time the workflow or frequency is saved, as described above. A version is a snapshot, so an earlier version keeps the names it was saved with. A reference to a deleted object keeps its stored name. A renamed frequency is not part of this: the name stored beside it is refreshed when the workflow is saved. A frequency a job uses on its Frequencies tab is looked up by name when the workflow builds, so renaming it stops that deployed workflow's jobs from building until each job is given the renamed frequency again and the workflow is saved and deployed — see Frequencies.
Required references are a threshold dependency's threshold, a resource dependency's resource, a workflow's frequencies, and an Annual Plan frequency's calendar. A save that cannot resolve one is refused, naming the object:
- Threshold 'CORE_READY' is deleted. Restore it or use a different threshold.
- Frequency 'WEEKDAYS' not found, or you do not have permission to view it.
Optional references — a job's tags, a dependency's predecessor frequency, an event's frequency, a workflow's Additional Holiday Calendar and a frequency's exclusion calendar — do not block a save when the object they were saved with stops resolving. Such a reference is left as it is, so one stale setting cannot stop every unrelated edit. (A reference typed with a name only, and no object of that name, is refused either way.)
So deleting an object and creating a new one under its name does not carry the old object's references over to the new one. A workflow save whose threshold dependency still names the deleted threshold, for instance, is refused rather than quietly switched to its namesake. Restore the deleted object, or pick the new one in the workflow.
A reference to a deleted object fell back to its name, so it silently moved to whichever new object had taken that name, changing what the workflow depended on or ran by. And a frequency, threshold, resource or tag reference that arrived with an identity was stored without being checked at all. A workflow last saved before this release can still hold such an unchecked identity. Until that workflow is saved again, Cross Reference does not list it against the object, and the object can be deleted while the workflow still uses it.
Import and Copy
Importing objects
An import bundle's names are held to exactly the rule the matching editor would apply — the
generic policy for properties, tags, calendars, frequencies, thresholds and resources, and the
workflow rule for workflows. Import used to apply a single stricter rule to everything, which is why
a property called $TempFolder could be created directly and then failed to import.
Two consequences are worth knowing before an export-and-import round trip — see Automation export and import for the bundle itself:
- A workflow name over 40 characters no longer imports as a new workflow. Import previously
accepted up to 255, so a bundle can contain a name that
Workflowsitself has never accepted. Overwriting a workflow that already holds such a name still works, because that is not a rename. - A name an overwriting bundle already matches is exempt, the same way an unchanged name is exempt in an editor. This is what lets an object with a legacy name survive its own export and re-import.
Copying an object
Where an object can be copied — from its list page, from global search, or from
its detail page — the dialog offers <original name> - Copy as the default. If that would
exceed the object's length limit, the original part is shortened so the suggested name always fits;
for a workflow, that means the 40-character ceiling. A script is the exception: because a script
name cannot contain spaces, its copy is offered as <original name>_Copy, with any spaces in
the original turned into _.
The copy is a new name, so it gets the full policy. The dialog checks it as you type and shows the problem on the field, rather than letting the save fail.
Troubleshooting
| Symptom | Cause | What to do |
|---|---|---|
| Name cannot contain control characters | The name contains a tab, newline or other non-printing character — usually from pasting out of a spreadsheet or a document. | Retype the name, or paste into a plain-text editor first. |
| Name cannot be blank or start or end with whitespace | The name is empty or padded. Reaches you only when a name is submitted without going through an editor. | Trim the name. |
| Name must be between 3 and 255 characters | Under the minimum for this object type. Service requests and scripts allow one character; most other objects need three. | Lengthen the name. |
| Script name cannot contain spaces | A new or renamed script name contains a space or other whitespace. | Replace the spaces, for example with _. A script whose stored name already has a space saves as long as you leave the name unchanged. |
| Name must be between 1 and 40 characters | A workflow or schedule instance name over the 40-character ceiling. | Shorten it to 40 characters. |
| Name must be 40 characters or less, on a workflow's name field in the editor | You changed the workflow's name to one over 40 characters. A stored name you leave unchanged is not checked. | Shorten it, or put the stored name back exactly. |
| A name field reports an error on a name you did not type | The name was changed — even by a character you cannot see, such as deleting padding from a legacy name. | Restore the name exactly, or commit to a full rename. |
| An existing object's name is rejected when you try to save an unrelated field | The name was normalized before being submitted, which reads as a rename. | Reload the page and retry so the stored name is submitted unchanged. |
| A workflow save is refused with Threshold 'X' is deleted. Restore it or use a different threshold. (or the same for a frequency, resource or calendar), though an object of that name exists | The workflow refers to the deleted object, and a new one has since taken its name. The reference is not moved to the new object. | Restore the deleted object, or pick the new one in the workflow and save. |
See also
- Workspaces — the objects a workspace groups, and their names
- Properties — how a property is referenced by name in a token
- Versions and deployments — the job-name rules the version gate checks
- Schedule instances — the additional rules on an instance name