Global search and replace for Lotus Notes

Teamstudio Configurator allows users to search and replace text across an entire database, either in a design or documents. Automating this potentially error-prone, repetitive task significantly enhances application quality, and alleviates developer frustration, allowing them to concentrate on more complex problems to make better use of their skills.

Managing Mass Changes to Application Data - Teamstudio Configurator Datasheet

Use Case: Pharmaceutical Industry - ISO Compliance

Teamstudio Configurator allows users to search and replace text across an entire database, either in a design or documents. Learn how one of Europe's privately held pharmaceutical companies implemented Teamstudio Configurator and saved 10 hours of weekly development work.

A Best Practices Tip for Application Development

A Low Maintenance Way of Placing Those Version Numbers Exactly Where You Want Them

Version numbers are essential in application development simply because they allow users to identify which iteration of an application is being worked on. Without them, for example, you could spend hours trying to track down the source of a bug you thought you already fixed when in actuality you could be looking in the wrong version!

The difficulty with incorporating version numbers can be the manual methods available to do so. These processes tend to become problematic because of the required maintenance or simply because they're easily forgotten. A simple solution is to use Teamstudio Configurator.

Wouldn't it be great if you could put version numbers anywhere and everywhere in your applications? Do you want to put version numbers in places that cannot display computed fields, such as pages? Do you want your version numbers to show up in the database or frameset titles?

If the answer to any of the above is yes, you'll be glad to know that there is a very easy way to do all these things, using some simple text and Teamstudio Configurator.

First, place some unique text in your application where you want the version number to show up. See the following database title:

Next, Use Configurator to search for your unique text and replace it with the version number.

The output is a completely configured database ready to be rolled out into production, and everyone will know what version it is.

Another example of adding version numbers is when you want a field or a collection of fields to display the same version number information. Using the same techniques from above you can easily add version number info directly to the field design on the form.

Using Configurator for including version numbers in your applications is extremely straight-forward and error-free. Plus, Configurator's scripting capability makes it ideal to incorporate these changes into your automated build or deployment process.