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

box 383 10 Notifications upon events 393 11 Macros . . . . . 3 Process configuration 1658 4 Protocols 1721 5 Items 1749 6 Supported functions 1779 7 Macros 1809 8 Unit symbols 1846 9 Time period syntax [OCR图片](/uploads/documents/2/c/2/2c2eedfd4603463d23c69c196a94327e/983f2a18.png) Macros User macros supported in item and item prototype names User macros are now supported in item names and item prototype names. Note It is also now supported to search for item name with the macros resolved, which previously was not supported. The item name with resolved macros is stored in a separate database table (item_rtname), which

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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|

and template groups 404 9 Templates out of the box 405 10 Notifications upon events 414 11 Macros 457 12 Users and user groups 468 13 Storage of secrets 475 14 Scheduled reports 481 8. Service 3 Process configuration 1498 4 Protocols 1548 5 Items 1573 6 Supported functions 1600 7 Macros 1631 8 Unit symbols 1666 9 Time period syntax 1668 10 Command execution 1668 11 Version compatibility after discovery: • Tags • Macros • Templates It is possible to link additional templates and add more tags and macros as well as update or remove existing tags and macros. Templates inherited from a

and template groups 387 9 Templates out of the box 388 10 Notifications upon events 397 11 Macros 442 12 Users and user groups 453 13 Storage of secrets 461 14 Scheduled reports 467 15 Data configuration ..... 1602 4 Protocols ..... 1666 5 Items ..... 1692 6 Supported functions ..... 1721 7 Macros ..... 1749 8 Unit symbols ..... 1787 9 Time period syntax ..... 1788 10 Command execution Administration menu no longer contains submenu related to alerting and user management. Also: • Housekeeping, Macros and Audit log that previously were submenus of Administration -> General have been moved one level

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