Error: Objects reactivating automatically after direct SQL update in Automic Automation Engine

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

This article explains why objects may appear to revert to an active state after being deactivated via direct SQL updates to the database. It provides the recommended methods for auditable object management.

Symptoms

• Objects deactivated using SQL return to an active state.
• Changes to the inactive flag do not persist after an engine restart or object modification in the Automic Web Interface (AWI).
• No audit trail exists for the deactivation in the Revision Report.

Environment

• Automic Workload Automation
• Automation Engine

Cause

Bypassing the Automation Engine (AE) with direct SQL updates to the AE table only modifies a single flag. The AE manages objects as full definitions; when an object is saved or processed, the engine rewrites the entire definition based on its internal state. A direct SQL update does not synchronize with the stored object definition, leading to the engine reverting the flag to its last known valid state during subsequent operations.

Resolution

Do not use SQL commands to modify object attributes. Use one of the following supported methods to ensure data consistency and auditability:

1. Automic Web Interface (AWI): Manually toggle the Active checkbox in the object's General settings. This ensures the full object definition is rewritten and synchronized.
2. REST API Bulk Updates: For mass deactivations, use the REST API PATCH endpoint. Updates through the API are processed by the engine and correctly synchronized. 
3. Enable Object Auditing: To track changes for compliance (e.g., SOX), enable auditing in the system settings:

• • Set the OBJECT_AUDIT key in the UC_CLIENT_SETTINGS variable to Y for the specific client.
  • Use the UCYBDBRR utility to generate revision reports.