Share this page
Known Issues
This section contains known issues for StarTeam Extensions.
Custom Fields not Recognized
The caching of server connections improves the form server’s performance, but changes to customizable properties and new properties are not automatically recognized by APEs. Use one of the following work-arounds:
- You can force-log-off all users after making the property customization. This causes the cached server connection to be recreated with the new information.
- You can perform the modification after hours if everyone logs off as they leave.
- Tell all users to shut down their form servers. When the APE is restarted, the connection is reestablished with the new information.
Things to Check
- Make sure that the server description’s computer name or IP address and endpoint are correct. Also be sure that your username and password are correct.
- The StarFlow Extensions project cannot be renamed. StarTeam Extensions looks for this project when doing anything regarding APEs and workflow. If this project is renamed or missing, StarTeam Extensions functionality will fail.
- Java requires a minimum of 256 colors to start any AWT or Swing-based graphical user interface. When you try to start the StarTeam Server from the Start menu on a computer with too few colors, you see a DOS box blink on the screen then go away.
Use of Process Items
Marking process items as fixed, finished or completed as part of the check-in process changes the value of the internal property field named Status for the item type. It works well for users of the standard property dialogs. However, if the item type uses a custom workflow process, this can cause problems and should be avoided. For example, if you mark a change request as fixed as part of check in, the Addressed In property is automatically set to Next Build. However, the workflow control property for a change request is never the Status field (because of the application’s built-in workflow). The value of the workflow control property is not changed by this check-in process and the next build label can become attached to the process item erroneously.
