Client 0 system objects overwritten during Automic Automation upgrades
search cancel

Client 0 system objects overwritten during Automic Automation upgrades

book

Article ID: 439427

calendar_today

Updated On:

Products

Automic SaaS CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

After performing a system upgrade or applying a Hotfix (HF), custom configurations, keywords, or properties within specific system objects in Client 0 are missing or have reverted to default values. A common example is the UC_MONTH calendar losing its custom keywords.

Environment

Version: ALL

Cause

During the upgrade process, the Automation Engine updates its initial data and system objects. Specific objects in Client 0 are designated as system-owned and are overwritten by the DB Load utility to ensure they align with the new version's requirements. This behavior is by design to maintain system integrity and compatibility with new features.

Affected Objects While this list is not exhaustive, the following objects are known to be reset or overwritten during upgrades:

  • UC_MONTH (Calendar): Keywords and validity periods are reset to defaults.
  • UC_TRUSTEDCERTS (Static Variable): May be removed or replaced by a generic version to support new security protocols (e.g., SMTPS).
  • UC/UC (User): Authorizations and Privileges may be reinitialized, particularly in version 24.4.x.  (Note: UC/UC object is not overwritten, only the Privileges and Authorizations as a way of adding new entries between major version upgrades)

Resolution

To ensure custom configurations are preserved through the upgrade lifecycle, follow these best practices:

  1. Use Non-Zero Clients: Do not store business-critical customizations in Client 0 system objects. For calendars like UC_MONTH, copy the object into a non-zero client and apply your keywords there.
  2. Naming Conventions: If you require a "global" object in Client 0, create a new object with a unique name (e.g., UC_MONTH_CUSTOM) rather than modifying the default system object.
  3. Post-Upgrade Verification:
    • Compare customized objects in Client 0 against backups before starting the processes.
    • Manually restore specific objects if they were replaced by generic versions.