This facility will be delivered in ZMF 8.3
In ERO area audit with ARS, we would like an enhancement, much like complex/participating schemes, were you can point all your recompile/relinks from auto-resolve to a specific package within the release.Ā
This makes the management and deployment of those components easier to implement.Ā Many of our apps that use ERO converted from the complex/part. scheme and liked they idea they could do that in that setup but not in ERO.
This facility will be delivered in ZMF 8.3
In ERO area audit with ARS, we would like an enhancement, much like complex/participating schemes, were you can point all your recompile/relinks from auto-resolve to a specific package within the release.Ā
This makes the management and deployment of those components easier to implement.Ā Many of our apps that use ERO converted from the complex/part. scheme and liked they idea they could do that in that setup but not in ERO.
There is an existing decision process for choosing which of the area feeder packages is used for the results of an autoresolve. It takes into account the application of the main component being rebuilt along with other criteria. It is possible (although it will have to be researched) that we could implement a 'preferred package' list (you would need one per appl represented in the release) for the results of autoresolve actions. The autoresolve processor would then use one of these as long as it didn't break existing selection rules. We would have to message something about the decision process.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
