# Phoenix Keywords

Phoenix features over 2000+ unique keywords. Keywords are used in Text Marks, Bearer Bars, Custom Marks, and Barcodes to create dynamic marks that update in real time as the underlying data changes. Text keywords are also used during export to create unique, job-specific filenames automatically.

# New in 8.0

The Dynamic Keywords have changed during the Phoenix 8.0 release, and some keywords from older versions are no longer available in Phoenix. Note that no new keywords were deprecated or changed since version 7.0. The list of changes from 6.0–7.0 can be found at the following links along with more info:

• Keyword Mappings
• Deprecated Keywords

#Index Numbers (.#.)

In many keywords, you will see a # symbol separating components of a keyword. This symbol represents an index number. This means that it could apply to any number of potential items. For example, <project.product.#.layouts> is a keyword that returns which layouts a given product is on. To specify which product, you simply replace the # with the number of the product you want. So if you want to find the layouts that the first product in the project is on, you would use <project.product.1.layouts>

#Number Padding (.pad.#>)

Phoenix 7.0 added support for padding integer-based keywords by a specified amount. This allows you to ensure that returned have the same number of characters, regardless of the actual value. For instance, if a project has 10 layouts, previously the <layout.index> keyword would return 1 for the first layout, 2 for the second layout, and so on up to 10 for the tenth layout. Now, you can add padding, so <layout.index.pad.3> would return 001, 002, and 010 for those same layouts!

# Navigating the Keywords Documentation

The complete list of text keywords available in Phoenix is below. Keywords in Phoenix are contextual. For instance, bleed can refer to a component bleed with a keyword like <component.bleed.margin> or a page bleed like <part.page.#.bleed.bottom> or any other number of bleed values. Even though the context is different, bleed is still bleed, just the context of what bleed you want is what is changing.

Our keyword documentation is setup to reflect these relationships and the context. To navigate to a definition, simply click on any part of a keyword to go to that part's page. From here, you will find any definitions that apply, as well as links to other keyword parts. If you are looking for a particular definition, the easiest way to find a specific keyword (out of the over 800 available!) is to use the Find feature in your browser. Press command (or control) + "F", then type in the keyword you're searching for. That will take you to the keyword on this page. From there, you can click on the link to navigate to that keyword's page.

#CSV Export Keywords

Phoenix 8.0 introduced the ability to create custom csv reports exported from Phoenix projects. These reports allow you to create a csv with exactly the data that you need, and these are configured with the use of keywords

There are four types of keywords that are exclusive to this CSV export, so you will not be able to use them in other places in Phoenix. These keywords are lane, ribbon, roll, and lane. Each of these keywords is only available in CSV export and only for roll-related data sources.