In each AXIS object which utilizes AXIS Script, the user is expected to create a small program or procedure (a "formula") which either defines a specific set of numeric values (e.g. the specific assumptions provided through a Formula Table) or a defines a production batch procedure controlling the execution of AXIS processes and calculations (e.g. an AXIS System Formula).  For each such object, the AXIS Script Editor is the interface used to write and maintain this formula.  There is also an AXIS Script Debugger which allows the user to track the values of intermediate variables as the Formula is being executed as part of AXIS calculations, in a controlled step-wise manner.   

The user is responsible for learning and using basic programming techniques, such as naming and declaring his own variables for storing intermediate values, and the creation and use of user defined subroutines and subfunctions, as appropriate.  In addition to a large library of predefined functions that are vendor provided, there are also predefined sets of input variables available for the programmer to use (specific to each formula object), and predefined output variables that can be used in subsequent AXIS calculations, all of which are documented in the Help text for the specific Formula Table being defined.

AXIS Script is written in a free-form text window.  The editor automatically recognizes and colour codes statements and other supported language elements, according to their type.  If words in the written procedure are not colour coded, they are presumed to be either operators, constants or variables, which thus provides feedback to the programmers as to possible syntax errors.  Tooltips also help explain the expected syntax of parameters on each vendor supplied function.  Prior to actually using a Formula Table in a Cell recalculation, you may ask AXIS to precompile the formula which allows detection and correction of syntax errors that would otherwise halt the Cell calculation.  Error messages will identify the location of the syntax error in the code.  The editor also allows you to preset multiple breakpoints which will halt the execution of the code to reveal intermediate calculated values and thus confirm the validity and correctness of more complex coded procedures. 

Programmers should use traditional good programming practices such as using meaningful variable names for user defined local variables, indenting lines within nested loops to reveal the structure of code, and liberal use of comments statements within the code itself.