Select Doctype

First you choose the doctype. For status codes the use of the Tag doctype seems natural.

Create Parent Tag

To group all our status codes we define a parent tag document first.

You may add any information to this document, but its main purpose is to hold our three status tokens together.

Create Value Range

Add as child to the parent tag a new document for each value of your value range. All of these values are based on the Tag doctype.

Now we need to add some document properties to define the order of the values (Sort Key) and their visual representation (CSS Style Information).

Please make sure that the value for the CSS Style Information is indeed proper CSS (including the semicolon at the end!)

Note that the third column of the table contains document property controls where we add the hide control. This will signal the renderer that this line is of no interest to our readers and is therefore not visible in the view mode of the document.

Add one document for each value of your range as a child to the Status tag document.

This is the result:

$<Status> = [${Name}]

Define Range Property

To use the value range in your documents you typically ask the template author to define a blueprint and add the configuration to the template. In this example we will do this manually first. That is the a property is manually added to a document instance by the author.

<tr>
  <th>Status</th>
  <td>
    <ac:structured-macro ac:name="projectdoc-name-list">
      <ac:parameter ac:name="doctype">tag</ac:parameter>
      <ac:parameter ac:name="property">Status</ac:parameter>
      <ac:parameter ac:name="where">$&lt;Parent&gt;=[Status]</ac:parameter>
      <ac:parameter ac:name="empty-as-none">false</ac:parameter>
    </ac:structured-macro>
 </td>
 <td> </td>
</tr>

Select a Value

To select a value the author can check the valid set of values by deselecting the Empty Where Clause Handling.

Select one of the values and set it as the value to the Names parameter.

Save the macro and then save the page. The result is this:

Clumsy Selection

The author needs to use a workaround employing the Empty Where Clause Handling parameter to get a list of valid values in the browser. She then needs to type (or copy-paste) the value.

PDAC-632 - Getting issue details... STATUS

Multiple Values allowed

 The Name List Macro also allows to specify multiple values.

While this is a valid use case on its own, it does not support the restrictive character of the use case we show here.

PDAC-630 - Getting issue details... STATUS

No Enforcement for Value Range

The Name List Macro currently does not force users to choose one of the values.

This is a valid use case to support authors to add values on the fly. It does not support the restrictive character of the use case we show here.

PDAC-631 - Getting issue details... STATUS