Advanced Cloud Security Documentation
Index

Compliance Tables

The Compliance Tables feature allows you to select which database tables should be tracked by the Compliance module. This is part of the Build phase and is required before configuring compliance rules.

Prerequisites

Before using Compliance Tables:

  • ACS must be installed and registered
  • You need the Security + Compliance license tier
  • The Compliance module must be enabled

What are Compliance Tables?

Compliance Tables define which Business Central tables will have:

  • Field change tracking enabled
  • Approval workflow capabilities
  • Audit logging for sensitive changes

Accessing Compliance Tables

  1. Open Advanced Cloud Security from the Tell Me search
  2. Click Compliance Tables in the Build phase column
  3. The Compliance Table Selection page opens

Selecting Tables for Compliance

Adding a Table

  1. Click New to add a row
  2. In the Table No. field, use the lookup to select a table
  3. Configure the page associations

Page Associations

For compliance to work, ACS needs to know which pages display the table data:

Field Description
Table No. The table to track
Table Name Auto-filled table name
List Page 1-4 List pages showing this table
Card Page 1-4 Card pages for this table
List Page AddAfter Field to insert compliance indicator after (list)
Card Page AddAfter Field to insert compliance indicator after (card)

Why Multiple Pages?

Business Central often has multiple pages for the same table:

Table Possible Pages
Customer Customer List, Customer Card, Mini Customer List, etc.
Vendor Vendor List, Vendor Card, Vendor Bank Account, etc.
Item Item List, Item Card, Item Ledger Entries, etc.

Configure all pages where users might edit compliance-tracked fields.

AddAfter Fields

The "AddAfter" fields specify where ACS should insert compliance status indicators on pages:

  1. Open the page in Business Central
  2. Note a field name that appears before where you want the indicator
  3. Enter that field name in the AddAfter field

Commonly Tracked Tables

Here are tables commonly selected for compliance tracking:

Table Use Case
Customer Credit limits, bank accounts, tax IDs
Vendor Bank accounts, payment terms
Employee Personal information, banking details
Item Critical item data, costs
Bank Account All banking information
User Setup Approval limits, permissions

Table Selection Best Practices

Select Only Necessary Tables

  • More tables = more tracking overhead
  • Focus on tables with genuinely sensitive data
  • Consider regulatory requirements

For each table:

  1. List all pages that display/edit the data
  2. Add each relevant page to the configuration
  3. Test that compliance indicators appear correctly

Plan Your AddAfter Locations

The compliance indicator should be:

  • Visible without scrolling
  • Near related important fields
  • Consistently placed across pages

Compliance Activation

After selecting tables, you must activate compliance:

  1. Go to the Compliance Activated column
  2. Check the box for tables ready for compliance
  3. Regenerate the extension

Tables with activation = No are configured but not actively tracking.

Workflow After Table Selection

After selecting compliance tables:

Select Tables
      ↓
Configure Page Associations
      ↓
Activate Compliance for Tables
      ↓
CREATE EXTENSION ← Required!
      ↓
Configure Compliance Rules (Phase 2)

Removing Tables from Compliance

To stop tracking a table:

  1. Uncheck Compliance Activated
  2. Regenerate the extension

Or to remove completely:

  1. Delete the table row
  2. Regenerate the extension

Note: Existing compliance history is retained.

Troubleshooting Table Selection

Table Not in List

If you can't find a table:

  • Ensure you have symbols refreshed
  • Check if the table exists in your version
  • Some system tables may not be available

Compliance Indicator Not Showing

If the indicator doesn't appear on a page:

  1. Verify the page is listed in the configuration
  2. Check the AddAfter field is correct
  3. Ensure the extension was regenerated
  4. Verify compliance is activated for the table

Page Not Found

If a page number shows an error:

  • Verify the page exists
  • Check that you have permissions to the page
  • Ensure the page is a list or card type

Extension Generation

Remember: You must regenerate the extension after:

  • Adding new compliance tables
  • Removing compliance tables
  • Changing page associations
  • Changing AddAfter fields
  • Activating or deactivating compliance

Without regenerating, changes will not take effect.