cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Enable AsStored configuration in case of multiple seeds for Promotion Request Collector

Enable AsStored configuration in case of multiple seeds for Promotion Request Collector

Promotion Request Collector does not allow the usage of the "AsStored" configuration if multiple seeds were selected, in order to prevent collecting the same dependent objects in different Versions. Anyway, many customers nowadays want to rely rather on the AsStored configuration for the Promotion Objects Baseline than on the Latest configuration. And this decission was made disregarding the amount of seeds. So for these customers, the AsStored collection should work as well for multiple seeds. It will be a better idea to utilize an UI-Validator after the Collector step rather than just disabling the AsStored option, to avoid the multiple Version-conflict of dependents. Since most of realworld data structrures would work very well with AsStored combined with multiple seeds without resulting in version conflicts of common members.

4 Comments
Level 12

We will be introducing a TAN providing configuration guidance to enable users to pick As-Stored when there are multiple seed objects.

Some notes on the behavior

  1. It will appear in all Edit Filter locations for the Collector.  If desired you could write a validator to control that it shows in only specific environments
  2. The collector will still only show one Version for any given master.  If you have Asm 1 A.3 which use Child B.2 and Asm 2 A.7 which uses Child B.3 the collector will only return one version.  In this case if Asm 1 is the first seed it will return B.2.
    1. If this is on the Promotion Request you will get an indicator that a newer version exists and you could still collect (separately) and add it to the Promotion Request
    2. In a Change we always work with the Latest iteration for the given Revision so it would resolve to B.3
Level 3

Hallo Jeffrey,

with the new possibility to define manually As-Stored as the collection configuration for multiple seeds, could it be also possible to define, only for the promotion request wizard, the default collector configuration to use always As-Stored?

Regards

Christopher

Level 12

Christopher - we looked at this but its a much more significant project.  In general having better control over Config Spec or Default filters for these tools is of interest in the future.

Community Manager
Status changed to: Current Functionality