Assigning Actor Context Values

Use this procedure to assign actor context values using secadm. Actor context values are used in both application data and security processing, such as by affecting which data an actor (user) may view. Therefore, the values specified in this procedure will impact both.

If you need to add numerous actor context records, consider using secadm in script mode. For example, a script would be useful if you want to add an HROrganization context value for a large number of actors.

Note: 

When you use secadm to add actor context values, if the key field for which you want to assign context values has not been designated as a context property, the context property will be created. However, the isPervasive and userModifiable fields are set to false for the context property. If you need to modify those fields, use secadm actor ctxproperty.

Be sure to refer to the administration guide for your application to determine the specific actor context settings for your installed product(s).

  1. At a Landmark command prompt, type

    secadm actor context add actor dataarea KeyField Value

    where

    Option Description
    add Add the specified key field value (context value) to the specified actor.
    actor The actor that this assignment applies to.
    dataarea The data area that this assignment applies to.
    KeyField

    The key field you will assign context values to. The key field name is case-sensitive. The key field must be a valid key field in the data area.

    If the key field has not been already specified as a context property, running secadm actor context add will add it to the ContextProperty table. When a key field is added in this way to the ContextProperty table, the isPervasive and userModifiable fields are set to false for the context property.
    Value The value for the specified key field. The value is case-sensitive.
  2. If you are using any other Landmark application, stop and restart the application to implement the changes.

    Any application that has a full JVM (which includes the security classes) behind it must be relaunched to pick up security class changes.