Using Vault Variables for Dynamic File Paths Across Two Environments

Problem:
When migrating projects between two environments in Adeptia Connect, file paths can break if the secure server names differ.

For example:

• Environment 1 path: \\Env1-Server\ClientData

• Environment 2 path: \\Env2-Server\ClientData

Since Adeptia requires explicit server names for file paths (e.g., UNC paths), projects referencing one environment’s server path fail once deployed in another. Drive letters and vanity server names also don’t work reliably (e.g., Y:\ mount fails), making it difficult to maintain portability.

The requirement is:

• Define a server-level variable (e.g., $clientserver\clientdata).

• Ensure projects can move between environments without needing to manually update file paths.

• Keep client data on a separate secure file server (so .\solutions path cannot be used).

Solution:

This can be solved using Vault parameters in Adeptia Connect and a simple Custom Plugin.

Steps to Implement:

1. Create a Vault
   • Navigate to Configure > Security > Vault.
   • Create a new Vault and provide any name and alias name.
   • In the Parameters, enter the key name, and in the Value field, specify the full path of the source location.
   • Click Save.
     
     
2. Update the Process Flow
   • Add a Custom Plugin just after the Start Event, before the Source/Target Activity.
     
     
      

   • In the Custom Plugin activity, create a variable (e.g., var1) and set its default value in this format:

     {Vault.aliasName.key}

     Example:

     {Vault.VaultFP.path}

     (This refers to the Vault value you created above.)
      

   • In the Custom Plugin script, use the following code:

     String Path = service.getValueByName("var1");
     context.put("path", Path);

     

3. Update the Source Activity

   • In the Source Activity, create a variable at the activity level and map it with the path value from the context.
     
     

4. Run the process flow. The activity will dynamically resolve the correct file path depending on the environment where it’s deployed, without modifying the flow design.