The Script Editor

You can use the Script Editor to modify scripts that have been generated by a script generator, or to create a user-defined workflow script. For information on opening the Script Editor, see Workflow Customization at a Glance.

The Script Editor tab contains the following elements:

Script Editor toolbar. Contains buttons used when creating scripts. For details, see Understanding the Script Editor Commands.
Scripts Tree. Lists the event procedures to which you can add code. The event procedures are grouped by the module in which they are triggered. For details, see Workflow Event Reference.
Scripts pane. Displays the code of the selected event procedure. To create or modify a script, you add VBScript code to the event procedure. For details, see Creating a Workflow Script.
Messages pane. Displays any syntax errors encountered when you save or validate a script.

Cross Project Customization

ALM Editions: Cross project customization is not available for Quality Center Enterprise Edition. For more information about ALM editions and their functionality, see the Micro Focus Application Lifecycle Management User Guide: ALM Editions.

If you are working in a template or linked project, the Scripts Tree displays two sections under Workflow Scripts:

Template Scripts (Shared). Workflow scripts listed in this section are the scripts applied from the template to the linked project. For details on applying template customization, see Applying Template Customization to Linked Projects.

If you are working with a linked project, this section is displayed only when there are template scripts defined in the template. The template scripts cannot be edited in the linked project. If you remove a project from a template, the template scripts remain in the project and are editable.
Project Scripts. Workflow scripts listed in this section apply only to the template or linked project in which you are working. Scripts in this section of a template are not applied to linked projects.

When running workflow scripts for a linked project, ALM combines template scripts and project scripts into one script. Duplicate variables or functions in the template scripts and projects scripts can cause conflicts.

Additional considerations when working in a template project:

Scripts generated by one of the script generators are created under Template Scripts (Shared).
ALM adds the prefix Template_ to events in template scripts. By default, ALM triggers template event procedures. The project event procedure is triggered if the template event procedure does not exist, or if you instruct the template event procedure to call the project event procedure.

Each template event includes a commented call to the parallel project event. For example, the Template_Bug_New event in the template script is displayed as follows:
```
Sub Template_Bug_New
    On Error Resume Next
    `call Bug_New
    On Error Go To 0
End Sub
```
To instruct the template script to call the project event, remove the comment marker to activate the call to the project event, as follows:
```
Sub Template_Bug_New
    On Error Resume Next
    call Bug_New
    On Error Go To 0
End Sub
```