EPM Automate Working Directory Behavior Change

Summary:

Recent EPM Automate updates changed how files are generated and stored, redirecting outputs to the default ProgramData folder instead of the current working directory. This impacts multiple commands and breaks existing automation scripts, schedulers, relative-path workflows, and isolated execution environments. Requesting either restoration of the previous behavior or a supported way to configure the working/output directory for backward compatibility.

Content (please ensure you mask any confidential information):

I would like to raise a concern regarding the recent changes in EPM Automate file handling behavior.

Historically, EPM Automate commands generated and consumed files relative to the current working directory where the script was executed. This behavior was predictable, aligned with standard command-line tool conventions, and allowed existing automation frameworks to work reliably using relative paths and isolated execution folders.