Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Details
Print Page as PDF
Sub-Field: 200.051

Package: Kernel

NEW PERSON(#200)-->200.051

Sub-Field: 200.051


Information

Parent File Name Number Package
NEW PERSON(#200) KEYS 200.051 Kernel

Details

Field # Name Loc Type Details
.01 KEY 0;1 POINTER TO SECURITY KEY FILE (#19.1) SECURITY KEY(#19.1)

  • INPUT TRANSFORM:  S DIC("S")="I DUZ(0)=""@""!$D(^VA(200,DUZ,52,Y,0))!$D(^XUSEC(""XUMGR"",DUZ))!$G(PSOKEY)" D ^DIC K DIC S DIC=$G(DIE),X=+Y K:Y<0 X S:$D(X) DINUM=X
  • LAST EDITED:  NOV 03, 2023
  • HELP-PROMPT:  Enter the Security Key for this user
  • DESCRIPTION:  
    This is a security key that this person holds.
  • SCREEN:  S DIC("S")="I DUZ(0)=""@""!$D(^VA(200,DUZ,52,Y,0))!$D(^XUSEC(""XUMGR"",DUZ))!$G(PSOKEY)"
  • EXPLANATION:  Delegated with PSDRPH key, holders of PSDRPH/XUMGR key or users with FileMan access (@) can assign Keys
  • AUDIT:  YES, ALWAYS
  • DELETE TEST:  1,0)= I $P($G(^DIC(19.1,DA,0)),U,4)="Y"
  • LAYGO TEST:  1,0)= S Y=DA(1) X:$D(^DIC(19.1,+X,4)) ^(4)
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  200.051^B
    1)= S ^VA(200,DA(1),51,"B",$E(X,1,30),DA)=""
    2)= K ^VA(200,DA(1),51,"B",$E(X,1,30),DA)
  • CROSS-REFERENCE:  200.051^AC^MUMPS
    1)= N % S %=$P($G(^DIC(19.1,DA,0)),U) S:%]"" ^XUSEC(%,DA(1))=""
    2)= N % S %=$P($G(^DIC(19.1,DA,0)),U) K:%]"" ^XUSEC(%,DA(1))
    3)= This sets the XUSEC X-ref.
    This is the X-ref that keeps the ^XUSEC(keyname,DUZ) global in place. This global is used the menu system and other to check if a new person holds a given key.
  • CROSS-REFERENCE:  200^AB
    1)= S ^VA(200,"AB",$E(X,1,30),DA(1),DA)=""
    2)= K ^VA(200,"AB",$E(X,1,30),DA(1),DA)
    3)= X-ref whole file by KEY.
  • CROSS-REFERENCE:  200^AK^MUMPS
    1)= G FE51S^XUA4A7
    2)= G FE51K^XUA4A7
    3)= Special lookup X-ref for Applications.
    Special X-ref to allow applications to do lookup on just holders of a special key.
  • CROSS-REFERENCE:  ^^TRIGGER^200.051^1
    1)= K DIV S DIV=X,D0=DA(1),DIV(0)=D0,D1=DA,DIV(1)=D1,X=DUZ,DIU=$P(^VA(200,D0,51,D1,0),U,2),$P(^(0),U,2)=X,DIH=200.051,DIG=1 D ^DICR:$O(^DD(DIH,DIG,1,0))>0
    2)= Q
    3)= Edited trigger
    CREATE VALUE)= S X=DUZ
    DELETE VALUE)= NO EFFECT
    FIELD)= GIVEN BY
  • CROSS-REFERENCE:  ^^TRIGGER^200.051^2
    1)= K DIV S DIV=X,D0=DA(1),DIV(0)=D0,D1=DA,DIV(1)=D1,X=DT,DIU=$P(^VA(200,D0,51,D1,0),U,3),$P(^(0),U,3)=X,DIH=200.051,DIG=2 D ^DICR:$O(^DD(DIH,DIG,1,0))>0
    2)= Q
    3)= Edited trigger
    CREATE VALUE)= TODAY
    DELETE VALUE)= NO EFFECT
    FIELD)= DATE GIVEN
  • FIELD INDEX:  AUSERKEY (#497) MUMPS IR SORTING ONLY WHOLE FILE (#200)
    Short Descr: Index to monitor the Allocation/De-allocation of the XUORES Security Key.
    Set Logic: I $$PROVIDER^XUSER(DA(1)) S ^VA(200,"AUSER",$P(^VA(200,DA(1),0),U),DA(1))=""
    Kill Logic: I '$$PROVIDER^XUSER(DA(1)) K ^VA(200,"AUSER",$P(^VA(200,DA(1),0),U),DA(1))
    Whole Kill: Q
    X(1): KEY (200.051,.01) (forwards)
  • RECORD INDEXES:  AXUHUIKEY (#174) (WHOLE FILE #200)
1 GIVEN BY 0;2 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  NOV 03, 2023
  • DESCRIPTION:  
    This is a pointer to the person that entered this security key into this persons file.
  • AUDIT:  YES, ALWAYS
    WRITE AUTHORITY: ^
  • NOTES:  TRIGGERED by the KEY field of the KEYS sub-field of the NEW PERSON File
2 DATE GIVEN 0;3 DATE

  • INPUT TRANSFORM:  S %DT="EX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  NOV 03, 2023
  • DESCRIPTION:  
    This is the date that the security key was given to the person. There is know history.
  • AUDIT:  YES, ALWAYS
    WRITE AUTHORITY: ^
  • NOTES:  TRIGGERED by the KEY field of the KEYS sub-field of the NEW PERSON File
3 REVIEW DATE 0;4 DATE

  • INPUT TRANSFORM:  S %DT="E" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  NOV 03, 2023
  • HELP-PROMPT:  The date after which this persons holding the key should be reviewed.
  • DESCRIPTION:  
    This is the date after which the persons need for this security key should be reviewed.
  • AUDIT:  YES, ALWAYS
Info |  Details