For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Open sourceSupportFAQsDocs Home
DocumentationAPI referenceRelease notes
DocumentationAPI referenceRelease notes
  • Release notes
    • Overview
    • Changelog
      • Overview
      • Adapter Email replaced
      • AngularJS libraries removed
      • Ansible Playbook task response fixed
      • Automation Catalog deprecated and removed
      • Customizable UI not allowed in Platform 6
      • Decision task replaced by Evaluation task
      • Default adapter protocol
      • Delete Variables API removed
      • Dot notation not allowed in job variable names
      • ENC encryption deprecated
      • Form Builder removed
      • Get Server Health API changed
      • Itential Tools updated
      • OperationId tasks removed in Platform 6
      • Operational Data tab removed in Config Manager
      • Pre-Builts deprecation
      • Profiles deprecation
      • pushToArray requires preexisting arrays
      • Reduced integration responses
      • Remove default self-signed TLS certificates from container image
      • Retrieve references endpoint replaced
      • Server name property replaced
      • Service Catalog and Service Catalog Builder removed
      • Verify Config task removed
LogoLogo
Open sourceSupportFAQsDocs Home
On this page
  • Naming format
  • What should I do?
  • Related reading
Release notesBreaking changes

Dot notation not allowed in job variable names

Was this page helpful?
Previous

Form Builder removed

Next
Built with

This breaking change applies to the Platform 6 feature release.

Workflow job variable names can no longer contain the period character (.). Workflows that violate this rule cannot be run.

Naming format

❌ Invalid: my.invalid.variable.name

✅ Valid: my_valid_variable_name

Note that in exported workflow documents, variable names are not presented the same way as on the Workflow Canvas. The variable will include the job variable prefix $var.job., which includes dot notation. In this context, a valid equivalent to the example above looks like this: $var.job.my_valid_variable_name.

What should I do?

  • If you have exported a workflow that includes dot notation in the job variable name, you may still import the workflow, but you will be required to change the variable name before you can run it.

  • If you are upgrading your environment and there are existing workflows in the database that contain dot notation in the variable name, the upgrade may fail and throw an error. Modify the variable name to meet naming requirements before upgrading.

  • If you experience any issues or need assistance, contact the Itential Customer Support Team.

Related reading

  • Naming conventions