Audit of "Alert [em_alert]" is not capturing all field data updates. DescriptionBefore Madrid, the 'em_alert' table did not have any field checked true for audit data, yet the table was set with "Audit" as true. In most cases, this would allow all fields on the table to be audited. In Madrid and afterwards, the table is still set with auditing enabled, but only work note changes are captured on the 'sys_audit' table. Release or EnvironmentMadrid onward. CauseThe audit for 'em_alert' table is limited to only a single field (i.e work_notes) in order to limit the amount of 'sys_audit' records created. Given the nature of this table, auditing every field as it was set in London and before has caused performance degradation to both the updating/creation of 'em_alert' records and instance wide. If still wants to enable audit for fields other than “work_notes”, then we need to enable audit explicitly for required fields.ResolutionEnable field-level audit to capture the audit data required for your organization. Below is an example of how to do this (using the "State" field as an example): Go to "sys_dictionary.LIST" from application navigator 2. Filter for table "em_alert" and column name "state" 3. Open the record and choose "Advanced View" under "Related Links" 4. Enter "audit=true,edge_encryption_enabled=true" in field "Attributes" and save it. Repeat the process above for whatever fields your company deems as essential for auditing on the 'em_alert' table. CAUTION: Please do NOT apply this to every field on the 'em_alert' table for the reasons outlined above!