Workflow customization

Workflow scripts enable you to restrict and dynamically changes the fields and values in your modules. Therefore, you can write workflow scripts to customize the ALM desktop client user interface, and to control the actions that users can perform.

Workflow customization enables you to do the following:

What you can do Details
Create workflow scripts

You can use either the Script Generator or Script Editor tool to create workflow scripts, depending on your needs and skills.

  • Script Generator. The following Script Generator tools help you generate workflow scripts specifically for the Defect module. Using the tools, you do not need to familiar with VBScript.

    • Script Generator - List Customization for Defect Module. Customize the value list to be used for a secondary field, depending on the value of a primary field.

    • Script Generator - Add Defect Field Customization. Customize the New Defect dialog box.

    • Script Generator - Defect Details Field Customization. Customize the Defect Details dialog box.

    For details, see Generate workflow scripts using Script Generators.

  • Script Editor. The Script Editor tool help you write your own workflow scripts for all modules. To use this tool, you must be familiar with VBScript.

    For details, see Create and edit workflow scripts using Script Editor.
Edit workflow scripts

You view and edit existing workflow scripts in the Script Editor.

For details, see Create and edit workflow scripts using Script Editor.
Add toolbar buttons to a module window

Using the Script Editor, you can define toolbar buttons to be displayed in the window of an ALM module, or in the Manual Runner dialog box.

For details, see Add toolbar buttons.

Note: Workflow scripts run with the privileges of the logged-on user, not the privileges of the user who created the script. As a result, a script fails if it attempts any action or data change that the logged-on user is not privileged to perform, or if it accesses any restricted object that the user is not privileged to use. Therefore, a script developed by a privileged user should be tested with users that belong to the groups expected to trigger the script.