This chapter contains the following topics:
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.
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.
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.
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.
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.
This table lists the allowed actions you can perform 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 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.
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.
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)
JD Edwards objects include the following non-Object Librarian objects:
Data dictionary items
User defined code items