Book a Demo

Author Topic: Apply Auto Naming and Security  (Read 4306 times)

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Apply Auto Naming and Security
« on: August 21, 2014, 06:55:37 pm »
Here's a weird one.

In a security-enabled repository, in order to apply auto names to elements the package must be locked - but the elements must be UNlocked. Yer what?

This is the behavior in 1009, and there's no mention of any changes in the version histories.

Is this really by design? If so, what's the reasoning behind it?


/Uffe
My theories are always correct, just apply them to the right reality.

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
Re: Apply Auto Naming and Security
« Reply #1 on: August 21, 2014, 07:20:27 pm »
Hi Uffe,

once ago I had the same problem and reported a bug.
This is a "confirmed" bug in EA10 :-)

Good news:
In EA11 it is fixed: You need to lock the topmost package only and leave out all childs.
Than you can apply auto naming.

Best regards

Stefan
Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Apply Auto Naming and Security
« Reply #2 on: August 21, 2014, 08:14:18 pm »
Cool, thanks. My client is shifting to EA 11 next week, I should be able to hold them off with the ol' whip and chair till then. :)
My theories are always correct, just apply them to the right reality.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Apply Auto Naming and Security
« Reply #3 on: August 21, 2014, 11:24:54 pm »
Quote
Cool, thanks. My client is shifting to EA 11 next week, I should be able to hold them off with the ol' whip and chair till then. :)
So you are a tamer and your customer is a tiger?  8-)

q.