Messages

1

Bugs and Issues / Re: No spelling option for Polish language, please add :)

« on: October 10, 2017, 12:27:04 am »

Back from my vacations.

One "trick" that you might be able to use is to replace one of the existing languages.  Once upon a time, we needed to Test that our localisation was working correctly, but we mainly spoke English.  So I replaced the Estonian settings (sorry Estonia) with "Testonian" (pun intended) - a modified form of English that would ensure that any localised caption could be highlighted, but still be legible by the Developers and Testers.

Paolo, thanks - I know that one though. This does not work very well however,in EA 13.5 at least. Sometimes correct words are underlined in red and there is no way to make them not be. All in all it is a kind of solution but seems very buggy at least for Polish language and is not appropriate for production use.

Unfortunately, we have provided all the languages available for the dictionary software already.

Simon, thanks for the reply.
If this is a matter of 'providing' a language for the internal dictionary in EA - this is easily achievable. The only thing we need is the EA dictionary format specification (or better, but not necessary - a tool that implements this interface for reading and/or writing). If the format specification is available, the Polish community will provide ready-to-use dictionary files to Sparx.

Włodek

2

Bugs and Issues / No spelling option for Polish language, please add :)

« on: September 29, 2017, 08:39:53 pm »

This issue had been reported many years ago (by another EA user, Daniel Bachan) and is still a problem today. It prevents Polish-speaking users from using EA to its full potential, especially when working with templates.
There is a quite large user base of EA in Poland and many companies offer training for various aspects of using EA. Certainly there is no problem with the data for the dictionary - polish spelling dictionaries are available for many applications and the polish EA community could easily provide a comprehensive dictionary to Sparx.
Given there is a number of languages supported already adding another language should be easy.
Best Regards,
Włodek

3

Bugs and Issues / Re: Locking a root node without child packages in User/Group policy

« on: September 14, 2017, 01:48:12 am »

Well, in User/Group policy and EA 13.5 this is accessed by Package Control | Lock Package.
When a top (not the root at the moment) package has child elements this happens when I try to lock:

• select Full lock only - nothing happens
• select Full lock and Process Child Packages only - nothing happens
• select Full lock and Process Child Packages+Lock Diagram - the package and all child diagrams are locked
• select Full lock and Process Child Packages+Lock Diagram+Lock Elements - the package and all child elements are locked

The same is for User lock and Group lock, and the same if the Package is empty. I tried other combinations too.

The missing feature for me in the User/Group policy is the ability to lock a sole package without any children (as is possible in the policy you call RULtE). This is in order to prevent someone from adding child packages and/or other artifacts directly as children.

Anyway, big thanks for clarifications. I think I managed to achieve what I wanted, it was just quite unhandy to setup. I suppose the word 'sparxish' explains a lot .

4

Bugs and Issues / Re: Locking a root node without child packages in User/Group policy

« on: September 13, 2017, 09:25:40 pm »

With User/Group policy I am unable to lock a sole package without any child elements/packages. I was mistaken in my 1st sentence, when including children you can actually do that. But in order to achieve what I want I'll need to go Top-Down the model tree and rewrite all that was done before.
Are you able to lock a package without any children in User/Group policy? In RULtE policy you can do that.

5

Bugs and Issues / Re: Locking a root node without child packages in User/Group policy

« on: September 13, 2017, 07:59:58 pm »

In User/Group policy I cannot lock the root node, regardless of the options I use in the locking window.

I was hoping to build a model tree that has certain areas of the model locked by certain groups(roles), not exact user accounts as I do not know them yet.

For example:
Requirements model - locked by group named Systems analyst
Architecture - locked by group Architect
Tests - Tests engineer

I need an administrative account (or group/role) to be able to do this. Sadly, Enterprise Architect offers almost no flexibility to pre-configure the permissions for the model. I have to log in as a certain user to lock the package in his name.

This is partly solved by adding the admin account to every such group and applying group locks as in the example above. This gives some flexibility and allows to delegate control of a given package to a group. Within that group there can be conflicts and data loss of course, but these are confined, and users are urged to lock their work in their account's name. But then they can release that lock and allow other members of the group to work with them.

So when users connect to the model, there is a structure in place and permissions are set for them to work in certain areas while others are, from the start, read only.

Right now the only thing that ruins this approach is the root node which I cannot lock.
Is there a way to do this at all, even if it takes a SQL command on a raw DB ?

6

Bugs and Issues / Locking a root node without child packages in User/Group policy

« on: September 13, 2017, 02:09:09 am »

Hi,
We have a MySQL-based model repository in my company, I'd like to lock a root node (named for example 'Model') so no one can add 1st level child packages to it.
This does not seem to work however, with the User/Group policy. If I try to lock the root node so that no one (not a user nor a member of a group) can edit it - nothing happens.
We've chosen this policy to get some flexibility in allowing access to certain parts of the model.
Is it possible to lock the root node at all in this mode or should I switch to user-lock policy?
BR,
Włodek