02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 3: <strong>Implementer</strong> <strong>Administration</strong><br />

76<br />

Field Description<br />

Create User Profile Field Descriptions: Panel 2<br />

Defaults for check out and create request<br />

The following fields define the check out and promotion defaults for the user. The Chg field allows you<br />

to define whether the user can override the default value in the corresponding function. For example,<br />

specify a default target environment for promotion and specify Y in the Chg field allows the user to<br />

change the target environment when creating a request.<br />

NOTE When using a standard or emergency path to identify the check out or<br />

promotion location, the path values have precedence. The path value *USRPRF<br />

defaults the development environment or library from the user profile. This<br />

provides user-specific development locations, allowing you to control the default<br />

promotion locations.<br />

Check out from env Specify the default environment this user checks out from (usually a<br />

production environment).<br />

Development library Specify the default development library this user checks out to and<br />

promotes from. The library must not be defined to an <strong>Implementer</strong><br />

environment. Development library and development environment are<br />

mutually exclusive (personal development libraries are used when<br />

environments are not). <strong>MKS</strong> suggests using environments in place of<br />

personal libraries.<br />

Development env Specify the default development environment this user checks out to and<br />

promotes from. The development library and development environment<br />

are mutually exclusive.<br />

Crt rqs target env Specify the default primary environment this user promotes to (usually<br />

production or QA environment.) Mutually exclusive of Crt rqs tgt env grp<br />

field.<br />

Crt rqs tgt env grp Specify the existing default target environment group when this user<br />

creates a promotion request. Mutually exclusive of Crt rqs target env field.<br />

Project reference Specify the name of the default project when checking out or creating a<br />

promotion request. For example, when a developer is assigned to a<br />

general project or a single project for a long period, the developer does<br />

not have to repeatedly specify the project value.<br />

If the project has a defined application path, that path is the default when<br />

this user performs check out and create request. For details, see “Projectbased<br />

Application Paths” on page 142.<br />

Remove obj in from<br />

library<br />

Specify whether to automatically delete or retain objects in the from library<br />

after successful promotion.<br />

Y: Deletes objects after promotion. This is the default value.<br />

N: Retains objects after promotion. Authority to override this default<br />

when creating a request is defined in the User Controls fields on the<br />

previous panel.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!