When working within runtime environments, it's crucial to grasp the various activated components that facilitate seamless operation. These components include:
- Activated (Runtime) Environments
- Activated (Runtime) Functions
- Activated (Runtime) Environment Fields
- Activated (Runtime) Connections
In this context, we focus on runtime functions and how their state influences their usability within activities.
Key Components
Activated Environments:
These are the environments that have been set up and made operational. They form the backbone of your system, hosting all the necessary configurations and data connections.
Activated Functions:
These are functions within the environment that can either be in an API Active state or an API Internal state.
API Active functions are available for productive use and can be reliably integrated into activities.
API Internal functions remain in a developmental or testing phase and are not yet intended for live, operational use.
Activated Environment Fields:
These fields are integral to the environment and can be used to customize and parameterize activities. They provide the necessary inputs and controls that the activities require to function effectively.
Activated Connections:
These are the established data connections that link your environment with external data sources or other systems. Ensuring these connections are activated is crucial for maintaining data flow and system integration.