This chapter contains the following topics:
Object Management Workbench (OMW) is the primary component of the change management system for EnterpriseOne development. OMW automates many change management activities. OMW's automation relies on an administrator who carefully configures OMW roles and allowed actions, which makes configuring these areas one of the most important EnterpriseOne configuration tasks.
These sections show the allowed user actions that Oracle 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.For more information about OMW, see the JD Edwards EnterpriseOne Tools Object Management Workbench Guide
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
This section discusses how to:
Modify user roles.
Delete 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. |
Access the Object Management Setup form.
In Object Management Setup, click User Roles.
Select the user role you want to modify.
Double-click the first field that you want to change, and modify it.
Repeat step 3 to make all required modifications.
Click Find and verify that the modifications you made appear in the list.
Click OK.
Select Object Management Administration (GH9081) then Object Management Configuration (P98230)
Access the Object Management Setup form.
In Object Management Setup, click the User Roles button.
Click the cell to the left of the User Role that you want to delete.
Click Delete.
In the Confirm Delete query, click OK.
Repeat steps 2 through 4 to delete all desired user roles.
Click Find to verify that the user roles were deleted.
Click OK.
This section provides an overview of user defined codes for allowed user actions and discusses how to set up 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.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. |
Access the Object Management Setup form.
In Object Management Setup, click the Allowed Actions button.
Click Find to display previously defined user actions.
To create a blank row in which to add a definition, sort on the allowed user action to be worked on.
Complete one or more of the query by example (QBE) columns and click Find.
Scroll to a blank row at the bottom of the sorted list.
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.
Repeat this procedure until all allowed user actions are set up.
Click OK.