Skip to main content
Status: Delivered

This has been delivered in ZMF8.3 CR 131927 covers this idea.

Duplicate Components in same CMN Release - but different packages - should be reported in TestArea - even if no Checkin is done yet.

We had the case - where 2 programmes have create a new component with the same name - but in different application-packages (and different applications).

The more often case isĀ - that the same component is in different packages of the same application.

The problem was - that ERO TestArea does only report this - after the first has finished the work - and went to Area Checkin.

I would be much better, if ERO TestArea could already report duplicate components in different packages - as early detection. To solve this problem later - is always more effort.

Status: Delivered

This has been delivered in ZMF8.3 CR 131927 covers this idea.

Duplicate Components in same CMN Release - but different packages - should be reported in TestArea - even if no Checkin is done yet.

We had the case - where 2 programmes have create a new component with the same name - but in different application-packages (and different applications).

The more often case isĀ - that the same component is in different packages of the same application.

The problem was - that ERO TestArea does only report this - after the first has finished the work - and went to Area Checkin.

I would be much better, if ERO TestArea could already report duplicate components in different packages - as early detection. To solve this problem later - is always more effort.

This does not belong in the TestArea function as that it totally different and is related to what is checked into or not checked into an area. This functions is also called when an area it blocked and this may cause issue with getting the release install. 

This should be a totally different function. Not sure where to put this function yet. However, at checkout the history shows where the component is with in a given application. With ERO that would be very similar except it has to include other applictions in the case of shared baseline/area libraries. More likely a function on the release to check components for duplicates.

Terms & ConditionsAccessibility statement