When there are many user (script writer and especially full access) I think it's important to have audit trail to let admin know someone has created, modified, or deleted script or result.

In the current release of SilkTest(14); it is not possible to select and delete multiple items within Object Map, simultaneously. Each item has to first be selected, before clicking the Edit button; and then delete the item via the right-click context menu. This can be tedious when you have a lot of unneeded items in the Object Map; so please consider allowing multiple item selections within Object Maps.

Can we have the ability to navigate through code so when you right click a function name or variable the code jumps to variable declaration or function definition. And maybe also a way to get back, like we had in test partner.

The mapping of the Active Data File is currently hard coded path in the visual scripts.

Could Silk be enhanced to map active data as an external parameter?

When testing a Visual Script it would be great to point to a different location than the current Visual Script is pointing.

now the data is in the file system, due to security issue, most of client do not allow share folder.

Provide a method for reporting on

Total number of automated scripts
Total number of steps across all tests run
Total number of passed/failed verifications

If we want to print result file, we have to print it one by one. It will be take long time and energy if there are >100 result that have to be printed as requirement.
It will be very helpful if user can print multiple result (the latest version) at once

The custom options I save within Silk Test Workbech should be able to be pushed to all users that log in.

Currently in Silk test Workbench the options are saved per user, as an Administrator I wish to ensure the settings I apply are pushed to all users to ensure that all users are using the same options as myself.

This functionality would allow me to better manage my users and to ensure continuity throughout recording and playback of tests.

When you change a script name, you have to then go into every script which references the old script name and update the name. The scripts should be handled on an ID base so the name can be maintained at will.

A project Name like "PeopleSoft 9.1" is not allowed due to the decimal in the name field. A name like "PeopleSoft 91" does not look right.

When you rename a Visual Test after it has been executed; the current behavior of the Workbench, is that any existing Results assets will be orphaned, and are no longer associated with the parent test. I would like this behavior modified in a future release of SilkTest; so that Results are still associated with the Visual Test, even after renaming it.

When debugging a script, it is often useful to disable scripts. At times it would be helpful to be able to "hide disabled steps". This would let you focus your debugging efforts on which steps are functional. This is especially true for more complex scripts.

Please consider providing a Random function that would allow users to generate random values for common input fields such as Zip Code, Contact Number etc; within the Expression Designer when working with Visual Tests. Currently there is no means to accomplish this within Visual Tests; so the random values can only be created and consumed in .Net scripts, or sent back to a calling Visual Test as parameters.

Two things from Test Partner that would be nice in Silk Test
1. In Test Partner when you typed Sub name or Function and a name it would automatically put in the End Sub or End Function.
2. Also in Test Partner after (or before) a Sub or Function a Line would automatically be created to show where each Function is at. This would also make reading Functions easier in Silk Test

When recording Workbench Tests; please provide an option that allows the user to set the default behavior, in relation to BaseState execution. Currently this is enabled by default; and can be disabled by modifying the App Configuration settings in the start step of a Visual Test. However it would be better to have the option to change this behavior while recording.