Sample Change Request APEs

A sample change request APE is found in the Samples\ChangeRequest folder under the StarTeam Extensions installation folder.

In the JBuilder project named ChangeRequest.jpx, required fields (in this case, Priority, Synopsis, and Responsibility) are indicated in red. The tab name (in this case Synopsis) is in red to indicate that the tab has required property fields on it. The change request cannot be saved until a valid value is supplied for all required fields. The source code for the sample form is provided so you can use this form as a starting point for creating your own custom form.

Another such sample change request APE is found in the Samples\LinkTypeChangeRequest folder under the StarTeam Extensions installation folder. This sample is found in the JBuilder project named LinkTypeChangeRequest.jpx.

In addition to the capabilities of the previous change request APE, this APE can display a corporate logo and access the items to which the change request is linked. Some properties are displayed at all times. Clicking tabs changes only the lower part of the form

When using StarTeam Extensions for workflow management, the existing Status field found in the change request is not used as the workflow control property. The reasons for this are:

• Existing change requests and the built-in property editor dialog rely on specific status values being used for a change request.
• Changing this status value causes specific side effects. To isolate these side effects from the implementation of a custom workflow, a separate custom property is used. In general, you should try to keep the Status property in the state that most closely matches the corresponding Workflow Status. You should also change the public filters to include the Workflow Status field instead of the default Status field.