Files > SECURITY KEY

name

SECURITY KEY

number

19.1

location

^DIC(19.1,

description

This file holds the names of security keys that are used to lock options. To lock an option, the name of the key is entered in the Lock field of the Option File. To permit a user to unlock the option, the user's name is entered in the Holder field of this file. It is cross-referenced by name and holder.

applicationGroups

XU;XQ

Fields

#	Name	Location	Type	Details	Index	Description
.01	name(+)	0;1	FREE TEXT		B	Each entry in this File is the name of a key that defines some characteristic or capability for individual specified users. The capability might be access to some OPTION (file 19) which is permited with the authorization. Other functionalities (such as allowing scheduling overbook) might also be allowed only if the key is held. Keys are named with the standard package prefix formats; a 2-4 character package prefix for standard names or Z.
.02	descriptive name	0;2	FREE TEXT			This is a more descriptive name for the KEY than allowed in the namespaced name field.
.03	person lookup	0;3	SET OF CODES	l:LOOKUP		This field when set to 'lookup' will build a X-ref on the NEW PERSON file of all holders of the key. This will be under a X-ref of 'AK.'_ so that a package can lookup members of a group. There is a standard SECURITY KEY that will be sent out of 'PROVIDER' with the lookup flag set. Then a package can do a lookup of PROVIDER's with the following code: S DIC="^VA(200,",D="AK.PROVIDER",DIC(0)="AEQ" D IX^DIC
.04	keep at terminate	0;4	BOOLEAN	y:YES n:NO		If this field is set to YES (1) then this key will not be removed from a user in the New Person file when they are terminated. One example is the 'PROVIDER' key.
.05	send to j2ee	0;5	BOOLEAN	0:No 1:Yes		This field controls if this is a Security Key that should be sent to the J2EE application server for temporary role assignment. If this field is set to 'Yes' then this Security Key can be sent to the application server.
1	description	1;0	WORD-PROCESSING			This is a short description of the security key, indicating what the key locks out, and what class of users should be assigned the key.
3	subordinate key	3;0	MULTIPLE	19.13		Subordinate authorization are "given" when the "master" authorization is given. This allows easier and more efficient delegation of authorizations.
4	granting condition	4;E1,245	FREE TEXT			This is MUMPS code that set $T true if its OK for the person to be granted this key.
5	mutually exclusive keys	5;0	MULTIPLE	19.15