> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/model-and-simulation/edit-a-model-schematic/create-and-manage-designs/display-attributes-and-variables-on-the-schematic.md).

# Display Attributes & Variables on the Schematic

## Display object attributes

To display the text for a device, signal, or pin attribute on the schematic:

1. Edit the attribute value as required.
2. Enable the **Visible** option.
3. Click **Done**.

The attribute text will be displayed in its default position near the associated device, pin, or signal. You can reposition it as needed by dragging it with the pointer cursor.

When you right-click a **visible attribute text** on the schematic, a context menu provides access to several editing and formatting commands.

### Set attribute text style

Attribute text styles can be configured in two ways:

* **Globally**, to affect all attributes that use the default text style.
* **Individually**, for specific attribute types.

When an attribute has its own text style defined, it is considered an override and is not affected by changes to the global attribute text style.

To configure attribute text settings globally, open the **Options** ribbon, click **Design Preferences**, and then select the **Text** tab. In large designs, there may be a brief delay while the displayed attribute text is updated.

Changing the **global attribute text style** affects all visible attributes that use the default style. Text positions and alignment may be adjusted automatically to accommodate the new font or size.

The setting applies to:

* Device names
* Signal names
* Bundle breakout labels
* Bundle pin labels
* Other attribute text displayed on the schematic

It does **not** affect:

* Border text
* Pin numbers

## Display design attributes and system variables

The text facility supports special entries called **variables**, which can be inserted into **text boxes**. When the text is displayed or printed, each variable is automatically replaced with the corresponding system value or attribute field value. If a variable name is not recognized, it is displayed exactly as entered.

Text variables are particularly useful for title blocks and other schematic annotations that require information such as:

* Date
* Page number
* Drawing title
* Revision level
* Engineer name
* Other [design attributes](https://www.opal-rt.com/docs/hypersim/model-and-simulation/edit-a-model-schematic/create-and-manage-designs/manage-attributes.md)

By using variables, this information only needs to be entered and maintained in a single location. Any updates are then reflected automatically wherever the variable is used throughout the schematic, ensuring consistency and reducing manual maintenance.

{% stepper %}
{% step %}

### **Create a text block**

In the **Home** ribbon, under **Draw Graphics**, select **Text**, then click in an empty area of the schematic to place a new text object.
{% endstep %}

{% step %}

### Type your content with **the variable name**

Using the correct prefix:

* $ for **system variables** (date, time, page info, filename)
* & for **attribute variables** (design attribute fields)

Example:

Creation Date: $DATECREATED\
Author: \&Designer
{% endstep %}

{% step %}

### **Press Enter to finish**

The variable is immediately replaced by its current value on the schematic.

In some cases, the displayed information may not refresh immediately. If this occurs, press the **End** key or select **Redraw** in the View ribbon to force the schematic to refresh and display the updated information correctly.

Right-click the text box and select **Properties...** to configure its text style, including the font, size, background, border and other formatting options.
{% endstep %}
{% endstepper %}

### **System variables reference**

<table data-search="false"><thead><tr><th width="200.111083984375">Variables</th><th>Description</th></tr></thead><tbody><tr><td><strong>$DATENOW</strong></td><td>Replaced by system date written mm/dd/yy. This is the current date as maintained by the system clock</td></tr><tr><td><strong>$TIMENOW</strong></td><td>Replaced by system time written hh:mm. This is the current time as maintained by the system clock</td></tr><tr><td><strong>$DATECREATED</strong></td><td>Replaced by date the file was created, as maintained by the file system.</td></tr><tr><td><strong>$TIMECREATED</strong></td><td>Replaced by time the file was created, as maintained by the file system.</td></tr><tr><td><strong>$DATEMODIFIED</strong></td><td>Replaced by date the file was last modified, as maintained by the file system.</td></tr><tr><td><strong>$TIMEMODIFIED</strong></td><td>Replaced by time the file was last modified, as maintained by the file system.</td></tr><tr><td><strong>$PAGENUM</strong></td><td>Replaced by number of the page (within the current circuit level) the text is on.</td></tr><tr><td><strong>$NUMPAGES</strong></td><td>Replaced by total number of pages in the circuit level.</td></tr><tr><td><strong>$PAGETITLE</strong></td><td>Replaced by title of the page the text is on, as entered using the Pages command.</td></tr><tr><td><strong>$PRINTPAGENUM</strong></td><td>Replaced by page number in the printed sequence within the current Print command. This is used to number pages within a hierarchical design. NOTE: This is only valid for printed output. When it is drawn on the screen, it will show the same value as <strong>$PAGENUM.</strong></td></tr><tr><td><strong>$PRINTNUMPAGES</strong></td><td>Replaced by number of pages that will be printed by the current Print command. This is used to number pages within a hierarchical design. NOTE: This is only valid for printed output. When it is drawn on the screen, it will show the same value as <strong>$NUMPAGES.</strong></td></tr><tr><td><strong>$FILENAME</strong></td><td>Replaced by name of the design file, not including its directory path.</td></tr><tr><td><strong>$FILEPATH</strong></td><td>Replaced by name of the design file, including its directory path. If the file hasn’t been saved, this will be empty.</td></tr><tr><td><strong>$CIRCUITNAME</strong></td><td>Replaced by name of the circuit being printed. In the topmost circuit of a hierarchical design (or in any flat design), this is the same as $FILENAME. In a subcircuit, this will be the hierarchical name of the circuit.</td></tr></tbody></table>

The format used to display **date and time values** is determined by the Regional Settings control panel in Windows.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/hypersim/model-and-simulation/edit-a-model-schematic/create-and-manage-designs/display-attributes-and-variables-on-the-schematic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
