Control the auto-stereotyping rules
Each rule has its own switch, stored in the project. Turning one off stops it applying its stereotype to anything else; it leaves whatever it has already applied in place.
Switch a rule off
- Open Options → Project.
- Select the Touchstone group. It carries every project option this Resource declares, not only the rules.
- Clear the switch for the rule.
| Switch | Stops |
|---|---|
| Auto-apply <<Attribute>> stereotype to Concept properties typed by a PrimitiveType or an Enumeration | «Attribute» on a Property owned by a Concept and typed by a PrimitiveType or an Enumeration |
| Auto-apply <<Relation>> stereotype to Concept properties typed by a Concept | «Relation» on a Property owned by and typed by Concepts |
| Auto-apply <<StepAction>> stereotype to CallBehaviorActions calling Steps | «StepAction» on a CallBehaviorAction owned by and calling Steps |
Save the project to keep the choice. The setting travels with the model, so a colleague who opens it — or a Teamwork Cloud user who updates — gets the same behaviour. That is the point of storing it in the project rather than on the workstation: whether a model follows the method is a property of the model.
A switch is enabled unless someone turned it off, and the group appears only in projects that carry the Touchstone Profile.
Switch a rule back on
Set the switch again. The rule resumes on the next edit that brings an element into its scope — it does not sweep the model to catch up.
An element already in place is therefore not stereotyped by re-enabling alone. Touch it: retype the property, or rebind the action's behavior. Re-assigning a field the value it already holds does nothing, because the model fires no event when the old and new values are equal.
Make an existing model catch up
Apply the defining stereotype last. Applying «Concept» to a Class sweeps the properties it owns and the properties typed by it, so «Attribute» and «Relation» follow; applying «Step» to an Activity sweeps the actions it contains and the actions that call it. Stereotype the definitions, and the usages follow.
Turn everything off
Clear every switch in the group. There is no master switch and no system property.
The engine behind the switches, the gates it applies and why the switch lives in the project rather than on the workstation are Anvil's: How auto-stereotyping works.