About Action Parameter Bindings

Action parameter bindings represent the aggregate of an entity and its parameters in the context of an application role. Action parameter bindings enable you to map source data (a conceptual model entity, attributes defined for a conceptual model entity, and components defined for a conceptual model entity) to target data (parameters defined for technical actions).

The mapping information, or binding, is contained in an Action Parameter Binding (APB) entity. APB entities enable you to identify source data elements in a conceptual model and define how they contribute to the generation of technical action data elements.

For example, you may have a Network Address Template Resource entity defined with multiple technical actions. You can create an action parameter binding to map the source data from the conceptual model (data defined on Network Address Template Resource entity or elsewhere in the conceptual model) to the data that is required by a set of technical actions.

At run-time, action parameter binding configuration facilitates the analysis required during the Calculate Technical Actions (CTA) provider function, enabling CTA to determine the differences between a requested service configuration and the current service configuration. After the delta is determined, CTA can identify the technical actions required to affect the necessary changes in the network.

See Design Studio Concepts for more information about how action parameter bindings contribute to the Calculate Technical Actions provider function. See the Oracle Communications RSDOD Reference Solution Developers Guide for more information about generating CTA metadata.