Group locking with v16.1

[erobinson]

Has there been any changes to how this functionality works in v16.1? Before our upgrade to the latest Sparx version, I used to create a security group, assigned users to this group, and locked packages with this group lock. This worked without any issues.

After the upgrade we've had complaints that the group lock doesn't work. Even though users are assigned to the security group, the package still shows locked for them (i.e. have the red exclamation mark next to the package.

[Geert Bellekens]

Does this happen only to users with a longer name?

In that case you'll have to update the database schema to the latest version.

In a previous version the userID field of t_secuser was only 32 characters long. Since EA is now using the email address as login (actually it a userID but it looks like an email address) those 32 characters are no longer enough and get truncated.
So you might have user [email protected] that is part of your group, but that gets truncated to "firstName.VerylongLastName@thefullcomp" (or whatever 32 characters are)

Geert