Actually, you can have scripts that run for DIFFERENT locales.I have a set of scripts that run for Japanese as well as English locales. Idea is to have objects recorded in GUI Map with a locale independent physical description. This can be achieved in two ways.

• After recording the object in the GUI Map, INSPECT the description and ENSURE that no language specific properties are used. For ex: html_name property for an object of class: HTML text link could be based on the text. You can either remove these language dependent properties if it doesnt really affect your object recognition. If it does affect, you need to find another property for the object that is locale independent. This new property may be something thats already there or you need to create them, This leads to the next option.
• Have developers assign a locale independent property like ‘objname’ or something to all objects that you use in your automated scripts. Now, modify your GUI Map description for the particular object to look for this property INSTEAD of the standard locale dependent properties recorded by WR (these default properties are in GUI Map Configuration).

Actually, you can have scripts that run for different locales.I have a set of scripts that run for Japanese as well as English locales. Idea is to have objects recorded in GUI Map with a locale independent physical description. This can be achieved in two ways.