configuration-files.md

@@ -124,10 +124,12 @@ You can create a new or edit and old batch config in this user interface. To loa
   * Session Initialization is run once per history file in the submit script. This contains shell code the setups up the environment on the remote for the current job. We use this on the cluster to load modules (programs) and any other environment business.
 * Job Name (job_name)
   * Sets the name that is submitted to the scheduler. This can be used for reporting and monitoring
+  * This field accepts `[batch_dfn]` and `[batch_hfn]` string swaps
 * Job Initialization (job_init)
   * Is inserted before each datafile in a specific submit.sh script. We use this to add LD_RUN_PATH to LD_LIBRARY_PATH before running Amica in this reference pipeline.
 * M file name (mfile_name)
   * Used for the Octave/Matlab script file name, also used as the log name. This allows us to make log and mfile names that are a specific as we need.
+  * This field accepts `[batch_dfn]` and `[batch_hfn]` string swaps
 * Script Prefix / M File Init (m_init)
   * Is run in each m file that batch_context generates, used to setup environment specific settings and imports in Octave/Matlab
 * Submit Options / Custom scheduler options (submit_options)