Share this page
Configuring StarTeam Projects to Use APEs
By default, every project uses the standard property dialogs. When an APE is ready for use, you must change the project properties so that all the views in a project will use the APEs. Once set, every view in the project must use an APE instead of the standard dialog. However, each view can use a different APE that you have checked into the appropriate view-specific subfolder in the Projects folder of StarFlow Extensions project.
Note: Take care when setting the APE for a project that is in production because the new setting takes effect immediately. It is important to test any changes that are made to an APE prior to making this editor available to a wide audience.
To use an APE with a StarTeam item type:
- Click Project > Properties. The Project Properties dialog appears.
- Select the Editors tab.
- Select the Use Alternate Property Editor For <item> check box.
- Enter or browse for the correct APE. You enter the word Locator followed by the name of the APE.
Depending on the client, Locator is either a program or a signal to distribute resources, such as .jar and .xml files to client workstations. If specified here, whenever the application requests the APE, the client looks for the StarFlow Extensions project managed by the server configuration. If that project exists and contains a .propertyeditor.xml file with the specified name in either the Projects folder or an appropriate child folder, the client copies the tip revision of that resources referenced in that file to the client workstation (if they are not already there). Then the user edits items using the APE instead of the application’s standard properties dialog for the specified type of item.
