Previous  Next          Contents  Index  Navigation  Glossary  Library

Activating Flexfield Value Security

There are two levels where you must activate Flexfield Value Security, the value set level and the individual segment or parameter level. You make Flexfield Value Security available for your value set by checking Security Available. When you make security available for a value set, all segments and report parameters that use that value set can use security. You then enable security for a particular segment or parameter.

Security Available

With security available, you can create flexfield security rules, and you allow your rules to take effect for any segment or parameter that uses this value set and has security enabled. Otherwise, you disable all security rules for this value set.

You define security rules for this value set using the Define Security Rules window. Any security rules you define for this value set affect every segment (in any flexfield) that uses this value set, if the segment has security enabled.

Using the Flexfield Value Security feature may negatively affect your application performance. If you have many security rules or a large value set with many secure values, you may notice that a list of values on a segment appears slower than it would if you do not use Flexfield Value Security. Users with responsibilities where security is not enabled should not notice any loss in performance.

If you are using a validation table with special arguments such as :$FLEX$.Value_Set_Name for your value set, you should specify No in this field, since any security rules you have for your value set would ignore the values of these special arguments, and your rules could have effects other than what you intend.

You then enable security for a particular segment or parameter by checking Enable Security for that segment or parameter. Once you enable security on a segment, you must freeze and recompile the flexfield definition for that flexfield structure. Flexfield Value Security activates for that segment after you freeze and recompile your flexfield definition using the Key Flexfield Segments window or Descriptive Flexfield Segments window.


Key Flexfield Segments

Descriptive Flexfield Segments

Value Set Windows

Once you define your rule, you must assign your rule to a responsibility before the rule can be enforced. You assign your rule to a responsibility using the Assign Security Rules window. You may define rules for a segment that does not have security enabled, but your rule has no effect until you enable security for that segment and assign your rule to a responsibility.

After you define or make changes to your security rules, you and your users must either change responsibilities or exit from your application and sign on again in order for your changes to take effect.

See Also

Overview of Flexfield Value Security

Segment Values Window

Assign Security Rules

Effects of Flexfield Value Security

Understanding Flexfield Value Security

Defining Security Rules

Defining Security Rule Elements

Assigning Security Rules

         Previous  Next          Contents  Index  Navigation  Glossary  Library