Define Security Features
Security Features are the building blocks of Advanced Cloud Security. This guide explains how to create and configure security features.
What is a Security Feature?
A Security Feature is a named collection of security rules that can be assigned to users, security groups, or permission sets. Each feature can include:
- Field Controls - Hide or make fields read-only
- Action Controls - Hide page actions
- Data Access Rules - Filter which records users can see
Accessing Security Features
- Open Advanced Cloud Security from the Tell Me search
- Click Define Security Features in the Build phase column
- The Security Features list opens
Creating a New Security Feature
Basic Information
- Click New to create a new security feature
- Fill in the required fields:
| Field | Description | Example |
|---|---|---|
| Feature ID | Unique code (max 20 characters) | HIDE-COST |
| Name | Descriptive name | Hide Cost Information |
| Description | Detailed explanation | Hides all cost-related fields from non-purchasing users |
Tips for Feature IDs
- Use uppercase letters
- Use hyphens for readability
- Keep it short but meaningful
- Examples: SALES-EU, NO-POST, READ-ONLY-FIN
Adding Field Controls
Field controls allow you to hide fields, make them read-only, or disable them.
The Field Access Part
The Field Access part is embedded directly on the Security Features page, below the feature list. When you select a security feature, the Field Access part shows the field controls for that feature.
Adding Fields
To add a field control, create a new line in the Field Access part:
- Click in the Table Name column and use the assist edit (...) to select a table
- Click in the Field Name column and use the assist edit (...) to select a field from that table
- Click in the Page Name column and use the assist edit (...) to select the page where this field appears
- Set the security settings
Field Control Settings
For each field, you can set three independent properties:
| Setting | Options | Description |
|---|---|---|
| Visible | (blank) / Show / Hide | Whether the field appears on the page |
| Enable | (blank) / Enable / Disable | Whether the field is enabled |
| Editable | (blank) / Editable / Readonly | Whether the field can be modified |
A blank setting means no override is applied for that property.
Common Field Control Scenarios
| Scenario | Visible | Enable | Editable |
|---|---|---|---|
| Hide completely | Hide | (blank) | (blank) |
| Show but read-only | Show | (blank) | Readonly |
| Disable field | (blank) | Disable | (blank) |
Adding Page Controls
Page controls allow you to control visibility, enable, and editable settings for specific page controls (form fields identified by control name rather than table field).
The Page Controls Part
The Page Controls part is embedded on the Security Features page. When you select a security feature, it shows the page control entries for that feature.
Adding Page Controls
- Click in the Page Name column and use the assist edit (...) to select a page
- Click in the Control Name column and use the assist edit (...) to select a control from that page
- Set the security settings (Visible, Enable, Editable - same options as field controls)
Adding Action Controls
Action controls allow you to show or disable page actions (buttons, menu items).
The Action Access Part
The Action Access part is embedded on the Security Features page. When you select a security feature, it shows the action controls for that feature.
Adding Actions
To add an action control, create a new line in the Action Access part:
- Click in the Page Name column and use the assist edit (...) to select a page
- Click in the Action Name column and use the assist edit (...) to select an action from that page
- Set the Setting field
Action Control Settings
| Setting | Description |
|---|---|
| Show | Action appears normally (default) |
| Disable | Action is hidden from the user |
Types of Actions You Can Control
- Standard actions (Post, Release, etc.)
- Report actions
- Navigate actions
- Process actions
- Custom actions from extensions
Adding Data Access Rules
Data access rules filter which records a user can see.
The Data Access Filters Part
The Data Access Filters part is embedded on the Security Features page. When you select a security feature, it shows the data access filters for that feature.
Creating a Data Filter
To add a data filter, create a new line in the Data Access Filters part:
- Click in the Table Name column and use the assist edit (...) to select a table
- Click in the Field Name column and use the assist edit (...) to select a field from that table
- Enter the filter expression in the Filter Value column (use the lookup to select a filter code)
Filter Expression Examples
| Expression | Result | |
|---|---|---|
EUROPE |
Equals "EUROPE" | |
| `EUROPE | USA` | Equals "EUROPE" or "USA" |
<>BLOCKED |
Not equal to "BLOCKED" | |
1000..2000 |
Range from 1000 to 2000 | |
UF_50 |
Dynamic filter using filter code (user's ID) | |
UF_23 |
Dynamic filter using filter code (user's location) |
Dynamic Filters (Filter Codes)
Use filter codes for placeholders that are resolved at runtime. Filter codes are defined in the Filter Codes page and their values are configured per user in the User Security Filters page:
| Filter Code | Source |
|---|---|
UF_50 |
User ID Filter |
UF_2 |
User Name |
UF_23 |
Location Code |
UF_21 |
Salesperson/Purchaser Code |
| Custom codes | Event-supplied filter values |
See Filter Codes for the full list of built-in filter codes. See User Filters for configuring per-user filter values.
Security Feature Examples
Example 1: Hide Cost Information
Feature ID: HIDE-COST
Field Controls:
- Item Card: Unit Cost (Visible = Hide)
- Item Card: Last Direct Cost (Visible = Hide)
- Item List: Unit Cost (Visible = Hide)
- Purchase Line: Direct Unit Cost (Visible = Hide)
Example 2: Sales Region Filter
Feature ID: SALES-EU
Data Access:
| - Customer table: Country/Region Code = `DE | FR | IT | ES | NL | BE` |
|---|
Example 3: Read-Only Finance
Feature ID: READ-ONLY-GL
Field Controls:
- G/L Entry List: All fields (Editable = Readonly)
- General Journal: All fields (Editable = Readonly)
Action Controls:
- General Journal: Post (Setting = Disable)
- General Journal: Post and Print (Setting = Disable)
Managing Security Features
Deleting a Feature
- Select the feature to delete
- Click Delete
- Confirm deletion
Warning: Deleting a feature removes it from all assignments, including field controls, page controls, action controls, and data access filters.
Best Practices
Keep Features Focused
Create separate features for:
- Different functional areas
- Different security levels
- Different data regions
Use Meaningful Names
Good names make administration easier:
- ✓ "Hide Vendor Banking Information"
- ✓ "Sales Team - Western Region"
- ✗ "Feature1"
- ✗ "Security"
Document Your Features
Use the Description field to explain:
- Why the feature exists
- Who should have it assigned
- Any special considerations
Test Thoroughly
Before deploying:
- Create the extension
- Assign to a test user
- Verify all controls work
- Check for unintended side effects