Getting the Most out of Teamstudio Configurator

What can I use Teamstudio Configurator to search for?

Configurator searches only on text in either the database design or documents. The search string is limited to 254 characters.

If you select the Design check box, Configurator will search for occurrences of the search text anywhere in the database design. This includes all of the formula code, LotusScript, JavaScript, static text on forms, subforms, help\using and help\about documents, field help, popups, element titles (for example, form titles and view titles)... In fact, Configurator will search just about anywhere you can change text.

It cannot, however, search on the following information:

• Java
• Element properties
• Fonts
• Outlines
• Checkboxes

If you select the Documents check box, Configurator will search text anywhere it occurs in any Text, Rich Text, Keyword, Authors, Names or Readers field in the database documents.

You can also use Configurator to search and replace a single text string over hundreds of databases using a LotusScript agent. The configuration information needed can be found in the User Guide in the section under Teamstudio Configurator entitled Calling Configurator from LotusScript. An example script agent is located in the local tmslogs.ntf database installed with Teamstudio.

Configurator just posted error messages in my output log. What should I do?

Sometimes, Configurator posts error messages in the output log, or in rare cases may even crash the Notes client. If this occurs, check the release notes for known problems and disable the recompile modified design notes. Then, use the Design Notes tab to try to isolate the corrupted element that caused the error. Once you've found the element, use the Notes Designer to add miscellaneous edits to the element to attempt to resolve the issue.

The following are known issues, and can be found in the Teamstudio Configurator release notes:

• Configurator will not compile LotusScript in actions due to a bug in the Notes API. Configurator will not compile very large agents (>64k) due to a bug in the Notes API. (SPR# CSCN-4JZQZ7).
• Configurator may crash when attempting to compile very large actions (>64k). (SPR# WHAA-4VRQ3H).
• Configurator may not compile some forms/subforms/pages due to a bug in the Notes API. (SPR# SPEK-$KUVL2).