Scenario. Differing Dependencies Across Application Object Instances
Scenario. Differing Dependencies Across Application Object Instances
The following scenario will use an application with a complex set of dependencies where the dependencies in the deployed run-time application are different from the dependencies in the updated design-time application.
The following image shows the design-time and run-time applications:
The set of dependencies in the deployed run-time application do not match the set of dependencies in the updated design-time application to reflect how design-time and run-time instances of application objects are isolated in data structures. Since the time that the application was deployed, multiple users might have edited the design-time objects and redefined their dependencies without altering the run-time objects.
For example, the deployed application contains a mapping
Mapping B
that uses a data object
Physical Data Object B
and a mapping
Mapping C
that uses a mapplet
Mapplet A
.
Meanwhile, the design-time application has been revised such that the mapping
Mapping B
uses the mapplet
Mapplet A
and the data object
Physical Data Object B
, and the mapping
Mapping C
uses a reusable transformation
Reusable Transformation C
to transform the data in the data object
Physical Data Object B
.
Because the sets of dependencies are different across the design-time and run-time objects, you must use both the design-time and the run-time objects to identify a selected object's indirect and remote dependencies.