You can write scripts directly in the ePublisher AutoMap script editor window, or you can cut and paste scripts from another text editor. The ePublisher AutoMap script editor supports only text-based scripts. Any formatting or additional information available in a third-party script editor is lost when the script is pasted into the ePublisher AutoMap script editor.

ePublisher AutoMap treats scripts like DOS batch files. The script must be complete and valid or it will fail when the job runs. Although you can write all your scripts directly in the ePublisher AutoMap script editor; this approach may not be your best option.

When calling complex scripts, you may want to create and store those complex scripts in your file system and simply call those files from the script you create in the ePublisher AutoMap script editor. Since the script editor treats the scripts like DOS batch files, you can call other batch files, applications, or scripts written in any scripting language, such as VBScript, Perl, and Python. You can also pass parameters and script variables to the files you call. However, some variables have meaning only for certain types of scripts. For example, the DeployFolder variable is specific to a target and does not having meaning in a pre-build or post-build job script.