MKS Implementer 2006 Administration Guide

Chapter 3: Implementer Administration
142
To work with name rules for a specific object code for all environments
1 From the Implementer Menu, type 44 and press ENTER to access Work with Object
Codes.
2 Select an object code with option 2=Change, and press ENTER.
3 Press F18=Name Rules. The Work with Object Name Rules panel displays. The
Environment field displays the default value *ALL, indicating specific object codes for all
environments.
4 Press F6=Add. The Add Object Name Rules window displays.
5 Complete the fields as described in “Add Object Name Rules Field Descriptions” on
page 140.
6 Press ENTER. The Object Name Rules panel displays.
Project-based Application Paths
Implementer uses application paths in the development cycle to define the flow of members/
objects between environments. Implementer also uses application paths to determine the
location of source and related objects for an object, for example, when compiling with a check
out or create request action of recompile.
The application path provides control by restricting access so members/objects cannot move
outside of the defined flow. It also allows defaulting the From environment and target
environment values when checking out and creating a promotion request.
You can define an application path at the environment level or project level. Each path can
have a standard and an emergency path that a member/object follows from the time it is
checked out to the time it is promoted back into production.
Functionally, environment paths and project paths are identical, but certain business
situations make it more practical to use a project path. For example, two active projects in
development typically use different environment paths. By using a project path instead of an
environment path, you can avoid performing excessive overrides when checking out and
promoting items associated with one project that are not associated with the other project.
Project paths are beneficial when your development model consists of multiple test
environments, particularly when the test environments are determined on a project-byproject
basis.
Key Considerations
In check out and create request a project path overrides an environment path. In other
words, if a project with a defined path is specified, the project path is followed;
otherwise, the environment path is followed. For details, see page 101.