JD Edwards EnterpriseOne Tools

Solution Explorer Guide

Release 8.98 Update 4

E14720-02

March 2011

JD Edwards EnterpriseOne Tools Solution Explorer Guide, Release 8.98 Update 4

E14720-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 Solution Explorer

- 1.1 JD Edwards EnterpriseOne Solution Explorer Overview

- 1.2 JD Edwards EnterpriseOne Solution Explorer Implementation

- 1.2.1 JD Edwards EnterpriseOne Solution Explorer Implementation Steps

2 Using the Menu Design Mode

- 2.1 Understanding the Menu Design Mode

- 2.2 Understanding How to Set Up Task Views

- 2.3 Working with Task Views

- 2.3.1 Creating a New Task View

- 2.3.2 Changing a Task View

- 2.3.3 Deleting a Task View

- 2.4 Setting Up Tasks

- 2.4.1 Understanding Task Set Up

- 2.4.2 Finding JD Edwards EnterpriseOne Solution Explorer Task and Task Relationship Changes in Object Management Workbench

- 2.4.3 Creating a Task

- 2.4.4 Inserting an Existing Task

- 2.4.5 Applying Roles to a Task

- 2.4.6 Changing a Task

- 2.4.7 Deleting Tasks

- 2.4.7.1 Deleting an Instance of a Task

- 2.4.7.2 Deleting a Task from the Task Master Table (F9000)

- 2.4.8 Clearing Cache

3 Using the Menu Filtering Mode

- 3.1 Understanding Menu Filtering

- 3.1.1 Setting Up Menus with *ALL Role Filtering Considerations

- 3.1.1.1 Understanding how *ALL Role Filters Tasks

- 3.1.1.2 Deciding How Many Roles to Assign Users

- 3.1.2 Understanding Task View Roles

- 3.1.3 Filtering a Task View by Role

- 3.1.4 Changing a Role's View of a Task View

4 Using the Task Launching Mode

Glossary

Index

Preface

Welcome to the JD Edwards EnterpriseOne Tools Solution Explorer Guide.

Audience

This guide is intended for system administrators who are responsible for setting up tasks, task views, and task view roles.

This guide assumes you have a working knowledge of the following:

• The principles and customary practices of your business area.

• Computer desktop application usage and terminology.

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 Solution Explorer

This chapter contains the following topics:

- Section 1.1, "JD Edwards EnterpriseOne Solution Explorer Overview"

- Section 1.2, "JD Edwards EnterpriseOne Solution Explorer Implementation"

1.1 JD Edwards EnterpriseOne Solution Explorer Overview

Oracle's JD Edwards EnterpriseOne Solution Explorer provides you with a convenient method for accessing Windows-based JD Edwards EnterpriseOne applications, and creating/maintaining JD Edwards EnterpriseOne task views for Web or Windows.

JD Edwards EnterpriseOne Solution Explorer is comprised of the following three modes:

- Menu Design Mode
Use the Menu Design Mode to set up menus, tasks, task views, and task view roles.

- Menu Filtering Mode
Use the Menu Filter Mode to enable and disable tasks users assigned a certain role can perform.

- Task Launching Mode
Use the Task Launching Mode to navigate to development and administrative applications in JD Edwards EnterpriseOne using the Fast Path, or using the menu.

1.2 JD Edwards EnterpriseOne Solution Explorer Implementation

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

In the planning phase of your implementation, take advantage of all JD Edwards sources of information, including the installation guides and troubleshooting information.

1.2.1 JD Edwards EnterpriseOne Solution Explorer Implementation Steps

This list displays the steps for the JD Edwards EnterpriseOne Solution Explorer implementation.

- Set up task views.
See Understanding How to Set Up Task Views.

- Set up tasks.
See Setting Up Tasks.

- Set up task view roles.
See Applying Roles to a Task.

2 Using the Menu Design Mode

This chapter contains the following topics:

- Section 2.1, "Understanding the Menu Design Mode"

- Section 2.2, "Understanding How to Set Up Task Views"

- Section 2.3, "Working with Task Views"

- Section 2.4, "Setting Up Tasks"

2.1 Understanding the Menu Design Mode

Use the Menu Design Mode to set up menus, tasks, task views, and task view roles in JD Edwards EnterpriseOne Solution Explorer. Access Menu Design Mode by depressing the Menu Design Mode button located on the toolbar. Whether or not you have access to Menu Design Mode, and the type of access you have, depends on the permissions you have been assigned. You might be able to view Menu Design Mode, you might be able to make changes in Menu Design Mode, or you might not have access to it at all.

2.2 Understanding How to Set Up Task Views

Task views are groups of tasks arranged in a hierarchical tree structure. Tasks are the most discrete units in the JD Edwards EnterpriseOne Solution Explorer. Tasks are organized into hierarchical tree structures inside of task views. JD Edwards EnterpriseOne provides thousands of tasks, and you can add more of your own. When placed in a single task view, finding a specific task among thousands might be difficult and time-consuming.

JD Edwards EnterpriseOne Solution Explorer enables you to design many different task views, each displaying only some of the tasks in the system.

Typically, tasks are grouped in a task view because they relate to a common business system, process, or function. Logical selection and grouping of tasks in this way can help users find the functions that they need.

2.3 Working with Task Views

This section provides an overview of working with task views and describes how to:

- Create a new task view.

- Change a task view.

- Delete a task view.

2.3.1 Creating a New Task View

Create a new task view when you want to create a new category of tasks that you use to insert tasks and build task relationships. The tasks views that you create, design, and filter in JD Edwards EnterpriseOne Solution Explorer become part of the EnterpriseOne Menus in the JD Edwards EnterpriseOne Web Client.

Access JD Edwards EnterpriseOne Solution Explorer.

1. In JD Edwards EnterpriseOne Solution Explorer, select Add New Task View from the Tools menu.

2. In Task View Revisions, complete the following fields and options, and then click OK:

- Task View
Enter an internal ID for the task view. The ID must be between two and five digits and cannot contain alphabetic characters. If you start the ID with more than one zero, the system truncates it to a single zero. For example, if you type 005 as an ID, the system changes the ID to 05.

- Name

- Description
The name and the description do not have to be the same.

- Secured Task View

2.3.2 Changing a Task View

You can modify an existing task view. For example, you might want to change the name of a task view so that it more accurately reflects the category of tasks in that view.

Access JD Edwards EnterpriseOne Solution Explorer.

1. In JD Edwards EnterpriseOne Solution Explorer, select Work With Tasks from the Tools menu.
Alternately, if you want to change the current task view, right-click the top task view node and select Task Revisions from the menu. Skip to step 5.

2. In Work with Tasks, select Task Views from the Form menu.

3. In Work with Task Views, click Find.
Use the QBE row to refine your search.

4. Select the task view that you want to change, and then click Select.

5. In Task View Revisions, change any of the following fields and options, and then click OK:

- Name

- Description
The name and the description do not have to be the same.

- Secured Task View

2.3.3 Deleting a Task View

You can delete any task view from the system. Deleting a task view does not delete the tasks within the view from the system, however.

Access JD Edwards EnterpriseOne Solution Explorer.

1. In JD Edwards EnterpriseOne Solution Explorer, select Work With Tasks from the Tools menu.

2. In Work with Tasks, select Task Views from the Form menu.

3. In Work with Task Views, click Find.
Use the QBE row to refine your search.

4. Select a task view, and then click Delete.

5. In Confirm Delete, click OK.

2.4 Setting Up Tasks

This section provides an overview of task setup and discusses how to:

- Create tasks.

- Insert existing tasks.

- Apply roles to tasks.

- Change tasks.

- Delete tasks.

2.4.1 Understanding Task Set Up

To design and manage your system, you work with tasks, which are units of work that you use to build essential business processes. Tasks can be interactive programs, batch programs, workflows UDSs, and so on. You work with tasks in a JD Edwards EnterpriseOne Solution Explorer task view, which is a collection of related tasks that are hierarchically grouped in parent-child relationships and illustrated graphically by the task view menu. These task groups usually represent the steps in an essential business process such as Procure to Pay.

JD Edwards EnterpriseOne provides a large selection of tasks that are already grouped in relationships within different task views. You can modify already existing tasks and their relationships. You can also create new tasks, task relationships, and views.

Within a task view, you insert new or existing tasks and arrange the tasks in logical sequences. You create or revise tasks on an ongoing basis, and then insert them in a task view as necessary to build and enhance your business processes. The processes are fluid; that is, you can drag and drop tasks and task relationships to change the relationships and the order in which you perform tasks.

The system stores each task in a task view in the Task Master table (F9000) and assigns a unique ID to each one. Each task is a reusable object that you can insert into an existing task relationship, or you can use as a basis for creating a new task relationship. After you have inserted a task in a task view, you can move it, revise it, write documentation for it, set up processing options, set up versions, and locate it. You can accomplish any of these functions in a JD Edwards EnterpriseOne Solution Explorer task view by launching interactive programs or using features and functions that are included in JD Edwards EnterpriseOne Solution Explorer.

2.4.2 Finding JD Edwards EnterpriseOne Solution Explorer Task and Task Relationship Changes in Object Management Workbench

When you change tasks or task relationships in JD Edwards EnterpriseOne Solution Explorer, the change is logged in Object Management Workbench (OMW). If you have added or deleted tasks or task relationships, the information is stored in OMW so that you and others can easily find the tasks and task relationships that have changed. If you changed task properties from within the Work With Tasks program (P9000), the task is logged in OMW.

Note:
For your changes to be logged in OMW, your system administrator must have turned on OMW logging in the Security Workbench program (P00950) for your user ID. To determine whether your OMW logging is turned on, double-click the padlock button on the JD Edwards EnterpriseOne Solution Explorer status bar.

See Also:

- Creating a New Task View.

- Applying Roles to a Task.

2.4.3 Creating a Task

The tasks in task views are reusable objects that add to the flexibility of the JD Edwards EnterpriseOne Solution Explorer. Tasks reside in the Task Master table (F9000).

You can create a new task directly in the JD Edwards EnterpriseOne Solution Explorer by inserting a new task in a task view menu. You define the task using the Task Revisions form. When you create a task, you automatically create a relationship between the new child task and the parent task under which you inserted the new task.

Access JD Edwards EnterpriseOne Solution Explorer.

1. From Menu Design mode, right-click a folder and click Insert New Task from the menu.
The Task Revisions application displays.

2. In Task Revisions, complete the Task Name field.
If you accept upgrades or updates from JD EnterpriseOne, Solution Explorer will remove any custom tasks that you have created if you have named the tasks with a prefix JDE, BPM, or RMB. Make sure as you create new tasks that you use a prefix different than the ones listed here so that your custom tasks remain viable if an upgrade or update is performed on your system.

3. Select the Common tab, and then complete the following fields:

- Product Code

- Jargon

- Country Code
Leave this field blank if you want this task to be available for all users, regardless of their country codes. Otherwise, enter the country code that must be assigned to users before they can access this task.

4. Select the Executable tab, and then select one of the following task type options:

- Interactive
Select this option for a task that launches an interactive JD Edwards EnterpriseOne program.

- Batch
Turn on this option for a task that launches a JD Edwards EnterpriseOne batch program.

- URL
Turn on this option for a task that launches a web page.

- Folder
Turn on this option for a task to be used as an activity or nonsoftware placeholder in a task view. This task does not execute a function, but might have accompanying documentation that describes the activity.

- User Defined Code
Turn on this option for a task that launches a program that enables a user to modify UDC tables.

- EnterpriseOne Workflow
Turn on this option for a task that displays workflow processes.

- Crystal Enterprise
Turn on this option for a task that links to Crystal Enterprise. This task only works on the web. You should have Crystal Enterprise set up to use its task type.

5. If you turned on the Interactive option, complete the following fields:

- Application
Enter the object name of the program.

- Version
Complete this field only if you want to launch a specific version of a program. Click the Visual Assist to search for a version.

- Form
This is an optional field. To open a specific form in the program, enter the form ID. Click the Visual Assist to search for a form.

- Option Code

- Form Mode

- Application Type

6. If you turned on the Batch option, complete the following steps:

- Application

- Version
This is an optional field. To launch a specific version of a batch program, enter the version.

7. Select one of the following options:

- No Processing Options
Turn on this option to execute the batch program without processing options.

- Blind Execution
Turn on this option to execute the batch program without displaying its processing options.

- Prompt for Version
Select this option if you want to prompt the user to select which version of the batch program to run at execution.

- Prompt for Values
Select this option if you want to prompt the user to enter processing option values at execution.

- Data Selection
Select this option if you want to prompt the user to enter data selection at execution.

- Data Selection and Values
Select this option if you want to prompt the user to enter data selection and processing option values at execution.

8. If you turned on the URL option, complete the URL fields.

9. If you turned on the User Defined Code option, complete the following fields:

- Product Code

- User Defined Codes

10. To apply roles to the task, select Roles from the Form menu.

11. In Task Where Used, select the role that you want to apply to the task, and then select Change Status from the Row menu.
A check mark appears to indicate that the role is applied to the task. To remove a check mark, select Change Status from the Row menu again. To apply all roles to the task, select Enable All from the Form menu.

12. Click Close.

13. In Task Revisions, click OK.

2.4.4 Inserting an Existing Task

When you insert a task and thereby create a task relationship, the system stores the parent-child relationship that you create in the Task Relationships table (F9001). The system also stores the task view into which you inserted the task.

Because tasks are reusable objects, you can insert the same task into multiple task views.

Access a task view in JD Edwards EnterpriseOne Solution Explorer.

1. In a task view of JD Edwards EnterpriseOne Solution Explorer, select a task that will be the parent of the task that you want to insert.

2. Right-click the parent task, and then select Insert Existing Task from the menu.
The Task Relationship Revisions form appears. The form displays the parent task ID and all tasks that are children of the parent task that you selected.

3. In Task Relationship Revisions, click a new line, and complete the following required fields:

- Child Task ID

- Presentation Sequence
If you want the task that you are inserting to appear in a position other than last in the presentation sequence, change the number.

4. Complete any of the optional fields.

2.4.5 Applying Roles to a Task

You apply roles to tasks so that the tasks will be filtered properly in role-based task views. You can apply one or more roles to each task.

When a user launches a role-based task view, the system applies his or her login role to the view. If the system administrator has applied other roles to that user, he or she can view the task view by any of those roles to see a different set of tasks.

For example, a user might have two roles, General Accounting Clerk (the user's sign on role) and Accounts Payable Clerk. When the user launches a role-based task view, the system displays only those tasks to which the General Account Clerk role has been applied, such as Autoreconcile Void Payments, Autoreconcile Void Receipts, and Refresh Reconciliations File. The user can apply the Accounts Payable Clerk role to the task view, and the system displays only those tasks to which the Accounts Payable Clerk role has been applied, such as Speed Status Change, Create Payment Groups, and Work with Payments.

Users can switch roles only if they sign on to JD Edwards EnterpriseOne Solution Explorer with the *ALL role. If a user signs on with the *ALL role and then accesses a role-based task view, then the user can view all tasks that are visible to any of the roles assigned to the *ALL role.

For example, the *ALL role contains Role1 and Role2, but not Role3. When a user accesses a role-based task view, JD Edwards EnterpriseOne Solution Explorer displays all of the tasks that are available in Role1 or Role2. Tasks that are only available to Role 3 do not appear.

To apply roles to a task:

1. Select the task to which you want to apply roles.

2. Right-click the task, and then select Task Revisions.

3. In Task Revisions, select Roles from the Form menu.

4. In Task Where Used, click Find.

5. Select the parent of the task to which you want to apply roles, and then click Select.

6. In Role Definition, select the role to which you want to apply to the task, and then select Change Status from the Row menu.
A check mark appears to indicate that a role is applied to the task. To remove a check mark, select Change Status from the Row menu again. To apply all roles to the task, select Enable All from the Form menu.

7. Click Close.

8. In Task Revisions, click OK.

2.4.6 Changing a Task

When you change a task using this process, you affect all instances of the task in all task views where it resides.

Access a task view in JD Edwards EnterpriseOne Solution Explorer.

1. In Menu Design Mode, select the task that you want to change.

2. Right-click the task, and then select Task Revisions from the popup menu.

3. In Task Revisions, complete any changes that you want to make to the task, and then click OK.

2.4.7 Deleting Tasks

You can delete an instance of a task from a task view menu. However, performing this action does not delete the task itself; it merely eliminates the task from the task view. To delete a task from the system entirely, you must use the Work With Tasks program (P9000) to locate the task and then delete it from the Task Master table (F9000). You can delete a task from a task view. Doing so deletes the task only from the task view; it still exists in the Task Master table (F9000) and in any other relationship in which it has been inserted. Furthermore, you can still insert it into other task menus.

2.4.7.1 Deleting an Instance of a Task

Access a task view in JD Edwards EnterpriseOne Solution Explorer.

1. In JD Edwards EnterpriseOne Solution Explorer, open the task view that contains the task relationship that you want to delete.

2. Right-click the task that you want to delete, and then select Delete Relationship from the menu.

3. In Delete Relationship, click OK.

2.4.7.2 Deleting a Task from the Task Master Table (F9000)

To delete a task from the system completely, you must delete it from the Task Master table. Before you can do so, however, you must first delete all of the relationships for the task. This is equivalent to deleting the task in each task view menu in which it appears.

Access JD Edwards EnterpriseOne Solution Explorer.

1. In JD Edwards EnterpriseOne Solution Explorer, select Work With Tasks from the Tools menu.

2. Click Find.
Use the QBE row to refine your search.

3. Select the task that you want to delete, and then select Where Used from the Row menu.

4. In Task where Used, search for the parent of the current task by clicking Find.
The task might have more than one parent. If so, all of the parents appear.

5. Select the parent of the task that you want to delete, and then click Delete.

6. In Task Relationship Revisions, select the task that you want to delete, and then click Delete.

7. In Confirm Delete, click OK.

8. Click OK.

9. Repeat steps 5-8 for each parent of the task in the list.

10. In Task where Used, click Close.

11. In Work With Tasks, select the task that you want to delete, and then click Delete.

12. In Confirm Delete, click OK.

2.4.8 Clearing Cache

When you create, delete, or modify menus in JD Edwards EnterpriseOne Solution Explorer, they are saved to the same database from which the web client retrieves them. The web client stores them in a cache directory and then displays them in the JD Edwards EnterpriseOne Menu. To display new or modified menus, you must clear the cache directory. You clear the cache directory through Server Administration Workbench (SAW).

Access Server Administration Workbench.

1. Access and sign in SAW for JAS Servers.

2. From the Views menu, click Config.

3. Click Clear JD Edwards EnterpriseOne Menu Cache.

4. Open the web client.

5. Click the Menu Refresh button located on the JD Edwards EnterpriseOne Menu title bar.

3 Using the Menu Filtering Mode

This chapter contains the following topics:

- Section 3.1, "Understanding Menu Filtering"

3.1 Understanding Menu Filtering

Menu Filtering is the process that you use to selectively enable or disable tasks by role in a task view.

Access JD Edwards EnterpriseOne Solution Explorer.

1. In JD Edwards EnterpriseOne Solution Explorer, depress the Menu Filtering button.

2. Select the task view that you want to refine.
The system changes the task view menu display to indicate enabled and disabled tasks. Enabled tasks are indicated by a green check mark; disabled tasks are indicated by a red X

3. Expand the task tree in the task view to find a task that you want to enable or disable, and then select a task.

4. Click either the Enable or Disable button on the Toolbar.
You can also double-click the task to toggle between the enabled and disabled conditions.

5. Repeat steps 2-3 for each task you want to enable or disable.

6. When you have finished refining the task list, click the Save button on the toolbar.
Saving your configuration saves your changes to the Master Task Relationship table (F9001), so your changes will be available to all users who access that same database. JD Edwards EnterpriseOne Solution Explorer will prompt you to select the role to which your changes apply.

If you fail to save the changes, your changes will not remain when you exit from the JD Edwards EnterpriseOne Solution Explorer and then launch it again later.

7. Click the Show All in Menu Design mode button to toggle between hiding and displaying disabled tasks in the current task view menu for the currently selected role. This role is displayed beside the root node of the task view.

3.1.1 Setting Up Menus with *ALL Role Filtering Considerations

The *ALL role enables users to view a concatenation of all tasks that are available in any role that is assigned to the *ALL role in a single menu tree. JD Edwards recommends that you consider the information in this section as you design and plan your menus. These recommendations enable the filtering process to run more efficiently.

3.1.1.1 Understanding how *ALL Role Filters Tasks

When you set up menu filtering you can disable both single tasks and entire folders. If you disable a folder, all the tasks and subfolders within it are disabled. Any tasks that are disabled in every role included in the *ALL role will be filtered out of the menu tree in the web client when a user logs in using the *ALL role. If at least one role in the *ALL role has a task enabled, that task will display in the EnterpriseOne menu.

As the system processes each role during filtering, it stops processing and displays the task as soon as it finds a role in which the task is not disabled. Therefore, when you disable tasks, JD Edwards recommends that you sequence the roles in the order of the level of security, with the first role having the fewest disabled tasks (for example, the role that has the greatest access to functionality in the system). If you sequence your roles so that those with the least amount of disabled tasks are first, then the filtering process will take less time to complete.

3.1.1.2 Deciding How Many Roles to Assign Users

The system filters menus when users open a task view or expand a folder. If a user is assigned many roles and a depth of many imbedded tasks, they might want to sign into EnterpriseOne using the *ALL role, but switch to a specific role before opening a task view. This will decrease the amount of time for the filtering process.

When setting up menu filtering, consider the number of roles that each user requires. JD Edwards recommends that you keep the number of roles to a minimum. Increasing the number of roles increases the amount of time it takes to filter the tasks when users choose the *ALL (All My Roles) in the web client.

3.1.2 Understanding Task View Roles

You can use roles to customize certain task views or parts of task views for specific user groups. Roles define a subset of the tasks in the original task view. They enable you to customize and simplify task views for the end user.

Roles apply only to users who have access to those roles.

You can use roles to make different versions of task objects available to users, and you can vary the descriptions of the tasks, as well.

3.1.3 Filtering a Task View by Role

To filter a task view by role, you refine the task view using the Menu Filtering mode, and then save the results. You define the role or based on your needs analysis of the users.

Access a task view in JD Edwards EnterpriseOne Solution Explorer.

1. In a task view of JD Edwards EnterpriseOne Solution Explorer, click the Menu Filtering button on the Toolbar.

2. Select a parent task and expand the task tree to expose tasks that you want to disable.

3. Select each task that you want to disable, and then click the Disable button.

4. After you have disabled all of the tasks that you do not want to appear in the role, select the parent task.

5. Right-click and then select Save Role, or click the Save button on the tool bar.

6. In Save Role, select an existing role and then click Select, or create a new role.

See Also:

- "Adding Users to a Role" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

3.1.4 Changing a Role's View of a Task View

By modifying roles, you can control users' task view. Changing the name and version for the role helps you and other users understand the difference between different roles. The changes that you make to the role, such as assigning new task names, apply only to that role. The system preserves the properties that define the default task view. You are not replacing the original view; you are creating an alternative view to be used in specific situations that your business requires.

Access JD Edwards EnterpriseOne Solution Explorer.

1. In a JD Edwards EnterpriseOne Solution Explorer task view, click the Menu Filtering button on the Toolbar.

2. Right-click any task in the task view, and then select View By Role from the menu.

3. In View by Role, select the role to which you want to change, and then click Select.

4. Double-click a task to make its relationship active or inactive, or right-click a task in the task view and select Override Name to change the task name.

5. Right-click any task and select Save Role.

6. Select the role, and then click Select.

4 Using the Task Launching Mode

The Task Launching Mode is the default mode for JD Edwards EnterpriseOne Solution Explorer. Use the Task launching mode to navigate to the windows applications either through the menu or through the Fast Path.

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  C  D  I  J  M  S  T

A

access

creating task views, 2.3.1

deleting task views, 2.3.3

apply roles to a task, 2.4.5

C

change

task views, 2.3.2

tasks, 2.4.6

create a new task view, 2.3.1 create a task, 2.4.3, 2.4.3

D

delete

task views, 2.3.3

tasks, 2.4.7

tasks from Task Master table, 2.4.7.2

delete a task from the Task Master table, 2.4.7.2 delete an instance of a task, 2.4.7.1

I

insert an existing task, 2.4.4

J

JD Edwards EnterpriseOne Solution Explorer task view configuration, 2.4.1

M

modify, task views, 2.3.2

S

setting up, tasks, 2.4.1

T

task views

changing, 2.3.2

creating, 2.3.1

tasks

changing, 2.4.6

creating, 2.4.3

deleting, 2.4.7

deleting from Task Master table, 2.4.7.2

inserting, 2.4.4

setting up, 2.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.