How to: Create a Field Security

Create a field security header

1. Open the window Field Security by selecting Departments - Compliance - Security - Field and Dataset Security - Field Security. The field securities per table can be managed in this window (insert, modify or delete).

2. Insert a new field security for a table by pressing Ctrl+N.
Note: Only the Security Officer is entitled to create a new field security.

3. Complete the following fields in the header.

  • No.: Automatic and / or manual, based on the number series settings.
  • Description: E.g. Field Security Table 27 Item.
  • Table ID: Select the ID of the table that you want to secure on field level. Blocked tables in the Table Categories cannot be used for field security. If you select a table that is not categorized you will receive a message.

Click Yes if you are sure that you want to setup the field security for this table.

4. Filter Field No. and Filter Value: Optionally, only a part of a table can be secured by use of a filter. Select the field to be filtered on in Filter Field No. and fill in the Filter Value.

  • For option fields, e.g. document type and type in table Purchase Line, you can retrieve the available options by entering 0|1|2|3|4|5|6|7|8|9. The software replaces this with the options from the list if you leave the field, e.g. Quote|Order|Invoice|Credit Memo|Blanket Order|Return Order|6|7|8|9 for document type in table Sales Line. Remove any invalid or not required option.
  • The type of field in the table is visible when selecting a field.

5. Data Owner: Select the Permission Set (formerly User Role) of the Data Owner of the table.

  • The Data Owner is entitled to manage the field security for the table.
  • The field security settings for the table are not applicable for the Data Owner.
  • Only the Security Officer is entitled to assign a Data Owner to a field security or to create a new field security.

5. Default Editable: Select the option whether all fields of the table, that are not setup in the field security lines, will be editable or non-editable:

  • Setting is only applicable for users with the linked roles.

7. Start Date: Enter the date from which the field security applies (required).
8. End Date: Enter the date until which the field security applies (optional).

The default checks, defined in Setup Field and Dataset Security are copied when inserting a new field security.

Modifying the checks in the header applies also modifies the checks in the linked permission sets (formerly user roles). Deviating checks in the underlying linked permission sets are marked in the field Deviating Trigger Checks.

In the sub window of the window Field Security, fields of the table can be selected. Per field the security can be defined for editability and visibility. Not linked fields have the Default Editable setting from the header and are visible.

Note: If you are using the visibility option in the field security settings, some modifications to the applicable forms / pages are necessary. Depending on your version and configuration, the option whether the field will be visible or invisible might be hidden.

1. Open window Field Security.
2. Add a line per field.
3. Complete the following fields per line:

  • Field No.: Select the field to be secured.
  • Editable: Select the option whether the field will be editable or non-editable.
  • Initial Field Entry Allowed: Select the option whether the field might be filled and once it is filled it cannot be modified. If this option is not selected, the field security blocks any modification of the field.
  • No. of Assigned Permission Sets: See below.
  • Deviating Trigger Checks: Marked if checks differs from checks selected in header.

4. Description: can be used for documentation purposes.
5. Some fields are hidden by default:

  • Only Page Control: can disable editability of a field on the page, while it is editable on database level, e.g. from a code unit or a report.
  • Visibility: Fields might be made invisible on a page (customization might be needed).
  • No. of Customized Windows: This is an information field that shows the number of forms on which the invisibility property for the field is programmed (customized).

After defining the security of a Field you assign the Permission Set(s) (formerly user roles) for which the security is applicable.

1. Open window Field Security.
2. Select the line of the secured Field by selecting Actions (Alt+F10), Line, Assigned Permission Sets (or short key Ctrl+F7).
3. Click on arrow down button in the field Permission Set-ID to select the Permission Set for which the security is applicable.

4. Complete (optional) the assigned Permission Set with the field:

  • Company: Add a company name to set company specific security. If it is empty the security is for all companies.
  • Starting Date: Used for starting the assignment of the Permission Set at a specified date.
  • Ending Date: Used for ending the assignment of the Permission Set at a specified date.

5. If applicable, assign more Permission Sets.

Note: After changes in the Field Security setting a user has to login again to retrieve the appropriate new settings.
Note: Multiple (in)active configurations of field security on the same table for a user account can cancel each other out. The software is designed to work with the combination of all permissions given.

  • 2-controlware/05fieldanddatasetsecurity/5create_field_security.txt
  • Last modified: 2020/09/22 12:08
  • by marcel