Overview
The ATC scripting language is a set of English directives. A script command can span multiple lines. Each script begins in the context of the source document with which the script is associated.
Each command begins with the letters ATC followed by a colon. When you open the text editor, the first ATC: may already be there. For information on how to get to the text editor to create workflows, follow the links on the right sidebar.
The ATC Commands
The ATC commands are written in all caps here; however, only the ATC need be capitalized. The rest of the command can be in lowercase. For example, ATC: close is a valid command. Document and route names are case-sensitive, however.
Note: you can turn any command into a comment that will be ignored by adding an asterisk after ATC:. For example, ATC: * CALL will not run the ATC: CALL command. You can also start a text comment with ATC: * as in ATC: * This is just a comment.
Related KBAs:
- KBA-01759: Validation and Document Logic Overview
- KBA-01777: The Workflow Scripts Tool
- KBA-01778: How to Create a New ATC Workflow Script
- KBA-01779: How to Associate an Event with a Workflow Script
- KBA-01780: How to Create Workflow on a Document
- KBA-01781: How to Create Workflow in a Predefined Route
- KBA-01783: ATC Script Command Conditions
- KBA-01784: Examples of ATC Workflow Scripts
KBA-01782: Last updated: July 15, 2025 at 13:45 pm changes since previous version appear in green.