Skip to main content

Custom Queries

The Custom Queries screen lets each application override the SQL Nomasx-1 runs by default. One line per (Application, Method) pair — Method is the connector hook (for example get_users, get_assignments, get_object_usage) and SQL Blob carries the replacement SQL. Optional dedicated JDBC / user / password let the override target a different schema than the application's main one.

This is the extension point. When a source system stores its security tables differently from the canonical Nomasx-1 expectation, override the method here rather than touching the product.

At a glance​

Nomasx-1 · Settings · Global · Custom QueriesAPPMETHODAUDIT USERAUDIT DATE21 — SAP Prodget_usersadmin2026-04-2299 — Custom ERPget_object_usageadmin2026-05-02

Goal of the view​

  • Override per application. A row replaces the default query Nomasx-1 would run for the named method on the named application.
  • Add a separate connection if needed. When the override SQL targets a different schema or different credentials, the dedicated JDBC / User / Password columns carry them; otherwise the override runs against the application's main connection.
  • Trace the change. Audit user + Audit date record who introduced the override and when — useful when a scan starts behaving differently.

Columns​

ColumnSourceWhat it tells you
Application IDSQL_APPS_ID — application identifier. Joined to Applications for the friendly name.Which application the override applies to.
MethodSQL_METHOD — connector hook name.The query slot being overridden.
SQL BlobSQL_BLOB — text. Hidden by default.The replacement SQL fragment.
JDBC / User / PasswordSQL_JDBC, SQL_USER, SQL_PASSWORD — optional. Hidden.Dedicated connection used by the override.
Audit user / dateSQL_AUDIT_USER, SQL_AUDIT_DATE — who / when.Change traceability.

Edit dialog​

Click Add in the toolbar to declare a new override, or double-click a row to edit. The dialog has three tabs.

Edit override — SAP Prod · get_usersPropertiesDatabaseQueryApplication21 — SAP Prod ▾Methodget_usersTABSProperties: pair (Application, Method) that the override targets. Database: optional dedicated JDBC URL + credentials. Query: the replacement SQL.

Tab 1 — Properties​

The pair that identifies the override. Both fields are mandatory.

FieldWhat to enter
ApplicationDrop-down list of declared applications. The override applies to this one only.
MethodName of the connector hook (get_users, get_assignments, get_object_usage, …) being overridden.

Tab 2 — Database​

Optional dedicated connection. Leave the three fields empty to run the override against the application's main connection.

FieldWhat to enter
UserRead-only account used to run the override SQL.
PasswordPassword for the account. Stored encrypted.
JDBCJDBC URL when the override targets a different schema than the application's main one.

Tab 3 — Query​

The replacement SQL itself. Required.

FieldWhat to enter
SQL BlobMulti-line text. Paste the SQL Nomasx-1 should run instead of the default for the method declared on the Properties tab.

Tips & best practices​

  • Test the SQL outside Nomasx-1 first — a syntactically broken override surfaces as an empty grid on the consuming screen.
  • Keep override scopes tight. Override one method at a time rather than rewriting an entire branch — easier to maintain and to roll back.
  • Document the why in the change description during code review or in a ticket — six months later, the override has to be readable by a different administrator.
  • Remove the row when no longer needed so Nomasx-1 falls back to the default behaviour for that method.