Understanding Tokens

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

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

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

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

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

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