AWRA Help Center

This adds to Custom Fields. The governance screen is Settings → Custom Fields → Usage & Changes.

New Field Types

• Person, Department, Warehouse and Bin location — pick a real record instead of typing a name that drifts.
• Web link, Email and Phone — checked as the right kind of value.
• Barcode / QR — a code value of up to 120 printable characters.

Draft First

A new field can be saved as a draft. Drafts are hidden from forms, the API and the mobile app until you publish them, so you can set options and rules without a half-finished field appearing on everyone’s screen.

Approval For Breaking Changes

Switch on change approval on the Usage & Changes page and these changes wait for a second person: changing a field’s type, making it required, making it unique, retiring options that are in use, and archiving a field that holds values. It is off until you switch it on.

Before deciding, the approver sees an impact preview: how many values exist, how many records would be missing a now-required value, and which reports, workflows and app screens use the field. A rejection needs a note.

Sensitive Values

• Mark a field sensitive and every time someone views its value is recorded in the audit log. Revealing it needs the view sensitive custom fields permission.
• In the audit log, the value is masked, or shows only its last four characters if you choose. In Trash it is masked for anyone without the permission.
• Encryption at rest can be switched on per sensitive field. An encrypted field still enforces uniqueness, but filters, search and reports return no values for it, so encrypt only fields nobody needs to report on.

Validation

• Pattern library — KRA PIN, Kenyan national ID, Kenyan mobile number, Kenyan vehicle registration, five-digit postal code, upper-case code, IBAN and SWIFT/BIC.
• Cross-field rules — a value must be at least, more than, at most or less than another field, match it or differ from it, or be required when another field is filled in or empty.
• Date windows — not before or not after today, a number of days, weeks, months or years from today, or a fixed date.

Bulk Edits You Can Undo

Set a field’s value on up to 1,000 records at once. Each bulk edit is kept as a batch on the Usage & Changes page and can be rolled back. Rows the edit refused are listed with the reason and can be downloaded as a CSV to fix and retry. A rollback skips any value that has been changed since, or whose field has been archived, so it never overwrites later work.

Fields Used In Reports

A field’s edit screen lists the saved reports that use it, including reports nobody has opened yet, and archiving a field in use tells you how many reports it affects. A report that still uses an archived or removed field opens with a message naming the field, instead of an error, so you know which column to take out.

Importing Custom Field Values

Import files for vendors, customers, assets, asset custodians, warehouses, locations and the chart of accounts accept custom field columns, so a migration brings your extra data with it. See Importing Your Data.

For integrators, the custom field metadata API returns an ETag, so a client can check for changes cheaply.