MKS Implementer 2006 Administration Guide

Capability Option Administrator
Override emergency paths Y Y N N
Override remove from obj Y Y N N
Override remove from src Y Y N N
Defaults for check out and create request
Check out from env Y Y Y N
Develop lib. (or Env. below) Y Y Y N
Develop env. (or Library above) Y Y Y N
Crt rqs target env (or Env Group below) Y Y Y Y
Crt rqs target env grp (or Env above) Y Y Y Y
Project reference Y Y Y Y
Remove obj in from library Y Y Y Y
Remove src in from library Y Y Y Y
Enable one step checkout Y Y Y Y
Enable one step promotion Y Y Y Y
Products / Customer Options
Common Questions
How much authority should be given to developers?
Developers should be able to check out, create a request, compile a request, and access the
Workbench. Usually, you do not allow developers to move a request or perform setup
functions.
If users are restricted through Implementer to specific environments, is it possible for them to access
libraries outside of the product?
Yes. To restrict a user from a specific library outside of Implementer, use standard OS/400
security by using the Edit Object Authority (EDTOBJAUT) command to specify the user’s
authority to the library.
Should a developer be allowed to change the default path?
Project
Leader
Developer QA
Maintain Products Y Y Y Y
Maintain Product Versions Y Y Y Y
Maintain Customers Y Y Y Y
Users
This depends on how strictly your company wants to control member/object location along a
predefined path during development.
79