How do you work with headings and restrictions? If I e.g. set at restriction on a heading, all requirements under that heading is removed in the generated document (regardless of the individual work items restrictions), but the heading itself remains. How should you do if you want the headings to be treated as normal work items, i.e. if a heading is configured to be discarded in a generated document, how do you actually make that happen?
One question to Maxim: can one use several levels of Master Specification? I mean CRS (customer req spec) and PRS (product req spec)? What about relationships of reqs from Master PRS, are the copied automatically from Master Specification to Product Variant Specification? What about the connected Work Items? Are they also instantiated?
You can certainly define several levels of Master Specifications. Just add the restrictions from the Feature Model into the Restriction Field. Relationships are automatically copied over as the Variant that you build uses the branching mechanism of Polarion. That means it's not a real copy, but a pointer to the original spec until you overwrite it. Test Specificatins work similarly to Master Specifications. You can either enact propagations or restrict them based on the Feature Model as well.
![[#2024MAMA] ROSÉ (로제), Bruno Mars - APT. | Mnet 241122 방송](http://i.ytimg.com/vi/dgGqD28J6aQ/mqdefault.jpg)
How do you work with headings and restrictions? If I e.g. set at restriction on a heading, all requirements under that heading is removed in the generated document (regardless of the individual work items restrictions), but the heading itself remains. How should you do if you want the headings to be treated as normal work items, i.e. if a heading is configured to be discarded in a generated document, how do you actually make that happen?
One question to Maxim: can one use several levels of Master Specification? I mean CRS (customer req spec) and PRS (product req spec)? What about relationships of reqs from Master PRS, are the copied automatically from Master Specification to Product Variant Specification? What about the connected Work Items? Are they also instantiated?
You can certainly define several levels of Master Specifications. Just add the restrictions from the Feature Model into the Restriction Field.
Relationships are automatically copied over as the Variant that you build uses the branching mechanism of Polarion. That means it's not a real copy, but a pointer to the original spec until you overwrite it.
Test Specificatins work similarly to Master Specifications. You can either enact propagations or restrict them based on the Feature Model as well.
In my polarian showing variant server is not found hiw can i get variant server