Lost Information Item Conveyed Functionality

[GeistBW]

I somehow lost the ability to use the "Information Item Conveyed" Functionality of the "Information Flow" connector.  I was using it previously and didn't have any issues but now I don't get the "Add" button to activate.

I was don't some creating and removing of some new security groups but they were not associated with users yet, one group was but it had no permissions any longer and so I removed it.  But one login I tested with was never associated with these new groups or any I removed.  It was/is in a different group entirely.

Where is the permission for this functionality located?  How can I get this back?

Please HELP!!

[GeistBW]

Update:  I realized that my elements were locked because they were "promoted" to where we keep our final/production state diagrams/elements.  We do this so if someone is to change diagram or element they would need to get a copy via TimeAware clone process. Other connectors work just fine they can be added to these locked elements, just not the "conveyed Item" function of the Information flow connector.

So how do I keep these items locked so not everyone can make any change to the element they want, but still allow the Information Flow connector work as it should?  What am I missing?
Thanks

[qwerty]

I guess you need to reach out for Sparx support. Good luck.

q.

[GiD]

I faced the same problem recently. Is there any solution or hint from Sparx Support?

[Geert Bellekens]

The fact that EA still allows to create relations between locked elements is a bug in itself.
The items conveyed seems to behave correctly in this case.

You should unlock at least the source element before being able to change anything to its connectors.

Geert

[GiD]

Thanks Geert, yes I see and can agree to your reasoning.

Do you see indicators, or even have commitments, that Sparx will fix this bug to not allow the creation of connectors between locked elements? We actually use this feature or more correctly speaking this bug.

Thus a bug fixing could result in numerous invalid processing steps or workflows at arbitrary clients.
So I wonder, if Sparx really plans to introduce this bug fix?

Do you have some more information on this?

Cheers,   Gisbert

[Eve]

Hey Gisbert,

Just want to point out that one user considering something a bug doesn't mean that Sparx Systems does.

There is an option Settings > Security > Administrator > Apply Locks to Connectors

If you have that set to false (which I believe is the default) then any change that blocks new relationships because the source is locked would be a bug. On the other hand. If some property of a connector can't be edited due to locking without that being set to true, then report that as a bug.

[Geert Bellekens]

There is an option Settings > Security > Administrator > Apply Locks to Connectors

Thanks for that info Eve. I don't think I actually knew (or I have since forgotten) about that option.

Geert

[qwerty]

For me that's also the first time to hear about such an option.

q.

[GiD]

Hi Eve,

thank you for pointing to that security feature setting that might explain, why connectors can't be edited when the source element is locked.

In our case the security feature setting 'Apply Locks to Connectors' is not active (false).
Furthermore we also face this error when only the target element of the connector is locked, which is somehow not at all covered by the security feature setting.

So it looks like that we should report this behavior as a bug.

Thanks for your contribution, hints and comments!

Cheers,   Gisbert