Compliance Setup
Compliance Setup allows you to configure how compliance-tracked tables behave, including which approval rule applies and how approvals interact with field checks. This is part of the Configure Compliance phase.
Accessing Compliance Setup
- Open Advanced Cloud Security from the Tell Me search
- Click Compliance Setup in the Configure Compliance column
- The Compliance Table Configuration page opens
Understanding Compliance Setup
Compliance Setup shows tables that have been selected for compliance tracking (during the Build phase). For each table, you configure:
- Which approval rule governs changes
- How approvals relate to field checks
Note: Tables and fields are selected for compliance in the Build phase via Compliance Tables. The Compliance Table Configuration page configures how compliance works for those tables.
Compliance Table Configuration
Table-Level Settings
The page shows the following columns:
| Column | Description |
|---|---|
| Table No. | The table number (read-only) |
| Table Name | Name of the table (read-only) |
| Compliance Activated | Whether compliance is active for this table (set in Build phase, read-only here) |
| Compliance Approval Rule | The approval rule to apply when fields in this table are changed (lookup to Approval Rules) |
| Approval vs. Checks | Controls the order of approvals and field checks |
Approval vs. Checks Options
This setting controls when approval requests are triggered in relation to compliance field checks:
| Option | Behavior |
|---|---|
| Approvals after failed checks | Approval is requested only when a field check fails |
| Approvals after passed checks | Approval is requested only when field checks pass |
| Approvals after both | Approval is always requested regardless of check results |
Linking an Approval Rule
- Select a table in the list
- Click the Compliance Approval Rule column
- Use the lookup to select an approval rule (see Approval Rules)
- Choose the appropriate Approval vs. Checks setting
Configuring Compliance Fields
Opening Field Configuration
- Select a table in the Compliance Table Configuration
- Click the Fields action
- The compliance field list opens, showing only fields marked for compliance
Field-Level Settings
The field list shows:
| Column | Description |
|---|---|
| Field No. | The field number (read-only) |
| Field Name | Name of the field (read-only) |
| Show Mandatory Asterisk | Whether to display a mandatory indicator on this field |
| Field Checks | Count of compliance checks configured for this field (click to view/edit) |
Compliance Checks
Click the Field Checks count or use the Compliance Checks action to configure specific checks for a field. Compliance checks define the validation rules that are evaluated when a field value changes.
Common Fields to Track
Customer Table
| Field | Why Track |
|---|---|
| Credit Limit (LCY) | Financial control |
| Blocked | Operational impact |
| Payment Terms Code | Financial impact |
| Gen. Bus. Posting Group | Accounting impact |
Vendor Table
| Field | Why Track |
|---|---|
| Bank Account No. | Fraud prevention |
| IBAN | Fraud prevention |
| SWIFT Code | Fraud prevention |
| Payment Terms Code | Financial impact |
Employee Table
| Field | Why Track |
|---|---|
| Bank Account No. | Fraud prevention |
| Social Security No. | Privacy compliance |
| Birth Date | Privacy compliance |
Testing Compliance Setup
After configuration:
- Log in as a test user
- Try to modify a tracked field
- Verify the correct behavior based on your Approval vs. Checks setting
- Check that the approval request is created when expected
Test Scenarios
| Scenario | Expected Result |
|---|---|
| Change non-tracked field | Saves immediately, no compliance involvement |
| Change tracked field (Direct rule) | Change applied, compliance record logged |
| Change tracked field (Store For Approval rule) | Change held for approval |
Best Practices
Focus on Sensitive Fields
Don't track every field:
- Focus on financial data
- Focus on personally identifiable information (PII)
- Focus on fields with significant business impact
Consider User Experience
- Too many approval requirements frustrate users
- Balance security with productivity
- Get feedback from affected users
Document Your Configuration
Maintain documentation of:
- Why each field is tracked
- Which approval rule applies to each table
- Who typically approves what
Regular Review
Periodically review compliance configuration:
- Are all tracked fields still relevant?
- Are approval rules working effectively?
- Should new fields be added?