What kinds and number of project areas can participate in a shared configuration in CLM 5.x M6?
I received this question:
Is it a requirement that management of configurations in 5.x is within a single CLM life cycle project? Can the life cycle project have multiple instances of associated project from same tool (e.g. 1 DNG, 1 RTC, 2 RQMs or an instance with 1 DNG, 1 RQM, and 2 RTCs one agile one waterfall)?
Is it a requirement that management of configurations in 5.x is within a single CLM life cycle project? Can the life cycle project have multiple instances of associated project from same tool (e.g. 1 DNG, 1 RTC, 2 RQMs or an instance with 1 DNG, 1 RQM, and 2 RTCs one agile one waterfall)?
One answer
Any number of project areas of the various CLM applications can participate in a shared configuration. This can include multiple RM, CCM, QM, and DM project areas. The key constraints in 5.x M6 are (1) the project areas must be OAuth friends; and (2) you can't / shouldn't include the same project area twice. The latter constraint exists to avoid version skew (the same components/artifacts at two different versions) -- we haven't addressed this yet.