Enterprise Process Templates
We are investigating the level of configuration possible with the enterprise process templates. It appears at first glance that children templates can only configure their template as fine as the xmlns level (Types and Attributes, Enumerations, Workflows, Editor Presentations, etc). In other words, a child is either configuring all or none of an entire xmlns. Is this true?
We need a finer level of configuration than the xmlns to make this enterprise process work. Take enumerations for example. A child process must be able to make a change to one enumeration type while still accepting all other enumeration type changes from its master.
Can someone please better explain the level of master-child configuration available?
Kyle Christianson
IBM STG Rational Solutions Team
We need a finer level of configuration than the xmlns to make this enterprise process work. Take enumerations for example. A child process must be able to make a change to one enumeration type while still accepting all other enumeration type changes from its master.
Can someone please better explain the level of master-child configuration available?
Kyle Christianson
IBM STG Rational Solutions Team
2 answers
Hello Kyle,
You are correct that the level of granularity for configuraton data is the xmlns.
In the case of enumerations, customizing one enumeration in the child copies all existing enumerations into the area. This overrides the information coming from the process provider.
Please file an enhancement request for smaller level of granularity so that we do not lose track of your needs.
Thanks,
Martha
Jazz Developer, Process Team
You are correct that the level of granularity for configuraton data is the xmlns.
In the case of enumerations, customizing one enumeration in the child copies all existing enumerations into the area. This overrides the information coming from the process provider.
Please file an enhancement request for smaller level of granularity so that we do not lose track of your needs.
Thanks,
Martha
Jazz Developer, Process Team
We are investigating the level of configuration possible with the enterprise process templates. It appears at first glance that children templates can only configure their template as fine as the xmlns level (Types and Attributes, Enumerations, Workflows, Editor Presentations, etc). In other words, a child is either configuring all or none of an entire xmlns. Is this true?
We need a finer level of configuration than the xmlns to make this enterprise process work. Take enumerations for example. A child process must be able to make a change to one enumeration type while still accepting all other enumeration type changes from its master.
Can someone please better explain the level of master-child configuration available?
Kyle Christianson
IBM STG Rational Solutions Team