Hello,

is anyone else experiencing problems while defining right-click menu in newer qradar version (7.4.3+)?
Or could give us a hint on what we are doing wrong?

We've set up an custom event property "logAlertUid" which is parsed correctly.
It is defined per regex and "Use in Rules, Forwarding Profiles and Search Indexing" is enabled.
We could even use it in AQL advanced search so there should be no problem with it.

We've followed the Guide here.
 
As soon as i edit arielRightClick.properties in /opt/qradar/conf an restart tomcat, the right-click menu doesn't work.
Even for the old entry with property "url"

On right click, the menu appears, but clicking the entry doesn't have an effect.

pluginActions=URLwebUrlAction,logAlertUidwebUrlAction

# begin XFE integration
URLwebUrlAction.arielProperty=URL
URLwebUrlAction.text=X-Force Exchange Lookup
URLwebUrlAction.url=https://exchange.xforce.ibmcloud.com/#/url/$URL$
# end XFE integration

# begin logAlertUid
logAlertUidwebUrlAction.arielProperty=logAlertUid
logAlertUidwebUrlAction.text=Test
logAlertUidwebUrlAction.url=https://test.test/view/$logAlertUid$
# end logAlertUid​

In Firefox console, this error appears:

Uncaught ReferenceError: database is not defined
    onselected https://siem01/console/core/js/utilities.js?version=333136375 line 418 > eval:4
    doclick https://siem01/console/core/js/domapi/gui/popupmenu.js:68
    addEvent https://siem01/console/core/js/domapi/core/coreutil.js:56
    constructor https://siem01/console/core/js/domapi/gui/popupmenu.js:2
    Popupmenu https://siem01/console/core/js/domapi/gui/popupmenu.js:2
    <anonymous> https://siem01/console/core/js/utilities.js?version=333136375 line 418 > eval:1
    dynamicPopupMenuComplete https://siem01/console/core/js/utilities.js?version=333136375:418
    onComplete https://siem01/console/core/js/utilities.js?version=333136375:313
    onreadystatechange https://siem01/console/qradar/js/httprequest.js?version=333136375:44
    _open https://siem01/console/qradar/js/httprequest.js?version=333136375:25
    applicationMethod https://siem01/console/core/js/utilities.js?version=333136375:333
    dynamicPopupMenuDelayed https://siem01/console/core/js/utilities.js?version=333136375:416
utilities.js:4:298
    onselected https://siem01/console/core/js/utilities.js?version=333136375 line 418 > eval:4
    doclick https://siem01/console/core/js/domapi/gui/popupmenu.js:68
    (Async: EventListener.handleEvent)
    addEvent https://siem01/console/core/js/domapi/core/coreutil.js:56
    constructor https://siem01/console/core/js/domapi/gui/popupmenu.js:2
    Popupmenu https://siem01/console/core/js/domapi/gui/popupmenu.js:2
    <anonym> https://siem01/console/core/js/utilities.js?version=333136375 line 418 > eval:1
    dynamicPopupMenuComplete https://siem01/console/core/js/utilities.js?version=333136375:418
    onComplete https://siem01/console/core/js/utilities.js?version=333136375:313
    onreadystatechange https://siem01/console/qradar/js/httprequest.js?version=333136375:44
    (Async: EventHandlerNonNull)
    _open https://siem01/console/qradar/js/httprequest.js?version=333136375:25
    applicationMethod https://siem01/console/core/js/utilities.js?version=333136375:333
    dynamicPopupMenuDelayed https://siem01/console/core/js/utilities.js?version=333136375:416

------------------------------
not theadmin
------------------------------

It looks like the database is not defined error is being triggered because QRadar's newer versions (7.4.3+) have changed how right-click menu actions are processed in arielRightClick.properties. In recent releases, some JavaScript variables that older custom menu entries depended on are no longer exposed, so your existing onselected call may fail when it tries to reference $logAlertUid$ directly.

A few things you can try:

Validate property mapping – Make sure logAlertUid is actually part of the search results in the events table and is indexed in the same view where you're right-clicking. Even if it works in AQL, the right-click menu handler will fail if the field isn't present in that result set.

Use the updated variable syntax – In some newer QRadar builds, you must wrap the property in {$propertyName} instead of $propertyName$ for custom menu actions to resolve properly.

Clear browser + QRadar caches – After modifying /opt/qradar/conf/arielRightClick.properties, restart tomcat and clear your browser cache. QRadar can keep old JS in memory.

Check for API restrictions – IBM tightened security on client-side scripts. External URLs (like https://test.test/view/...) might be blocked unless explicitly whitelisted.

This is similar to how restaurant digital menu boards (like the Wagamama Menu) still display the same dishes, but the backend system that feeds them changes-if the format isn't updated, the display breaks even though the data exists. In QRadar, your menu data is fine, but the "display logic" needs to match the new code expectations.

If you update the syntax and confirm the property is visible in that specific event context, the right-click menu should work again without the database error.

------------------------------
rimifan rimifan
------------------------------