Thanks for your guidance. I was still unsuccessful using procedure #2. However, since you were successful I decided to try something close but different. The procedure I outline below worked fine. Why approaching it one way vs the other way does not work is beyond my current level.
Procedure to prevent the output of user-defined stereotyped Packages:
* Either use an existing eaDocX document or load up the profile and section for a new eaDocX document. I use the Compact Use Case profile provided in the ‘Exploring eaDocX’ examples.
* Bring up the ‘Profile’ tab (containing all elements potentially output)
* Single rt-click on ‘Package’ to bring up menu
* select ‘Create Profile for stereotype…’
* The element type will be grayed out ‘Package’
* In the ‘Available Stereotypes’ field, select ‘TestScriptContainer’
* In ‘Style’ field, select ‘None- do not print’
* Uncheck the ‘Copy formatting of un-stereotyped element’
* Select ‘Continue’
* Respond affirmatively to the pop-up confirmation dialog.
* Then using the ‘Generate Document’ menu: select ‘Full’
And this time the <> stereotyped packages do NOT print. Success!
The difference between the working and non-working version is how I call up the detailed ‘Package’ profile for editing. The non-successful method is to use the ‘Add Element’ button at the bottom of the Profile browser window. The successful method is to select the ‘Package’ element in the ‘Profile’ browser window to bring up the element’s menu and then select the ‘Create Profile for stereotype’ option.
The documentation talked about the former method as a means to prevent printing; the later I realized might be a backdoor access to the same sub-window and it was.
And I’ve just discovered (again) “Exploring – Inline formatting” and it describes how to prevent printing for different situations: by element type, by element stereotype, by specific element. The many detailed examples are great resources that I keep reviewing since I pick up fresh nuances on each read.
Thanks for your help.
