Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Eve

Pages: [1] 2 3 ... 532
I don't believe I implied it was the decorations themselves, merely that the inheritance process is defective.
I've confirmed that the issue preventing decorations (which is the one I believe you were referencing as being previously acknowledged) from being inherited from two levels of ancestry only impacts decorations. If there are other issues with inheritance then they are unrelated.

What surprised us was that ANY <stereotyperelationships> defined in Root¯R would break the QuickLinker!

Is this a behaviour that should be expected, or is this a defect (notwithstanding that the BPMN 2 technology hasn't been updated to use stereotyped relationships)?  We think it is a defect.  Your thoughts?
It's been a little while since I was actively working with the metamodel specified relationships. My gut reaction is that the behavior you're describing is at least a little surprising. I also know that the way the two methods interact is complex and where they are in conflict the metamodel should take priority. From the information available to me right now I wouldn't say it's a defect despite surprising me.

Not entirely sure about your conclusions.

It could be the second level of inheritance interfering with the BPMN quicklinker, but it could just be something particular about CmmnItm¯D itself. In either case, the information you've shared doesn't support that it's related to decorations.

Yes, decorations need an extension before EA will use them.

What do you mean by "empty stereotype"?
Create a new stereotype, don't change anything except perhaps the name/abstract.

Just to check my understanding:
When you create a new stereotype specializing BPMN2.0::Activity and another stereotype, it appears that EA no longer recognises that as a BPMN2.0::Activity.

If that's a correct interpretation. My initial reaction is that it sounds like something is going wrong. I can't take the time to try to debug it right now, the first step would be determining if it's something particular to StndrdItm¯D, or if you get the same problem with an empty stereotype.

The BPMN 2 technology hasn't been upgraded to use stereotyped relationships etc for its relationships. The quicklinker is still defined using the table, and your stereotype doesn't match its filters.

When you defined a rule, that resulted in overriding the table relationships for that connector type. A behavior that's in place so that a profile author can progressively implement rules.

Create Stereotypes Extending non-UML Objects

In short. It's related with a Generalization, not an extension.

PCS General Board / Re: Pool of db connections created by the PCS
« on: March 22, 2024, 08:28:48 am »
Yes, it is automatically managed. They are created transparently as needed and cleaned up if they haven't been used recently.

The number can be managed with the 'Max Simultaneous Queries' option.

In this case why do we have "Opaque" as an option in Action Kind?
OpaqueAction is a metaclass in the UML specification.

Bugs and Issues / Re: v16.1 - Line Width management BROKEN!
« on: March 14, 2024, 12:17:00 pm »
The second point DID occur to me when describing the problem
And that was really the whole point of my reply. Your initial post came across to me as a rant about everything being broken again. I attempted to bring the tone back to the point that there was a disconnect between your expectations and reality and one little defect that impacts one use case.

Since the code needs to be fixed because of the defect.  Why not fix it properly?
If I lived in an ideal world where I had unlimited developer hours I would agree. I don't get to pretend I live in that world, I'd rather push for the easy fix to be done before the harder one can even be considered.

General Board / Re: Notes colour not matching the manually set colour
« on: March 14, 2024, 08:08:26 am »
Note colour uses the global option.

You may be able to do it with a restricted perspective. (scroll down a bit)

You can also assign a perspective to a security group.

The problem is that the behavior that you're wanting to avoid is specific to creating that exact metaclass.

Just to support the fact that EA does that, and maybe to suggest what you want isn't actually a good idea... Action is actually an abstract metaclass. The authors of UML do not intend for it to be possible to directly create.

One additional point. You don't need the (UML::Action), that's specifically for creating a stereotype for a profile. You could even create a profiled version of the specialized actions like Profile::Stereotype(UML::CallBehaviorAction).

Is your file read only (or do you have write permissions to that file)?

Bugs and Issues / Re: v16.1 - Line Width management BROKEN!
« on: March 12, 2024, 08:44:49 am »
Feature Request: Connector Line width does not have a "profile default" lookup. (I don't think other profile styles for connectors do either) You'd like to see that added as new functionality. (Even if it's described as as an inconsistency issue with the way objects work)
Bug: Creating a profiled connector writes the profile line width into the local colour instead of the default.

I think those two points explain your observations.

Bugs and Issues / Re: Import Python fail
« on: March 12, 2024, 08:24:27 am »
I don't know if you actually reported this (I can't see it in the list of issues that are under investigation), but even when code engineering was my area I couldn't give a useful answer from this.

My only suggestion at the moment is to try 16.1.

Release Notes for 16.1 Build 1621

Code Engineering
  Improve Code Engineering/Code Editor to support Python 3.9 and Python 3.10 new features

If that doesn't work, then I'd suggest submitting a file to support for investigation.

Pages: [1] 2 3 ... 532