Script dependency rule sets allow dependencies to be created using XCM scripts. While script rules can take a little longer to configure than some of the other rule types, they are extremely flexible and are commonly used when the other predefined rule set types are unsuitable. When the dependency rule set type is Script, the window will look as follows.

When this type of dependency rule set is selected, the user must indicate which Script the dependency rule set should execute. This should be entered directly or selected from the dialogue box after clicking Browse. If the script is not located in the current project directory then its full path must be specified.

The user must also specify the database Range the XCM script will be executed over. By default the pre-defined range <All> is used, but this can be changed to limit the effects of the rule set to a particular portion of the deposit.

Only one script can be specified in a dependency rule set, although any number of dependency rule sets of this type can be created. This allows different XCM scripts to be executed over different database ranges.

The scripts used in this type of dependency rule set make use of several special XCM functions that allow the interrogation of existing dependencies and the creation of new dependencies. A list of the scripting functions related to dependency rules can be found in the XCM programming documentation and in the XCM quick reference guide.

To ensure XPAC manages dependency rules correctly, dependency scripts must be executed from within a dependency rule set. If the user attempts to execute a script that creates dependencies directly, an error message will be generated indicating the script must be called from within a dependency rule set.

In addition to standard dependencies, script functions are also provided to access more advanced dependency features such as release profiles and OR rule groupings. These features are described later in this chapter.

The two additional tabs on the right hand pane of the schedule set up window (Circular Reference Checking and Adjacency Tables) provide access to advanced properties that are not appropriate to this type of dependency rule set. The options on these tabs are therefore unavailable with this type of dependency rule set.