JD Edwards EnterpriseOne Tools

Object Management Workbench Guide

Release 8.98 Update 4

E14713-02

March 2011

JD Edwards EnterpriseOne Tools Object Management Workbench Guide, Release 8.98 Update 4

E14713-02

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction to JD Edwards EnterpriseOne OMW

- 1.1 JD Edwards EnterpriseOne OMW Overview

- 1.2 JD Edwards EnterpriseOne OMW Implementation

- 1.2.1 JD Edwards EnterpriseOne OMW Implementation Steps

2 Understanding JD Edwards EnterpriseOne OMW

- 2.1 JD Edwards EnterpriseOne OMW Projects

- 2.2 Default Projects in JD Edwards EnterpriseOne OMW

- 2.3 User Roles in JD Edwards EnterpriseOne OMW

- 2.4 Allowed Actions

- 2.5 Tokens

- 2.6 The JD Edwards EnterpriseOne OMW Interface

- 2.7 Object Librarian and Non-Object Librarian Objects

3 Understanding Projects in JD Edwards EnterpriseOne OMW

- 3.1 Understanding Default Projects

- 3.1.1 Default Projects

- 3.1.2 Roles in the Default Project

- 3.2 Understanding the Lifecycle of a Project

4 Working with Projects

- 4.1 Understanding Projects

- 4.2 Filtering and Searching for Projects

- 4.2.1 Form Used to Filter and Search for Projects

- 4.2.2 Filtering Projects

- 4.2.3 Performing Project Searches

- 4.2.4 Searching for Projects by Object

- 4.3 Creating New Projects

- 4.3.1 Creating New Projects

- 4.3.2 Adding Users to Projects

- 4.3.3 Removing Users from Projects

- 4.4 Changing Project Properties

- 4.4.1 Understanding Project Properties

- 4.4.2 Changing Project Properties

- 4.5 Advancing Projects

- 4.5.1 Understanding Project Advancement

- 4.5.2 Prerequisites

- 4.5.3 Advancing Projects

- 4.6 Adding Existing Projects to a Project

- 4.7 Deleting Projects

- 4.7.1 Understanding Project Deletion

- 4.7.2 Deleting Projects

5 Working with Objects

- 5.1 Understanding Objects

- 5.2 Creating Objects

- 5.2.1 Alternative Method to Accessing Design Tool Functionality

- 5.3 Searching for Objects

- 5.3.1 Understanding Object Searches

- 5.3.2 Searching for Objects

- 5.4 Adding Objects to Projects

- 5.4.1 Understanding Object Addition

- 5.4.2 Adding an Object

- 5.4.3 Adding Multiple Objects

- 5.5 Moving Objects

- 5.5.1 Moving an Object

- 5.5.2 Moving Multiple Objects

- 5.6 Removing Objects from Projects

- 5.7 Deleting Objects

- 5.7.1 Understanding Object Deletion

- 5.7.2 Deleting Objects

- 5.8 Downloading Object Specifications

- 5.8.1 Understanding Specification Downloads

- 5.8.2 Saving and Restoring Objects and Projects

- 5.8.3 Using the Advanced Get Feature

- 5.8.4 Performing Quick Gets on Objects

- 5.9 Checking Objects In and Out

- 5.9.1 Understanding Object Check In and Check Out

- 5.9.2 Checking Out Objects

- 5.9.3 Checking In Objects

- 5.9.4 Checking in Object Specifications without Checking in the Object

- 5.9.5 Erasing Checkouts

- 5.10 Changing Objects

- 5.10.1 Understanding Object Changes

- 5.10.2 Changing Objects

- 5.11 Maintaining Objects in Multiple Software Release

- 5.11.1 Understanding Objects in Multiple Software Releases

- 5.11.2 Prerequisite

- 5.11.3 Adding Same-Named Objects to a Project

- 5.11.4 Changing the Release Level of an Object on Your Project

- 5.11.5 Updating an Object to Match Another Object

- 5.11.6 Updating Different Objects in Different Releases

6 Working with Business Services

- 6.1 Understanding Business Services

- 6.2 Creating Business Service Objects

- 6.3 Searching for Business Service Objects

- 6.4 Viewing the OMW HTML Status Page

- 6.5 Designing Business Services

- 6.5.1 Pointing EnterpriseOne to JDeveloper Installation Path

- 6.5.2 Invoking JDeveloper

- 6.5.3 Adding Artifacts to a Business Service

- 6.6 Checking In, Checking Out, and Saving Business Services

- 6.6.1 Checking In Artifacts

- 6.6.2 Checking Out a Business Service Object

- 6.6.3 Understanding the Business Service Artifact List

- 6.6.4 Viewing Artifacts

- 6.6.5 Understanding Published Artifacts

- 6.6.6 Specifying a Published Artifact

- 6.6.7 Unpublishing a Published Artifact

- 6.6.8 Deleting a Business Service

- 6.7 Working with Business Services Properties

- 6.7.1 Adding a Business Service Property

- 6.7.2 Searching for a Business Service Property

- 6.7.3 Adding a Business Service Property to a Project

7 Working with Tokens

- 7.1 Understanding Tokens

- 7.2 Viewing the Token Queue

- 7.2.1 Understanding the Token Queue

- 7.2.2 Viewing the Token Queue

- 7.3 Inheriting Tokens

- 7.3.1 Understanding Token Inheritance

- 7.3.2 Inheriting Tokens

- 7.4 Switching Tokens

- 7.4.1 Understanding Token Switching

- 7.4.2 Prerequisite

- 7.4.3 Switching Tokens

- 7.5 Releasing Tokens Manually

- 7.5.1 Understanding Token Release

- 7.5.2 Releasing Tokens Manually

8 Working with Users

- 8.1 Understanding Users

- 8.2 Searching for Users

- 8.2.1 Understanding User Searches

- 8.2.2 Searching for Users by Name or ID

- 8.2.3 Searching for Users by Class or Group

- 8.3 Adding Users to Projects

- 8.3.1 Understanding Users in Projects

- 8.3.2 Adding Users to Projects

- 8.3.3 Removing Users from Projects

- 8.3.4 Changing User Properties

9 Working with Attachments

- 9.1 Understanding Attachments

- 9.2 Viewing Attachments

- 9.2.1 Viewing Attachments in the Design View

- 9.2.2 Viewing Attachments in JD Edwards EnterpriseOne OMW

10 Configuring JD Edwards EnterpriseOne OMW

- 10.1 Understanding JD Edwards EnterpriseOne OMW Configuration

- 10.1.1 JD Edwards EnterpriseOne OMW Configuration Options

- 10.1.2 The Configuration Process Flow

- 10.1.3 Activity Rules

- 10.1.4 Allowed Actions

- 10.1.5 Project and Object Logging

- 10.1.6 Project Constants

- 10.1.7 Object Save Locations

- 10.1.8 Object Action Notifications

- 10.1.9 Notification Subscriptions

- 10.1.10 Application and User Role Security

- 10.1.10.1 User Role Security

- 10.1.10.2 Administrative Update Security

- 10.2 Selecting a Configuration Option

- 10.2.1 Configuration Settings Indicators

- 10.3 Adding a New File Extension and New Package Prefix

11 Configuring User Roles and Allowed Actions

- 11.1 Understanding User Roles and Allowed Actions

- 11.1.1 New Project Pending Review (11)

- 11.1.2 Programming (21)

- 11.1.3 Rework-Same Issue (25)

- 11.1.4 QA Test/Review (26)

- 11.1.5 QA Test/Review Complete (28)

- 11.1.6 In Production (38)

- 11.1.7 Complete (01)

- 11.1.8 Default Allowed Actions that Cannot Be Changed

- 11.1.9 Default Object Types

- 11.2 Setting Up User Roles

- 11.2.1 Forms Used to Set up User Roles

- 11.2.2 Modifying User Roles

- 11.2.3 Deleting User Roles

- 11.3 Setting Up Allowed User Actions

- 11.3.1 Understanding User Defined Codes for Allowed User Actions

- 11.3.2 Form Used to Set Up User Actions

- 11.3.3 Setting Up Allowed User Actions

12 Configuring JD Edwards EnterpriseOne OMW Functions

- 12.1 Understanding JD Edwards EnterpriseOne OMW Functions

- 12.2 Disabling SAR Integration

- 12.2.1 Understanding SAR Integration

- 12.2.2 Forms Used with SAR Integration

- 12.2.3 Disabling SAR System Integration

- 12.2.4 Controlling Logging Detail

- 12.2.5 Controlling Development in the Event of a Logging Failure

- 12.3 Setting Up Project Constants

- 12.3.1 Form Used to Setup Project Constants

- 12.3.2 Setting Up Project Constants

13 Configuring Activity Rules

- 13.1 Understanding Activity Rules

- 13.2 Understanding the Project Promotion Lifecycle

- 13.3 Setting Up Project Status Activity Rules

- 13.3.1 Understanding Project Statuses

- 13.3.2 Form Used to Set up Project Status Activity Rules

- 13.3.3 Setting Up Project Status Activity Rules

- 13.4 Setting Up Object Transfer Activity Rules

- 13.4.1 Understanding Object Transfer Activity Rules

- 13.4.2 Form Used to Set up Object Transfer Activity Rules

- 13.4.3 Setting Up Object Transfer Activity Rules

14 Configuring Object Save Locations

- 14.1 Creating a Save Location

- 14.1.1 Understanding Path Codes

- 14.1.2 Form Used to Object Save Locations

- 14.1.3 Adding an Object Save Location

- 14.1.4 Modifying an Object Save Location

- 14.1.5 Deleting an Object Save Location

15 Creating Notification Subscriptions

- 15.1 Understanding Object Action Notifications

- 15.2 Configuring Notification Subscriptions

- 15.2.1 Forms Used to Configure Notification Subscriptions

- 15.2.2 Enabling or Disabling Object Action Notifications

- 15.2.3 Adding a Notification Subscription

- 15.2.4 Modifying Notification Subscriptions

- 15.2.5 Deleting a Notification Subscription

- 15.2.6 Sorting Notification Subscriptions

- 15.2.7 Creating Notification Subscriptions using the Notification Subscription Assistant

- 15.2.7.1 Accessing the Notification Subscription Assistant

- 15.2.7.2 Understanding Actions

- 15.2.7.3 Understanding Notification Subscription Fields

- 15.2.7.4 Understanding Recipients

16 Working with Logs

- 16.1 Understanding Object Management Logging

- 16.2 Using Logs

- 16.2.1 Forms Used with Object Management Logging

- 16.2.2 Viewing Project or Object Logs

- 16.2.3 Locating Object Logs

- 16.2.4 Locating Project Logs

- 16.2.5 Viewing Detail Logs

- 16.2.6 Reordering Log Record Fields

- 16.2.7 Printing Logs

- 16.2.8 Printing Event Rules

17 Working with JD Edwards EnterpriseOne OMW and SCM Integration

- 17.1 Configuring JD Edwards EnterpriseOne OMW and SCM Integration

- 17.1.1 Configuring JD Edwards EnterpriseOne OMW to Interface with ClearCase

- 17.1.2 Configuring Access to ClearCase

- 17.1.3 Configuring Pathcodes

- 17.1.4 Setting up a Backup Folder for Deleted Objects

- 17.1.5 Copying a Path Code

- 17.2 Understanding the SCM Tool

- 17.2.1 SCM Interface and Functionality

- 17.2.2 Source and Target Browsers

- 17.2.3 History, Source History and Target History, Label Contents Viewers

- 17.2.3.1 History Tab

- 17.2.3.2 Source History and Target History Tabs

- 17.2.3.3 Labeling Viewer

- 17.2.3.4 Button and Icons

- 17.2.4 Using the SCM Tool

Glossary

Index

Preface

Welcome to the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

Audience

This guide is intended for system administrators, developers, and technical consultants who are responsible for setting up roles and user actions and developing objects using Object Management Workbench (OMW).

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Related Documents

You can access related documents from the JD Edwards EnterpriseOne Release Documentation Overview pages on My Oracle Support. Access the main documentation overview page by searching for the document ID, which is 876932.1, or by using this link:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=876932.1

To navigate to this page from the My Oracle Support home page, click the Knowledge tab, and then click the Tools and Training menu, JD Edwards EnterpriseOne, Welcome Center, Release Information Overview.

This guide contains references to server configuration settings that JD Edwards EnterpriseOne stores in configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, and so on). Beginning with the JD Edwards EnterpriseOne Tools Release 8.97, it is highly recommended that you only access and manage these settings for the supported server types using the Server Manager program. See the Server Manager Guide on My Oracle Support.

Conventions

The following text conventions are used in this document:

Convention

Meaning

Bold

Indicates field values.

Italics

Indicates emphasis and JD Edwards EnterpriseOne or other book-length publication titles.

Monospace

Indicates a JD Edwards EnterpriseOne program, other code example, or URL.

1 Introduction to JD Edwards EnterpriseOne OMW

This chapter contains the following topics:

- Section 1.1, "JD Edwards EnterpriseOne OMW Overview"

- Section 1.2, "JD Edwards EnterpriseOne OMW Implementation"

1.1 JD Edwards EnterpriseOne OMW Overview

JD Edwards EnterpriseOne OMW from Oracle is the primary component of the change management system for 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. JD Edwards EnterpriseOne OMW automates many of these change management activities.

1.2 JD Edwards EnterpriseOne OMW Implementation

This section provides an overview of the steps that are required to implement JD Edwards EnterpriseOne OMW.

In the planning phase of your implementation, take advantage of all JD Edwards sources of information, including the installation guides and troubleshooting information. A complete list of these resources appears in the preface in About This Documentation with information about where to find the most current version of each.

1.2.1 JD Edwards EnterpriseOne OMW Implementation Steps

This section provides an overview of the steps that are required to implement JD Edwards EnterpriseOne OMW.

In the planning phase of your implementation, take advantage of all JD Edwards sources of information, including the installation guides and troubleshooting information. A complete list of these resources appears in the preface in About These Guides with information about where to find the most current version of each.

This table lists the steps for the JD Edwards EnterpriseOne OMW implementation.

1. Set up permissions to access and use JD Edwards EnterpriseOne OMW using Security Workbench.
See "Using Security Workbench" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

2. Add yourself to the system in a developer role so that you have permissions to create JD Edwards EnterpriseOne objects.
See Setting Up User Roles.

3. Set up permissions to create JD Edwards EnterpriseOne OMW projects.
See Setting Up Allowed User Actions.

4. Set up the appropriate database permissions so that you can add tables to the database, drop tables, and add and modify data.
Work with the database administrator to set up these permissions.

2 Understanding JD Edwards EnterpriseOne OMW

This chapter contains the following topics:

- Section 2.1, "JD Edwards EnterpriseOne OMW Projects"

- Section 2.2, "Default Projects in JD Edwards EnterpriseOne OMW"

- Section 2.3, "User Roles in JD Edwards EnterpriseOne OMW"

- Section 2.4, "Allowed Actions"

- Section 2.5, "Tokens"

- Section 2.6, "The JD Edwards EnterpriseOne OMW Interface"

- Section 2.7, "Object Librarian and Non-Object Librarian Objects"

2.1 JD Edwards EnterpriseOne 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.

2.2 Default Projects in JD Edwards EnterpriseOne OMW

The default project is your personal project that you use for development and research. It holds any miscellaneous development objects that you want to work with but that you have not associated with a specific project. JD Edwards EnterpriseOne creates a default project when you run JD Edwards EnterpriseOne OMW for the first time. Your JD Edwards EnterpriseOne logon is the name of your default project.

Use your default project to do these tasks:

- Research, develop, and prototype objects

- Review objects that you do not need to modify or check in

The default project is similar to other projects; however, the status of a default project does not change. Therefore, you cannot use a default project to transfer objects.

Some objects, such as versions, and reports can be created and edited outside of JD Edwards EnterpriseOne OMW. Nevertheless, any changes that you make to these objects must be tracked and managed. You use your default project to manage these objects. If you create or access such objects outside of JD Edwards EnterpriseOne OMW, these objects are added to your default project.

2.3 User Roles in JD Edwards EnterpriseOne OMW

Users must be assigned to a project before they can revise the project or the objects within that project. When you add a user to a project, you also identify the role of the user within the project. The user role defines the function of the user within the project organization and specifies the user's access to certain JD Edwards EnterpriseOne OMW functions, depending on the allowed actions associated with the role. User roles and their allowed actions are defined in the Object Management Configuration application.

Note:
Do not confuse user roles in the JD Edwards EnterpriseOne OMW with the concept of user roles as applied to other components of JD Edwards EnterpriseOne, such as Solution Explorer. JD Edwards EnterpriseOne OMW roles function independently of all other role-based systems in JD Edwards EnterpriseOne.

2.4 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 JD Edwards EnterpriseOne OMW Configuration program.

2.5 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.

Projects hold tokens for an object, and each object has only one token. You can check out an object only if your project holds the token for the object. In this way, an object can reside in several projects, but can be checked out and checked in only by qualified users of the project that holds the token. However, you can allow other projects to share an object's token, thereby allowing the object to be checked out and checked in by qualified users of one or more projects. Only one person can check out an object at a time.

Note:
Only Object Librarian objects have tokens.

See Adding Objects to Projects.

See Object Librarian and Non-Object Librarian Objects.

This table lists the allowed actions you can perform while your project holds the token:

Action

Description

Allow Another Project to Inherit the Token

This action forces both projects to be advanced together as if they were one project and allows multiple fixes to be applied to an object.

Switch the Token to Another Project

The project that donates the token returns to the queue as the first project waiting for the token when the new project inherits the token. This action allows an emergency fix to be applied immediately. Token switching should be restricted to a specific user role to ensure security of the objects.

Release the Token

You can release the token and allow the next project in the queue to receive the token. The token can be released manually or configured to be released when a project advances to a new status. The token can be released when the project's status first changes or as late as when the project is closed. You must configure token release according to object type. Some object types, such as business functions, can hold their tokens longer, while other object types can give up their tokens earlier. You must also, set up tokens for release at a predefined object transfer point.

Your organization's change control procedures determine how you configure the object-transfer activity rules to release tokens. If you do not define object-transfer activity rules to release tokens, developers risk overwriting the changes of other developers.

2.6 The JD Edwards EnterpriseOne OMW Interface

From left to right, the initial JD Edwards EnterpriseOne 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.
This list describes how the color of an Object Librarian Object button indicates its status:

- Gray Object Button with Check Mark: Another project holds the token for this object.

- Colored Object Button (not gray): The project that contains the object holds the token for this object.

- Colored Object Button with Check Mark (not gray): The project that contains the object holds the token for the object, and the object is checked out.

- Gray Object Button: This object is not checked out and no project currently holds the object for the token.
Non-Object Librarian Object buttons do not vary in appearance.

Objects to be deleted are marked in bold in this window.

- 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 JD Edwards EnterpriseOne 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.

2.7 Object Librarian and Non-Object Librarian Objects

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

In JD Edwards EnterpriseOne 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 (UBE)

- Business functions (BSFN)

- Business views (BSVW)

- Data structures (DSTR)

- Interactive applications (APPL)

- Media objects (GT)

- Tables (TBLE)

JD Edwards objects include the following non-Object Librarian objects:

- Data dictionary items

- User defined code items

- Workflow objects

- Menus

3 Understanding Projects in JD Edwards EnterpriseOne OMW

This chapter contains the following topics:

- Section 3.1, "Understanding Default Projects"

- Section 3.2, "Understanding the Lifecycle of a Project"

3.1 Understanding Default Projects

This section discusses:

- Default projects.

- Roles in default projects.

3.1.1 Default Projects

When you run JD Edwards EnterpriseOne OMW for the first time, the system creates a default project and tags it with your user ID. The default project is your personal project that you can use for development and research.

You can use default projects to do the following:

- Develop objects that are later moved into a regular project.

- Store objects to be added to a project later.

- Automatically store objects worked on outside of JD Edwards EnterpriseOne OMW.

A default project is similar to a project except that the project status of a default project never changes. Therefore, you cannot use a default project to transfer objects.

Non-Object Librarian objects can be accessed outside of JD Edwards EnterpriseOne OMW. If you access objects such as versions, user defined codes, menus, or the RDA outside of JD Edwards EnterpriseOne OMW, these objects are added to the default project. Any changes that you make to these objects must be tracked and managed through the default project. Modifications to non-Object Librarian objects are always logged.

If you want to advance the status of an object, use JD Edwards EnterpriseOne OMW to move the object from the default project to a project.

3.1.2 Roles in the Default Project

Although your default project appears immediately, you have one role only (usually Originator), as configured by your system administrator. You might need to add yourself to your default project in another role, such as Developer.

See Also:

- Working with Projects.

- Creating New Projects.

- Adding Users to Projects.

3.2 Understanding the Lifecycle of a Project

This topic discusses a typical project lifecycle from inception to completion. It includes steps required by a SAR-based (software action request) system. If you are not using a SAR-based system, some of the following steps might not apply to you. Furthermore, depending on your business's software development procedures, the steps that you follow and their order might vary from the following process.

1. Based on the task to be accomplished, create a new project.

2. Add users to the project.
When you add a user, you define the role of the user, based on the actions that you want that user to be able to perform within this project. You might need to add a user more than once if you want the user to be able to perform actions allowed by different roles. As the project progresses, you can continue to add (or remove) users as required.

When you create a project with SAR integration turned off, you are automatically added to that project in the role determined by your system administrator (usually, as the Originator). You might want to add yourself to the project in other roles as well.

When you create a project with SAR integration turned on, the person who entered the SAR is added to the project in the role of Originator.

3. Add objects to the project.
Qualified users might be adding objects to the project throughout much of its lifecycle.

If you create a new object, drag and drop the object from your default project to the project as appropriate.

4. Check objects out and in.
To be able to save your changes to an object, you must check the object out, apply your changes, and check the object in.

You can check out an object only if no other projects hold the token for that object. If the token is available, it passes to your project when you check the object out. If another project already holds the token for the object, you can join a token queue to be notified when the token becomes available.

After checking out an object and modifying it, you can save your changes without checking the object in.

When you check an object in, the system will not release the token from the project. As long as your project holds the token, another qualified user in your project can check the object out, but users in other projects cannot. You can enable users in other projects to check an object out by removing the object from the project.

5. Advance the project.
As the project progresses through its lifecycle, you must change its status. You do this by advancing the project. When you advance a project, the allowed actions for some roles might change and some objects might be transferred to other locations. Status-based role changes and transfers are configured by your system administrator.

6. Complete the project.
Based on your processes, you might archive or delete the project when finished. In JD Edwards EnterpriseOne OMW, 01 (Complete) is a closed status.

4 Working with Projects

This chapter contains the following topics:

- Section 4.1, "Understanding Projects"

- Section 4.2, "Filtering and Searching for Projects"

- Section 4.3, "Creating New Projects"

- Section 4.4, "Changing Project Properties"

- Section 4.5, "Advancing Projects"

- Section 4.6, "Adding Existing Projects to a Project"

- Section 4.7, "Deleting Projects"

4.1 Understanding Projects

In JD Edwards EnterpriseOne OMW, all development is performed within the context of a project.

By default, when you click Find on JD Edwards EnterpriseOne OMW, the project window displays all of the projects to which you are added in at least one role. The project list can become lengthy, and you might want to filter the list so that only certain projects appear. For example, if you have a Developer role on some projects, you might want to filter the list so that you view only those projects with a development status. You can filter by user, role, and status.

In addition to projects in which you have a role, you can also view any other projects in the system. You can search for projects based on a variety of criteria, including object. If you complete the filter fields in the project window before you perform a search, you can refine the search based on the information that you enter in the filter fields.

Note:
Searches are case-sensitive. When you complete fields, verify that you entered the search criteria using the commonly accepted spelling and case. If you receive no search results, try different capitalization or spelling.

4.2 Filtering and Searching for Projects

This section discusses how to:

- Filter projects.

- Perform project searches.

- Search for projects by object.

4.2.1 Form Used to Filter and Search for Projects

Form Name

FormID

Navigation

Usage

JD Edwards EnterpriseOne OMW

W98220A

In Solution Explorer, enter JD Edwards EnterpriseOne OMW in the Fast Path field˙.

Work with JD Edwards EnterpriseOne OMW projects.

4.2.2 Filtering Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, enter the role and complete the following fields in the project window:

- User. This field is required. When you launch the JD Edwards EnterpriseOne OMW, this field displays your ID. You can also enter other user IDs in this field.

- Status. The range that you enter is inclusive. To search for projects with a specific status, enter the status code in both fields.

2. Click Find.

4.2.3 Performing Project Searches

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select Advanced Search from the Form menu.

2. If you entered a user ID on the previous form, the JD Edwards EnterpriseOne OMW Project Search and Select by Project User form appears, and you can limit the search by enter the user role and project status.
To search for projects with a specific status, enter the status code in both fields. The range that you enter in these fields is inclusive.

The JD Edwards EnterpriseOne OMW Project Search and Select form appears if you did not complete any of the filter fields in the project window. These fields are unavailable on the JD Edwards EnterpriseOne OMW Project Search and Select form.

3. Enter the desired criteria in the Query by Example (QBE) columns, and then click Find.

4. Select one or more projects, and then click Select.
The projects that you chose appear in the project window.

4.2.4 Searching for Projects by Object

This search method places all of the selected projects in the project window.

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select Search by Object from the Form menu.

2. In JD Edwards EnterpriseOne OMW Project Search and Select by Object, enter the desired criteria in the Query by Example (QBE) columns, and then click Find.

3. Select one or more projects, and then click Select.

4.3 Creating New Projects

You create new projects to use as containers for objects and users that are grouped for a specific purpose. For example, you can create separate projects for different system enhancements. Through logging, projects also enable you to track the evolution of objects within the project, as well as the project itself.

This section discusses how to:

- Create new projects.

- Add users to projects.

- Remove users from projects.

4.3.1 Creating New Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click Add.

2. In Add JD Edwards Object to the Project, click JD Edwards EnterpriseOne OMW Project, and then click OK.

3. In Adding a Project, select how you want to create the project, and then click OK.
The option to create a project using a SAR is valid when SAR integration is enabled. This form is unavailable if your system is does not use the JD Edwards SAR system.

4. In Project Revisions, click the Summary tab, and enter a project ID.
JD Edwards recommends that you use the following format when you name your projects:

YYYzzzzz

YYY is a company-specific code.

zzzzz is a unique, five-digit number.

For example, ABC00001 might be the name of a project.

5. Complete the following fields:

- Description

- Type

- Severity

- Product System Code

- Release

6. Click the Dates tab, and then enter the planned completion date.

7. (Optional) Click the Category Codes tab, and then enter category codes 1 through 10.

8. Click the Attachments tab, and then add optional text comments to document the new project.

9. Click OK.

4.3.2 Adding Users to Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the project to which you want to add the users.

2. Set up a list of users to add to the destination project by performing a search using the Search tab in the information window.

3. In the search form, select the user to be added to the destination project.

4. Verify that the owner's node in the destination project in the project window is highlighted. If it is not highlighted, click it.

5. With the user to be added highlighted, click the Add Object or User to Project button in the center column.

6. In Add User to Project, enter the role and lead, and then click OK:

Note:
To add a user in more than one user role, repeat the add user procedure and select a second user role for the same user. Different functions are enabled for different user roles, according to their allowed (user) actions. These actions are configured by the administrator for your project using the configuration program of the JD Edwards EnterpriseOne OMW.

4.3.3 Removing Users from Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select a user in the project window.

2. Click the Remove Object or User from Project button in the center column.

Note:
Removing a user from a project does not delete the user from the system.

4.4 Changing Project Properties

This section provides an overview of project properties and discusses how to change project properties.

4.4.1 Understanding Project Properties

You can view and modify the following properties of any project that you select:

- Description

- Type

- Severity

- Product system code

- Release information

- Start date

- Planned completion date

- Category codes

- Text attachments

4.4.2 Changing Project Properties

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click a project, and then click Select.
You can also click the Design button in the center column.

2. In Project Revisions, click the Summary tab, and then revise the information in the following fields:

- Description

- Type

- Severity

- Product System Code

- Release

3. Click the Dates tab, and then revise the start date and the planned completion date.

4. (Optional) Click the Category Codes tab, and then revise category codes 1 through 10.

5. Click the Attachments tab, and then add optional text comments to document the project.

6. Click OK.

4.5 Advancing Projects

This section provides an overview of project advancement, lists prerequisites, and discusses how to advance projects.

4.5.1 Understanding Project Advancement

After development is complete for all objects in a project, the status of the project must be advanced to send the project through the development cycle. Changing the status of a project might affect the allowed actions of certain roles.

JD Edwards EnterpriseOne OMW can be configured to enable users, based on their roles, to perform specific actions when a project is at a specific status. For example, a user who is assigned to a project in the role of developer might be able to perform the following actions before the project is advanced: check out, design, and check in. However, after the project is advanced to the next status, a developer might not be able to perform any actions at all.

Changing the status of a project can also initiate actions, such as transferring objects in the project and deleting from the system objects that have been marked for removal. You cannot advance a default project.

4.5.2 Prerequisites

Before advancing projects:

- Ensure that all of the objects in a project are checked in, including objects in projects that will inherit a token.

- In SAR-based systems, ensure that you complete all required SAR fields.

4.5.3 Advancing Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the project to be advanced.

2. Click the Advance Project button in the center column.

3. Click the field labeled >>>, and then enter the desired project status.
Your choices are limited, based on the current status of the project and on your company's specific procedures, which are defined in the JD Edwards EnterpriseOne OMW Configuration application.

Note:
Select the Validate Only option to validate the status change without actually advancing the status of the project. This option enables you to verify that the project is valid before attempting any object transfers. Any projects that are linked to it through token inheritance are validated at this time as well.

4. Check for dependencies, if applicable.
When you advance a project, you can use the Check Dependency feature to determine whether the project contains objects that can be rolled up when an ESU is created. If the system finds a rule violation, the project is not transferred.

5. Click OK.
If you did not select the Validate Only option, the system advances the project status and initiates any required object transfers and deletions. Otherwise, the system validates only the project status.

Use the JD Edwards EnterpriseOne OMW logging system to view any errors that occurred during the status change. If you cannot advance the project, verify the following:

- All of the objects in the project are checked in, including objects in projects that inherit a token.

- If you are using a SAR system, you have completed all of the required fields in the SAR.

4.6 Adding Existing Projects to a Project

In addition to objects and users, projects can contain other projects. You can add a project to a project or, if the target project and the project to be added both appear in your project window, you can move the project to be added under the target project using drag-and-drop. The methods for adding and moving projects are identical to the methods for adding and moving objects.

See Working with Objects.

4.7 Deleting Projects

This section provides an overview of project deletion and discusses how to delete projects.

4.7.1 Understanding Project Deletion

When you delete a project, the system removes all objects and owners from the project. The project is then completely deleted from the system.

If you delete a project that contains objects that are checked out, the system erases the check out for each object before deleting the project. If the project holds any tokens, the system releases them as well.

4.7.2 Deleting Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click a project, and then click Delete.
The system confirms the deletion.

2. Click OK in the Confirm Delete query.

5 Working with Objects

This chapter contains the following topics:

- Section 5.1, "Understanding Objects"

- Section 5.2, "Creating Objects"

- Section 5.3, "Searching for Objects"

- Section 5.4, "Adding Objects to Projects"

- Section 5.5, "Moving Objects"

- Section 5.6, "Removing Objects from Projects"

- Section 5.7, "Deleting Objects"

- Section 5.8, "Downloading Object Specifications"

- Section 5.9, "Checking Objects In and Out"

- Section 5.10, "Changing Objects"

- Section 5.11, "Maintaining Objects in Multiple Software Release"

5.1 Understanding Objects

JD Edwards EnterpriseOne OMW enables you to administer database objects in a tool that displays nodes, tables, business views, indexes, and programs hierarchically. Rather than have an administrator manage all of the objects and track what modifications went with which SAR/Project, you do it yourself. You can create and manage a variety of objects with JD Edwards EnterpriseOne OMW, including:

- Applications

- Business functions

- Data structures

- Tables

- Business views

- Data and menu items

- User defined codes (UDCs)

- Workflow processes

5.2 Creating Objects

Access JD Edwards EnterpriseOne OMW.

1. From the JD Edwards EnterpriseOne OMW, click Add.

2. In Add JD Edwards Object to the Project, click the object type that you want to create, and then click OK.
The Add Object form appears. The contents of this form vary based on the type of object that you are creating.

3. In Add Object, complete the fields as appropriate for the type of object you are creating, and then click OK.
Depending on the object that you are creating, a design form, which provides the functions you need to design the object, might appear. For example, if you create an interactive application, the Interactive Application Design form appears. Click the Design Tools tab to access the buttons that launch Form Design Aid, Work with Vocabulary Overrides, Work with Interactive Versions, and so on.

Note:
The Object Librarian name for a business view can have a maximum of 9 characters and should be formatted as follows: VzzzzzzzA.

5.2.1 Alternative Method to Accessing Design Tool Functionality

After you create an object you can also access the appropriate design tool by clicking the object, and then clicking one of the following buttons located on the left-hand side of the screen:

- Start Design
Select an object and then click the Start Design button to automatically launch the design tool associated with the object.

- Start BusBuild
Select a business function object that you have designed, and then click Start BusBuild to launch the tool used to build the business function.

- Start Browse ER
Select an object and then click Start Browse ER to view the object's event rules.

- Run HTML
Select an application and then click Run HTML to execute the application in HTML format.

5.3 Searching for Objects

This section provides an overview of object searches and discusses how to search for objects.

5.3.1 Understanding Object Searches

Conducting an efficient search is preliminary to adding objects to a project. You can search for objects by category and type, or you can perform an advanced search and find objects based on other criteria.

Note:
Searches are case-sensitive. When you enter your search criteria, enter the commonly accepted spelling in standard capitals and lower case. If you receive no search results, try different capitalization or spelling.

5.3.2 Searching for Objects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the Search tab.

2. Complete the following fields, and then click the button next to the Search field:

- Category. You can search a variety of categories. For example, to find a report, select Object Librarian as the category because reports are Object Librarian objects. To find a project, select JD Edwards EnterpriseOne OMW Project. To find a user, select Owners.

- Search Type. Valid choices for this field vary based on the category that you select. If you set the search type to Object Name|Version Name, you can use the | delimiter to specify a search suffix. For example, if the category is Object Librarian and the search type is object name, entering R0008P|XJDE* displays all XJDE versions of object R0008P (Date Patterns Report).

- Search. Entries in this field must match the Search Type that you select.

3. To search for objects based on criteria other than category, search type, and name, click Advanced Search.

4. In Object Librarian Search and Select, enter the desired criteria in the Query by Example columns, and then click Find.

5. Select one or more objects, and then click Select.
The objects that you chose appear in the information window.

See Also:

- Adding Objects to Projects.

5.4 Adding Objects to Projects

This section provides an overview of object addition and discusses how to:

- Add an object.

- Add multiple objects.

5.4.1 Understanding Object Addition

An object must exist within one of your projects before you can work with it. You can add an existing object to a project, or you can create a new object for a project. When you create a new object, the system places it in the current project that you have selected. If you did not select a project before creating the object, the system places it in your default project. Adding an object to a project neither checks out the object nor downloads the specifications of the object to your local environment.

Note:
If you try to add an object to a project that already exists in that same project, the Release Search & Select form appears because the system enables you to modify the same object across multiple releases.

See Also:

- Adding Objects to Projects.

- Checking Objects In and Out.

5.4.2 Adding an Object

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the project to which the object will be added.

2. Find the object to add to the destination project by performing a search using the Search tab in the information window.

3. When the search completes, on the search form, select the object to be added to the destination project.

4. Verify that the destination project is highlighted in the project window. If it is not highlighted, click it.

5. With the object to be added highlighted, click the Add Object or User to Project button in the center column.

5.4.3 Adding Multiple Objects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the project to which the objects will be added.

2. Find the objects to add to the destination project by performing a search using the Search tab in the information window.

3. Verify that the destination project is highlighted in the project window. If it is not highlighted, click it.

4. From the Row menu, select Advanced, and then select Add All Objects.
The system adds all of the objects that fit the search criteria to the project that you selected in step 1.

5.5 Moving Objects

You can move objects from one project to another by dragging and dropping them. Both projects and the object must be visible in your project window. This task can be used to move users from one project to another or to move a project to another project.

This section discusses how to:

- Move an object.

- Move multiple objects.

5.5.1 Moving an Object

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, in the project window, click and hold the mouse button on the object that you want to move.

2. Drag the object over the target project and release the mouse button.
The system removes the object from the source project and adds it to the target project.

5.5.2 Moving Multiple Objects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, in the project window, click the project that contains the objects that you want to move.

2. From the Row menu, select Advanced, and then select Move Objects.

3. In Move Multiple Objects Search & Select, in the To Project field, enter the project to which you want to move the selected objects.

4. In the detail area, click the objects that you want to move.

5. Click Select.
The system moves the objects from the source project to the target project. This process might take several minutes, depending on the number of objects that you selected.

5.6 Removing Objects from Projects

This action removes the reference to the object from the project; it does not delete the object. This task also can be used to remove users from a project.

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select an object in the project window.

2. Click the Remove Object or User from Project button in the center column.
Alternatively, you can select the object, click the Row exit, and then click Remove Object.

5.7 Deleting Objects

This section provides an overview of object deletion and discusses how to delete objects.

5.7.1 Understanding Object Deletion

You can delete any object from the server that is configured for the project's current status. You can also mark an object for deletion from its transfer locations upon project advancement or from its current save location (the location where the system saves the object when you click the Save button in the center column of JD Edwards EnterpriseOne OMW).

You can also use this task to remove the specifications for Object Librarian object from your workstation.

When you select Delete Object from Server, the system deletes the object from locations that are defined in the transfer activity rules when you click OK. If you select Mark Object to be Deleted from Transfer Locations, the system deletes the object from any other configured locations when the project advances.

For an Object Librarian object, you can delete the local and save specifications. If the Object Librarian object is checked in, you can delete the checked-in version of this object by choosing Delete Object from Server. If you select Mark Object to be Deleted from Transfer Locations, the Object Librarian object is deleted from its transfer locations, which are defined in the transfer activity rules when the Project Status is advanced.

5.7.2 Deleting Objects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select an object in the project window.

2. Click Delete.
A Delete form appears. Your available options vary depending on the object type and whether the object has been checked in.

3. Select one or more of the following options, and then click OK:

- Delete Object from Server
Click View Locations for a list of locations from which the object is deleted when you select this option. This action occurs as soon as you click OK.

- Delete Object Locally
This action occurs as soon as you click OK.

- Delete Object from the SAVE location
This action occurs as soon as you click OK.

- Mark Object To Be Deleted From Transfer Locations
Objects marked for deletion from transfer locations appear in bold letters in the project window. They are deleted from the transfer locations when the project status is advanced.

- Remove Object from ALL locations
This option selects all of the above options.

5.8 Downloading Object Specifications

This section provides an overview of specification downloads and discusses how to use the advanced get feature.

5.8.1 Understanding Specification Downloads

To download checked-in object specifications from the server that is defined for the current status, select the object and click the Get button in the center column. Use this function when someone else has been working on the object and you want to see the changes, or when you have made changes to the object but want to abandon them in favor of another version of the object.

The Get button enables you to get the specifications for objects that reside in your path code only. However, you can download the specifications of an object that resides in other areas of the system. For example, you might want to get the specifications for an object as it existed in a previous software release. Use the advanced get feature to specify the location of the object that you want to download.

Note:
If you want to review the object and not save any changes, use the Get button to copy the latest specifications to your local workstation instead of checking out the object and then erasing the checkout.

5.8.2 Saving and Restoring Objects and Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select the object or project that you want to save.

2. Click the Save button in the center column.
The jdeomw dialog box displays. OMW provides two methods with which to save an object. The first method is to save the object to a zip file. If you save the object to a zip file, OMW saves the object or project as a local copy in a format compatible with Zip, Jar and JDEdwards Change Assistant technologies.The second method is to save the object to a shared database location. The shared location is configured by your OMW administrator, and is the most common method with which you will save objects or projects.

3. Click Yes to save the object to a zip file, or click No to save the object to a pathcode save location.

4. If you clicked Yes, continue to step 5. If you clicked No, OMW saves the object to pathcode save location.

5. On the Select Folder form, select the folder to which you want to save the object, and then click Open.

To restore an object or project, access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select the object or project that you want to restore.

2. Click the Restore button in the center column.
The jdeomw dialog box displays and provides options for you to choose from where you want to restore the object. You can choose to restore the object from a zip file, or to restore the object from the Save location specified by the OMW administrator.

3. Click Yes to restore the object from a zip file, or click No to restore the object from a pathcode save location.

4. If you clicked Yes, continue to step 6. If you clicked No, OMW restores the object from the pathcode save location.

5. On the Select Folder form, select the PAR file from which you want to restore the object or project, and then click Open.
OMW restores the object or project.

5.8.3 Using the Advanced Get Feature

Advanced Get on Projects enables you to get projects from any pathcode. To perform an Advanced Get on Projects, every object in the project must reside in the pathcode from which you have selected the project. This functionality is only applicable to Object Librarian objects, for example, applications, UBEs, DSTR. It is not functional with UDCs, DDs, menus, and so forth.

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select an object in the project window.

2. From the Row menu, select Advanced, and then select Advanced Get.
You are prompted to decide whether you want to overwrite local specifications.

3. Click one of the following options:

- Yes
If you select Yes, go to step 5.

- No
If you select No, continue with step 4.

4. In Path Code Search & Select, enter the path code, and then click Find.

5. Select the location of the object that you want to get, and then click Select.

5.8.4 Performing Quick Gets on Objects

Quick Gets enable you to perform Gets on objects returned to the OMW Project Search and Select by Object form, and the Object Librarian Search and Select form. From these forms, you can select one or many objects to Get.

Note:
When you Get an object you copy the object and its specifications to your work area without checking out the object.

Access OMW.

1. On the Search tab of the main OMW interface, in the Category field, select Object Librarian.

Note:
Object Librarian is the only category for which Quick Gets is enabled.

2. Click Advanced Search.

3. On the Object Librarian Search and Select form, click Find.

4. Select the objects you want to Get, click the Row menu, and then click Quick Gets.
The Overwrite Specifications Confirmation form displays with the following options:

Default – This option copies an object and its specifications from the configured checkout location to your work area without checking the object out.

Advanced - Advanced Get on Projects enables you to get projects from any pathcode. To perform an Advanced Get on Projects, every object in the project must reside in the pathcode from which you have selected the project. This functionality is only applicable to Object Librarian objects, for example, applications, UBEs, DSTR. It is not functional with UDCs, DDs, menus, and so forth.

If you choose this option, you will get the Pathcode & Select form. Enter criteria for which you want to search, and then click Select. OMW returns you to the OMW main screen.

Additionally, you can access Quick Gets using the following method:

1. From the Row menu, select Select by Object.
The OMW Project Search and Select by Object form displays.

2. Enter criteria for which you want to search, and then click Select. OMW returns you to the OMW main screen, and then click Find.

3. Choose the objects you want to get, and then click the Row menu, and then click Quick Gets.

4. From the Row menu, select Quick Gets.
The Overwrite Specifications Confirmation form displays with the following options:

Default – This option copies an object and its specifications to your work area without checking the object out.

Advanced - Advanced Get on Projects enables you to get projects from any pathcode. To perform an Advanced Get on Projects, every object in the project must reside in the pathcode from which you have selected the project. This functionality is only applicable to Object Librarian objects, for example, applications, UBEs, DSTR. It is not functional with UDCs, DDs, menus, and so forth.

If you choose this option, you will get the Pathcode & Select form. Enter criteria for which you want to search, and then click Select. OMW returns you to the OMW main screen.

5.9 Checking Objects In and Out

This section provides an overview of object check in and check out and discusses how to:

- Check out objects.

- Check in objects.

- Erase checkouts.

5.9.1 Understanding Object Check In and Check Out

You can check out an Object Librarian object that resides in your projects provided that the token for the object is either available or held by the project in which the object currently resides. Only one user at a time can check out an object. Checkout fails if the object is already checked out or if the token is unavailable. If the token is unavailable, you can join the token queue for the desired object. If you join the token queue, you will be notified when the token is available and your project will receive the token.

Check in an object when you want to upload its specifications to the server and make it publicly available. When you check in an object, the system records the project in which the object resides and ensures that only changes made under the current project are transferred when the project is advanced to a status that triggers a transfer. If you move an object from one project to another using the drag-and-drop method, the system tracks the change and records the new project for the object. However, consider the following scenario:

1. You add an object to a project and check it out.

2. You change the object and check it in.

3. You use the right-facing arrow in the center column to remove the object from the project.

4. You later add the object to a different project.

In this scenario, the system cannot track the object because it passes out of a project completely. Therefore, when you advance the second project, if the system needs to transfer the object as part of the advance, the transfer will fail because the object's last known check in project location and its current project location do not match.

When you drag-and-drop an object, the system updates its tables in such a way that the transfer can occur. This is not the case when you remove an object from a project and then add it to a different project later.

If an object is checked out, you can erase the checkout. When you erase a checkout, local changes are not uploaded to the server. Erasing the checkout for an object does not release its token, but it does enable other developers who are assigned to the same project to check out the object.

5.9.2 Checking Out Objects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select an object in the project window.

2. Click the Checkout button in the center column.
JD Edwards EnterpriseOne OMW indicates that an object is checked out by superimposing a check mark over the object's button. Additionally, data about the object that appears in the information window is updated to reflect its checked out status.

Note:
If the object is unavailable, the system asks if you want to be added to the token queue for the object. If you select to join the queue, the system alerts you when the token is released and assigns the token to your project. To determine which project holds the token for an object, select the object in the project window and click the News/Status tab in the information window. The information in the News/Status window only refreshes if the window is selected. If the Search window is selected, the information in the News/Status window is not updated when you select different objects. Additionally, if you have joined a token queue, your position in the queue appears here.

5.9.3 Checking In Objects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select a checked-out object in the project window.

2. Click the check in button in the center column.
JD Edwards EnterpriseOne OMW indicates that an object is checked in by removing the check mark that was superimposed over the object's button when it was checked out.

5.9.4 Checking in Object Specifications without Checking in the Object

You can check in an object's specifications without losing your ability to modify the object. This enables you to check in a partially completed object without having to check the object back out to continue development on it.

Access JD Edwards EnterpriseOne OMW.

1. Select an object.

2. From the View menu, choose Checkin/Checkout.

5.9.5 Erasing Checkouts

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select a checked-out object in the project window.

2. Click the Erase Checkout button in the center column.
JD Edwards EnterpriseOne OMW indicates that an object is no longer checked out by removing the check mark that was superimposed over the object's button when it was checked out.

5.10 Changing Objects

This section provides an overview of object changes and discusses how to change objects.

5.10.1 Understanding Object Changes

When you create an objects, JD Edwards EnterpriseOne OMW enables you to define the properties of the object. JD Edwards EnterpriseOne OMW also provides access to design tools and system actions for the object. Similarly, after the object is created, you can use JD Edwards EnterpriseOne OMW to modify the object and its specifications.

Your system administrator can also specify a separate save location that is different from your local environment and from the location of the object on the server. You save objects to this location when you select the object and click the Save button in the center column. Retrieve an object from its save location by selecting the object and clicking the Restore button in the center column. Note that the save location for the object must be different from its system location.

You must check out the object before you modify it to be able to check the object back in and upload the changes.

As users modify objects, the changes exist only in their local environments until they either save the object to its save location or check in the object to its system location.

5.10.2 Changing Objects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select an object in the project window.

2. Click the Design button in the center column.
An appropriate design form for the object appears. The current properties of the object appear on the form.

3. Make the necessary changes to the object, and then click OK.

5.11 Maintaining Objects in Multiple Software Release

This section provides an overview of objects in multiple software releases, lists a prerequisite, and discusses how to:

- Add same-named objects to a project.

- Change the release level of an object on your project.

- Update an object to match another object.

- Update different objects in different releases.

5.11.1 Understanding Objects in Multiple Software Releases

Same-named objects in different software releases can be modified in JD Edwards EnterpriseOne OMW in the same project. After adding the objects to the project, you can maintain them independently or you can update one to match the other. When working on objects from separate releases, JD Edwards EnterpriseOne OMW handles save and check in file paths for you, based on the Object Management Configuration. You perform the necessary modifications and use the JD Edwards EnterpriseOne OMW functions as you would normally.

Important:
Changing and maintaining objects in multiple releases can cause problems due to JD Edwards EnterpriseOne object interdependencies. Changing an object in one version and then updating the object in another version to match might cause dependent objects to malfunction.

5.11.2 Prerequisite

Determine the paths of the objects that you want to modify.

5.11.3 Adding Same-Named Objects to a Project

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, add the first object to the project.

Note:
The object is added to the project at the current release level of your JD Edwards EnterpriseOne.

2. Add the same object to the project again.

3. In the Release Search and Select form, click Find.
All available releases for which the object can be added to the project appear.

4. Click the release you want, and then click Select.
The object is added to the project for the selected release level.

5.11.4 Changing the Release Level of an Object on Your Project

Access JD Edwards EnterpriseOne OMW

1. In JD Edwards EnterpriseOne OMW, select Advanced from the Row menu, and then select Change Release.

2. In the Release Search and Select form, click Find.
All available releases for which the object can be added to the project appear.

3. Click the release that you want, and then click Select.
The object is added to the project for the selected release level.

5.11.5 Updating an Object to Match Another Object

Access JD Edwards EnterpriseOne OMW.

1. Check out the object A from release A.

2. Modify the object.

3. Check in the modified object A.

4. Check out the object B from release B.

5. Select object B, select Advanced from the Row menu, and then select Advanced Get.

6. Click Yes to override local specifications.

7. In Path Code Search & Select, find and select the path code in which the release A version of the object was checked in, and then click Select.
In your project, the release B version of the object is modified to match the release A version of the object.

8. Check in object B.

5.11.6 Updating Different Objects in Different Releases

Access JD Edwards EnterpriseOne OMW,

1. Check out the object from release A.

2. Modify the object.

3. Check in the modified object.

4. Check out the object from release B.

5. Modify the object.

6. Check in the modified object.

6 Working with Business Services

This chapter contains the following topics:

- Section 6.1, "Understanding Business Services"

- Section 6.2, "Creating Business Service Objects"

- Section 6.3, "Searching for Business Service Objects"

- Section 6.4, "Viewing the OMW HTML Status Page"

- Section 6.5, "Designing Business Services"

- Section 6.6, "Checking In, Checking Out, and Saving Business Services"

- Section 6.7, "Working with Business Services Properties"

6.1 Understanding Business Services

Business services are JD Edwards EnterpriseOne business function objects that are used for interoperability between JD Edwards EnterpriseOne and other applications or systems. Business services are written in the Java programming language and provide business service operations that access the business logic in JD Edwards EnterpriseOne for many supported business transactions, such as journal entries, exchange rates, accounts payable vouchers, inventory look-ups, pricing, sales orders, and so on. You use Oracle's JDeveloper tool and the Java programming language to create a business service. The JD Edwards EnterpriseOne web services framework provides a set of foundation packages that helps you create a business service. Each foundation package contains a set of interfaces and related classes. All business service classes extend from ServiceBusinessFunction.

See "JD Edwards EnterpriseOne Tools Business Services Development Overview" in the JD Edwards EnterpriseOne Tools Business Services Development Guide.

6.2 Creating Business Service Objects

You create business services in OMW.

Access JD Edwards EnterpriseOne OMW.

1. Select an open OMW project and press the Add button.

2. Select the Business Function radio button on the Add EnterpriseOne Object form and click OK.

3. On the Add Object form, complete the following fields:

- Object Name
The naming convention for business services is J*******. If the business service is going to be published, the naming convention is JP*****.

- Description
The description of a record in the Software Versions Repository file. The member description is consistent with the base member description.

- Product Code
A user defined code that identifies a system.

- Product System Code
A user defined code that specifies the system number for reporting and jargon purposes.

- Object Use
Object Use Designates the use of the object. For example, the object may be used to create a program, a master file, or a transaction journal.

4. Select the BSSV radio button.
The Package Prefix field becomes available.

5. In the Package Prefix field, click the Visual Assist in the Source Language group.
The Package Prefix is the parent Java package for all of the classes contained in the Business Service object. OMW will only allow the selection of administrator configured package prefixes. Oracle recommends that you click the Visual Assist for specifying the package prefix.

6. On the BSSV Package Prefix Search & Select screen, click Find.

7. Click the package prefix you want associated with your business service and then click Select.

8. Click OK.
From here, you can click the Design Tools tab, and click Invoke JDeveloper to design artifacts for the business service. See Designing Business Services.

6.3 Searching for Business Service Objects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the Search tab.

2. Complete the following fields, and then click the button next to the Search field:

- Category: Select Object Librarian.

- Search Type: Select Object Name.

- Search: If you know the business service object name, type it in the Search field. If you do not, type J* to search for business services, and JP* to search for published business services.

3. Click the Search button locate to the right of the Search field.
OMW returns all of the objects that match your search criteria.

See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide

6.4 Viewing the OMW HTML Status Page

The News/Status tab indicates the select object's status in OMW. For business services, the News/Status tab shows you the following information about the business service you have selected:

- Object Name

- Description

- Object Type

- BSFN Type

- Javadoc

- Product Code

- Object Status

- Manager

- Supervisor

- Pathcode

- User

- Machine Key

- Date

- Time

- Project that holds the token for this object

- Is this project inheriting the token for this object

Additionally, you can view token information from the News/Status tab. This tab displays the following information about the token:

- If the current project holds the token

- How many projects are waiting for the token

- If this project is inheriting it's token

- If this project is in the token queue

- What the projects' place is in the queue

Access JD Edwards EnterpriseOne OMW.

1. Select the business service on which you want to view News/Status.

2. Click the New/Status tab located to the right of the object tree.

3. On the Select Tab drop-down menu, select one of the following:

- Summary: Select this option if you want to view the Object Librarian/Object Status information of the selected business service.

- Token: Select this option if you want to view the token information of the selected business service.

6.5 Designing Business Services

You create business services in OMW and add Java code to them through JDeveloper. The Java code is contained in.java files, called artifacts, and make up the functionality of the business service. From JDeveloper, you add Java code to the business service. Artifacts contain business service operations that Java code uses to interact with EnterpriseOne. These artifacts and business service operations display in OMW after you have checked them out, and then checked them in.

6.5.1 Pointing EnterpriseOne to JDeveloper Installation Path

You can access JDeveloper through OMW to design your business services after you have created them. Use JDeveloper to create artifacts in Java for your business services.

See JDeveloper Installation guide for more information about installing JDeveloper.

Access JD Edwards EnterpriseOne OMW.

1. Open the project in which the business service object resides, and select the business service object.

2. Click the Design button.

3. On the Business Function Design form, click the Design tab.

4. Click JDeveloper Install Path.
In the blank field located at the bottom of the screen, specify your client install folder where your JDeveloper application resides. OMW launches the JDeveloper application specified on this form when you click the Invoke JDeveloper button. Use the visual assist button located to the right of the field to help you browse to the specific folder in which your JDeveloper resides.

6.5.2 Invoking JDeveloper

Once a business service has been added to OMW, you can use OMW to launch JDeveloper if you want to add or make changes to the business service artifacts.

Note:
Using OMW to launch JDeveloper installs the EnterpriseOne integration components into JDeveloper. Only after JDeveloper installs these integration components will you be able to use the EnterpriseOne wizard to create projects in JDeveloper, to call EnterpriseOne business functions, to create Value Objects, and so forth. Additionally, invoking JDeveloper from OMW creates a workspace for EnterpriseOne objects and the JDeveloper project for the business service, if these two items do not already exist. A check will occur every time JDeveloper is invoked. Configuration only happens if the check fails.
Access JD Edwards EnterpriseOne OMW.

1. Open the project in which the business service object resides, and then select the business service object for which you want to invoke JDeveloper.

2. Click the Design button.

3. On the Business Function Design form, click the Design tab.

4. Click Invoke JDeveloper.

6.5.3 Adding Artifacts to a Business Service

You add artifacts to a business service through JDeveloper. For more information about adding artifacts, see the JDeveloper online documentation.

Access JD Edwards EnterpriseOne OMW.

1. From the OMW Design tab, click Invoke JDeveloper.

2. On the Save Files dialog box, click OK to save all of the .jpr files that are selected.

Note:
Only your specific .jpr file will have changed. You can also select to save just your .jpr. To do so, deselect the other files and click OK.

3. Click the business service you created in OMW.

4. Select the business service, the right-click and select New.

5. On New Gallery, click Java Class, and then click OK

6. On Create Java Class, in the name field, type the name of the new artifact you are adding.

7. Accept the default values and selections.

8. Click OK.
The artifact Java file displays under the business service.

9. Enter the business service operations in the artifact.

10. Click Save All.

11. Click File, and then Exit.

6.6 Checking In, Checking Out, and Saving Business Services

When you check in business service objects, OMW enables you to view the artifacts associated with the objects and enables you to select which artifacts you want to check in. OMW will only allow those artifacts that have been configured correctly to be checked in. When checked in, the business service object is moved to the centralized EnterpriseOne pathcode.

When you save a business service object, OMW checks in all artifacts to the save pathcode, including those not configured properly.

Note:
When you check in a project that contains business services, OMW requires you to input information as you check in the business service objects that is not required for other object types. Therefore OMW first checks in the business service objects, then checks in the remaining objects so that you need to be present only during the business service check in.
Therefore OMW first checks in the business service objects, then checks in the remaining objects so that you need to be present only during the business service check in.

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select the business service object that is checked-out.

2. Click the Check-in button in the center column.

3. The View Artifacts to Check In form displays. A list of artifacts displays in the grid with the following information:

- Artifact Name

- Artifact Path

- Artifact State

- State Description
A green check mark indicates that the item is checked in. A circle with a line through it indicates that the file cannot be checked in because it is not configured properly for check in.

4. Select the artifacts you want to check in by clicking the columns to the left of the Artifact Name field, if necessary. Selecting artifacts adds or removes the green check mark.

5. Click OK.

To save a business service object, access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select the business service object that is checked out.

2. Click the Save button in the center column.
JD Edwards EnterpriseOne OMW indicates that an object is checked in by removing the check mark that was superimposed over the object's button when it was checked out.

6.6.1 Checking In Artifacts

To check in artifacts in OMW, you must first add them to the business service object in JDeveloper.

Access JD Edwards EnterpriseOne OMW.

1. From the OMW Design tab, click Invoke JDeveloper.

2. Click the business service you created in OMW.

3. Right-click, and select New Java class.

4. Click OK.

5. Name the artifact and make any changes you need.

6. Click OK, and then click Save.

7. In OMW, click OK.

When you check in the business service from OMW, you will check in the artifacts as well.

6.6.2 Checking Out a Business Service Object

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select the business service object in the project window.

2. Click the Checkout button in the center column.
The View Artifacts to Check Out form displays.

3. Click OK.
Artifacts for the business service will be overwritten when you check out a business service object.

6.6.3 Understanding the Business Service Artifact List

Artifacts are the files or components that comprise a Business Service in EnterpriseOne. You can view which artifacts are checked into the pathcode for the Business Service. For OMW to display the artifacts that are associated with a business service, the associated business service must be checked in.

Note:
OMW displays those artifacts that are located on your local machine. The artifacts located on another server might be different.

6.6.4 Viewing Artifacts

When you check out a business service, the View Artifacts to Check Out form displays. A list of the artifacts associated with the business service displays in the grid. Everything in this grid will be downloaded from the deployment server to the client server.

Access JD Edwards EnterpriseOne OMW.

1. Open the project in which the business service object resides, and then select the business service object that contain the artifacts you want to view.

2. Click Design.

3. On the Design Tab, click the View Checked in Artifacts button.
The View Checked in Artifacts form displays. This form provides information about the artifacts that comprise the business service in a specific pathcode. This form provides only limited information on what artifacts are present for the business service on the local development client. The artifact file you want to view is on your local machine. This file is different on the server than it is on your local machine.

4. View the following fields for artifact information:

- Business Service Name

- Package Prefix

- Pathcode: This field contains the pathcode from which the information is being retrieved.

- Published Class Name: This field indicates if an artifact in the business service is published. The field is populated with the name of the artifact that is published in the business service. This artifact is a Java class that defines which business service operations in the business service are accessible from the Web Services server. If this field is blank then this business service is not published.

5. In the grid located at the bottom of the form, EnterpriseOne displays a list of all of the artifacts that make up the business service in the specified pathcode. Each grid record indicates the artifact name, the artifact internal path, and the artifact state description.
The artifact internal path is made of many folders that are nested inside the business service root folder. The root folder of a business service is as follows:

<E1 install folder>\<pathcode folder>\java\source\<package prefix>\<Business Service name>

For example, if you have business service JPTEST on a DV812 client, and the package prefix is oracle.e1.bssv. JPTEST's root folder is as follows:

C:\B9\DV812\java\source\oracle\e1\bssv\JPTEST\

Furthermore, if the grid lists an artifact named testing.java, and the internal path is util\testing, then the full path to testing.java on the development client will be as follows:

C:\B9\DV812\java\source\oracle\e1\bssv\JPTEST\util\testing\testing.java

The last two columns in the grid indicate the state of the artifact. The state can be either that the artifact was checked into the pathcode but is not currently found on the local client, or that the artifact was checked into the pathcode and is also currently found on the local client.

6. Click OK.

6.6.5 Understanding Published Artifacts

A published business service gives exposure to one or more business service functions by providing an interface that is available to the public as consumable web services. A published business service is a Java interface that provides a wrapper for the business service operations where the actual business logic is performed.

You use the same tools and framework to create a published business service that you used for creating a business service.

All published business service classes extend from PublishedServiceBusinessFunction.

6.6.6 Specifying a Published Artifact

When you check in a business service, you specify the valid artifacts you want published. Valid artifacts are those that meet the rules that are set for publishable artifacts.

Access JD Edwards EnterpriseOne OMW.

1. In JDeveloper, add your business service operations to an artifact and then save the artifact.

2. In OMW, select the business service that contains the artifact and click Check In from the middle bar.

3. From the Row exit, click Select Publish.
The Are you sure you wish to proceed with the check in? dialog box displays. This dialog box alerts you that which artifact is published could have severe ramifications. It is recommended that you click Cancel.

For published artifacts, the standard naming convention is JP******.

4. Click OK.

6.6.7 Unpublishing a Published Artifact

You might want to unpublish an artifact for many reasons, including if the artifact no longer needs to be exposed to the web, or if you want to delete a business service.

Access JD Edwards EnterpriseOne OMW.

1. When you check in a business service, the View Artifacts to Check In form displays. Click the Form Exit, and click Unpublish Artifact.
The Are you sure you wish to proceed with the check in? dialog box displays.

2. Click Yes.

3. Click OK.

6.6.8 Deleting a Business Service

You cannot delete a business service that has published artifacts. Therefore you must unpublish all artifacts to delete a business service.

Access JD Edwards EnterpriseOne OMW.

1. Select the business service you want to delete from the appropriate Objects folder.

2. Click Delete.

3. On the Delete of … form, select one or all of the options:

- Delete Object from Server

- Delete Object Locally

- Delete Object from the SAVE Location

- Mark Object to be Deleted from Transfer Locations

- Remove Object from ALL Locations

4. Click OK.

6.7 Working with Business Services Properties

You can manage business service properties through OMW.

See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.

6.7.1 Adding a Business Service Property

Access JD Edwards EnterpriseOne OMW.

1. On OMW, click Add.
The Add EnterpriseOne Object to Project form displays.

2. Click the BSSV Property radio button.

3. Click OK.

4. On the Add BSSV Property, complete the following fields:

- Key

- Value

- Description

- Level

- BSSV

- Group

5. Click OK.

6.7.2 Searching for a Business Service Property

Access JD Edwards EnterpriseOne OMW.

1. On the Search Tab, from the Category field, select Business Service Property.

2. Click in the Search Type field.

3. In the search field, type the BSSV Property name, and then click Search.

6.7.3 Adding a Business Service Property to a Project

Access JD Edwards EnterpriseOne OMW.

1. Select the BSSV Property in the Search field, and click the Add Object or User to Project button located in the center column.

2. In the Release field, click the Search button and select a release from the list.

3. Click Select.

4. Click Close.

7 Working with Tokens

This chapter contains the following topics:

- Section 7.1, "Understanding Tokens"

- Section 7.2, "Viewing the Token Queue"

- Section 7.3, "Inheriting Tokens"

- Section 7.4, "Switching Tokens"

- Section 7.5, "Releasing Tokens Manually"

7.1 Understanding Tokens

In JD Edwards EnterpriseOne OMW, Object Librarian objects use tokens to minimize the possibility of one user overwriting another user's changes. Each object has a single token, and it is associated with a project when the object is checked out. Checking in the object does not release the token; instead, the token is released when the status of the project changes to a level determined by your system administrator. At that time, another developer can check out the object and receive the token.

These three actions are allowed while your project holds the token:

- Allow another project to inherit the token. This action forces both projects to be advanced together as if they were one project and allows multiple corrections to a project to be applied to a single object. No matter how many projects have inherited the token, however, only one user at a time can check out the object. For a project to successfully inherit a token, the target project must be at the same status as the source project.

- Switch the token to another project. After the token is switched, the project that loses the token will be placed in the token queue as the first project that is waiting for the token. When you configure JD Edwards EnterpriseOne OMW, token switching should be restricted to a specific user role so that you can maintain object security.

- Release the token. A project owner can give up the token and allow the next project in the queue to receive it.

JD Edwards EnterpriseOne OMW might have been configured to release tokens for different object types at different project status levels. Therefore, all object types might not give up their tokens during the same change in project status.

7.2 Viewing the Token Queue

This section provides an overview of the token queue and discusses how to view the token queue.

7.2.1 Understanding the Token Queue

JD Edwards EnterpriseOne OMW attempts to acquire a token for an object when you check out an object. If the token is unavailable, the information window displays information about the token, such as which project currently holds it, the user who checked it out, and when the user checked it out. You can join the token queue so that you are notified when the token is released and your project is assigned the token. Projects in the token queue are assigned the token in the order in which the users requested the token. In addition to joining the token queue, you can select to inherit the token.

When a project has a token, the token stays with that project until the project advances to a status that is configured in the activity rules for release of the token or until it is switched or released manually. When the token is released, the next project in the token queue is notified and assigned the token. Each Object Librarian object has one token per release.

If you join a token queue and then decide later that you do not need the token, remove the object from your project to relinquish your position in the queue.

7.2.2 Viewing the Token Queue

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click an object in the project window.

2. From the Row menu, select Advanced, and then select Token Queue.
The View Object's Token Queue form appears. The form shows which project currently holds the token and which projects, in order, are in the queue.

See Also:

- Inheriting Tokens.

7.3 Inheriting Tokens

This section provides an overview of token inheritance and discusses how to inherit tokens.

7.3.1 Understanding Token Inheritance

Token inheritance can be useful when developers have the same object in multiple projects for which they would like to implement changes simultaneously, without having to wait for other projects that are holding the token to progress through the project life cycle.

To inherit tokens, both the project holding the token and the inheriting project must be at the same project status. After a token is inherited, these projects will be linked and will automatically advance in project status together until the token is released. Therefore, if the project status of one project is advanced, the project status of its linked projects also advances. If one or more projects are linked through token inheritance, ensure that all development in the linked projects is complete before you advance the projects. The user who is attempting to advance the project must be assigned a role that permits this action in all of the linked projects, or the advance attempt will fail.

All project advancement requirements must be met for all projects that are linked through token inheritance; if one project fails to advance, JD Edwards EnterpriseOne OMW does not advance any of the other linked projects. If an advancement failure occurs, review the logs for all of the linked projects to determine where the errors occurred.

7.3.2 Inheriting Tokens

Access JD Edwards EnterpriseOne OMW.

1. Attempt to check out an object for which another project holds the token.
The system asks you whether you wish to enter the token queue for the object or inherit the token.

2. Select to inherit the token, and then click OK.

Note:
If you have inherited the token but cannot check out the object, the object is already checked out by another user. You cannot check out the object until the other user checks it in or until checkout is erased. This action prevents you from overwriting changes when you inherit the token.

7.4 Switching Tokens

This section provides an overview of token switching, lists a prerequisite, and discusses how to switch tokens.

7.4.1 Understanding Token Switching

A project owner whose role allows switching tokens may take the token from the project that currently holds it and assign it to another project. Switching tokens might be necessary when you need to make an emergency change. If a change in another project needs to be implemented to an object in your project, you can switch the token to the other project to allow the change.

Note:
After the token is returned, the user from whom the token was taken can save the object, check the object out, and then restore the object to return the object to its previous state before switching. However, the user must manually implement any changes made during the switch.

To switch a token, you must be an owner in both the holding and the requesting projects. Your role in both projects must be one that enables you to switch tokens at the current status of the project and for the object type.

7.4.2 Prerequisite

The token requester should attempt to check out the object and then join the token queue.

7.4.3 Switching Tokens

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select the object that has the token that you want to switch.

2. Click the Switch Token button on the central column.

3. In Project Token Queue Search and Select, click Find.
A list of projects in the token queue appears.

4. Select the project to which you want to give the token, and then click Select.
The current token owner should save the object before you switch the token.

7.5 Releasing Tokens Manually

This section provides an overview of token release and discusses how to release tokens manually.

7.5.1 Understanding Token Release

You can release a token manually if you decide you do not need to modify an object. Additionally, you can release the token if you want to allow the next person in the token queue to check out the object for development. If you have made changes to an object and checked it in, another developer in another project must refrain from checking in the object until after your project has been promoted to a status where the system transfers the object to the next path code, or your changes will not be transferred.

See Also:

- Advancing Projects.

7.5.2 Releasing Tokens Manually

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, either erase the check out or check in the object that has the token that you want to release, if appropriate.

2. Select the object, and then click the Release Token button in the center column.

8 Working with Users

This chapter contains the following topics:

- Section 8.1, "Understanding Users"

- Section 8.2, "Searching for Users"

- Section 8.3, "Adding Users to Projects"

8.1 Understanding Users

To be able to perform JD Edwards EnterpriseOne OMW tasks, one must first exist as a user in the related JD Edwards EnterpriseOne system. Then, when you add a user to a project, you assign that user at least one JD Edwards EnterpriseOne OMW role. You can control what actions each user can perform by assigning at least one role to that user. The user role defines the user's function within the project organization. Roles in the JD Edwards EnterpriseOne OMW system are separate from roles in JD Edwards EnterpriseOne software. When you define user roles, you specify a user defined code value or job title for roles that can be played on a project. You can either assign predefined user roles or create your own user roles.

You can also remove a user from a project by removing all of the user's roles for that project.

8.2 Searching for Users

This section provides an overview of user searches and discusses how to:

- Search for users by name or ID.

- Search for users by class or group.

8.2.1 Understanding User Searches

Conduct a search before you add users to a project. You can search for user names or IDs, or you can perform an advanced search and find users based on their class or group.

Note:
Searches are case-sensitive. When entering your search criteria, enter the commonly accepted spelling in standard capitals and lower case. If you receive no search results, try different capitalization or spelling.

8.2.2 Searching for Users by Name or ID

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the Search.

2. Complete these fields:

- Category
Enter Owners.

- Search Type

- Search
Entries in this optional field must match the search type that you selected.

You can use | to specify a search suffix. For example, if the category is Owners and the search type is Address Book# | Search Type, entering *|E displays all entries in the Address Book with a search type of E for employee.

3. Click the Search button next to the Search field.

8.2.3 Searching for Users by Class or Group

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the Search.

2. Complete these fields:

- Category
Enter Owners.

- Search Type

3. Click Advanced Search.

4. In JD Edwards User ID Search and Select, complete one or more of the Query by Example columns and click Find.

5. Select the users that you want, and then click Select.

8.3 Adding Users to Projects

This section provides an overview of users in projects and discusses how to:

- Add users to projects.

- Remove users from projects.

- Change user properties.

8.3.1 Understanding Users in Projects

To affect a project and the objects within that project, a user must be added to the project. When added to the project, a user is assigned a specific role. This role dictates the kind of actions that the user can perform. A user can be added to a project more than once with different roles. Additionally, some roles can be associated with several users. For instance, a project might include several developers.

8.3.2 Adding Users to Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, click the project to which you want to add the users.

2. Set up a list of users to add to the destination project by performing a search using the Search in the information window.

3. In the search form, select the user to be added to the destination project.

4. Verify that the owner's node in the destination project in the project window is highlighted. If it is not highlighted, click it.

5. With the user to be added highlighted, click the Add Object or User to Project button in the center column.

6. In Add User to Project, enter the role and lead, and then click OK:

Note:
To add a user in more than one user role, repeat the add user procedure and select a second user role for the same user. Different functions are enabled for different user roles, according to their allowed (user) actions. These actions are configured by the administrator for your project using the configuration program of the JD Edwards EnterpriseOne OMW.

8.3.3 Removing Users from Projects

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select a user in the project window.

2. Click the Remove Object or User from Project button in the center column.

Note:
Removing a user from a project does not delete the user from the system.

8.3.4 Changing User Properties

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select a user (owner) in the project window, and then click Select.

2. In Project User Details, complete these fields, and then click OK:

- User Role

- Project Lead

- Estimated Hours

9 Working with Attachments

This chapter contains the following topics:

- Section 9.1, "Understanding Attachments"

- Section 9.2, "Viewing Attachments"

9.1 Understanding Attachments

JD Edwards EnterpriseOne OMW enables you to add text, graphic, OLE, and file attachments to projects and to Object Librarian objects within projects. These attachments are available only through JD Edwards EnterpriseOne OMW; they neither affect the way in which the object functions nor are they available when a user employs the object. You use this feature to document the creation, purpose, and intended use of objects in the system.

9.2 Viewing Attachments

This section discusses how to:

- View attachments in the Design view.

- View attachments in JD Edwards EnterpriseOne OMW.

9.2.1 Viewing Attachments in the Design View

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, create an object or project, or select an existing object or project, and click the Design button in the center column.

2. In the design form, click the Attachments.

9.2.2 Viewing Attachments in JD Edwards EnterpriseOne OMW

Access JD Edwards EnterpriseOne OMW.

1. In JD Edwards EnterpriseOne OMW, select a project.

2. Click the News/Status.

3. From the Row menu, select Attachments.
If attachments exist, they appear in the information window.

10 Configuring JD Edwards EnterpriseOne OMW

This chapter contains the following topics:

- Section 10.1, "Understanding JD Edwards EnterpriseOne OMW Configuration"

- Section 10.2, "Selecting a Configuration Option"

- Section 10.3, "Adding a New File Extension and New Package Prefix"

This chapter provides an overview of JD Edwards EnterpriseOne OMW configuration and discusses how to select a configuration option.

10.1 Understanding JD Edwards EnterpriseOne OMW Configuration

This section discusses:

- JD Edwards EnterpriseOne OMW configuration options.

- The configuration process flow.

- Allowed actions.

- Project and Object Logging.

- Project Constants

- Object Save Locations

- Object Action Notifications

- Notification Subscriptions

- Application and User Role Security

10.1.1 JD Edwards EnterpriseOne OMW Configuration Options

The JD Edwards EnterpriseOne OMW automates many of the object management tasks users performed manually in previous releases of the software. Much of this automation requires careful configuration by the system administrator through the JD Edwards EnterpriseOne OMW Configuration program.

Use the JD Edwards EnterpriseOne OMW Configuration program to configure these optional features:

Option

Description

Constants

Enables you to set general constants pertaining to JD Edwards EnterpriseOne OMW projects.

SAR System Integration

Enables you to disable SAR system integration with JD Edwards EnterpriseOne OMW and, thus, JD Edwards EnterpriseOne development tools.

Logging System

Enables you to specify the project and object events to be logged. In the event that logging fails, you can also disable development or allow development but disable transfers.

Object Action Notification

Enables you to enable and disable Object Action Notification, which sends a notification message when an action such as checkin or checkout is performed on an object.

Notification Setup

Enables developers to be notified, using subscription, when actions are performed on an object.

Activity Rules

Enables you to add and modify project statuses and object transfer activity rules.

User Roles

Enables you to maintain user roles.

Allowed Actions

Enables you to assign to a user role the actions allowed for each object type during a specific project status.

Save Locations

Enables you to add, modify, and delete the locations where you save objects.

10.1.2 The Configuration Process Flow

This list provides a recommended process flow for using all of the JD Edwards EnterpriseOne OMW configuration tools. The list contains each configuration function in the process flow, along with the topic in which you can find more information about each function.

Note:
These items in the process flow require advance preparation: assigning user roles, applying allowed actions to users, and setting up project status rules and object transfer rules.
Before configuring these functions, make sure you understand user roles, allowed actions, project status rules, and object transfer rules.

This table shows the recommended process flow for JD Edwards EnterpriseOne OMW configuration as follows:

Configuration Function

Procedure Location

Assigning User Roles

See Configuring User Roles and Allowed Actions.

Applying Allowed Actions to Users

See Configuring User Roles and Allowed Actions.

Disabling SAR Integration with JD Edwards EnterpriseOne OMW

See Configuring JD Edwards EnterpriseOne OMW Functions.

Setting Up Project Constants

See Configuring JD Edwards EnterpriseOne OMW Functions.

Setting Up Project Status and Object Transfer Rules

See Configuring Activity Rules.

Adding, Modifying, and Deleting Object Save Locations

See Configuring Object Save Locations.

Controlling Development in the Event of Logging Failure

See Configuring JD Edwards EnterpriseOne OMW Functions.

Controlling Logging Detail

See Configuring JD Edwards EnterpriseOne OMW Functions.

Enabling or Disabling Object Action Notification

See Creating Notification Subscriptions.

Adding, Modifying, and Deleting Notification Subscriptions

See Creating Notification Subscriptions.

Viewing Major and Detail Logs

See Working with Logs.

10.1.3 Activity Rules

These two types of activity rules exist:

- Project status activity rules

- Object transfer activity rules

Project status activity rules define the possible paths for an JD Edwards EnterpriseOne OMW project. For a given project status, these rules define the possible next project statuses to which the project can be advanced.

For each project status activity rule, one or more object transfer activity rules can exist. Each object transfer activity rule defines a FROM and TO location, where objects of this type are moved from and to for a specific software release.

For example, one object transfer activity rule can specify that all APPL objects be transferred from the DV810 location to the PY810 location during a specified project status change.

10.1.4 Allowed Actions

The Allowed Actions form enables you to assign allowed actions to user roles for each object type during a specific project status. You must create the user role before configuring any allowed user actions.

Using allowed actions, administrators can restrict the actions that users with a specific role can perform.

10.1.5 Project and Object Logging

JD Edwards EnterpriseOne OMW logging tracks information about projects and objects. A major log is created whenever:

- A project is created, copied, or deleted.

- The project status is changed.

- A new or existing object is added to or removed from a project.

- An object is created, copied, or deleted.

- An object is checked in, checked out, saved, restored, transferred, or retrieved.

For every significant step or event within these actions, the system creates a detail log and attaches it to the major log record.

10.1.6 Project Constants

The Object Management Constants form enables an administrator to set these general constants pertaining to JD Edwards EnterpriseOne OMW projects:

Type of Constant

Description

Project Status for Users' Personal Default Projects

The default status assigned to a default project within the JD Edwards EnterpriseOne OMW. This project constant can be any one of the standard project status codes.

Project Status for All New Projects

The status assigned to a project when it is first created. This project constant can be any one of the standard project status codes or you can create a status and code for this purpose.

User Role to be Assigned to the Project's Originator

When a project is created, the originator is added as a user on the project. This project constant defines the user role assigned to the originator.

10.1.7 Object Save Locations

The Object Save Locations form indicates the save location for Object Librarian (OL) objects. Defining the save location will enable users to transfer objects that are saved into the path code specified. Currently, only the save locations for Object Librarian objects may be defined.

10.1.8 Object Action Notifications

The Object Action Notifications form enables you to activate or deactivate object action notification. The Object Action Notification System sends you an email each time an event, such as check in or checkout, occurs to one of your objects. Object action notification is enabled by default.

10.1.9 Notification Subscriptions

The notification system sends email messages to users about changes to objects, such as object check in and checkout, in the system. The Notification Subscriptions form enables you to add, delete, and modify notification subscriptions, as well as to sort notification subscription records by criteria that you select.

10.1.10 Application and User Role Security

You should secure these applications using application security:

- P98230 - JD Edwards EnterpriseOne OMW Configuration System

- R98210B - Object Management Log Purge

- P98231 - JD Edwards EnterpriseOne OMW Transfer Activity Rules Director

10.1.10.1 User Role Security

You can prevent users from adding a user to a project by using row-level security for the F98221.puJD Edwards EnterpriseOne OMWur field. This field contains the user defined code of the user role for each user in a specific project.

However, all users must be able to add these user roles when setting up a new project:

- Originator

- Supervisor

- Manager

- Developer

- QA

- Product Support

If these roles are not assigned when a user attempts to perform certain actions on a project, then the actions will fail. The administrator role should be secured from all but a few users. Although you can secure the manager and supervisor roles, you should not. Instead, you should create a role, such as product manager, that can be secured. This new user role can be granted security attributes, such as being allowed to switch a token from one project to another.

10.1.10.2 Administrative Update Security

You should secure all actions, including project status change, for project statuses 40 (Production Development), 41 (Transfer Production to Prototype), and 42 (Transfer Prototype to Development). These statuses enable administrators to apply fixes to objects in the Production path code and then to promote the objects back to development. The ability to do so should be limited to administrators only.

10.2 Selecting a Configuration Option

All configuration options are set up through the JD Edwards EnterpriseOne OMW Configuration System application (P98230). You select the option that you want to configure by clicking the button that corresponds to the desired option.

Select Cross Application Development Tools (GH902) then Object Management Configuration (P98230).

Access the JD Edwards EnterpriseOne OMW Configuration System application.

1. If necessary, click the General Tab to display function options.

2. Click one of these buttons to configure the corresponding function:

- Constants

- SAR System Integration

- Logging System

- Object Action Notification

- Notification Setup

- Activity Rules

- User Roles

- Allowed Actions

- Save Locations

10.2.1 Configuration Settings Indicators

Some of the function buttons on the Object Management Setup Form have setting indicators next to them. Settings indicators describe the current setting for the SAR System Integration, Logging System, and Object Action Notification options. The purpose of each setting indicator is as follows:

Indicator

Description

SAR System Integration Indicator

Indicates whether the SAR (Software Action Request) system is integrated with the JD Edwards EnterpriseOne OMW. SAR integration is enabled or disabled.

Logging System Indicator

Indicates whether full or reduced logging of project or object events is selected.

Object Action Notification Indicator

Indicates whether the object notification system is enabled or disabled.

See Also:

- "Working with the Cross Reference Facility Application" in the JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

10.3 Adding a New File Extension and New Package Prefix

The H95 CA UDC determines the file type a user can check into OMW while creating business services, and the package prefixes they can select.

To add a new file extension

1. In EnterpriseOne, type UDC in the Fast Path.

2. On Work With User Defined Codes, type H95 in the Product Code field.

3. Type CA in the User Defined Codes field.

4. Click Add.

5. In the new row that displays in the grid, complete the following fields:

- Codes: Enter the new file extension that you want users to be able to check in.

- Description 1

6. Type a description of the type of extension you are adding.
The Special Handling and Hard Coded fields are optional.

7. Click OK.

To add a new package prefix

1. In EnterpriseOne, drill down to the Object Configuration Management menu.

2. From the Form exit, click BSSV Package Prefix.

3. In the blank line at the bottom of the Package Prefix grid, type the new package prefix you want to add.

4. Click OK.

11 Configuring User Roles and Allowed Actions

This chapter contains the following topics:

- Section 11.1, "Understanding User Roles and Allowed Actions"

- Section 11.2, "Setting Up User Roles"

- Section 11.3, "Setting Up Allowed User Actions"

11.1 Understanding User Roles and Allowed Actions

Configuring user roles and allowed actions is one of the most important JD Edwards EnterpriseOne OMW configuration tasks. JD Edwards EnterpriseOne OMW's automation relies on an administrator who carefully configures these areas.

These sections show the allowed user actions that JD Edwards recommends for each user role and the responsibility of the person in that user role, organized by the project status at which these actions should be authorized.

For status changes that initiate a transfer, the user role must be authorized to perform both the status change and transfer actions.

Note:
You might want to allow the Manager and Supervisor roles to perform the same actions as the Developer role, in case the Developer cannot perform assigned duties or needs to have work verified.

11.1.1 New Project Pending Review (11)

This table shows user roles and allowed actions for projects with a status of 11 (new projects pending review):

User Role

Recommended Allowed Action

Explanation

Originator

Status Change

Originator might need to advance the status to 91 - canceled. Entered in Error

Manager, Supervisor

Update Project

Change values for the project

Manager, Supervisor

Update Users

Change values for the user

Manager, Supervisor

Status Change

Advance project to the next status

11.1.2 Programming (21)

This table shows user roles and allowed actions for projects with a status of 21 (programming):

User Role

Recommended Allowed Action

Explanation

Developer

Add Objects

Add objects to project in order to fix or enhance

Developer

Remove Objects

Remove objects that were incorrectly added

Developer

Check Out

Check out objects from the server

Developer

Check In

Check in objects to the server

Developer

Get

Get objects from the server

Developer

Status Change

Advance project to the next status

Developer

Transfer

Transfer objects on status change

11.1.3 Rework-Same Issue (25)

This table shows user roles and allowed actions for projects with a status of 25 (rework-same issue):

User Role

Recommended Allowed Action

Explanation

Developer

Status Change

Change project to 21 - Programming status

11.1.4 QA Test/Review (26)

This table shows user roles and allowed actions for projects with a status of 26 (QA test/review):

User Role

Recommended Allowed Action

Explanation

Quality Analyst

Get

Get objects from the server

Quality Analyst

Status Change

Advance project to next status

11.1.5 QA Test/Review Complete (28)

This table shows user roles and allowed actions for projects with a status of 28 (QA test/review complete):

User Role

Recommended Allowed Action

Explanation

Manager, Supervisor

Update Project

Change values for the project

Manager, Supervisor

Status Change

Advance project to the next status

Manager, Supervisor

Transfer

Transfer objects on status change

11.1.6 In Production (38)

This table shows user roles and allowed actions for projects with a status of 38 (in production):

User Role

Recommended Allowed Action

Explanation

Manager, Supervisor

Status Change

Advance project to the next status

11.1.7 Complete (01)

This table shows user roles and allowed actions for projects with a status of 01 (complete):

User Role

Recommended Allowed Action

Explanation

Developer

Remove Objects

Remove objects from projects at status 91 that might have been added but not removed

11.1.8 Default Allowed Actions that Cannot Be Changed

These default allowed actions cannot be changed. This information is provided for reference only:

Value

Description

01

Transfer

02

Check In

03

Check Out

04

Delete

05

Add

06

Copy

08

Save

09

Restore

10

Design

11

Get

12

Remove Object from Project

13

Update a Project

16

Add Object to a Project

21

Switch Token

23

Force Release from Token Queue

30

Erase Check Out

11.1.9 Default Object Types

These default object types are provided for reference only:

Value

Description

01

Object Librarian objects

02

Data items

03

Versions

04

UDCs

05

Menus

06

Documentation record (SAR object)

11

Transfer record (SAR object)

12

History record (SAR object)

11.2 Setting Up User Roles

This section discusses how to:

- Modify user roles.

- Delete user roles.

11.2.1 Forms Used to Set up User Roles

Form Name

FormID

Navigation

Usage

Object Management Setup

W98230R

Object Management Administration menu (GH9081) then Object Management Configuration (P98230)

Access forms to configure notification subscriptions.

User Roles

W0004AH

In Object Management Setup, click the User Roles button.

Used to add, modify, and delete user roles.

11.2.2 Modifying User Roles

Access the Object Management Setup form.

1. In Object Management Setup, click User Roles.

2. Select the user role you want to modify.

3. Double-click the first field that you want to change, and modify it.

4. Repeat step 3 to make all required modifications.

5. Click Find and verify that the modifications you made appear in the list.

6. Click OK.

11.2.3 Deleting User Roles

Select Object Management Administration (GH9081) then Object Management Configuration (P98230)

Access the Object Management Setup form.

1. In Object Management Setup, click the User Roles button.

2. Click the cell to the left of the User Role that you want to delete.

3. Click Delete.

4. In the Confirm Delete query, click OK.

5. Repeat steps 2 through 4 to delete all desired user roles.

6. Click Find to verify that the user roles were deleted.

7. Click OK.

11.3 Setting Up Allowed User Actions

This section provides an overview of user defined codes for allowed user actions and discusses how to set up allowed user actions.

11.3.1 Understanding User Defined Codes for Allowed User Actions

The Allowed Actions Form lets you assign allowed actions to user roles for each object type during a specific project status. These user defined codes (UDCs) define allowed JD Edwards EnterpriseOne OMW actions involving objects:

- 01 — Transfer

- 02 — Check in

- 03 — Check out

- 04 — Delete

- 05 — Add

- 06 — Copy

- 07 — Install

- 08 — Save

- 09 — Restore

- 10 — Design

- 11 — Get

- 12 — Remove object from project

- 13 — Update the project

- 16 — Add an object to the project

- 21 — Switch tokens

- 23 — Release from token queue

- 30 — Erase check out

- 38 — Status change

For example, if you want the developer to be allowed to check in all object types when the project is at project status 21, you would enter these values in the Allowed Actions Form:

Field

Value

User Role

02 - Developer

Object Type

*ALL

System Code

System

Allowed Action

02 - Check in

Project Status

20 - Programming

Note:
Before setting up allowed actions, you must add the user role to the User Roles UDC by using the User Defined Code form.

11.3.2 Form Used to Set Up User Actions

Form Name

FormID

Navigation

Usage

Object Management Setup

W98230R

Object Management Administration menu (GH9081) then Object Management Configuration (P98230)

Access forms to configure notification subscriptions.

Allowed Actions

W98230G

In Object Management Setup, click the Allowed Actions button.

Used to set up user allowed actions.

11.3.3 Setting Up Allowed User Actions

Access the Object Management Setup form.

1. In Object Management Setup, click the Allowed Actions button.

2. Click Find to display previously defined user actions.

3. To create a blank row in which to add a definition, sort on the allowed user action to be worked on.

4. Complete one or more of the query by example (QBE) columns and click Find.

5. Scroll to a blank row at the bottom of the sorted list.

6. Complete these fields in the blank row:

- JD Edwards EnterpriseOne OMW User Role

- Object Type

- Project Status

- System Code

- System Code Reporting

- Action

Note:
You can enter *ALL in any field except User Role. Typing *ALL in a field indicates that the user role chosen can work with all object types, project statuses, or actions.

After you complete a row, a new blank row appears.

7. Repeat this procedure until all allowed user actions are set up.

8. Click OK.

12 Configuring JD Edwards EnterpriseOne OMW Functions

This chapter contains the following topics:

- Section 12.1, "Understanding JD Edwards EnterpriseOne OMW Functions"

- Section 12.2, "Disabling SAR Integration"

- Section 12.3, "Setting Up Project Constants"

12.1 Understanding JD Edwards EnterpriseOne OMW Functions

To configure JD Edwards EnterpriseOne OMW functions, you can disable the Software Action Request (SAR) system. This action is necessary if your company does not use SARs. You can also control logging detail and disable or limit development when logging fails. Finally, you can set up project constants to track the course of project development.

12.2 Disabling SAR Integration

This chapter provides an overview of SAR integration and discusses how to:

- Disable SAR system integration.

- Control logging detail.

- Control development in the event of a logging failure.

12.2.1 Understanding SAR Integration

Most companies do not have the SAR (Software Action Request) system. You can verify that SAR integration is disabled by checking the settings indicator to the right of the SAR System Integration button on the Object Management Setup Form.

If you do not have the SAR system installed and the SAR System Integration settings indicator shows that SAR integration is enabled, you must disable SAR integration.

12.2.2 Forms Used with SAR Integration

Form Name

FormID

Navigation

Usage

Object Management Setup

W98230R

Object Management Administration menu (GH9081) then Object Management Configuration (P98230)

Access forms to configure notification subscriptions.

SAR Systems Integration

W98230A

In Object Management Setup, click the SAR System Integration button.

Disabling SAR System Integration

Object Management Logging System

W98230B

In Object Management Setup, click the Logging System button.

Used to specify which project and object events you wish to have logged.

12.2.3 Disabling SAR System Integration

Access the Object Management Setup form.

1. In Object Management Setup, click the SAR System Integration button.

2. Make sure the Integrate SAR System option is blank.

3. Verify that all other fields are deselected.

4. Click OK.

12.2.4 Controlling Logging Detail

The Object Management Logging System form enable you to specify which project and object events you wish to have logged.

Access the Object Management Setup form.

1. In Object Management Setup, click the Logging System button.

2. Select the Reduce Logging Detail check box.

3. Double-click the Log Actions and Detail Log Items folders.

4. Double-click items for which you do not want to log details.
A red X appears next to the deselected items.

5. Repeat step 3 to deselect all unwanted log detail items.

6. Click OK.

12.2.5 Controlling Development in the Event of a Logging Failure

The Object Management Logging System form also enables you to disable development or to allow development but disable transfers if logging fails.

Access the Object Management Setup form.

1. In Object Management Setup, click the Logging System button.

2. To disable development if logging fails, select the "Do not allow any development"option.

3. To permit development but disable object transfers in the event of a logging failure, select the Allow development but do not allow any transfers option.

Note:
The "Allow development but do not allow any transfers" option is the default value.

4. Click OK.

12.3 Setting Up Project Constants

The Object Management Constants form enables you to set general constants pertaining to JD Edwards EnterpriseOne OMW Projects. These project constants are:

- Project status for users' personal default projects

- Project status for all new projects

- User role to be assigned to the project originator

- External role for users outside of JD Edwards EnterpriseOne OMW

12.3.1 Form Used to Setup Project Constants

Form Name

FormID

Navigation

Usage

Object Management Setup

W98230R

Object Management Administration menu (GH9081) then Object Management Configuration (P98230)

Access forms to configure notification subscriptions.

Object Management Constants

W98230Q

In Object Management Setup, click the Constants button.

Used to set up project constants

12.3.2 Setting Up Project Constants

Access the Object Management Setup form.

1. In Object Management Setup, click the Constants button.

2. To enter a project status for a user's personal default project, click the visual assist for this field: Enter the Project Status for user's personal default project.

3. Double-click a project status.

4. To enter the initial project status for all new projects, click the visual assist of this field: Enter the initial Project Status for all new projects.

5. Double-click a project status.

6. To enter the User Role to use when assigning the originator to a project, click the Visual Assist for this field: Enter the User Role to use when assigning the originator to a project.

7. Double-click a project status.
When a user accesses objects that are outside of JD Edwards EnterpriseOne OMW, the user will be added to the project in the external role. Therefore, this role defines what actions users outside of JD Edwards EnterpriseOne OMW are able to perform on objects.

Note:
You can click the Attachments buttons next to the three fields to view their respective attachments.

13 Configuring Activity Rules

This chapter contains the following topics:

- Section 13.1, "Understanding Activity Rules"

- Section 13.2, "Understanding the Project Promotion Lifecycle"

- Section 13.3, "Setting Up Project Status Activity Rules"

- Section 13.4, "Setting Up Object Transfer Activity Rules"

13.1 Understanding Activity Rules

The Activity Rules button on the Object Management Setup form enables you to set up both project status activity rules and object transfer activity rules. Project status activity rules define the activities that occur during a project development cycle. Object transfer activity rules work in conjunction with project status activity rules to define the From and To locations for moved objects.

13.2 Understanding the Project Promotion Lifecycle

The normal project promotion life cycle is as follows:

11 > 21 > 26 > 28 > 38 > 01

Where

11 = New project pending review

21 = Programming

26 = QA test/review

28 = QA test/review complete

38 = In production

01 = Complete

During a normal project promotion cycle, developers check objects out of and in to the Development path code; promote them to the prototype path code; and then promote them to the Production path code before declaring them complete.

Administrators can follow a different promotion cycle, as follows:

11 > 40 > 41 > 42 > 01

Where

11 = New project pending review

40 = Production development

41 = Transfer from Production to Prototype

42 = Transfer from Prototype to Development

01 = Complete

During this promotion cycle, administrators check objects out of and in to the Production path code to apply fixes, and then demote the objects to the Prototype path code and the Development path code. Developers should not use this promotion cycle. JD Edwards recommends that you apply status activity rules that limit this promotion cycle to a specific group: those with the User ID for administrators.

13.3 Setting Up Project Status Activity Rules

This section provides an overview of project statuses and discusses how to set up project status activity rules.

13.3.1 Understanding Project Statuses

You can set up statuses for a project as development progresses from one phase to the next. For example, the project might move from a programming phase to a manager review phase. For each of these transitions you will define the these parameters:

- Whether this project status rule is active

- The System Role to which this project status transition applies

- The related "To" project status

- The related "From" and "To" SAR* statuses
Complete the From and To SAR status only if you have SAR integration turned on.

13.3.2 Form Used to Set up Project Status Activity Rules

Form Name

FormID

Navigation

Usage

Object Management Setup

W98230R

Object Management Administration menu (GH9081) then Object Management Configuration (P98230)

Access forms to configure notification subscriptions.

Project Status Activity Rules

W98230E

In Object Management Setup, click the Activity Rules button.

Used to set up Project Status Activity Rules

13.3.3 Setting Up Project Status Activity Rules

Access the Object Management Setup form.

1. In Object Management Setup, click the Activity Rules button.

2. Click Find.
All available From project statuses appear.

3. Click the From Project Status for which you want to set up one or more To project statuses.

4. Click Select.
Project Status Activity Rules lists all valid To project statuses for the From project status you chose.

The current project status appears in the From Project Status field.

5. Scroll to the blank row at the bottom of the list and complete these fields:

- Active
This field can be used to allow only specific users or only users who are members of a specified group to perform a status change. To make the rule available to everyone, enter *PUBLIC in this field.

- User/Role
You can perform all project status activity rules that apply to your user ID, group, and the *Public role.

- To Project Status

- From SAR Status
Complete for projects with SARs and only if you have SAR integration turned on. If SAR integration is disabled, these columns are disabled.

- To SAR Status
Complete for projects with SARs and only if you have SAR integration turned on. If SAR integration is disabled, this column is disabled.

A blank row appears below the row you completed.

6. Repeat step 5 to set up or modify other To project status entries for this particular From Project Status.

7. Click OK when you are done.

8. Select the next From Project Status and repeat steps 5 through 7 to set up project activity rules for each remaining From Project Status.

9. When all project activity rules are complete, click OK to return to the Work with Object Management Activity Rules form.

10. Click Close.

13.4 Setting Up Object Transfer Activity Rules

This section provides an overview of object transfer activity rules and discusses how to set up object transfer activity rules.

13.4.1 Understanding Object Transfer Activity Rules

You must configure object transfer activity rules for each object type used in a project that you want to perform an action on.

For each object type you want to perform an action on, you must define this information:

- Project statuses at which users can check in, check out, and get objects ("getting" an object means copying its specifications to your work area without checking it out)

- At which status change you would like objects to be transferred

- Project statuses at which object tokens are released

These object location tasks must be performed when setting up object transfer activity rules:

- Define FROM and TO transfer locations for each object type at each project status transition-for example, when project status 21 (development) changes to project status 26 (prototype). In this example, objects are transferred from DV810 to PY810.

- Define checkout and get locations for Object Librarian object types.

- Define checkin locations for Object Librarian objects.

Note:
Transfer activity rules can occur in any order. For example, you might have one status change that will require more than one object transfer. If you expect an object to transfer from DV810 to PY810 and then to PD810, you will want to set up rules to transfer the object from DV810 to PY810 and from DV810 to PD810 because the object could be retrieved in any order.

13.4.2 Form Used to Set up Object Transfer Activity Rules

Form Name

FormID

Navigation

Usage

Object Management Setup

W98230R

Object Management Administration menu (GH9081) then Object Management Configuration (P98230)

Access forms to configure notification subscriptions.

Object Transfer Activity Rules

W98230F

In Object Management Setup, click the Activity Rules button.

Used to setup Object transfer Activity Rules.

13.4.3 Setting Up Object Transfer Activity Rules

Access the Object Management Setup form.

1. In Object Management Setup, click the Activity Rules button.

2. Click Find to display all available project statuses.

3. Double-click the From Project Status folder for which you want to set up object transfer activity rules.

4. Click one of the related To project statuses.
This field defines the To Project Status, which completes the From and To Project Status transition for which you want to configure object transfer activity rules. For each From and To Project Status transition, you can create multiple object transfer activity rules for different object types.

5. Click Select.

6. Scroll to the blank row at the bottom of the list. Complete these fields for the object type desired:

- Active

- User/Role
This field can be used to allow the activity rule to apply only specific users or only users who are members of a specified group. To make the rule available to everyone, enter *PUBLIC in this field.

Users will only perform the object transfer activity rules that apply to them based on a *Public, user role, and user ID hierarchy. If a rule exists for a role to which they belong, the *Public role will not be performed. If a role exists for their user ID, neither the *Public, not the user role rule be executed.

- Object Type

Note:
*ALL may not be used when defining transfer activity rules.

- From Location

- To Location

Note:
Object Librarian objects use path codes for the From Location and To Location values, whereas non-Object Librarian objects use data source values. For Versions, if a path code is entered, the F983051 record and the specs for the version are transferred (for batch versions), and if a data source is entered, just the F983051 record is transferred between the defined locations. Usually, you will want to use Path Codes for Version.

- Object Release
This field contains the release level of JD Edwards EnterpriseOne that you are currently working on. The From Release value should be the same as the To Release value.

- To Release
Currently not used. This field is populated with the From Release value.

- Release Token

- Allowed Action
A blank row appears when you have finished. When you set up transfer activity rules for Workflow objects, an additional form appears. Use the form to provide From and To Data Source values for the Task Specifications table (F98811) records.

- Mandatory Flag
The mandatory flag works in conjunction with the enable/disable flag. It is used to indicate that an object status activity rule must be performed in order for the project to successfully advance. If a role is marked as mandatory and it is inactive, then the rule must be performed and a project with an object type that would use the rule may not advance until the rule is activated. Otherwise, a rule that is inactive and not mandatory will be ignored.

7. Repeat this procedure to set up or modify other object types for this project status transition.

8. Click OK to return to the Object Management Activity Rules form.

9. Select the next From and To project status transition, and repeat this procedure to set up its object transfer activity rules.

10. Repeat step 9 until all object transfer activity rules are complete.

11. Click OK to return to the Object Management Activity Rules form.

12. Click Close.

Note:
When you set up transfer activity rules for APPL objects, you must also define rules for User Override Object types so that JD Edwards EnterpriseOne OMW can transfer any *PUBLIC user overrides for the APPL objects. If you do not do so, APPL objects will not transfer successfully.

14 Configuring Object Save Locations

This chapter contains the following topics:

- Section 14.1, "Creating a Save Location"

Using JD Edwards EnterpriseOne OMW, you can create a save location, which is a path code developers use to save their objects. With the save location created, you add the path code to the system, allowing saved objects to be transferred, and you can modify or delete save locations.

14.1 Creating a Save Location

This section provides an overview of path codes and discusses how to:

- Add an object save location.

- Modify an object save location.

- Delete an object save location.

14.1.1 Understanding Path Codes

During the installation process, an additional path code might not have been created to use as your JD Edwards EnterpriseOne OMW save location. To use this feature, you must create a path code where developers can save their objects while they are in development. When users perform a Save, their objects are checked into the path code defined as the save location; when they perform a Restore, objects are retrieved from this location.

14.1.2 Form Used to Object Save Locations

Form Name

FormID

Navigation

Usage

Object Management Setup

W98230R

Object Management Administration menu (GH9081) then Object Management Configuration (P98230)

Access forms to configure notification subscriptions.

Object Save Locations

W98230K

In Object Management Setup, click the Save Locations button.

Used to add, modify, or delete Object Save Locations

14.1.3 Adding an Object Save Location

The Object Save Locations form indicates the save-off location for Object Librarian (OL) objects. Defining the save location will transfer objects that are saved into the path code specified. Currently, only the save locations for Object Librarian objects may be defined.

Access the Object Management Setup form.

1. In Object Management Setup, click the Save Locations button.
The Location column contains the names of path code associated with the environment into which the user is logging into. Users logging into environments that use different path codes may be saved to different path codes.

2. To add a new save location, click a blank field in the Location column.

3. Click the Visual Assist button.

4. Locate and double-click the current location of the object.
The Object Save Locations form reappears with your object's current location in the Location column.

5. In the same row, scroll to and double-click the Save Location field located to the right of the Location field clicked previously.

6. Click the Visual Assist button.

7. Scroll to and double-click the new save location of the object.
The Object Path Save Locations form reappears with your object's new save location in the Save Location column.

8. Click OK.

14.1.4 Modifying an Object Save Location

Access the Object Management Setup form.

1. In Object Management Setup, click the Save Locations button.

2. Click the Save Location field.

3. Click the Visual Assist button.

4. Scroll and double-click the new save location for the object.
The Object Save Locations form reappears with the modified object save location in the Save Location column.

5. Click OK.

14.1.5 Deleting an Object Save Location

Access the Object Management Setup form.

1. In Object Management Setup, click the Save Locations button.

2. In Object Save Locations, select the record to be deleted.

3. Click Delete.

4. Click OK in the Confirm Delete box.

5. Click OK.

15 Creating Notification Subscriptions

This chapter contains the following topics:

- Section 15.1, "Understanding Object Action Notifications"

- Section 15.2, "Configuring Notification Subscriptions"

15.1 Understanding Object Action Notifications

Notification subscriptions allow you to alert users using email about changes to objects in the system, such as object checkins and checkouts. After you enable object notification, you can add, modify, delete, or sort notification subscriptions. The Object Action Notification System is initially enabled by default.

You can set up notification subscriptions two ways. The first is by entering information into the Notification Subscription form (P98230), the second is by using the Notification Subscription Assistant. The Notification Subscription Assistant enables you to setup notifications by entering information into predefined fields, rather than filling in the notification subscription form. See the Understanding Object Action Notifications section for information about using the Notification Subscription form.

15.2 Configuring Notification Subscriptions

This section discusses how to enable or disable notification subscriptions.

15.2.1 Forms Used to Configure Notification Subscriptions

Form Name

FormID

Navigation

Usage

Object Management Setup

W98230R

Object Management Administration menu (GH9081) then Object Management Configuration (P98230)

Access forms to configure notification subscriptions.

Object Action Notification

W98230D

In Object Management Setup, click the Object Action Notification button.

Enable or disable action notifications.

Notification Subscriptions

W98230L

In Object Management Setup, click the Notification Setup button

Add, delete, modify, and sort notification subscriptions.

15.2.2 Enabling or Disabling Object Action Notifications

Access the Object Action Notification form.

1. In Object Action Notification, to enable object action notification, select the Activate Object Action Notification option
If enabled, the notification system sends email messages to users regarding actions taken on JD Edwards EnterpriseOne objects by JD Edwards EnterpriseOne OMW. Use the JD Edwards EnterpriseOne OMW Notification Subscriptions form in the Configuration Application (P98230) to configure the notification system.

2. To disable object action notification, clear the Activate Object Action Notification option.

3. Click OK.

Note:
Notification that users are added to or removed from projects always occurs, even when object action notification is disabled. In this situation, an email message is sent to the user.

15.2.3 Adding a Notification Subscription

Notification Subscriptions can be created for an action performed on these objects:

- All objects of the specified system code.

- All objects of a specified type.

- All objects of a combination of 1 and 2.

- A specific object name and type.

Note:
Until you are familiar with how each field is utilized, Oracle recommends that you use the Notification Subscription Assistant to add a notification subscription. SeeCreating Notification Subscriptions using the Notification Subscription Assistant.

Access the Notification Subscriptions form.

1. In Notification Subscriptions, click Find to display the current notification subscriptions.

2. Scroll to a blank row and complete these mandatory fields:

- JD Edwards EnterpriseOne OMW User Role

- Action

3. Complete these optional fields:

- Object Type

- Object Name

- Reporting System Code

- Path Code
A new row appears when you are finished.

4. Repeat steps 2 and 3 until all notification subscriptions are added.

5. Click OK.
For definitions of each field, see Understanding Notification Subscription Fields, or place your cursor in the field and press F1.

15.2.4 Modifying Notification Subscriptions

Access the Object Management Setup form.

1. In Object Management Setup, click the Notification Setup button.

2. In Notification Subscriptions, click Find to display the current notification subscriptions.

3. Select the fields to be modified and make the changes.

4. Click OK.

15.2.5 Deleting a Notification Subscription

Access the Object Management Setup form.

1. In Object Management Setup, click the Notification Setup button.

2. In Notification Subscriptions, select the record to be deleted.

3. Click the Delete button.

4. Click OK in the Confirm Delete query.

5. Click OK.

15.2.6 Sorting Notification Subscriptions

Access the Object Management Setup form.

1. In Object Management Setup, click the Notification Setup button.

2. In Notification Subscriptions, above the rule headers, click the Query by Example column to be filtered.
If a search button appears, click it and double-click the filter criteria. In other Query by Example columns, enter the filter criteria.

3. Click Find.
The filtered notification subscriptions appear.

4. Click OK.

15.2.7 Creating Notification Subscriptions using the Notification Subscription Assistant

When setting up notification subscriptions using the Notification Subscription Assistant, you first identify what action performed on an object that will trigger the notification, and second identify the person or role to which the notification will be sent. You select to send notification subscriptions to an individual user or role, to users playing a specified role on the project on which the action is being performed on the object, or to users playing a specified role on a different project. You can also select to send notification subscriptions to only the person flagged as the lead within the role.

15.2.7.1 Accessing the Notification Subscription Assistant

Access the Notification Subscription Assistant.

1. Type P98230 in the Fast Path.

2. Click Notification Setup.

3. Click Add.

15.2.7.2 Understanding Actions

Some of the actions you assign require or enable you to enter different types of information. For example, if the action you select is Delete, you can enter a path code that identifies from where the object is being deleted. Not all actions require the same information. This section identifies the fields that need to be completed according to the action you enter into the Object Management Action field.

Action

Fields

01 Transfer

Path Code
Object Name

Object Type

System Code

02 Checkin

Path Code
Object Name

Object Type

System Code

03 Checkout

Path Code
Object Name

Object Type

System Code

04 Delete

Path Code
Object Name

Object Type

System Code

05 Add

Object Type
System Code

06 Copy

Object Name
Object Type

System Code

08 Save

Path Code
Object Name

Object Type

System Code

09 Restore

Path Code
Object Name

Object Type

System Code

10 Design

Object Name
Object Type

System Code

11 Get

Object Name
Object Type

System Code

12 Remove Object from Project

Object Name
Object Type

System Code

13 Update a Project

Object Name
Object Type

System Code

16 Add Object to Project

Object Name
Object Type

System Code

21 Switch Token

Object Name
Object Type

System Code

23 Force Release From Token Queue

Object Name
Object Type

System Code

30 Erase Checkout

Object Name
Object Type

System Code

38 Status Change

When project advances from status
To Status

Project Name

Object Type

System Code

Notify if the action is performed on any sub-project with this project.

15.2.7.3 Understanding Notification Subscription Fields

After you have entered an action in the Object Management Action field and pressed Tab, you enter information about the object being acted upon in the fields that display in the Notification Subscription Action field. This table is a list of the fields and a description of what you must enter:

Path Code

The path code is a pointer to a set of JD Edwards EnterpriseOne Objects, and is used to keep track of set of objects and their locations in JD Edwards EnterpriseOne.

Object Name

A 200-character field that serves as an identifier for a JD Edwards EnterpriseOne object. When used in conjunction with an JD Edwards EnterpriseOne OMW Object Type (JD Edwards EnterpriseOne OMWOT), it uniquely identifies any JD Edwards EnterpriseOne object.

Object Type

In JD Edwards EnterpriseOne, an object has traditionally been a reusable entity based on software specification created by the JD Edwards EnterpriseOne tools. These objects included Object Librarian Objects, such as interactive application (APPL), as well as batch applications (UBE), and data structure (DSTR) objects. In JD Edwards EnterpriseOne OMW, we have expanded this definition to include other Non Object Librarian type objects or data source based rather than path code based objects. These include User Defined Controls (UDC), Workflow, Menus, and Data Items. OL Objects:

Batch Applications

Business Functions

Business Views

Data Structures

Event Rules

Interactive Applications

Media Objects

Tables

Data Dictionary items

UDC items

Workflow items

Menus

System Code

A user defined code that specifies the system number for reporting and jargon purposes.

Project Name

A 200-character field that serves as an identifier for a JD Edwards EnterpriseOne project. When used in conjunction with an JD Edwards EnterpriseOne OMW Object Type (JD Edwards EnterpriseOne OMWOT), it uniquely identifies any JD Edwards EnterpriseOne object.

When the project advance from status

A code that indicates the status from which an object will be advanced. Recognized status codes:

01 Complete

11 Pending Review

17 Plan or Research

18 Design

19 Design Review

21 Programming

22 Programming Test

23 Manager Review

24 Transfer to Production

25 Rework

26 QA test

28 QA Test Complete

To status

A status to which you advance a project from a start status. Recognized status codes:

01 Complete

11 Pending Review

17 Plan or Research

18 Design

19 Design Review

21 Programming

22 Programming Test

23 Manager Review

24 Transfer to Production

25 Rework

26 QA test

28 QA Test Complete

Notify if the status change is performed on any sub-projects within this project

An option that, if selected, sends a notification when the status change you entered in the fields is made to a sub-project of the project you entered in the Project Name field.

15.2.7.4 Understanding Recipients

After you have entered an action, entered the appropriate information into the allowed fields, and click OK, you select to whom you want the notification sent when the action is performed on the object. You select to whom you send the notification by choosing these options and entering information into the associated fields:

Option

Field

Task

To this specified user ID or role

User Role

Enter a specific user ID or role. When the action is performed on the object, this specific user or all users assigned to a role will receive a notification.

To all users playing a role on the project being acted upon

JD Edwards EnterpriseOne OMW user role

Enter a user role. When the action is performed on the object, any user that is assigned this role on the project will receive a notification. You can select the "Only users playing this role that are flagged as leads" so that only those individuals with lead status within the role receive the notification.

To all users playing a role on a project other than the project being acted upon

Project Name JD Edwards EnterpriseOne OMW User Role

Enter a project name and user role. When the action is performed on the indicated object, any user that is assigned this role on the indicated project will receive a notification. You can select the "Only users playing this role that are flagged as leads" so that only those individuals with lead status within the role receive the notification.

16 Working with Logs

This chapter contains the following topics:

- Section 16.1, "Understanding Object Management Logging"

- Section 16.2, "Using Logs"

16.1 Understanding Object Management Logging

JD Edwards EnterpriseOne OMW contains an object management logging application. Project and object logs provide an excellent way to review the development history of projects or objects. Furthermore, you can view log details for any log record currently appearing on your monitor. From the Work With Log Detail form, you can bring up the actual log entry in the View Full Log Text window.

This application also allows you to rearrange log fields to customize software development reporting. You can view all logs, view sorted logs, or show only the last logging action for an object or project. These two tasks must be performed together to produce customized project and object development reports:

- Reorder log record fields

- Print logs

16.2 Using Logs

This section discusses how to:

- View project or object logs.

- Locate object logs.

- Locate project logs.

- View detail logs.

- Reorder log record fields.

- Print logs.

- Print Event Rules

16.2.1 Forms Used with Object Management Logging

Form Name

FormID

Navigation

Usage

Work with Object Management Logs

W98210A

Select Application Development (GH902), Object Management (P98230), then Object Management Logging (P98210).

Used to work with object management logs.

Work with Project Logs

W98210B

In Object Management Logging, click the Work with Project Logs button.

Used to work with project logs.

Work with Object Logs

W98210C

In Object Management Logging, click the Work with Object Logs button.

Used to work with object logs.

View Full Log Text

W98210D

In Object Management Logging, click the View Full Log Text button.

Used to view full log text.

View Error Codes

W98210F

In Object Management Logging, click the View Error Codes button.

Used to view error codes.

16.2.2 Viewing Project or Object Logs

Access the Work with Object Management Log form.

1. In Work With Object Management Log, perform one of these actions:

- Click Find to view logs for all projects and their objects in JD Edwards EnterpriseOne OMW.

- Enter sorting criteria in the Query by Example cells to filter search results, and then click Find.

- Select the Show Only Last Action option to show only the last logging action for a given project or object.

2. Click Close.

16.2.3 Locating Object Logs

Access the Work with Object Management Log form.

1. In Work With Object Management Log, click Form and then click Object Logs.

2. In Work With Object Logs, you can do these tasks:

- Click Find to show all JD Edwards EnterpriseOne OMW object logs.

- Enter data in the Query by Example cells to narrow your search and click Find.

- Select the Show Only Last Action option to show only the last logging action.

- Click the Check for Attachments button to check for object attachments.

3. Click Close.

16.2.4 Locating Project Logs

Access the Work with Object Management Log form.

1. In Work With Object Management Log, click Form and then click Project Logs.

2. In Work With Project Logs, you can perform these functions:

- Click Find to show all JD Edwards EnterpriseOne OMW project logs.

- Enter data in the Query by Example cells to narrow your search, and then click Find.

- Select the Show Only Last Action option to show only the last logged action for the selected project.

- Click the Check for Attachments button to check for attachments.

3. Click Close.

16.2.5 Viewing Detail Logs

Access the Work with Object Management Log form.

1. Double-click any log record you want to research. Or, click the desired log record row to highlight it, and then click Select.

2. Click Find.
The detail log record for the selected log appears. All sequence details for the selected Log record appear in ascending numerical order.

3. To view the full text of the Description field, click it and then click Select.
The View Full Log Text window appears, showing the actual log entry.

4. Click the Previous and Next buttons to move between detail logs.

5. Click Close.

16.2.6 Reordering Log Record Fields

Access the Work with Object Management Log form.

1. In Work With Object Management Log, click Sequence.

2. Click the first column you want to sort in the Columns Available window.

3. Click the right-pointing arrow to move it to the Columns Sorted window on the right.

4. Repeat steps 3 and 4 as required until all the columns you want to view are in the correct sort order.
If you make an error, you can move columns back to the Columns Available window for resorting. Select the column to be resorted and the left-pointing arrow.

5. Click OK in the Select Grid Row Sort Retrofire to reorder the log columns.

16.2.7 Printing Logs

Access the Work with Object Management Log form.

1. In Work with Object Management Log, click File and then Print Screen.

2. Modify print settings as required.

3. Click OK in the Print form.

16.2.8 Printing Event Rules

Access the Search Event Rule Objects form.

1. Select one of the following options:

- Show Application Objects

- Show Report Objects

- Show NER Business Function Objects

2. Click Find.

3. Select an object in the grid.

4. Click Print ER.
The event rules associated with the object you select display in a printable format in a text editor.

17 Working with JD Edwards EnterpriseOne OMW and SCM Integration

This chapter contains the following topics:

- Section 17.1, "Configuring JD Edwards EnterpriseOne OMW and SCM Integration"

- Section 17.2, "Understanding the SCM Tool"

17.1 Configuring JD Edwards EnterpriseOne OMW and SCM Integration

JD Edwards EnterpriseOne OMW enables you to integrate with third-party Source Control Management (SCM). SCM applications store objects that you create in JD Edwards EnterpriseOne OMW and create new versions of an object each time you check it in. Since older versions are saved, you can refer back to them to review changes. This is especially useful in determining at what point in the development process errors might have compromised an object.

Your ability to integrate with an SCM from JD Edwards EnterpriseOne OMW depends on whether the functionality that provides the integration is turned on or off. You can decide which JD Edwards EnterpriseOne OMW objects you want integrated in an SCM. For example, you might want to enable integration for report and business function objects while leaving table, business view, and data structure objects untouched.

This table shows the objects to manage, along with the components for which versions are created.

Metadata Object

Components on which an SCM application creates versions

BSFN

The source (.c) and header (.h) files of both C and NER business function objects. For NER business functions, an JD Edwards EnterpriseOne OMW will create a readable event rules printout.

TBLE

The header (.h) file.

BSVW

The header (.h) file.

DSTR

A generated text file containing the type definition of the data structure object.

APPL

A generated text file containing an application level printout of the event rules contained in the application.

UBE

A generated text file containing an application level printout of the event rules contained in the batch application.

17.1.1 Configuring JD Edwards EnterpriseOne OMW to Interface with ClearCase

Access the Object Management Configuration form.

1. Click the Configure Source Management Integration button.

2. On the Source Management Setup form, select the Enable JD Edwards EnterpriseOne OMW/SCM Integration check box to enable JD Edwards EnterpriseOne OMW/SCM integration, or clear the check box to disable JD Edwards EnterpriseOne OMW/SCM integration.

3. If you have opted to enable JD Edwards EnterpriseOne OMW/SCM integration, select the following object types that you want to integrate between the applications:

- Applications

- Batch Applications

- Business Function

- Data Structure

- Tables

- Business Views

4. In the Choose the source code management software to integrate with field, select ClearCase.

5. Select or clear the Enable backup on delete check box. If you select check box, the system renames and moves an object's text components when the object is deleted from an ERP pathcode. If you clear the check box, the system removes an object's text components from the folder location that is associated to the ERP pathcode from which the object was deleted. This folder resides on the SCM server.

6. Click OK.

17.1.2 Configuring Access to ClearCase

When JD Edwards EnterpriseOne OMW interfaces with ClearCase, it uses a "view" to decipher what in ClearCase a user is allowed to access. This view has rules associated to it that enable or restrict users' access to certain objects. For example, you might want one set of users to have access only to application objects; another set of users to have access to business view objects. Therefore, you can have many views and many users to whom you want to assign the same view. Instead of manually assigning the same set of rules to a view for each user, you can create a view profile that contains a set of rules that are automatically assigned to a view each time the view is used, eliminating you from having to manually assign the rules to each view for each user accessing it.

You must complete the Access Configuration process before you can complete the Pathcode Configuration process.

Access the Object Management Configuration form.

1. Click the Access Configuration button.
You must complete the Access Configuration before you can continue to the Pathcode Configuration.

2. On the Work with Source Management Access form, click the Add button to add a new SCM view, or click the Find button, and click a view from the list.
If you want to add an access configuration, continue to step 4. If you choose an existing access configuration, go to step 6.

3. Click Add.

4. In the View field, enter a view name.

5. In the View Profile field, enter the path and directory where the view profile you want to use resides in Clear Case.
JD Edwards EnterpriseOne OMW will validate that this is a valid and accessible path to a view profile.

6. Click OK.

7. Click Close.

17.1.3 Configuring Pathcodes

In JD Edwards EnterpriseOne OMW, when a user saves, checks in, or transfers an object, the object's specifications are placed in the pathcode that has been assigned to the object. This pathcode is specified by the transfer activity rules. Because of the integration of JD Edwards EnterpriseOne OMW and ClearCase, when a user saves, checks in, or transfers an object, a .txt file is generated that contains information on the object. This file must be placed in a directory located in ClearCase. When you configure a pathcode, you define the location in which JD Edwards EnterpriseOne OMW will place the .txt. file in ClearCase.

The .txt files that are generated are dependent upon the file type that are assigned to the object. There are several different file types, each containing its own set of information. These file types are already assigned by default to the object. The following table lists the file types associated with each object:

Object Type

File Type

NER
ER

ER — Event Rule Printout
NH — NER Business Function Header

NS — NER Business Function Source

C BSFN

BH — C Business Function Header
BS — C Business Function Source

APPL

ER — Event Rule
DH — Data Structure Header

UBE

ER — Event Rule
DH — Data Structure Header

TABLE

TH — Table Header

BSVW

VH — View Header

DSTR

DH — Data Structure Header

NA

BF — Backup Folder

NA

DF — Default

When you configure a pathcode, you define in what folder the .txt files that are generated for each file type will reside. For example, you might want all .txt files that are generated for objects with the ER file type associated with them to reside in an ER folder.

Access the Object Management Configuration form.

1. Click the Path Configuration button.

2. On the Source Management Pathcode Configuration form, click the Add button.

3. In the Path Code field, enter the pathcode and directory in Clear Case where you want the generated .txt files to be placed.
You can also click the Visual Assist button and select a pathcode from the list.

Note:
If the directory does not exist, select the Create Folder check box to have JD Edwards EnterpriseOne OMW create the folder.

4. In the EnterpriseOne File Type field, enter a file type.
JD Edwards EnterpriseOne OMW uses this file type to sort the .txt files into the appropriate folders in Clear Case. For example, all ER .txt files will be placed in the one folder you entered or chose in step 3. Oracle recommends that you always assign the Default file type to at least one pathcode. The Default folder is the location where the .txt files will be placed should you fail to assign a pathcode to a file type.

17.1.4 Setting up a Backup Folder for Deleted Objects

You can ensure that the .txt files that are generated when a user deletes an object are saved to a folder upon deletion. To do so, configure a pathcode record where the file type is BF.

17.1.5 Copying a Path Code

You can copy the information associated with a pathcode. This ability enables you to quickly and easily create records for a new pathcode without having to manually associate information to it that already exists for another pathcode.

Access the Work With Source Management Pathcode Configuration form.

1. Click the Find button to retrieve existing pathcodes.

2. Click the pathcode you want to copy, and then click the Copy Pathcode row exit.

3. On the Copy Source Management Pathcode Configuration form, enter the new pathcode in the To Path Code field.
You can also click the Visual Assist button and choose an existing pathcode.

4. Click OK.

17.2 Understanding the SCM Tool

The SCM tool is an interface that enables ERP developers to access all of the archival information collected on JD Edwards EnterpriseOne OMW objects. The SCM tool displays the version history information collected by JD Edwards EnterpriseOne OMW and enables ERP developers to find details about how one version of a text component differs from another version. The SCM tool is secure and contains functionality that is tailored for ERP developers to view version history information created by the integration with SCM.

You access the SCM tool through JD Edwards EnterpriseOne OMW.

17.2.1 SCM Interface and Functionality

The SCM tool contains panes from which you select objects and view information about them. Two of the panes are browsers from which you can select objects to view information about the objects. The other parts of the interface display the information about the objects you selected.

17.2.2 Source and Target Browsers

The Source and Target browsers contain tree structures. The tree contains a folder and file structure of either the SCM server to which the tool is currently connected, or the file and folder structure of the local machine on which you are working. Which folder and file structure the browsers display is dependent on the Server tab located at the bottom of each browser you select. When you select a file or folder, the field located at the top of the browsers is populated with the full path to that selected file or folder. You can also manually enter a path into the field if you know the path in which a file or folder is located.

See "Button and Icons".

The Source and Target browsers contain three node types. The following table shows the node icons, the node type, and contains a description of the icon:

Icon

Node Type

Description

File

Represents a file.

No Access

Represents anything in the storage structure to which the current user does not have permissions to access.

Folder

Represents a folder.

17.2.3 History, Source History and Target History, Label Contents Viewers

To the right of the browsers are the following four tabs:

- History

- Source History

- Target History

- Label Contents

17.2.3.1 History Tab

The History tab consists of two tables that display information about the folder or file selected in the Source or Target browsers. When you select a folder or file that resides on an SCM server in either browser, the version history for that folder or file displays in the corresponding History viewer. For each version, the viewer displays the version number (this is the version number assigned the version by the SCM server), the SCM user that checked the version in, the time the version was checked in, the date the version was checked in, and the comment the version with which the version was checked in. On top of the table is a text field that indicates the SCM file for which the history is displayed. The same is true respectively for the target history viewer and the target file browser.

17.2.3.2 Source History and Target History Tabs

When you select a file in the Source browser, and when you select a revision of the file in the Source History viewer and press the Visual Assist button, the SCM tool displays the contents of the selected file in the Source Viewer tab. The same is true for the for the Target File viewer; when you select a file in the Target browser, and when you selected a revision of the file in the Target History viewer, the SCM tool displays the contents of the selected file in the Source Viewer tab. Two text fields reside on top of the file contents pane: the File and the Revision fields. The File field displays the pathname and name of the SCM file that you selected. The lower text field displays the version of the file that you selected.

Both the Source Viewer and Target History tabs are divided into two panes: the top displays the selected file's contents, the bottom contains a text field you use to search for specific lines of text within the content. After the SCM tool finds the specific text, it displays the text in the bottom pane. You can enter any literal string.

The SCM tool clears any content loaded in either the Source Viewer or the Target Viewer tabs when you select a different file or folder in the respective browsers.

17.2.3.3 Labeling Viewer

If the SCM with which JD Edwards EnterpriseOne OMW is integrated supports revision labeling functionality, the SCM tool displays a Label Contents tab, which contains the Label Contents viewer. When you select an SCM folder node in either the Source or Target browser, the SCM tool displays the label information for the folder or file selected. At the top of the Label Contents viewer is the Path field. This field displays the folder path that is currently selected in the SCM if the folder is at a level that contains revision labels. Directly below the Path field are two edit fields: From and To. When you click the Search button next to these fields, the SCM tool will search for all labels that exist for the SCM folder specified in the Path text field. The system displays all labels that are found as a node in the tree underneath the Search button. The To and From edit fields are filters for the Search button. If you enter a value in the From edit field, the SCM tool displays only those labels that have names greater than the value in the From field. If you enter a value in the To field, the SCM tool displays only those labels that have names that are less than the value in the To field.

An exception to the explanation listed above is if the To and From values are the same, in which case, the SCM tool displays only the label that has a name that matches the To and From field.

17.2.3.4 Button and Icons

The following table displays the icons and buttons in the SCM tool, and describes their functionality.

Icon

Name

Action Menu Item (Hot Key)

Enabled

Function

Get

Get (Ctrl + G)

When you select an SCM server file in the source file browser and a local client folder in the target file browser.

Loads a copy of the revision of the file you selected in the source file browser and moves it to the folder selected in the target file browser.

Compare

Compare (Ctrl + Z)

When you select any file in the source file browser and you select a file with the same file extension in the target file browser.

Loads the configured file comparison tool to compare the following files: the selected revision of the file in the source file browser to the selected revision of the file in the target file browser.

Merge

Merge (Ctrl + M)

When you select any file in the source file browser and a local client file with the same file extension in the target file browser.

Loads the configured file merge tool to compare the differences between the selected revision of the file selected in the source file browser to the file selected in the target file browser, then allow the developer to merge those differences into the file selected in the target file browser.

Get Label

Get Label Files (Ctrl + L)

When at least one file is selected in the label contents viewer and a local client folder is selected in the target file browser.

Brings a copy of the specific revision of the selected files that are attached to the selected revision label down to the local client folder selected in the target file browser.

17.2.4 Using the SCM Tool

Access JD Edwards EnterpriseOne OMW.

1. From JD Edwards EnterpriseOne OMW, click the Form exit, and then click SCM Tool.

2. On Source Code Management Tool, click the folder containing the contents you want to view or modify, and then click an object.

3. Click the appropriate tab to view the associated information.

Glossary

Accessor Methods/Assessors

Java methods to “get” and “set” the elements of a value object or other source file.

activity rule

The criteria by which an object progresses from one given point to the next in a flow.

add mode

A condition of a form that enables users to input data.

Advanced Planning Agent (APAg)

A JD Edwards EnterpriseOne tool that can be used to extract, transform, and load enterprise data. APAg supports access to data sources in the form of rational databases, flat file format, and other data or message encoding, such as XML.

application server

Software that provides the business logic for an application program in a distributed environment. The servers can be Oracle Application Server (OAS) or WebSphere Application Server (WAS).

Auto Commit Transaction

A database connection through which all database operations are immediately written to the database.

batch processing

A process of transferring records from a third-party system to JD Edwards EnterpriseOne.

In JD Edwards EnterpriseOne Financial Management, batch processing enables you to transfer invoices and vouchers that are entered in a system other than JD Edwards EnterpriseOne to JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Accounts Payable, respectively. In addition, you can transfer address book information, including customer and supplier records, to JD Edwards EnterpriseOne.

batch server

A server that is designated for running batch processing requests. A batch server typically does not contain a database nor does it run interactive applications.

batch-of-one

A transaction method that enables a client application to perform work on a client workstation, then submit the work all at once to a server application for further processing. As a batch process is running on the server, the client application can continue performing other tasks.

best practices

Non-mandatory guidelines that help the developer make better design decisions.

BPEL

Abbreviation for Business Process Execution Language, a standard web services orchestration language, which enables you to assemble discrete services into an end-to-end process flow.

BPEL PM

Abbreviation for Business Process Execution Language Process Manager, a comprehensive infrastructure for creating, deploying, and managing BPEL business processes.

Build Configuration File

Configurable settings in a text file that are used by a build program to generate ANT scripts. ANT is a software tool used for automating build processes. These scripts build published business services.

build engineer

An actor that is responsible for building, mastering, and packaging artifacts. Some build engineers are responsible for building application artifacts, and some are responsible for building foundation artifacts.

Build Program

A WIN32 executable that reads build configuration files and generates an ANT script for building published business services.

business analyst

An actor that determines if and why an EnterpriseOne business service needs to be developed.

business function

A named set of user-created, reusable business rules and logs that can be called through event rules. Business functions can run a transaction or a subset of a transaction (check inventory, issue work orders, and so on). Business functions also contain the application programming interfaces (APIs) that enable them to be called from a form, a database trigger, or a non-JD Edwards EnterpriseOne application. Business functions can be combined with other business functions, forms, event rules, and other components to make up an application. Business functions can be created through event rules or third-generation languages, such as C. Examples of business functions include Credit Check and Item Availability.

business function event rule

See named event rule (NER).

business service

EnterpriseOne business logic written in Java. A business service is a collection of one or more artifacts. Unless specified otherwise, a business service implies both a published business service and business service.

business service artifacts

Source files, descriptors, and so on that are managed for business service development and are needed for the business service build process.

business service class method

A method that accesses resources provided by the business service framework.

business service configuration files

Configuration files include, but are not limited to, interop.ini, JDBj.ini, and jdelog.properties.

business service cross reference

A key and value data pair used during orchestration. Collectively refers to both the code and the key cross reference in the WSG/XPI based system.

business service cross-reference utilities

Utility services installed in a BPEL/ESB environment that are used to access JD Edwards EnterpriseOne orchestration cross-reference data.

business service development environment

A framework needed by an integration developer to develop and manage business services.

business services development tool

Otherwise known as JDeveloper.

business service EnterpriseOne object

A collection of artifacts managed by EnterpriseOne LCM tools. Named and represented within EnterpriseOne LCM similarly to other EnterpriseOne objects like tables, views, forms, and so on.

business service framework

Parts of the business service foundation that are specifically for supporting business service development.

business service payload

An object that is passed between an enterprise server and a business services server. The business service payload contains the input to the business service when passed to the business services server. The business service payload contains the results from the business service when passed to the Enterprise Server. In the case of notifications, the return business service payload contains the acknowledgement.

business service property

Key value data pairs used to control the behavior or functionality of business services.

Business Service Property Admin Tool

An EnterpriseOne application for developers and administrators to manage business service property records.

business service property business service group

A classification for business service property at the business service level. This is generally a business service name. A business service level contains one or more business service property groups. Each business service property group may contain zero or more business service property records.

business service property key

A unique name that identifies the business service property globally in the system.

business service property utilities

A utility API used in business service development to access EnterpriseOne business service property data.

business service property value

A value for a business service property.

business service repository

A source management system, for example ClearCase, where business service artifacts and build files are stored. Or, a physical directory in network.

business services server

The physical machine where the business services are located. Business services are run on an application server instance.

business services source file or business service class

One type of business service artifact. A text file with the .java file type written to be compiled by a Java compiler.

business service value object template

The structural representation of a business service value object used in a C-business function.

Business Service Value Object Template Utility

A utility used to create a business service value object template from a business service value object.

business services server artifact

The object to be deployed to the business services server.

business view

A means for selecting specific columns from one or more JD Edwards EnterpriseOne application tables whose data is used in an application or report. A business view does not select specific rows, nor does it contain any actual data. It is strictly a view through which you can manipulate data.

central objects merge

A process that blends a customer's modifications to the objects in a current release with objects in a new release.

central server

A server that has been designated to contain the originally installed version of the software (central objects) for deployment to client computers. In a typical JD Edwards EnterpriseOne installation, the software is loaded on to one machine—the central server. Then, copies of the software are pushed out or downloaded to various workstations attached to it. That way, if the software is altered or corrupted through its use on workstations, an original set of objects (central objects) is always available on the central server.

charts

Tables of information in JD Edwards EnterpriseOne that appear on forms in the software.

check-in repository

A repository for developers to check in and check out business service artifacts. There are multiple check-in repositories. Each can be used for a different purpose (for example, development, production, testing, and so on).

checksum

A fixed-size datum computed from an arbitrary block of digital data for the purpose of detecting accidental errors that may have been introduced during its transmission or storage. JD Edwards EnterpriseOne uses the checksum to verify the integrity of packages that have been downloaded by recomputing the checksum of the downloaded package and comparing it with the checksum of the original package. The procedure that yields the checksum from the data is called a checksum function or checksum algorithm. JD Edwards EnterpriseOne uses the MD5 and STA-1 checksum algorithms.

connector

Component-based interoperability model that enables third-party applications and JD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOne connector architecture includes Java and COM connectors.

Control Table Workbench

An application that, during the Installation Workbench processing, runs the batch applications for the planned merges that update the data dictionary, user-defined codes, menus, and user override tables.

control tables merge

A process that blends a customer's modifications to the control tables with the data that accompanies a new release.

correlation data

The data used to tie HTTP responses with requests that consist of business service name and method.

credentials

A valid set of JD Edwards EnterpriseOne username/password/environment/role, EnterpriseOne session, or EnterpriseOne token.

cross-reference utility services

Utility services installed in a BPEL/ESB environment that access EnterpriseOne cross-reference data.

database credentials

A valid database username/password.

database server

A server in a local area network that maintains a database and performs searches for client computers.

Data Source Workbench

An application that, during the Installation Workbench process, copies all data sources that are defined in the installation plan from the Data Source Master and Table and Data Source Sizing tables in the Planner data source to the system-release number data source. It also updates the Data Source Plan detail record to reflect completion.

deployment artifacts

Artifacts that are needed for the deployment process, such as servers, ports, and such.

deployment server

A server that is used to install, maintain, and distribute software to one or more enterprise servers and client workstations.

direct connect

A transaction method in which a client application communicates interactively and directly with a server application.

See also batch-of-one and store-and-forward.

Do Not Translate (DNT)

A type of data source that must exist on the iSeries because of BLOB restrictions.

embedded application server instance

An OC4J instance started by and running wholly within JDeveloper.

edit code

A code that indicates how a specific value for a report or a form should appear or be formatted. The default edit codes that pertain to reporting require particular attention because they account for a substantial amount of information.

edit mode

A condition of a form that enables users to change data.

edit rule

A method used for formatting and validating user entries against a predefined rule or set of rules.

Electronic Data Interchange (EDI)

An interoperability model that enables paperless computer-to-computer exchange of business transactions between JD Edwards EnterpriseOne and third-party systems. Companies that use EDI must have translator software to convert data from the EDI standard format to the formats of their computer systems.

embedded event rule

An event rule that is specific to a particular table or application. Examples include form-to-form calls, hiding a field based on a processing option value, and calling a business function. Contrast with the business function event rule.

Employee Work Center

A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. Each user has a mailbox that contains workflow and other messages, including Active Messages.

enterprise server

A server that contains the database and the logic for JD Edwards EnterpriseOne.

Enterprise Service Bus (ESB)

Middleware infrastructure products or technologies based on web services standards that enable a service-oriented architecture using an event-driven and XML-based messaging framework (the bus).

EnterpriseOne administrator

An actor responsible for the EnterpriseOne administration system.

EnterpriseOne credentials

A user ID, password, environment, and role used to validate a user of EnterpriseOne.

EnterpriseOne development client

Historically called “fat client,” a collection of installed EnterpriseOne components required to develop EnterpriseOne artifacts, including the Microsoft Windows client and design tools.

EnterpriseOne extension

A JDeveloper component (plug-in) specific to EnterpriseOne. A JDeveloper wizard

is a specific example of an extension.

EnterpriseOne object

A reusable piece of code that is used to build applications. Object types include tables, forms, business functions, data dictionary items, batch processes, business views, event rules, versions, data structures, and media objects.

EnterpriseOne process

A software process that enables JD Edwards EnterpriseOne clients and servers to handle processing requests and run transactions. A client runs one process, and servers can have multiple instances of a process. JD Edwards EnterpriseOne processes can also be dedicated to specific tasks (for example, workflow messages and data replication) to ensure that critical processes don't have to wait if the server is particularly busy.

EnterpriseOne resource

Any EnterpriseOne table, metadata, business function, dictionary information, or other information restricted to authorized users.

Environment Workbench

An application that, during the Installation Workbench process, copies the environment information and Object Configuration Manager tables for each environment from the Planner data source to the system-release number data source. It also updates the Environment Plan detail record to reflect completion.

escalation monitor

A batch process that monitors pending requests or activities and restarts or forwards them to the next step or user after they have been inactive for a specified amount of time.

event rule

A logic statement that instructs the system to perform one or more operations based on an activity that can occur in a specific application, such as entering a form or exiting a field.

explicit transaction

Transaction used by a business service developer to explicitly control the type (auto or manual) and the scope of transaction boundaries within a business service.

exposed method or value object

Published business service source files or parts of published business service source files that are part of the published interface. These are part of the contract with the customer.

fast path

A command prompt that enables the user to move quickly among menus and applications by using specific commands.

file server

A server that stores files to be accessed by other computers on the network. Unlike a disk server, which appears to the user as a remote disk drive, a file server is a sophisticated device that not only stores files, but also manages them and maintains order as network users request files and make changes to these files.

final mode

The report processing mode of a processing mode of a program that updates or creates data records.

foundation

A framework that must be accessible for execution of business services at runtime. This includes, but is not limited to, the Java Connector and JDBj.

FTP server

A server that responds to requests for files via file transfer protocol.

HTTP Adapter

A generic set of services that are used to do the basic HTTP operations, such as GET, POST, PUT, DELETE, TRACE, HEAD, and OPTIONS with the provided URL.

instantiate

A Java term meaning “to create.” When a class is instantiated, a new instance

is created.

integration developer

The user of the system who develops, runs, and debugs the EnterpriseOne business services. The integration developer uses the EnterpriseOne business services to develop these components.

integration point (IP)

The business logic in previous implementations of EnterpriseOne that exposes a document level interface. This type of logic used to be called XBPs. In EnterpriseOne 8.11, IPs are implemented in Web Services Gateway powered by webMethods.

integration server

A server that facilitates interaction between diverse operating systems and applications across internal and external networked computer systems.

integrity test

A process used to supplement a company's internal balancing procedures by locating and reporting balancing problems and data inconsistencies.

interface table

See Z table.

internal method or value object

Business service source files or parts of business service source files that are not part of the published interface. These could be private or protected methods. These could be value objects not used in published methods.

interoperability model

A method for third-party systems to connect to or access JD Edwards EnterpriseOne.

in-your-face error

In JD Edwards EnterpriseOne, a form-level property which, when enabled, causes the text of application errors to appear on the form.

jargon

An alternative data dictionary item description that JD Edwards EnterpriseOne appears based on the product code of the current object.

Java application server

A component-based server that resides in the middle-tier of a server-centric architecture. This server provides middleware services for security and state maintenance, along with data access and persistence.

JDBNET

A database driver that enables heterogeneous servers to access each other's data.

JDEBASE Database Middleware

A JD Edwards EnterpriseOne proprietary database middleware package that provides platform-independent APIs, along with client-to-server access.

JDECallObject

An API used by business functions to invoke other business functions.

jde.ini

A JD Edwards EnterpriseOne file (or member for iSeries) that provides the runtime settings required for JD Edwards EnterpriseOne initialization. Specific versions of the file or member must reside on every machine running JD Edwards EnterpriseOne. This includes workstations and servers.

JDEIPC

Communications programming tools used by server code to regulate access to the same data in multiprocess environments, communicate and coordinate between processes, and create new processes.

jde.log

The main diagnostic log file of JD Edwards EnterpriseOne. This file is always located in the root directory on the primary drive and contains status and error messages from the startup and operation of JD Edwards EnterpriseOne.

JDENET

A JD Edwards EnterpriseOne proprietary communications middleware package. This package is a peer-to-peer, message-based, socket-based, multiprocess communications middleware solution. It handles client-to-server and server-to-server communications for all JD Edwards EnterpriseOne supported platforms.

JDeveloper Project

An artifact that JDeveloper uses to categorize and compile source files.

JDeveloper Workspace

An artifact that JDeveloper uses to organize project files. It contains one or more project files.

JMS Queue

A Java Messaging service queue used for point-to-point messaging.

listener service

A listener that listens for XML messages over HTTP.

local repository

A developer's local development environment that is used to store business service artifacts.

Location Workbench

An application that, during the Installation Workbench process, copies all locations that are defined in the installation plan from the Location Master table in the Planner data source to the system data source.

logic server

A server in a distributed network that provides the business logic for an application program. In a typical configuration, pristine objects are replicated on to the logic server from the central server. The logic server, in conjunction with workstations, actually performs the processing required when JD Edwards EnterpriseOne software runs.

MailMerge Workbench

An application that merges Microsoft Word 6.0 (or higher) word-processing documents with JD Edwards EnterpriseOne records to automatically print business documents. You can use MailMerge Workbench to print documents, such as form letters about verification of employment.

Manual Commit transaction

A database connection where all database operations delay writing to the database until a call to commit is made.

master business function (MBF)

An interactive master file that serves as a central location for adding, changing, and updating information in a database. Master business functions pass information between data entry forms and the appropriate tables. These master functions provide a common set of functions that contain all of the necessary default and editing rules for related programs. MBFs contain logic that ensures the integrity of adding, updating, and deleting information from databases.

master table

See published table.

media storage object

Files that use one of the following naming conventions that are not organized into table format: Gxxx, xxxGT, or GTxxx.

message center

A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user.

messaging adapter

An interoperability model that enables third-party systems to connect to JD Edwards EnterpriseOne to exchange information through the use of messaging queues.

messaging server

A server that handles messages that are sent for use by other programs using a messaging API. Messaging servers typically employ a middleware program to perform their functions.

Monitoring Application

An EnterpriseOne tool provided for an administrator to get statistical information for various EnterpriseOne servers, reset statistics, and set notifications.

named event rule (NER)

Encapsulated, reusable business logic created using event rules, rather that C programming. NERs are also called business function event rules. NERs can be reused in multiple places by multiple programs. This modularity lends itself to streamlining, reusability of code, and less work.

Object Configuration Manager (OCM)

In JD Edwards EnterpriseOne, the object request broker and control center for the runtime environment. OCM keeps track of the runtime locations for business functions, data, and batch applications. When one of these objects is called, OCM directs access to it using defaults and overrides for a given environment and user.

Object Librarian

A repository of all versions, applications, and business functions reusable in building applications. Object Librarian provides check-out and check-incapabilities for developers, and it controls the creation, modification, and use of JD Edwards EnterpriseOne objects. Object Librarian supports multiple environments (such as production and development) and enables objects to be easily moved from one environment to another.

Object Librarian merge

A process that blends any modifications to the Object Librarian in a previous release into the Object Librarian in a new release.

Open Data Access (ODA)

An interoperability model that enables you to use SQL statements to extract JD Edwards EnterpriseOne data for summarization and report generation.

Output Stream Access (OSA)

An interoperability model that enables you to set up an interface for JD Edwards EnterpriseOne to pass data to another software package, such as Microsoft Excel, for processing.

package

JD Edwards EnterpriseOne objects are installed to workstations in packages from the deployment server. A package can be compared to a bill of material or kit that indicates the necessary objects for that workstation and where on the deployment server the installation program can find them. It is point-in-time snapshot of the central objects on the deployment server.

package build

A software application that facilitates the deployment of software changes and new applications to existing users. Additionally, in JD Edwards EnterpriseOne, a package build can be a compiled version of the software. When you upgrade your version of the ERP software, for example, you are said to take a package build.

Consider the following context: “Also, do not transfer business functions into the production path code until you are ready to deploy, because a global build of business functions done during a package build will automatically include the new functions.” The process of creating a package build is often referred to, as it is in this example, simply as “a package build.”

package location

The directory structure location for the package and its set of replicated objects. This is usually \\deployment server\release\path_code\package\package name. The subdirectories under this path are where the replicated objects for the package are placed. This is also referred to as where the package is built or stored.

Package Workbench

An application that, during the Installation Workbench process, transfers the package information tables from the Planner data source to the system-release number data source. It also updates the Package Plan detail record to reflect completion.

Pathcode Directory

The specific portion of the file system on the EnterpriseOne development client where EnterpriseOne development artifacts are stored.

patterns

General repeatable solutions to a commonly occurring problem in software design. For business service development, the focus is on the object relationships and interactions. For orchestrations, the focus is on the integration patterns (for example, synchronous and asynchronous request/response, publish, notify, and receive/reply).

print server

The interface between a printer and a network that enables network clients to connect to the printer and send their print jobs to it. A print server can be a computer, separate hardware device, or even hardware that resides inside of the printer itself.

pristine environment

A JD Edwards EnterpriseOne environment used to test unaltered objects with JD Edwards EnterpriseOne demonstration data or for training classes. You must have this environment so that you can compare pristine objects that you modify.

processing option

A data structure that enables users to supply parameters that regulate the running of a batch program or report. For example, you can use processing options to specify default values for certain fields, to determine how information appears or is printed, to specify date ranges, to supply runtime values that regulate program execution, and so on.

production environment

A JD Edwards EnterpriseOne environment in which users operate EnterpriseOne software.

Production Published Business Services Web Service

Published business services web service deployed to a production application server.

program temporary fix (PTF)

A representation of changes to JD Edwards EnterpriseOne software that your organization receives on magnetic tapes or disks.

project

In JD Edwards EnterpriseOne, a virtual container for objects being developed in Object Management Workbench.

promotion path

The designated path for advancing objects or projects in a workflow. The following is the normal promotion cycle (path):

11>21>26>28>38>01

In this path, 11 equals new project pending review, 21 equals programming, 26 equals QA test/review, 28 equals QA test/review complete, 38 equals in production, 01 equals complete. During the normal project promotion cycle, developers check objects out of and into the development path code and then promote them to the prototype path code. The objects are then moved to the productions path code before declaring them complete.

proxy server

A server that acts as a barrier between a workstation and the internet so that the enterprise can ensure security, administrative control, and caching service.

published business service

EnterpriseOne service level logic and interface. A classification of a published business service indicating the intention to be exposed to external (non-EnterpriseOne) systems.

published business service identification information

Information about a published business service used to determine relevant authorization records. Published business services + method name, published business services, or *ALL.

published business service web service

Published business services components packaged as J2EE Web Service (namely, a J2EE EAR file that contains business service classes, business service foundation, configuration files, and web service artifacts).

published table

Also called a master table, this is the central copy to be replicated to other machines. Residing on the publisher machine, the F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.

publisher

The server that is responsible for the published table. The F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.

QBE

An abbreviation for query by example. In JD Edwards EnterpriseOne, the QBE line is the top line on a detail area that is used for filtering data.

real-time event

A message triggered from EnterpriseOne application logic that is intended for external systems to consume.

refresh

A function used to modify JD Edwards EnterpriseOne software, or subset of it, such as a table or business data, so that it functions at a new release or cumulative update level.

replication server

A server that is responsible for replicating central objects to client machines.

rules

Mandatory guidelines that are not enforced by tooling, but must be followed in order to accomplish the desired results and to meet specified standards.

secure by default

A security model that assumes that a user does not have permission to execute an object unless there is a specific record indicating such permissions.

Secure Socket Layer (SSL)

A security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery.

selection

Found on JD Edwards EnterpriseOne menus, a selection represents functions that you can access from a menu. To make a selection, type the associated number in the Selection field and press Enter.

serialize

The process of converting an object or data into a format for storage or transmission across a network connection link with the ability to reconstruct the original data or objects when needed.

Server Workbench

An application that, during the Installation Workbench process, copies the server configuration files from the Planner data source to the system-release number data source. The application also updates the Server Plan detail record to reflect completion.

SOA

Abbreviation for Service Oriented Architecture.

softcoding

A coding technique that enables an administrator to manipulate site-specific variables that affect the execution of a given process.

source repository

A repository for HTTP adapter and listener service development environment artifacts.

Specification merge

A merge that comprises three merges: Object Librarian merge, Versions List merge, and Central Objects merge. The merges blend customer modifications with data that accompanies a new release.

specification

A complete description of a JD Edwards EnterpriseOne object. Each object has its own specification, or name, which is used to build applications.

Specification Table Merge Workbench

An application that, during the Installation Workbench process, runs the batch applications that update the specification tables.

SSL Certificate

A special message signed by a certificate authority that contains the name of a user and that user's public key in such a way that anyone can "verify" that the message was signed by no one other than the certification authority and thereby develop trust in the user's public key.

store-and-forward

The mode of processing that enables users who are disconnected from a server to enter transactions and then later connect to the server to upload those transactions.

subscriber table

Table F98DRSUB, which is stored on the publisher server with the F98DRPUB table and identifies all of the subscriber machines for each published table.

super class

An inheritance concept of the Java language where a class is an instance of something, but is also more specific. “Tree” might be the super class of “Oak” and “Elm,” for example.

table access management (TAM)

The JD Edwards EnterpriseOne component that handles the storage and retrieval of use-defined data. TAM stores information, such as data dictionary definitions; application and report specifications; event rules; table definitions; business function input parameters and library information; and data structure definitions for running applications, reports, and business functions.

Table Conversion Workbench

An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.

table conversion

An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.

table event rules

Logic that is attached to database triggers that runs whenever the action specified by the trigger occurs against the table. Although JD Edwards EnterpriseOne enables event rules to be attached to application events, this functionality is application specific. Table event rules provide embedded logic at the table level.

terminal server

A server that enables terminals, microcomputers, and other devices to connect to a network or host computer or to devices attached to that particular computer.

transaction processing (TP) monitor

A monitor that controls data transfer between local and remote terminals and the applications that originated them. TP monitors also protect data integrity in the distributed environment and may include programs that validate data and format terminal screens.

transaction processing method

A method related to the management of a manual commit transaction boundary (for example, start, commit, rollback, and cancel).

transaction set

An electronic business transaction (electronic data interchange standard document) made up of segments.

trigger

One of several events specific to data dictionary items. You can attach logic to a data dictionary item that the system processes automatically when the event occurs.

triggering event

A specific workflow event that requires special action or has defined consequences or resulting actions.

user identification information

User ID, role, or *public.

User Overrides merge

Adds new user override records into a customer's user override table.

value object

A specific type of source file that holds input or output data, much like a data structure passes data. Value objects can be exposed (used in a published business service) or internal, and input or output. They are comprised of simple and complex elements and accessories to those elements.

versioning a published business service

Adding additional functionality/interfaces to the published business services without modifying the existing functionality/interfaces.

Versions List merge

The Versions List merge preserves any non-XJDE and non-ZJDE version specifications for objects that are valid in the new release, as well as their processing options data.

visual assist

Forms that can be invoked from a control via a trigger to assist the user in determining what data belongs in the control.

vocabulary override

An alternate description for a data dictionary item that appears on a specific JD Edwards EnterpriseOne form or report.

web application server

A web server that enables web applications to exchange data with the back-end systems and databases used in eBusiness transactions.

web server

A server that sends information as requested by a browser, using the TCP/IP set of protocols. A web server can do more than just coordination of requests from browsers; it can do anything a normal server can do, such as house applications or data. Any computer can be turned into a web server by installing server software and connecting the machine to the internet.

Web Service Description Language (WSDL)

An XML format for describing network services.

Web Service Inspection Language (WSIL)

An XML format for assisting in the inspection of a site for available services and a set of rules for how inspection-related information should be made.

web service softcoding record

An XML document that contains values that are used to configure a web service proxy. This document identifies the endpoint and conditionally includes security information.

web service softcoding template

An XML document that provides the structure for a soft coded record.

Where clause

The portion of a database operation that specifies which records the database operation will affect.

Windows terminal server

A multiuser server that enables terminals and minimally configured computers to display Windows applications even if they are not capable of running Windows software themselves. All client processing is performed centrally at the Windows terminal server and only display, keystroke, and mouse commands are transmitted over the network to the client terminal device.

wizard

A type of JDeveloper extension used to walk the user through a series of steps.

workbench

A program that enables users to access a group of related programs from a single entry point. Typically, the programs that you access from a workbench are used to complete a large business process. For example, you use the JD Edwards EnterpriseOne Payroll Cycle Workbench (P07210) to access all of the programs that the system uses to process payroll, print payments, create payroll reports, create journal entries, and update payroll history. Examples of JD Edwards EnterpriseOne workbenches include Service Management Workbench (P90CD020), Line Scheduling Workbench (P3153), Planning Workbench (P13700), Auditor's Workbench (P09E115), and Payroll Cycle Workbench.

workflow

The automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules.

workgroup server

A server that usually contains subsets of data replicated from a master network server. A workgroup server does not perform application or batch processing.

XAPI events

A service that uses system calls to capture JD Edwards EnterpriseOne transactions as they occur and then calls third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested notification when the specified transactions occur to return a response.

XML CallObject

An interoperability capability that enables you to call business functions.

XML Dispatch

An interoperability capability that provides a single point of entry for all XML documents coming into JD Edwards EnterpriseOne for responses.

XML List

An interoperability capability that enables you to request and receive JD Edwards EnterpriseOne database information in chunks.

XML Service

An interoperability capability that enables you to request events from one JD Edwards EnterpriseOne system and receive a response from another JD Edwards EnterpriseOne system.

XML Transaction

An interoperability capability that enables you to use a predefined transaction type to send information to or request information from JD Edwards EnterpriseOne. XML transaction uses interface table functionality.

XML Transaction Service (XTS)

Transforms an XML document that is not in the JD Edwards EnterpriseOne format into an XML document that can be processed by JD Edwards EnterpriseOne. XTS then transforms the response back to the request originator XML format.

Z event

A service that uses interface table functionality to capture JD Edwards EnterpriseOne transactions and provide notification to third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested to be notified when certain transactions occur.

Z table

A working table where non-JD Edwards EnterpriseOne information can be stored and then processed into JD Edwards EnterpriseOne. Z tables also can be used to retrieve JD Edwards EnterpriseOne data. Z tables are also known as interface tables.

Z transaction

Third-party data that is properly formatted in interface tables for updating to the JD Edwards EnterpriseOne database.

Index
A  B  C  D  F  G  I  J  L  M  N  O  P  R  S  T  U  V

A

Activity rules

project status, 13.3

activity rules

object transfer, 13.4

overview, 10.1.3

add

business service property, 6.7.1, 6.7.3

object save location, 14.1.3

projects to a project, 4.6

user to project, 8.3

add an object to an JD Edwards EnterpriseOne OMW project, 5.4.2 add multiple objects to an JD Edwards EnterpriseOne OMW project, 5.4.3 Add Object form, 5.2 add same-named objects to a project, 5.11.3 advance project, 4.5 Advanced get, 5.8.3 allowed (user) actions

setting up, 11.3

allowed actions, 2.4 artifacts

business service, 6.5.3

check in, 6.6.1

B

business service, 6.1

add artifacts, 6.5.3

artifact, 6.6.4

artifact list, 6.6.3

check in, 6.6

check out, 6.6, 6.6.2

create objects, 6.2

delete, 6.6.8

design, 6.5

invoke JDeveloper, 6.5.2

JDeveloper, 6.5.1

objects, 6.2

property, 6.7

property, add to project, 6.7.3

property, search, 6.7.2

published artifacts, 6.6.5

save, 6.6

search, 6.3

status, 6.4

business service property, 6.7

add, 6.7.1, 6.7.3

search, 6.7.2

C

change object properties, 5.10.2

change the release level of an object, 5.11.4

check objects in, 5.9.3, 6.6

check objects out, 5.9.2, 6.6, 6.6.2

concepts, allowed (user) actions, 2.4

configuration

notification subscriptions, 15.1

object save locations, 14

options, 10

overview, 10

settings indicators, 10.2.1

create

object save location, 14.1

project, 4.3

D

default project, 3.1.2

managing non-Object Librarian objects, 3.1

managing non-object librarian objects with, 2.2

overview, 3.1

delete

object save location, 14.1.5

objects from projects, 5.7.2

project, 4.7

user from project, 4.3.3, 8.3.3

detail

controlling logging, 12.2.4

development

controlling in event of logging failure, 12.2.5

disable SAR integration, 12.2

F

forms

Add Object, 5.2

functions

configuring notification subscriptions, 15.1

G

Get object specifications, 5.8

I

inherit token, 7.3

integration

disabling SAR system, 12.2

J

JD Edwards EnterpriseOne OMW

activity rulesoverview, 10.1.3

allowed (user) action, 2.4

allowed (user) actionssettingup, 11.3

conceptsallowed (user) actions, 2.4

configurationoptions, 10

configurationoverview, 10

configurationsettings indicators, 10.2.1

configurationworkflow, 10.1.2

configuring object save locations, 14

creating objects, 5

developmentcontrolling, 12.2.5

logging detailcontrolling, 12.2.4

logging system, 10.1.5

non-Object Librarian objectsmanaging using default project, 3.1

non-object librarian objectsmanagingusing default project, 2.2

notification subscriptionsoverview, 10.1.9

object action notificationsoverview, 10.1.8

object librarian and non-object librarian objects, 2.7

object overview, 5

object save locationadding, 14.1.3

object save locationcreating, 14.1

object save locationdeleting, 14.1.5

object save locationmodifying, 14.1.4

object save locationoverview, 10.1.7

object transfer activity rulesoverview, 13.4

objectadd object to project, 5.4

objectbutton definitions, 2.6

objectcreating a new object, 5

objectdelete objects fromproject, 5.7

objectget object specifications, 5.8

objectmaintain objects inmultiple software releases, 5.11

objectmove an object, 5.5

objectproperties, 5.10

objectremove objects fromproject, 5.6

objectsearching for objects, 5.3

objectview status, 2.6

project, 4

project constantsoverview, 10.1.6

project constantssettingup, 12.3

project promotion life cycle, 13.2

project status activity rules, 13.3

project statusallowed actions, 10.1.4

projectadd projects to, 4.6

projectadvance project status, 4.5

projectadvanced search, 4.2.3

projectcreate, 4.3

projectdefault project, 2.2

projectdelete, 4.7

projectmodify, 4.4

projectmodify description, 4.4.2

projectsdefaultprojects, 3.1

projectsearch for by associatedobjects, 4.2.4

projectview status, 2.6

SAR integrationdisabling, 12.2

security application, 10.1.10

token, 2.5

token queue, 7.2

tokeninherit, 7.3

tokenrelease, 7.5

tokenswitch, 7.4

user role, 2.3

user rolessecuring, 10.1.10.1

useradd to project, 8.3

userdelete from project, 4.3.3, 8.3.3

users, 8

usersearch, 8.2

JD Edwards EnterpriseOne OMW objects

create, 5.2

JDeveloper, 6.5.1

invoke, 6.5.2

L

locations

configuring object save locations, 14

log, 10.1.5

controlling detail, 12.2.4

log failure

controlling development in event of, 12.2.5

log system, 10.1.5

M

main form

components, 2.6

news/status view, 2.6

search view, 2.6

maintain objects in multiple software releases, 5.11 modify

project, 4.4

project description, 4.4.2

modifying an object's save location, 14.1.4 move multiple objects in an JD Edwards EnterpriseOne OMW project, 5.5.2 move objects, 5.5 move objects in an JD Edwards EnterpriseOne OMW project, 5.5.1

N

Non-Object Librarian Object

examples, 2.7

managing using default project, 2.2, 3.1

object librarian object

distinguished from, 2.7

notification subscriptions

overview, 10.1.9

notifications

object action, 10.1.8

O

object

add object to project, 5.4

adding save location, 14.1.3

button definitions, 2.6

create, 5

creating a save location, 14.1

delete objects from project, 5.7

deleting save location, 14.1.5

getting object specifications, 5.8

maintain objects in multiple software releases, 5.11

modifying save location, 14.1.4

move an object, 5.5

overview, 5

properties, 5.10

remove objects from project, 5.6

saving locations, 10.1.7

searching for objects, 5.3

view status, 2.6

Object Action Notification

overview, 10.1.8

Object Librarian Object

examples, 2.7

non-object librarian object

distinguished from, 2.7

object save locations

adding, 14.1.3

creating, 14.1

deleting, 14.1.5

modifying, 14.1.4

overview, 10.1.7

object transfer activity rules

overview, 13.4

P

project

add projects to, 4.6

add user to, 8.3

advance project status, 4.5

advanced search, 4.2.3

create, 4.3

delete, 4.7

delete user, 4.3.3, 8.3.3

modify, 4.4

modify description of, 4.4.2

overview, 4

search for by associated objects, 4.2.4

view status, 2.6

viewing, 4.1

project constants

overview, 10.1.6

setting up, 12.3

project promotion life cycle

JD Edwards EnterpriseOne OMW, 13.2

project status

advance, 4.5

project status activity rules

overview, 13.3

setting up, 13.3

project window, 4.1 projects

default, 3.1.2

default projects, 3.1

lifecycle, 3.2

published artifacts, 6.6.5

specify, 6.6.6

unpublish, 6.6.7

R

release token, 7.5

remove objects from projects, 5.6

S

SAR

disabling integration, 12.2

save location

adding, 14.1.3

creating, 14.1

deleting, 14.1.5

modifying, 14.1.4

overview, 10.1.7

search

advancedprojects, 4.2.3

projectby associated objects, 4.2.4

user, 8.2

search for objects, 5.3 security

application, 10.1.10

user roles, 10.1.10.1

set up allowed (user) actions, 11.3 set up project constants, 12.3 set up project status activity rules, 13.3 subscriptions

notification, 10.1.9

switch token, 7.4

T

token, 7.2

defined, 2.5

inheriting, 7.3

release, 7.5

switch, 7.4

token queue

view, 7.2.2

U

update

different objects in different releases, 5.11.6

update an object to match another object, 5.11.5 user

add to project, 8.3

delete from project, 4.3.3, 8.3.3

overview, 8

search, 8.2

user roles, 2.3

securing, 10.1.10.1

V

view

attachments in Design view, 9.2.1

attachments in the JD Edwards EnterpriseOne OMW, 9.2.2

object status, 2.6

project status, 2.6

projects, 4.1

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.