AWI: SHIFT+Click in Schedule selects all from the top

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

In the Automic Web Interface (AWI), using SHIFT + Click to select a range of objects within a Schedule causes all objects from the very beginning of the list to be selected, rather than just the expected range between the initial selection and the second click.

This issue is most visible when opening a Schedule via "Search for Use." The object is highlighted by default, but when a user holds SHIFT and clicks further down the list, the system ignores the highlighted object's position and selects everything from the top down to the clicked object.

This unexpected behavior can lead to accidental mass-deletion or modification of scheduled objects if the excessive selection is not noticed.

Steps to Reproduce

1. Create a Schedule object.

2. Add 10 objects to the schedule, ensuring one of them is distinct.

3. Place the distinct object in the middle of the schedule (e.g., in the 5th position).

4. Save the schedule.

5. Search for the distinct object, right-click it, and select Search for use.

6. Open the newly created Schedule object from the search results.

7. By default, the distinct object (in the 5th position) is highlighted in yellow.

8. Hold SHIFT and click the 10th object in the list.

• Expected Behavior: Only the 5th through the 10th objects are selected.

• Actual Behavior: All objects from the 1st to the 10th are highlighted and selected.

Environment

AWI 24.4.x (Confirmed in 24.4.1 HF2, 24.4.2, and 24.4.3)

Cause

This is a defect in the Automic Web Interface (AWI). When a Schedule is opened from a results list, the UI visually highlights the object, but the internal selection anchor does not correctly match the UI information.

Resolution

Workaround To ensure the correct range is selected, click anywhere outside the schedule list or explicitly click the starting object once to firmly establish the selection anchor before using SHIFT + Click.

Resolution This issue has been acknowledged as a bug and is fixed in the following release:

• Automation Engine / Automic Web Interface 24.4.5 (Note: This issue does not occur in version 26.0 and higher).