listsprite @enduml - application-state-flow ### 15.6 ArchiMate Macros #### 15.6.1 Archimate Macros and Library A list of Archimate macros are defined Archimate-PlantUML here which simplifies the creation Archimate is natively on the Standard Library of PlantUML. #### 15.6.2 Archimate elements Using the macros, creation of ArchiMate elements are done using the following format: Category_ElementName (nameOfTheElement from github, not from StdLib. All sprites are in grayscale, but most collections define specific macros that include appropriate (vendor-specific) colors. ## Example: ## 24 Skinparam command You can

You may also include the common.puml file, eg: !include , which contains helper macros defined. With the common.puml imported, you can use the NAME_OF_SPRITE(parameters...) macro. Example include the AzureCommon.puml file, eg: !include , which contains helper macros defined. With the AzureCommon.puml imported, you can use the NAME_OF_SPRITE(parameters...) macro may also include the common.puml file, eg: !include , which contains helper macros defined. With the common.puml imported, you can use the NAME_OF_SPRITE(parameters...) macro. Example

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 10 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495 7 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . host of the discovery rule. 14 New mass update options It is now possible to: • Mass update user macros defined on a host or template level • Mass unlink templates when using host or template mass update:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 10 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307 7 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . item. Low-level discovery macros in item preprocessing Low-level discovery macros now can be used in item preprocessing steps for item prototypes. User macros and user macros with context can be used in

Preprocessing and custom macros in low-level discovery Low-level discovery configuration has gained additional options of preprocessing the discovery result and extracting custom macros from the preprocessed Discovery rule filter| |In Zabbix 4.2|Discovery rule $\\rightarrow$ Preprocessing $\\rightarrow$ Custom macros $\\rightarrow$ Discovery rule filter|macros may be extracted and then the filter conditions are applied to the result. ## Preprocessing Low-level

Visualization 421 7 Templates 458 8 Templates out of the box 459 9 Notifications upon events 478 10 Macros 533 11 Users and user groups 543 12 Storage of secrets 550 8. Service monitoring 551 9. Web setup 1497 3 Process configuration 1526 4 Protocols 1607 5 Items 1626 6 Triggers ..... 1653 7 Macros ..... 1688 8 Unit symbols ..... 1713 9 Time period syntax ..... 1714 10 Command execution Exchange server increased by 24% in July (0.69) comparing to June (0.56)" The new expression macros and new macro functions ('fmttime' and 'fmtnum') are used to build this message.

Templates ..... 475 9 Templates out of the box ..... 476 10 Notifications upon events ..... 497 11 Macros ..... 550 12 Users and user groups ..... 560 13 Storage of secrets ..... 568 14 Scheduled reports configuration ..... 1589 4 Protocols ..... 1673 5 Items ..... 1691 6 Supported functions ..... 1718 7 Macros ..... 1771 8 Unit symbols ..... 1799 9 Time period syntax ..... 1800 10 Command execution reference is now the first parameter of history functions (as host/item) • Changed syntax for expression macros The outlined changes can be observed in the following examples: |New syntax|Old syntax|Comment|

7 Templates 407 8 Templates out of the box 407 9 Notifications upon events 413 10 Macros 467 11 Users and user groups 473 8. Service monitoring 479 9. Web monitoring 482 Protocols ..... 1267 5 Items ..... 1285 6 Preprocessing ..... 1311 7 Triggers ..... 1326 8 Macros ..... 1349 9 Unit symbols ..... 1369 10 Setting time periods ..... 1370 11 Command execution each trigger that now has a new Operational data field. This field accepts an arbitrary string with macros, most importantly, the $ \{ITEM.LASTVALUE<1-9>\} $ macro. ![Image](/uploads/documents/2

Templates ..... 343 8 Templates out of the box ..... 344 9 Notifications upon events ..... 348 10 Macros ..... 388 11 Users and user groups ..... 395 8. Service monitoring ..... 400 9. Web monitoring Installation 1002 3 Daemon configuration 1008 4 Protocols 1044 5 Items 1060 6 Triggers 1084 7 Macros 1104 8 Unit symbols 1116 9 Setting time periods 1117 10 Command execution 1118 11 Recipes correlation, while the trigger may still show a problem (changed {EVENT.VALUE} and {EVENT.STATUS} macros can be used instead) • Host is indicated using the {HOST.NAME} macro • Problem notifications have

266 4 Events 278 5 Visualisation 279 6 Templates 322 7 Notifications upon events 322 8 Macros 356 9 Users and user groups 358 7. IT services 364 8. Web monitoring 367 1 Web monitoring configuration ..... 969 4 Protocols ..... 1003 5 Items ..... 1003 6 Triggers ..... 1023 7 Macros ..... 1045 8 Setting time periods ..... 1057 9 Command execution ..... 1057 10 Recipes for [Image](/uploads/documents/9/a/f/c/9afcb1fb7c59648377bdf65886bee909/p11_1.jpg) Additionally, three new macros are supported in parameter fields - {ALERT.SENDTO}, {ALERT.SUBJECT} and {ALERT.MESSAGE}, resolving