Nomajde
Nomajde is a companion application for JD Edwards EnterpriseOne, published by Nomana-IT and built with Liberty Next. It gathers the day-to-day administration of JD Edwards — users, roles, security workbench, environments, UDC tables, master data and BI Publisher scheduling — into a few searchable grids with inline editing, and writes every change straight to JD Edwards through SQL and the AIS REST API.
The problem Nomajde solves
JD Edwards is a depth product. Most day-to-day tasks — add a user, attach a role, update a UDC value, schedule a BIP report — require navigating between five or six forms, sometimes across the fat client and the web client. Operators get the job done; they spend twice the time they should.
Nomajde replaces the form ping-pong with one screen per topic, the one-row-at-a-time editor with grid editing and Excel upload, and the unwritten audit trail with a logged history of every run and every change.
What Nomajde is
A web application that sits next to JD Edwards and reads its data live — through SQL on the JDE security and master tables, and through the JDE AIS REST API for the operations that need a JDE workflow behind them (password reset, user provisioning, processing-option overrides). Every screen writes back to JDE — no staging copy, no replay.
The four pillars
- UDC types and UDC codes — one grid per topic, with Excel upload for roll-out loads.
- Address Book, customers, suppliers, items, GL accounts — same shape, same grid editing.
- The required-field checks JDE runs at row save are enforced here too — no half-written record reaches JDE.
- Add and edit JDE users — SQL writes the user master and the display preferences, AIS REST provisions the security record and the password.
- Reset password — one click; the call goes to the JDE AIS endpoint and the new password is active immediately.
- Import Security and Merge Roles — copy or merge the full security setup (application, action, row, column, processing-option, tab, exit, image, UDO, menu-filtering) from a source user / role to a target, in a guided workflow.
- Security Workbench — every JDE security type on one grid, with type-aware dialog and Excel upload for SI-delivered bundles.
- AP, AR, GL grids — filter on any column (company, supplier, document, amount, date), drill into the details.
- Schedule BIP reports from a single form — pick the program, the version, the data selection, the run time.
- The generated output (PDF or XML) is archived next to the run. Download, e-mail, resend in one click.
- Every BIP run is logged — who scheduled it, when it ran, what was produced.
- The enterprise, web and AIS servers checked through Server Manager every five minutes — state, health, failed checks.
- Availability over 24 hours per instance on the overview, the instances in trouble first.
- A failed check sends the job's alerts; a failed instance can be stopped automatically.
A sample of what you see
The Security Workbench grid — every JDE security entry on one row, with the action flags side by side and the dialog adapting to the security type.
The User Management grid, with the editable user record, the attached roles and environments, and the workflow that combines a SQL write with an AIS API call.
The application map
The menu follows the work, from the home page to the maintenance jobs.
| Section | What it covers |
|---|---|
| Overview | The home page: what Nomajde does, the live figures of the JD Edwards instance, the entry points of each domain. |
| Data Explorer | Free analysis of the security and development data, and of the models shipped by the JD Edwards presets. |
| Master Data | UDC types and UDC codes — every grid supports filter, sort, inline edit and Excel upload —, and the Address Book: address book, customers and suppliers, read-only, with Open in JDE. |
| Security Maintenance | User Management, User Preferences, Role Management, Role Relationships, Environments, Security Workbench, UDO Security. The JD Edwards security catalogue condensed into a few screens with grid editing. |
| Development | Object Librarian, Data Dictionary and Cross Reference, read-only. |
| Monitoring | JDE Servers: the health checks of the JD Edwards servers over a period, and the history of each one. |
| Jobs | Re-merge the security, refresh the data dictionary, check the JDE servers, with a live log. |
Who uses it
| Role | What they typically open Nomajde for |
|---|---|
| JDE security administrator | The five Security Maintenance screens — add a user, attach a role, run Import Security on a clone, walk through the security workbench grid. |
| AP / AR operator | The transaction grid — open invoices across companies and environments on one page, with bulk filters and drill-through. |
| Master-data steward | Address Book, customer and supplier maintenance with required-field checks; UDC types and codes for the catalogue work. |
| Reporting analyst | One form to schedule BIP, the archive of past runs, e-mail distribution. |
| Ops engineer | JDE Servers — the health of every enterprise, web and AIS server, its availability over 24 hours, the alerts of the check. |
Roles inside Nomajde
The application ships four roles.
| Role | What it grants |
|---|---|
| Viewer | Read every screen, run reports, no edits. |
| Operator | Everything a Viewer does, plus AP / AR / master-data edits and scheduling reports. |
| Security | Everything an Operator does, plus the Security Maintenance section (User, Role, Role Relationships, Environments, Security Workbench). |
| Administrator | Everything above, plus environment configuration, AIS endpoint, archive retention. |
A typical deployment keeps Operator separate from Security — the person processing transactions is not the same one managing access rights.