Developer Tool Guide

10.4.1
- 10.5.6
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.0

Back Next

Example. Identifying Affected Objects

The following example shows how you can identify the affected objects that the Incremental Deployment Wizard fetches from the run-time application.

You might have an application that contains two mappings

Mapping A

and

Mapping B

that share a physical data object

Data Object A

, and a workflow

Workflow B

that uses the mapping

Mapping B

. After you deploy the application, you edit the mapping

Mapping A

and decide to update the mapping in the run-time application.

You create a patch that inherits only direct dependencies and select the mapping

Mapping A

. Because you select the mapping, the patch inherits the data object that the mapping uses,

Data Object A

Since the wizard expects the Data Integration Service to replace the run-time instances of the mapping and the data object, the wizard locates any parent objects that use the mapping or the data object in the run-time application. The mapping

Mapping B

uses the data object, so the wizard marks the mapping as an affected object.

Because the mapping

Mapping B

will be updated in the run-time application and the workflow

Workflow B

uses the mapping

Mapping B

, the workflow

Workflow B

is also an affected object.

The following image shows the design-time and run-time conditions, the selected mapping, the dependencies that the patch inherits, and the affected objects: