documentation page. The links are placed under the question mark icon, when opening the item helper window from the item configuration form (click on Select next to the item key field). Preprocessing Advanced to filter problems by their state (unacknowledged/acknowledged/acknowledged by me); • Standard window close button has been added to popup windows intended for configuring and mass updating of the map is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory,

copying items, triggers and graphs between hosts or templates are now opened in a modal (pop-up) window. 6 What’s new in Zabbix 6.4.1 MariaDB 10.11 support The maximum supported version for MariaDB is is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, preferably a subdirectory of the source dir. For example, E:\pcre2-10.39\build. 5. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui

single problems for a defined time period. A problem can be suppressed through the problem update window that is opened when acknowledging a problem: For more details see Problem suppression. Multiple italics. Miscellaneous • The form for API token creation and editing is now opened in a modal (popup) window. • Locale ”British English” (en_GB) is available again in Zabbix frontend. • German and Vietnamese is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory,

page for more details. Detail editing as popup window In several configuration sections of Zabbix frontend detail editing is now opened as a popup window. This is implemented for: • Action conditions options in one screen. For example, details of an action operation are now opened in a separate popup window. New filtering options for dashboard widgets 20 Dashboard widgets Problems by severity and Problem is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory,

Host editing as popup The form for host creation and editing is now opened in a modal (popup) window, in Configuration → Hosts, Monitoring → Hosts and in any page, where there is a host menu or other is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, preferably a subdirectory of the source dir. For example, E:\pcre2-10.39\build. 5. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui

is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, preferably a subdirectory of the source dir. For example, E:\pcre-8.41\build. 5. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui The build directory should now contain a usable build system - Makefile. 15. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and navigate to the Makefile mentioned above

is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, preferably a subdirectory of the source dir. For example, E:\pcre-8.41\build. 5. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui The build directory should now contain a usable build system - Makefile. 15. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and navigate to the Makefile mentioned above

Clicking in the parameter field or on the view/edit button next to the parameter field will open a window for entering the code block. 7 Validation and throttling rules New options have been added to media type works. To do that in the media type list, click on Test in the last column. A testing window will open where you can enter a Send to recipient address and send a test message subject and body body by clicking on Test. 15 Test success or failure message will be displayed in the same window. Regular expression-based matching in auto-registration conditions Regular expression match is now supported

possible to see webhook script response type and webhook script response data in the test modal window. 22 8 What’s new in Zabbix 4.4.3 This minor version contains no functional changes. 9 What’s possible to click on Select next to the field and select one or more templates from the list in a popup window. The templates that have been selected in the Link new templates field are linked to the host/template is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory,

new in Zabbix 3.0.3 1 Frontend improvements 1.1 Global script results The global script result window has regained a header with the script name. Information about the executed command is now displayed is used here. 3. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, on a Windows machine. 3. Let’s assume that sources are in e:\zabbix-3.0.24. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. Go to e:\3.0.24\build\win32\project. 4