> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/pim3/reference/product-model-setup/product-structures/product-structure-details/variation-definitions/variation-definition-details.md). # Variation definition details ## Variation definitions ### Alias An alias for this variation definition. The alias must not contain special characters or whitespaces. ### Display name A display name for this variation definition. ### Defining properties The properties whose values define one variant from other variants of the same product. ### Name properties The properties you want to include in the name. ### Name pattern Use the name pattern to dictate how property values should be used to render the name. Use {0}, {1}, {2} etc. to indicate in the pattern where you want the attributes you choose to be rendered. ## Defining attributes ### Defining attributes to always show Defining attributes are by default only available to variants using a variation definition containing that specific defining attribute. If you want a defining attribute to always be available no matter if it is part of the variation definition, select it here. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.struct.com/pim3/reference/product-model-setup/product-structures/product-structure-details/variation-definitions/variation-definition-details.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.