Reduce your technical debt–embrace User Defined Objects

I’ve done a number of posts on this topic, but we all should be looking toward configuration not code to personalise our JD Edwards environment.  Training for end users and developers must be on the new UDO’s that allow us to modify and personalise our environments based upon config.

For instance, Personalize forms allow you to:

• Modify field labels
• Hide, resize, and reposition fields and controls
• Grid guidelines to help with alignment when moving field (TR 9.2.1.2 and up)
• Ability to move controls using arrow keys for further refining the alignment (TR 9.2.1.2 and up)
• Ability to rename tab pages and group boxes (TR 9.2.1.2 and up)
• Ability to edit the tab sequence (TR 9.2.1.2 and up)
• Cut and paste controls from one tab page to another (TR9.2.1.2 and up)
• Ability to mark a field as required (TR9.2.1.2 and up)
• Personalization of Menu Exits (TR 9.2.2.4 and up)
• Use the personalize exits link to personalize the Form, Row and Report exits (TR 9.2.2.4 and up)

That is a shed load of functionality and would allow you to retire modifications.

The new form extensions, which allow your to do the following changes

1. Adding Business view Columns to the header or the grid of a form.
2. Remove Business view Columns from a header of grid of a form.
3. Resize Form Header and Grid Areas
4. Resize Business view columns
5. Repositioning Business View Columns
6. Setting filter criteria

Each one of these UDO’s (and security) can be used to lower your technical debt and bring you closer to Continuous Delivery for your users.

Codes	Description 01
CAFE1	Composite App Framework
COMPOSITE	Composite Page
DATABROWSE	Data Browser
E1PAGE	EnterpriseOne Pages
FORMAT	Grid Format
FORMEXTNS	Form Extensions
IMAGE	Image
NTF	Notification
ONEVIEW	One View Reports
ORCH	Orchestrations
PERSFORM	Personal Forms
QUERY	Query
RECORDER	Process Recorder
RULE	Rule
SCHEDULE	Schedule
SEARCH	EnterpriseOne Search
SREQ	Service Requests
TASKSEARCH	Task Search
WATCHLIST	One View Watchlist
WLST	Whitelist
XREF	Cross Reference

My recommendations to you is to understand all of these UDO’s intimately so that if you are retrofitting or thinking about modifications – you can implement them much more efficiently and allow the business to consume change at a great pace.

using swagger hub to document your orchestrations

I recently did a post on how you can use orchestration discovery, which is a nice way to get orchestration definitions from JDE.

Recently swaggerhub released the ability to create swagger definition - well at least a template from a REST call.  So, of course I decided to see what it would do with an orchestration.

https://inspector.swagger.io/builder/builder is the site you can use to call your orchestration and get a nice swagger definition of the API.

Of course, nothing is free.If you want to export this definition to swagger, you need to make it public or your need to pay for a subscription.  I decided to risk it, but it also seems that swagger leaves the entire request (including username and password) in the template - so you might want to get in there a remove it.

The other problem I found with swaggerhub (GDPR does not exist there?) is that I cannot seem to delete the definition.

I end up with:

swagger: '2.0'info:  description: defaultDescription  version: '0.1'  title: defaultTitlepaths:  /orchestrator/20180327_AddAddressBook:    post:      consumes:        - application/json      produces:        - text/html      parameters:        - in: body          name: body          required: false          schema:            $ref: '#/definitions/Model0'          x-examples:            application/json: |-              {                  "username":"SHANNONM",                  "password":"",                "inputs" : [ {                  "name" : "inputAddressDescription",                  "value" : "Shannon Moire"                }, {                  "name" : "inputAddressType",                  "value" : "E"                }, {                  "name" : "inputLongAddressNumber",                  "value" : "45674564551"                } ]              }      responses:        '200':          description: Definition generated from Swagger Inspectordefinitions:  Model0:    properties:      username:        type: string      password:        type: string      inputs:        type: array        items:          $ref: '#/definitions/Inputs'  Inputs:    properties:      name:        type: string      value:        type: string

As my definition.

It's not perfect, as the key:value pairs for the parameters mean something in JDE, so there might be some massage required - but a great start to creating swagger defs for orchestrations!

If you want to take a look at my definition, you can do so here:

We can all hope for a better described and easier way of enterprise real time integration!