-
-
Notifications
You must be signed in to change notification settings - Fork 272
Label Expressions
Expression | Display |
---|---|
${name} |
Name |
${documentation} |
Documentation |
${content} |
Text content of a Note |
${type} |
Type of object |
${viewpoint} |
Viewpoint name (applies to folders and diagram objects in ArchiMate Views) |
${strength} |
Applies only to ArchiMate Influence connections and displays its Strength, if set |
${properties} |
Display all Property key/values in a list like "key: value" |
${propertiesvalues} |
Display all Properties' values in a list |
${properties:separator:key} |
Display the values of all instances of the given Property having "key" as key, concatenated using "separator" as separator |
${property:key} |
Display the value of the Property whose key is "key" |
model
- references the current Model
view
- references the current View
mfolder
- references the folder for the current ArchiMate concept in a View
vfolder
- references the folder for the parent View of an object
<relationship>:source
- references the source object of the first connected relationship with the given name (triggering
, access
, specialization
, composition
, assignment
, aggregation
, realization
, serving
, influence
, flow
, association
)
<relationship>:target
- references the target object of the first connected relationship with the given name (triggering
, access
, specialization
, composition
, assignment
, aggregation
, realization
, serving
, influence
, flow
, association
)
connection:source
- references the source object of the first non-ArchiMate connection
connection:target
- references the target object of the first non-ArchiMate connection
Expression | Display |
---|---|
$model{name} |
Display the value of the name of the model |
$model{documentation} |
Display the value of the documentation of the model |
$model{property:key} |
Display the value of the Property in the model whose key is "key" |
$view{name} |
Display the value of the name of the parent View |
$view{documentation} |
Display the value of the documentation of the parent View |
$view{property:key} |
Display the value of the Property in the parent View whose key is "key" |
$mfolder{name} |
Display the value of the name of the parent folder of an ArchiMate concept |
$mfolder{documentation} |
Display the value of the documentation of the parent folder of an ArchiMate concept |
$mfolder{property:key} |
Display the value of the Property in the parent folder of an ArchiMate concept whose key is "key" |
$vfolder{name} |
Display the value of the name of the parent View of an object |
$vfolder{documentation} |
Display the value of the documentation of the parent View of an object |
$vfolder{property:key} |
Display the value of the Property in the parent folder of the parent View of an object whose key is "key" |
$composition:source{name} |
Display the value of the name in the source object connected by the first Composition relationship |
$triggering:target{documentation} |
Display the value of the documentation in the target object connected by the first Triggering relationship |
$connection:source{name} |
Display the value of the name in the source object connected by the first non-ArchiMate connection |
$connection:target{documentation} |
Display the value of the documentation in the target object connected by the first non-ArchiMate connection |
Some core Label expression can be used with folders. Folder label expressions affect the display of child objects, not the folder itself. Folders inherit the label expression of their parent folder.
An example:
${name} ${viewpoint}
- When applied to a folder containing Views, each View will display its name and viewpoint (if set)
If you value and use Archi please consider making a donation. Thanks!
- Developer
- About using Archi or ArchiMate
- Label Expressions
- Add letters to elements to distinguish between layers
- Archi Command Line Interface
- How to create a packaged version of Archi (including configuration and plugins)
- How to create your own report for Archi
- SQL queries in the HTML report
- Pattern based modelling with Archi
- ArchiMate language customization in Archi
- How to disable the "Check for Updates..." menu item
- The Archi.ini File
- Roadmap or potential new features
- Feature requests, the roadmap and managing expectations
- HTML export v3
- List of feature requests and potential roadmap items
- Generate Deliverables (Reporting) Requirements
- Sketch and Canvas revamp ideas
- Ideas for a nice and elegant way to implement profiles and concepts customization
- Roadmap for Archi 2.8
- Known issues
- Other