...
Environments are collections of variables that can be referenced within fields of your responder or action suite. You can use environment variables to specify endpoints, database table names, connection properties, such as login credentials, and so on. The names of variables will be substituted with the assigned values in the active environment. By switching which environment is the "active" environment, you can dynamically switch the environment-specific values at runtime.Environments can also be used to switch virtual asset modes. For example, assume you configured a responder to forward traffic to an external endpoint. By using an environment variable for the endpoint (instead of a fixed value), you can easily redirect message forwarding to different endpoints. This allows .pva files to act like proxies; one environment can point to a real asset while another points to a virtual asset. Environments are automatically defined when you generate a Parasoft asset from a definition, such as WSDL, but you can also manually define environments as described below.
...
You can right-click on a variable and choose Mask Variable Value to hide the value in the interface.
If Masked Environment Variables Sensitive Data is enabled in your preferences (see see Miscellaneous Settings), masked environmental variables will also be hidden from traffic viewers, REST Clients, JSON/XML Data Banks and Assertors, and in the Event Monitoring Details.
...