Parent object not properly locked when using button Back in AWI after opening inner object
search cancel

Parent object not properly locked when using button Back in AWI after opening inner object

book

Article ID: 244554

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Using AWI 12.3, it's been observed an edge case that could cause an Object not to be properly locked when a User was in Edition mode on it.

To get to this situation, we have this example where a Workflow contains a Jobs, if we double click on the JOBS, and then use the back Button in AWI to go back to the Workflow in edition mode, the object is not Locked as expected.

We first open the Workflow:

Then we double click on this jobs JOBS.UNIX.AFR which opens the object on Edit mode and then we click on the "Back" arrow within AWI:

As a result, we go back to the parent Workflow in Edit mode, BUT if we take a look at the folder, the "Opened By" column for this Workflow is empty which is not expected, it should be opened by this user to avoid another one modifying it at the same time.

Environment

Release : 12.3.x

Component : Automic Web Interface

Cause

Defect in AWI 12.3.x (and maybe also previous versions)

Resolution

The problem has been fixed in Automic Web Interface 21.0.0 and superior due to the fact that the button "Back" was removed from the Object panel when opening it.

Since the "Back" button of the Web Browser (see below) needs to be used, the problem does no longer exist.