Support dynamic variable substitution in Virtual Folder local file path (Local filesystem)

Currently in webMethods ActiveTransfer (tested on version 10.15), when configuring a Virtual Folder with a physical location mapped to the local file system, the "Local file path" field only accepts a static, hard-coded path (e.g., FILE://C:/Transfers/PartnerA/). There is no support for dynamic variable substitution within this field.

This is a significant limitation for organizations that need to route files dynamically based on contextual attributes such as:

• Username or partner ID (e.g., FILE://C:/Transfers/{username}/)
• Date or timestamp (e.g., FILE://C:/Transfers/{date:yyyy-MM-dd}/)
• Environment variables or custom ActiveTransfer variables
• Transfer metadata (e.g., {partner}, {sender}, {receiver})

Requested Enhancement:

Extend the Virtual Folder "Local file path" field to support ActiveTransfer variable substitution syntax (consistent with how variables are already supported in post-processing and scheduled actions), so that administrators can define a single virtual folder that resolves to different physical paths at runtime based on transfer context.

Business Impact:

Without this feature, organizations must create one separate virtual folder per partner, per environment, or per date-based directory structure — leading to configuration sprawl, increased maintenance overhead, and reduced scalability. Dynamic path support would significantly simplify multi-partner MFT deployments and align local filesystem behavior with the flexibility expected in enterprise MFT platforms