We are currently unable to record and playback scripts using the Citrix client. The current support matrix states it only supports up to the 7.0 client. We need support for the 7.5 client. Is there any enhancement available for this?

BrowserStart in bdlt currently allows you to set certain options like screen size. It would be helpful to extend this function to allow extra parameters to specify window position (if running multiple users in visible mode for debugging) and the ability to go visible on error and pause on error for debugging, which allows the window to become visible and pause when an error state is encountered. Time for debugging would be greatly reduced for support and customers.

Currently, script correlation can only be done after a Try Script run. The recommended approach is Record->Run Try Script->Create Recording Rules. If we can start correlating and creating recording rules directly from the recorded log, this will make the task simpler for users who already know the application well enough so that they don't have to re-run the Try Script to start correlating.

Ability to define the no.of iterations my transactions inside the script should run. Currently, this is done within the script. So, say if I have to run 5 iterations of each script and there 20 scripts in my project I will have to manually open each one and update the counts and change it back when needed. This is a pain. Easier way to do it would be outside of the scipt. Please consider.

Currently, SilkPerformer can not do extractions/parameterization from recorded true log. In LoadRunner, there is no need to run any replay before user can start extracting or adding text checks to the script. All of these can be done from the log captured during recording. Even when the script is changed and updated, the synchronization of the recorded log and the script is still maintained without any need to run Try Script.
Advantages of the described approach for the customers scenario will enhance SilPerformer's usability.
SI #2793265

The ability to easily add/remove CloudBurst agents for specific scripts/workloads in the same way that you can currently with locally installed agents.
Currently you need to do this on the 'agent assignment" tab of the Workload Configuration dialog but it would be useful if CloudBurst agents were treated just as local agents.

Currently if you wished to implement restrictions you have to go into each policy and add a Grant for each user, if a way to simply inact these policies globally (for all policies and all users) was added then it would save customers lots of time.

Provide a tutorial on how to work with Restful Webservice with Silk Performer SOA Edition with topics like:
- Restful Quickstart
- JSON / REST
- XML / REST

I would like to be able to post my Silk 4J test results in a format that all team members can view. I wish there were an option on the to export or saveas html for xlg files.

Exporting truelog for a xls, html or pdf to usnig that results

The in private mode set in IE by default for SP 15 onwards is interfering with the recording on some environments which don't allow in private mode to be used. When this happens the in private argument needs to be removed or IE wont open. It would be beneficial to either remove this, or have this as a separate IE profile so users could select whether they wanted to use in private or not. Alternatively if the installer could check if the gpo which disables this functionality is in place and install the appropriate application profile.

The requirement for this enhancement stems from the business need of being able to create multiple workloads with each workload serving a specific purpose (for example to test a specific browser type cross test scenario). Each workload is configured to test a specific browser and/or scenario and therefore needs to retain its response time thresholds for comparisons against future results.

Unfortunately, currently when you take a new baseline all existing response time thresholds are overwritten, making comparisons against future results difficult.

SI #2780163

Maintaining SilkPerformer test results in SilkCentral over the long duration.
To generate Silk Performer like report you need to know lots of load test specific parameters like TestDefExecIDpkfk id. It should be easier to comparing results across multiple execution. When using the Repository it’s really easy, a LoadTest id gets generated; but when we store results in SilkCentral the load test id is zero.

Ability to automatically run a load test, generate the report in html format and generate a cross load result of new build against previous build (baseline) to detect the performance imipact (html format), without the manual involvement. Thus the command line features of silk performer components are very important.

Up to and including SP10 when running a test the new results subfolder would keep track of and increment a Run number. Starting with SP15 the introduction of using the workload name and adding a timestamp to the name of the results folder, the results folder name defaults to the workload name and does not "remember" the previously used folder name. Please bring back the Run number! It is much easier for reporting and tracking.

Include a parameter in the MeasureStart and MeasureStop function to exclude the thinktimes within.

Having to launch Perfexp as the remote server user should be improved. I should be able to give a user account with the relevant permissions when monitoring perfmon.

When using multiple instances of Performance Explorer on different machines; have an option to start monitoring and "write data" for all of these monitors.
This is already possible using the command line but a GUI option would be helpful.

Currently, SilkPerformer automatically connects to the internet when you start the workbench. It connects to some CloudBurst servers and to Microfocus. While this may be considered useful for some customers, it's quite annoying when your Silk installation can't reach the internet. Please make it an option you can disable.

Limit can be workaround as described http://community.microfocus.com/borland/test/silkperformer-applicationperformancetesting/w/knowledgebase/10249.why-are-some-jmx-measures-not-written-to-tsd-file-even-though-they-can-be-monitored-with-performance-explorer.aspx (old KB #20624).

Please consider implementing the associated Change Request