Calling Data file from Temporary Results directory on Remote Agent, using ProcessInitialize, fails
Upon a remote agent machine during a load test execution or TryAgent test, a temporary folder called LocalData_* is created which will house, temporary project files, including .bex and .ltp files. The folder's location is, C:\Users\Public\Public Documents\Silk\Silk Performer 18.5.
When the tests have completed, the folder is cleared and removed from the system.
In prior versions of Silk Performer (pre 18.0 and 18.5), when a data file was added to the project via the Data files section.
That file too was also transferred to the temporary directory upon the agent machine.
It meant that when logic was included within the script using the Process Control functions, ProcessInitialize() and ProcessStart(), the temporary data file could be successfully called and utilized during test execution:
Due to a change of approach in recent versions for caching data files on agents, the data file was not transferred to the temporary LocalData_* folder. Meaning the use of the above logic would fail, as the file did not exist.
With the application of hotfix 3 for Silk Performer 18.5, a version of the data file is now available once again within the temporary LocalData_* folder upon the remote agent system.
Therefore including logic such as the example above within your script (GetDirectory / Process Control functions), that intentionally call a data file from temporary folder on an agent machine, will now succeed.