Create and manage GUI business components

Relevant for: GUI components only

This task describes the different operations you can perform to manage business components, and contains general considerations and guidelines.


  • Connect UFT One to an ALM project.

  • Ensure you have the required ALM permissions. For details on setting user group permissions in the Business Components module, see the Business Process Testing User Guide and the Application Lifecycle Management Administrator Guide.

Back to top

Create a new business component

To create a new business component:

  1. Select one of the following:

    • File > New > Business Component

    • File > New > Business Component from Sprinter Automated Test Data File

    • File > Add > New Business Component

    • File > Add > Business Component from Sprinter Automated Test Data File

    In the New Business Component Dialog Box, select a folder in the Business Components module in ALM in which to store your component and give your component a name.

  2. In the Application Area field , click the Browse button to select a suitable application area from within the ALM Test Resources module. After choosing your application area, click OK.

  3. If you are creating a business component from a Sprinter automated test data file, specify the location (on the file system) of the test data file.

  4. A new business components opens in the Keyword View (for keyword components) or in the Editor (for scripted components).

    Although the component does not yet contain content, it does contain all of the required settings and resources that were defined in the application area on which it is based. You can view these settings in read-only format by choosing File > Settings. If you later need to change these settings, you can do so in the associated application area.

Back to top

Convert a manual component to an automated component

This section explains how to convert a manual component to an automated component.

Caution: Converting manual components cannot be undone.

To convert a manual component to an automated component:

  1. To start the conversion process do one of the following:

    • Select File > Open > Business Component. In the Open Dialog box, select a manual component. Manual components are represented by a component icon with an M in the left corner of the icon.

    • Add a manual component to a business process test. In the test grid or canvas, select Automate Component > Scripted/Keyword GUI.

  2. UFT One asks whether you want to convert the manual component to a keyword component.

  3. Click Yes to continue with the conversion (cannot be undone).

  4. In the New dialog box, select an application area for your component and click OK. As UFT One downloads, opens, and converts the component, the operations it performs are displayed in the status bar.

    Each manual step from the manual component is converted into a ManualStep operation in the Keyword view. You can now work with the component like any other component.

    Note: If the application area you select does not yet contain all of the required resources and settings, you can still add steps using the ManualStep function or the Comment option. This enables you to type in manual steps as you would in ALM or in another application, such as Microsoft Excel or Microsoft Word.

  5. Back to top

Convert the keyword GUI component to a scripted GUI component

  1. Open the keyword component you want to convert.

  2. Select File > Convert to Scripted Component. When prompted, click OK to proceed with the conversion.

Back to top

Associate a different application area with your component

Do one of the following:

  • Select File > Change Application Area.

  • Right-click on a component node and select Change Application Area.

In the Change Application Area Dialog Box, you select a different application area and click OK to change the application area associated with a component.

Back to top

Delete a component

You delete a component in ALM, regardless of whether it was created in UFT One or in ALM.

Back to top