The Configure Transformation Scenario dialog is used to associate a
scenario from the list of all scenarios with the edited document by selecting an entry from
the list. The dialog is opened by pressing the
Configure Transformation Scenario
button on the Transformation toolbar of the document view. Once
selected the scenario will be applied with only one click on the
Apply Transformation Scenario on
the same toolbar. Pressing the
Apply
Transformation Scenario button before associating a scenario with the edited
document will invoke first the Configure Transformation Scenario dialog
and then apply the selected scenario.
If there is only one scenario that can be associated with edited document,
Configure Transformation Scenario dialog is not displayed, scenario
is associated with edited document and transformation is executed. This situation can appear
both for project scenarios and global scenarios when there is only one scenario in list of
possible scenarios that include document type scenarios and project/global scenarios.
Association of that scenario can be changed by opening Configure Transformation
Scenario dialog with an action having the same name (Configure Transformation Scenario) from
the toolbar.
Open the Configure Transformation Scenario dialog using one of the methods previously presented or by selecting .
The Scenario type allows you to choose what type of user defined transformation scenario is displayed:
If you want an XSLT scenario select as Scenario type either XML transformation with XSLT or XSLT transformation then complete the dialog as follows:
The following buttons are shown immediately after the input field:
The advanced options include two options that are not available globally in the user preferences: the initial XSLT template and the initial XSLT mode of the transformation. They are Saxon specific options that allow imposing the name of the first XSLT template that starts the XSLT transformation or the initial mode of transformation.
The advanced options specific for Saxon HE / PE / EE are:
Note that any external DTD is likely to be read even if not used for validation, because DTDs can contain definitions of entities.
The advanced options available only in Saxon PE / EE are:
The advanced options available only in Saxon EE are:
When creating a scenario that applies to an XML file, Oxygen fills the XML URL field with the default variable ${currentFileURL}. This means the input for the transformation is taken from the currently edited file. You can modify this value to other file path. This is the case of currently editing a section from a large document, and you want the transformation to be performed on the main document, not the section. You can specify in this case either a full absolute path: file:/c:/project/docbook/test.xml or a path relative to one of the editor variables, like the current project file: ${pdu}/docbook/test.xml .
When the scenario applies to XSL files, the field XSL URL is containing ${currentFile}. Just like in the XML case, you can specify here the path to a master stylesheet. The path can be configured using the editor variables or the custom editor variable.