Create from… — endpoints and screens from JD Edwards
Create from… writes, from what JD Edwards itself describes, an endpoint dedicated to one object — one report version, one table, one form, one business function, one orchestration — or a complete screen on a JD Edwards application. Nobody types a path or a JSON body: the object is searched by name, a few questions are answered, and each input becomes a labelled field with its help and its default.
It is the short way to put a JD Edwards form in a Nomajde grid, with saves that go through the form — so JD Edwards' own rules, defaults, security and messages apply.
Access: Liberty Next → Data → Connectors, connector ais_connection, tab Endpoints, button Create from….
At a glance
The three steps
- Find — choose what to create from, type a name or part of a description, and pick the object in the results.
- Answer — the questions depend on the object: the columns to return, the fields to fill, the button pressed. AIS describes the object without running it on data.
- Create — the endpoint is added to the connector, unsaved and open for review: rename it, adjust a label, then save the connector. When a screen is asked for, a second dialog asks for the application, the screen identifier, its title and whether to add it to the menu, and everything is created and saved together.
Each endpoint created has its own permission and sits under the heading of its JD Edwards application (P01012 — Address Book).
What can be created
| Create from | Type to search | What is built |
|---|---|---|
| A JDE application (its list and its record) | An application (P01012) or part of its description (address). | The endpoints that read, add, change and delete a record — and a screen on them. |
| A report version | The beginning of a report's name (R0010…). | An endpoint that submits that version. |
| A table or a business view | Part of a name or of a description. | An endpoint that reads it. |
| A JDE form | An application, a form (W01012B) or part of a form's description. | An endpoint that uses that form — or a screen on it. |
| A business function | A function name, a source object (B0000130) or part of a description. | An endpoint that runs it. |
| An orchestration | Part of a name, of a description or of a category. | An endpoint that runs it. |
A JDE application — the easy way
This is the one to start with. It asks what an operator knows, and finds the rest: the application's list (its find / browse form) and the form a record is edited in.
| Question | Meaning |
|---|---|
| What to create | The endpoints and a screen on them (the default), or The endpoints only (read, add, change, delete). |
| What identifies a record | The column(s) of the list a record is found by before it is changed or deleted. The first column is proposed. |
| The fields a record is edited with | Proposed: the fields the list shows. Tick the others to fill — each becomes a field of the add and of the change. |
| The list's own fields when it looks for a record | Only when the list does not find a record by its key alone: a fixed value per field, by alias (AT1=* — every search type). Usually blank. |
| Version of the application | ZJDE0001 by default. |
The dialog says what it found — the list, its number of columns, the form a record is edited in — and warns when the list shows nothing without a filter on the JD Edwards in use: the screen will then ask for one.
The screen created reads the list in a grid and opens a row in a record form: the same columns, the key locked once the record exists, a column no save carries shown but not typed.
A report version
| Question | Meaning |
|---|---|
| Processing options to fill | Each one becomes a field, with the version's current value as its default. The others keep the version's value. |
| Columns to select on | Each one becomes a required field, compared with equal and added to the version's saved selection, which is kept. |
The endpoint — Submit R0010P / XJDE0001 — is marked as changing data.
A table or a business view
| Question | Meaning |
|---|---|
| Columns to return | None chosen = every column. |
| Columns to filter on | Each one becomes a required field: the rows whose column equals the value. |
| Maximum rows | 100 by default. |
The endpoint says where its rows are: a screen can use it as its source, the columns named by their JD Edwards alias so that the dictionary gives their labels.
A JDE form
The complete generator, for a form the easy way does not cover. AIS describes the form — its fields, its grid columns, its buttons.
| Question | Meaning |
|---|---|
| What to create | One endpoint (as set below), or A screen on this form: its rows in a Liberty grid, and the endpoints it needs. |
| A screen: the columns that identify a row (its key) | Needed for the screen to save. None chosen = a screen that only reads. |
| Values passed by the calling form | For a form opened from another one with greyed fields: the numbers of those values and a name for each — 1=Product_Code, 2=UDC_Type. Without them such a form saves wrong data. |
| Fields and grid filters to fill | Each one becomes a field. A grid filter left blank does not filter, and accepts A*, >… |
| What is done to a row of the grid | Add a row, Change the row the grid filters find, Delete the row the grid filters find. |
| Find the row with a leading * | For codes stored right-justified, like a UDC code: 002 is found as *002. |
| A record is edited in | This form's grid, or another form of the application — Work With Addresses lists, Address Book Revision edits. |
| Edited in another form: when JDE warns | Save all the same (OK is pressed again) and report the warning, or Save nothing: the warning is the error. |
| Button pressed | Find reads. Any other button does what the form does — OK saves, Delete deletes — and the endpoint is marked as changing data. |
| Fields and columns to return | None chosen = all of them. |
The guarantees of a save
A change or a delete through a form is several actions in one JD Edwards session: find the row, check what was found, act, press OK.
- Nothing is done unless exactly one row is found — none, for an add.
- A record edited in another form goes the user's way: found in the list, the list's own button pressed (Select, Add, Delete), the other form filled and its OK pressed.
- A warning stops the first OK as it does for a user; it is accepted or refused according to the choice above, and reported with the save.
- After a delete the record is looked for again: a form that deleted nothing is an error.
- A field the screen does not send is not typed in the form; a field the user cleared is.
- When the form refuses — a required field left blank, a value it does not accept — the save fails with the form's own message.
- The forms and the session are always closed, an error included: no JD Edwards session and no record lock are left behind.
A business function, an orchestration
| Create from | Questions | Result |
|---|---|---|
| A business function | Parameters to pass (each becomes a field; the others are left to the function) and Parameters to return. | Run <function> — an error fails the call with its message, a warning is reported and the call stands. |
| An orchestration | None: the dialog lists its inputs. | Run <orchestration> — one field per input, on the address of its version; an input that is a list of rows stays one JSON field, with the rows' shape as its example. |
An SQL screen saved through the forms
A screen that reads a JD Edwards table by SQL — fast, every column, paging — can keep its read and save through the forms: in the screen designer, Saves through names the AIS connector, and the update, insert and delete are the record endpoints created above. A field of the endpoint takes the value of the column that carries the same data item (ALPH from ABALPH): nothing to map by hand. See A screen on an API endpoint.
Keeping endpoints up to date
An endpoint remembers what it was created from. When the report, the table, the form or the orchestration changes in JD Edwards — after an update, for instance:
- Refresh from the server, on the endpoint, builds it again and shows what changes before applying it; the name, the label and what was written on its fields are kept.
- Check N generated, above the list, asks JD Edwards for every generated endpoint and lists those that no longer match.
Tips & best practices
- Start with A JDE application; go to A JDE form only for a header-detail form, a form opened with greyed values, or a specific button.
- Try the read endpoint in the Test tab before creating the screen: an empty list there is an empty screen later.
- For a UDC-like form, name the values passed by the calling form: typed in the fields instead, the form saves a blank code.
- Give the endpoints that change JD Edwards to the roles that may do the same thing in JD Edwards — no more.
- Add a non-regression case on each generated endpoint the business depends on.
- The AI assistant knows the procedure: ask it to create a Liberty screen on a JDE form.
Related
- JD Edwards services (AIS) — the catalogue.
- API endpoints and A screen on an API endpoint — the framework side.