NameMapping
I have a windows application named PX3000Client. Created testscripts for it and everything works. Decided to include debug informations within the applications and renamed the app to PX3000Client_...
Forum Discussion
Hi Albert,
If the name of the executable (the name of the process) is used in your mapping criteria, then definitely the change of the name will break the name mapping recognition. (BTW, it would help if you let us know what errors occur when 'scripts do not work anymore'.)
One possible aproach is to create a project variable, assing it the name of the executable (the name of the process) and then edit namemapping scheme so that it uses not hardcoded process name, but the value of the variable (see 'Adding Identification Properties to Mapping Criteria', 'Edit the Property Value Dialog' and 'Edit Name Mapping Item Dialog' helptopicsfor more details). I expect that it will be enough to edit only the process identification entry.
If the name of the executable (the name of the process) is used in your mapping criteria, then definitely the change of the name will break the name mapping recognition. (BTW, it would help if you let us know what errors occur when 'scripts do not work anymore'.)
One possible aproach is to create a project variable, assing it the name of the executable (the name of the process) and then edit namemapping scheme so that it uses not hardcoded process name, but the value of the variable (see 'Adding Identification Properties to Mapping Criteria', 'Edit the Property Value Dialog' and 'Edit Name Mapping Item Dialog' helptopicsfor more details). I expect that it will be enough to edit only the process identification entry.
