Sync modification by ATTACH_SYNC: User not always documented
search cancel

Sync modification by ATTACH_SYNC: User not always documented

book

Article ID: 227479

calendar_today

Updated On:

Products

CA Automic One Automation

Issue/Introduction

When instruction ‘attach_sync’ is used to assign a Sync object to an execution dynamically
the field Modified by (SYNC ==> General ==> History) contains UNKNOWN.

A  SYNC Object (SYNC.NEW.1) is updated by a simple SCRI that runs a simple command line is executed.

=============================================================================

: attach_sync , "SYNC.NEW.1", "SET_AKTIV", "SET_PASSIV", "SET_PASSIV", "W"

=============================================================================

Check the 'Modified by' field of the SYNC Object, when the problem happens this filed will contain 'UNKNOWN'.

When the problem happens then the SQL Statements similar to this

=============================================================================

select oh_idnr,OH_CRUSERIDNR,OH_MODUSERIDNR,OH_CRDATE,OH_MODDATE, oh_name from oh where oh_name='SYNC.NEW.1' and oh_client=22;

=============================================================================

returns for OH_MODUSERIDNR the output

=============================================================================

1069186 1003001 1061109567 2021-03-22 10:46:16 2021-03-22 14:48:15 SYNC.NEW.1

=============================================================================

The IDR 1061109567 was returned systematically at each occurrence even on different system. There is no User object related to this IDNR.

 

Environment

Release : 12.3 Component : AUTOMATION ENGINE

Cause

This is a bug detected in Automation Engine 12.3.4 HF1 and 12.3.5.

 

Resolution 

A problem has been fixed, where "UNKNOWN" was shown in "Modified by" field of a Sync Object instead of a valid user.

Resolution

Resolution 

A problem has been fixed, where "UNKNOWN" was shown in "Modified by" field of a Sync Object instead of a valid user.

 

This bug will be fixed in the following versions/releases:

AE 12.3.8 -- available

AE 21.0.1 -- available