In the FT job we set the destination with a relative path as follows "../../rapidautomation/staging/smgr_log_00.txt". This needs to be resolved based on agent installed location.
In windows agent version '21.0.14+build.1747062623762' non java agent installed in E: drive, we can see the file is transferred to E drive where the agent is installed
U00011133 OK '27447' Bytes, '339' Records for file '/opt/Automic/Automation.Platform/ServiceManager/temp/smgr_log_00.txt'->'E:\Automic21\Agentsapidautomation\staging\smgr_log_00.txt' transferred. Duration '00:00:00'.
In windows agent version '24.4.0+hf.3.build.1747927237919 . It is installed in D: drive but the files are transferred to C :drive
U00011133 OK '27447' Bytes, '339' Records for file '/opt/Automic/Automation.
The use of relative paths and their behavior are (currently) not defined in the documentation.
As a workaround, the customer can use absolute paths in their JOBF definitions. Since the resolution of relative paths depends on the (target) platform, specifying absolute paths is more concise than using relative paths.
The product documentation will be enhanced to include this information.