Environment Configuration

1. What is an Environment?▸

An Environment represents a target system where rating and scenario execution can be performed, such as Design, Development, QA, Staging, or Production.

2. Why do I need to configure an Environment?▸

Environment configuration allows the platform to connect to the appropriate rating engine or deployment endpoint used for scenario execution and analysis.

3. What is the difference between Environment Name and Environment Type?▸

Environment Name identifies the specific environment (e.g., QA, Staging, Production).

Environment Type categorises the environment based on its purpose (e.g., Design, Development, Testing, Production).

4. Can multiple products use the same Environment?▸

Yes. An environment can be configured for one or more products, provided the required rating engine and deployment configurations are available.

5. What is a Default Environment?▸

The Default Environment is automatically selected when users create and execute new What-If scenarios, reducing manual configuration effort.

6. What are Host and Port used for?▸

Host and Port define the connection details required to communicate with the target rating engine or application endpoint during scenario execution.

7. When should SSL Required be enabled?▸

SSL should be enabled when the target environment requires secure encrypted communication. This is typically recommended for QA, Staging, and Production environments.

8. Can I modify an Environment after it is created?▸

Yes. Administrators can update environment details such as host, port, product mapping, SSL settings, and default environment designation as business needs change.