GetEnvironmentProperties returns information about the application’s environment. It takes no inputs and the outputs depend on which environment it is in. These outputs come from the EPInstallation.config file, but any changes made to the file will not be reflected in EASYProcess until the application is closed and reopened. GetEnvironmentProperties is generally used to fill in part of a file path that is being created, allowing us to use one process to create different file paths for different environments.
GetEnvironmentProperties Use Examples
Creating a File Path
In this example we are using GetEnvironmentProperties to fill in part of a file path being created to save an image at.
In this case, GetApplicationProperties is being used alongside GetEnvironmentProperties to create the file path, but we will only be focusing on GetEnvironmentProperties. Since this service takes no inputs, it just has to be connected to the process flow and we will be able to use its outputs in services that follow it. Here is what the output will look like:
Below we can see an evaluate expression inside of the ImageInfo evaluate service from the canvas above. This uses the PhysicalPath node of GetEnvironmentProperties to create a new expression named SliderPath.
The SliderPath expression is then used in the last service to save a file in the directory that it points to.
The benefit of using GetEnvironmentProperties in this situation is being able to save an image to different directories based on the environment you’re in. If this process were run in the Development Environment, the image would be saved in C:\EASYProcess\eCommerce_DV\EASYCommerce\Images\Slider_Images.
But if this were to be run in the QA Environment, the image would be saved in C:\EASYProcess\eCommerce_QA\EASYCommerce\Images\Slider_Images.