AE v24 problems

[Michael A. Lowry]

I thought I'd create a dedicated thread for discussion of the AE v24 problems we've identified. I hope this will help others who are considering (or are in the process of) upgrading to v24.

Description	Jira ID	KB article	Fix v.
Problems with Package.UTF8.DB.Migration v1.0.2 (E.g., mistakes in finalize SQL statements)	PCK_UTF8_DB-1	KB367040	?
AWI rename dialog box imposes old v21 length validation on Title field (255 instead of 512)	AE-36447	KB281316	24.1
Incorrect field length validation during XML import for Title, Archive key 1, and Archive key 2 fields	AE-36576	KB367085	24.1
Problems with IntAccount field (Inconsistent length validation, import via REST API crashes WPs)	AE-36575	KB367043	24.2
Shift-F10 keyboard shortcut for displaying contextual menu does not work.	AE-36660		?
Documentation of AE object attributes needs to be updated.	DOCU-5771		24.1

Most of these problems are directly or indirectly related to UTF-8 support. I'll add Jira IDs & links to KB articles when they become available.

Update 2024.09.19 913 CEST: Added links to three KB articles.

[Keld Mollnitz]

Hi @Michael A. Lowry,

thanks for sharing. I think you are doing an amazing job and sharing your findings with the community. This is something that should come from Broadcom itself, but unfortunately this is not the case.

/Keld.

[Michael A. Lowry]

All of the AE problems I reported have been accepted as bugs. The problem with the DB migration action pack is still under investigation.

The bugs are not listed in the known issues section of the AE v24.0.0 release notes, and so far there do not appear to be any KB articles. 

[Donato Faggella]

Hi @Michael A. Lowry. Thanks for sharing. 

------------------------------
Donato Faggella
DevOps Engineer III
Swisscom (Suisse) SA
------------------------------

[Michael A. Lowry]

The problem with the UTF-8 migration tool has been accepted as a bug. It will be fixed in a forthcoming update to the package.

[Michael A. Lowry]

Broadcom has begun to publish KB articles on the problems identified in v24.0.0. Several of these bugs are due to be fixed in Automic Automation v24.1.0, due in late June or early July 2024.

[Michael A. Lowry]

I have a few updates.

Fixed in v24.1: AE-36447, AE-36576, DOCU-5771

Fixed in v24.2: AE-36575

Not fixed yet: AE-36660

Unknown: PCK_UTF8_DB-1 (See the dedicated discussion thread.)

[Michael A. Lowry]

I did some tests and found that AE-36575 is not completely fixed in v24.2.

Bug	Several fields are cut off when using Unicode characters when saved over Application Interface and AWI. A problem has been solved where several fields are cut off when using Unicode characters when saved over Application Interface and AWI. For example Archive Key 1/2, Int. Account and Source/Target paths were affected.	AE-36575
KB article	Mismatch between AWI field validation and AE DB storage for IntAccount field. This is due to 2 defects in the Automation Engine  Length check in JAVA Api checks for code units and not bytes. because of this, there is no error message returned on "save" - but the value truncated afterward by UCUDB32 REST API also allows the storage of more data than UCUDB32 can read.	KB367043

In my tests, it was possible to insert only 8 four-byte UTF-8 characters in the IntAccount field.

Allowed: 😀😀😀😀😀😀😀😀

Not allowed: 😀😀😀😀😀😀😀😀a

If one attempts to enter one more character, the AWI displays the error message: The maximum length is 16 characters.

[Leon Carroll]

On V24.2 the workflow seems to be fully zoomed out when opening up a more complex workflow in the process monitor.  I'm using the bundled Jetty version of the AWI

[Leon Carroll]

I'm finding that Usergroups are not displaying the full list of users in AWI 24.2 but exporting via JSON has the members listed.  The users display the usergroups assigned ok.  Other clients with less users seem to be ok but not sure if that is related.

Sometimes the folders collapse or are not displayed fully in the tree after following a link. I've had reports of an error displayed on filtering the process manager to the current user, though i haven't been able to reproduce that.

Note that the RA Core supports JDK17 but all the RA Solutions support JDK11.  The Activemq library does not load if the RA_JMS is running JDK17

[Leon Carroll]

I have a ticket open for the usergroup administration bug with Tricise, I wondered if anyone else had experienced this as this is blocking me from releasing 24.2 to our next environment up the chain. 

I can reproduce this in all clients even in 0 with UC/UC

Create a user, Create a usergroup.  Add the user to the group.  The user is not displayed in the list but on save it can be retrieved in the JSON export. The usergroup is dispayed on the user's groups.   Open the usergroup, make a change to the usergroup permissions and save and the user is removed again.    So I can't see who is a member of a usergroup, and I can't change the permissions of a usergroup without losing most of the members of the usergroup.

LDAP sync works and correctly adds/removes users so I think it is just with the AWI view of it.

 Update 28.10.2024

This is where there are over 200 users or so in client. Only the first few names sorted alphabetically will be shown on a usergroup.

Update 15.11.2024

Sorting the users from Z-A will show the users only with the higher value letters.

[Leon Carroll]

This zoom issue is now tracked as issue DE154931 

[Leon Carroll]

I've found that Objects marked as a favourite in an earlier version of Automic, when exported via REST or JSON in V24.2 give the path of the user object instead of the object path. 

To clear this, the object needs to be exported as xml, deleted or renamed, and imported again as a new object.  Alternatively, removing the favourite also clears this. It can then be re-favourited without issue in v24

Broadcom ticket 35883441

-

To filter objects in the Process Monitor by username, requires that the user has access to the Administration tab permission.

-

The RA Rest solution Jar in 24.2 HF1 has not been signed and the DB Load utility gives a warning on loading.

- *Update 15.11.2024 *

Rename object causes a refresh on each keypress of the object name field, losing focus on the that field.  You have to click back into the object name field on each keypress.

[Michael A. Lowry]

Broadcom has updated KB367043 with a note acknowledging that the problem is only partially fixed in v24.2.

This is partially fixed in v24.2.0 (available): It is no longer possible to store invalid information in the database.

A second fix is underway as part of a general improvement: The field IntAccount will be extended to 200 characters (up from 16). This improvement will also fix the live field validation in AWI. In other words, before saving it will show a warning message if the content is not accepted.