4 Understanding Creating and Managing Objects

This chapter contains the following topics:

4.1 Understanding Object Management Workbench

Object Management Workbench is the primary component of the change management system for JD Edwards EnterpriseOne development. A change management system is vital to a productive development environment because it helps organize a myriad of development activities and helps prevent problems, such as when a developer intermixes components from different releases or when multiple developers simultaneously change an object. Object Management Workbench automates many of these change management activities.

This section discusses:

  • OMW projects

  • Allowed actions

  • Tokens

  • The OMW interface

  • Object Librarian and non-Object Librarian objects

4.2 OMW Projects

Projects are composed of objects and owners. All development of objects within JD Edwards EnterpriseOne must be performed within the context of a project. Usually, you must first create or select a project, add an object to it, and then you can work with that object. Typically, objects are included in a project because they have been modified or created by a developer to complete a specific task.

In addition to objects, users can be associated with different projects. In fact, before you can add an object to a project, you must have been added to the project as a user in a role that has permission to add objects. A user can be assigned to the same project more than once with different roles. Projects may also contain other projects.

See "Working with Projects" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

4.3 Allowed Actions

Allowed actions are rules that define the actions that may be performed by a user who is assigned a specific user role. You set up these rules for each user role, object type, and project status by using the Object Management Workbench Configuration program.

See "Configuring User Roles and Allowed Actions" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide

4.4 Tokens

Some objects use tokens to minimize the possibility of one user overwriting another user's changes to an object. The token management system organizes application development by providing a single checkout environment. Tokens provide a change control solution in a system that does not support merging or multiple versions of object specifications.

Note:

Only Object Librarian objects have tokens.

See "Working with Tokens" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

4.5 The OMW Interface

From left to right, the initial OMW form displays these features:

  • The project window, which displays your projects and their related objects and users. To view your current projects, click Find.

  • The center column, which contains action buttons that you use to perform actions on a selected object. Available buttons vary based on your roles in the current project and on the status of the project in which the selected object resides. When you first launch OMW, no buttons appear in the center column because you have not selected an object.

  • The information window, which displays a Web site; project status and release information; object or user information; and search results. Initially, the window displays a Web site or HTML page. The contents change based on your tab and object selections. For example, when you select a project or an object in the project window, the information window displays information about the selected project or object. To return this window to its initial state, click News on the toolbar.

See "The JD Edwards EnterpriseOne OMW Interface" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

4.6 Object Librarian and Non-Object Librarian Objects

OMW provides control of EnterpriseOne objects in a simple, integrated, graphical user interface for software development. In EnterpriseOne, an object is a reusable entity based on software specifications that are created by the EnterpriseOne development tools.

In OMW, this definition is expanded to include non-Object Librarian objects that are data source-based rather than path code-based.

JD Edwards EnterpriseOne objects include the following Object Librarian objects:

  • Batch applications and versions

  • Business functions

  • Business views

  • Data structures

  • Interactive applications

  • Media objects

  • Tables

EnterpriseOne objects include the following non-Object Librarian objects:

  • Data dictionary items

  • User defined code items

  • Workflow objects

See "Object Librarian and Non-Object Librarian Objects" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.