Book a Demo

Author Topic: v15.2 – Show Element Property string doesn’t suppress for some item types  (Read 3281 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
We use the IsSpec (UI: Is Specification) property for our own (and most useful) purposes in our MDG.
We use the [ ] Show Element Property String  (set to false) to suppress the {specification} string appearing on the item on diagrams.

However, this doesn't seem to universally apply.  Many Items Types respond, others don't.  We've noticed that those types that don't allow "access" to the [ ] Is Specification property on the details page (usually because the details page is suppressed) can't hide it.

If the intent is to NOT allow us to set/unset the property (via the UI), then the property should NEVER be rendered!  Since the property can be set by many other means (other than direct injection into the database, the value may be set to True regardless of the EAUI behaviour.

Please rectify,
Reported,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
If you're using "direct injection into the database" then I'm glad you're getting unexpected results.

Again, you aren't sharing the basic information like what elements you are complaining about.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
If you're using "direct injection into the database" then I'm glad you're getting unexpected results.

Again, you aren't sharing the basic information like what elements you are complaining about.
I just mentioned that that was our method, there are other methods such as the use of the element.IsSpec from the Element Class in scripts.

If I'd used that would you still be glad I'm getting unexpected results?   ;)

As per the types involved, we've already done some analysis and found what we expect to be the common factor - as I described. But I have specific examples as Component, and Activity.  Class is NOT affected as one would expect from our analysis.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!