What you’ll learn

Explain the configuration and custom fields control purpose behind custom field cleanup

Configure custom field definitions, validation parameters, and module rollouts

Handle configuration settings overrides, options cleanups, and security controls

Provide audit-ready change logs and configuration histories

Lesson 1 of 3 Reading 12 min

Scan stale definitions

Custom Field Cleanup focuses on identifying stale field definitions, broken options lists, restoring setups, and executing force purges. In AWRA, custom fields and configuration parameters allow tenants to adapt database tables to unique business operations without breaking data structure.

The primary objective is database stability and change control. Configuration admins should test definitions and validation rules before wide deployment.

In practice, an admin scans the settings index, deactivates a stale field, and executes a force delete approval.

Field cleanup path

Scan

Analyze custom field usage logs and column storage.

Flag

Identify stale definitions or broken options lists.

Deactivate

Soft-delete configuration and archive values.

Purge

Trigger force delete approvals to clean database tables.

Configuration model

Custom field definitions modify active database schemas.
Input validation rules protect data value format and type.
Settings overrides require security controls and approvals.
Always verify template layouts before run-time value imports.

Lesson 2 of 3 Workshop 14 min

Audit deactivations histories

The operating routine is to scan stale definitions tables, verify deactivation logs, manage restorations, and run force purges. That sequence prevents data formatting errors and keeps parameters aligned with policies.

Before publishing configuration updates, check custom fields list, database usage rates, soft-delete logs, restore parameters, and deletion approvals. These safety gates protect data values, user inputs, and reporting stability.

An administrator can verify active parameters, clear settings caches, or run cleanups directly from the builder.

Cleanup decision guide

Signal	Check	Action
Field unused for 1 year	No database transactions	Soft-delete definition and archive data
Option list contains errors	Check list parameters	Deactivate broken options and cleanup
Restore requested	Review audit justifications	Restore soft-deleted custom column
Force delete requested	Requires database cleanup	Route to executive approval gate

Admin decisions

Restrict layout changes to certified system administrators.
Lock global defaults using security approval overrides.
Resolve values validation errors during template imports.
Ensure data cleanups occur on a regular cadence.

Lesson 3 of 3 Practice 14 min

Perform force deletions

Configuration updates and field overrides should leave proof. Useful evidence includes cleanup scans, deactivation logs, restore approvals, and force delete approvals, which is required for audit logs reviews and system restores.

Management should review configuration drift: stale custom fields, broken dropdown options, or unapproved overrides point to settings reviews needs.

In practice, closure means stale fields are deactivated, database columns are pruned, and cleanup logs are archived.

Field cleanup checklist

Scan report is complete

Deactivations are logged

Restorations are tested

Force delete is approved

Log files are archived

Oversight validation

Confirm that change logs record configuration updates.
Verify that database constraint tests are successful.
Validate that custom options match active guidelines.
Ensure configuration rollbacks are tested and ready.

| AWRA OpsHub

Custom Field Cleanup

What you’ll learn

Course content

Scan stale definitions

Audit deactivations histories

Perform force deletions

Finished the material?

More in this path

Workflow Builder Basics

Approval Workflows

Security & Data Protection

Need a quick answer while you read?

AwraIQ