Text file that lists the full path to, and name of, the script files available to the application. You can specify that scripts be run at startup by including them in the scripts.ini file.
Startup scripts for xDM Library Tools are not allowed in PADS flow.
You do not need to specify the full path to the script files if they exist in one of the default directories listed in Search Order for Scripts. These scripts and forms often contain menu or command customizations or custom process integration forms. These are typically files with .vbs or .efm extensions. Additionally, batch and executable files (.bat and .exe, respectively) may be executed on the Windows platforms. In Unix or Linux operating systems, file with execute permissions may be specified.
Multiple scripts.ini files may exist in different directories specified by the WDIR environment variable, in which case the scripts named within are executed according to the search order.
If there are multiple scripts with identical names in the various searched directories, only the first such script that the application encounters will be executed.
When you develop a scripts.ini file, keep in mind that the following special characters have particular significance:
[application] |
Square brackets must be used to enclose the name of the application to which the scripts apply. |
* |
The asterisk is a wild card. When a script is located via a search that uses a wild card, the search stops. Therefore the wild card cannot be used to launch multiple scripts with similar names. |
; |
The semicolon is the comment character. Any text that follows a semicolon is considered comment text until a new line is located. |
%variable_name% $variable_name |
Environmental variables can be used in scripts. For example, $HOME can be used to identify the home directory. |
Script numbering in the scripts.ini file must be sequential. If scripts are numbered non-sequentially, the first non-sequential script that is encountered, and all that follow it, are ignored.
None
The following is an example of a scripts.ini file:
[Viewdraw]
script#0=MyMenuByName.vbs
; This line is an example of a comment.
script#1=ToolBar.vbs
script#2=AddCorpMenus.vbs
script#4=BadExample.vbs ; This entry, and all the following are ignored
script#5=Ignored.vbs ; because script#3 is missing.