Changes to same objects in path (0055) identifies what other transports in a transport path contain the same objects as those contained within the transport(s) being analysed. It was requested by a few existing customers that want to stop new versions being imported into a system until an older version that has already been imported into that system had been tested and deployed to Production
The analyser can look for the object in other transports i) Forward, ii) Backward or iii) Forward and Backward in the Path, depending on how the exact requirement
Parameters
| Parameter | Description |
|---|---|
| CHECK_BACK_AND_FORWARD | Define whether you want to look only Forward, only Backward or both Backward and Forward in the Path. |
| EXCLUDE_MERGE | Can be used to exclude Merge transports from the Analysis results. |
| EXCLUDE_PROJECT | Can be used to exclude all Transports relating to Business Tasks associated to the same Project(s) from the Analysis results. |
| EXCLUDE_TOC | Can be used to exclude Transport of Copies transports from the Analysis results. |
| IGNORE_SAME_TASK | Can be used if you want to ignore other transports assigned to same Business Task that contain the same object(s). |
| KEY_NO_RELATED_VIEWS | By default, when transporting table entries, views that use the same table in key fields will be considered a conflict. This behaviour can be turned off with this flag. |
| KEY_NO_WILDCARDS | If this flag is set, wildcards are not considered when searching for conflicting table entries. |
Post your comment on this topic.