Our organization has allowed applications to be assigned to multiple portfolios. A great capability in Mega APM.
This has had the uninteded consequence of double counting applications when aggregating from a portfolio perspective.
We do believe that it allowing applications to be associated with multiple initiatives / portfolios does make sense in the context of complex portfolio transformation.
We would prefer to NOT include a discriminator in the name of the portfolio.
We could add a MetaAttribute to the portfolio metaclass, but again that would require a customization.
Thoughts? Suggestions?
Thanks!
