Book a Demo

Author Topic: EA14 Find in Browser - incorrect Element Name search definition  (Read 3367 times)

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
EA14 Find in Browser - incorrect Element Name search definition
« on: January 18, 2019, 02:09:12 am »
Hi,

The project browser search has been removed in EA14.1 to call the Element Name search.
Since it used to be rather slow in previous versions, I can understand this change, however looking at the Element Name search definition, it does not make sense as it searches on various fields including the Parameter name set as compulsory.
I would have expected to search on the Element name only with the Contains condition and Required set to true.

Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: EA14 Find in Browser - incorrect Element Name search definition
« Reply #1 on: January 18, 2019, 04:47:29 am »
It's not gone, just harder to find.
If you select Portals | Show Toolbar | Project Tools you can use the old find in project browser function.

Geert

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Re: EA14 Find in Browser - incorrect Element Name search definition
« Reply #2 on: January 18, 2019, 06:14:10 pm »
Thanks Geert.
In the meantime I'll submit a bug report on the Element Name search.
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: EA14 Find in Browser - incorrect Element Name search definition
« Reply #3 on: January 21, 2019, 09:32:36 am »
I use the Element Name search frequently, for elements that don't even support operations. Never had a problem with it. (In fact I didn't know that it extended beyond the element name and alias)

The search still works because the options for it specify 'At least one Table' rather than 'All Tables'.

The required checkbox works such that for each table all the required fields need to match and one or more non-required fields need to match.

Because there is only one condition on that table, that required mark will make no difference. You can't get a match on that table without it being matched. So it is required either way.

In contrast, every other table in the search has both alias and name. If you marked either of those as required, it would have the effect that both are automatically required.