I'm trying to create a custom toolbox with some stereotypes I created. I'm following this guide: https://sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/create_toolbox_profiles_using_.html.
This is my profile diagram:
However, when I try to add the stereotypes to the toolbox page, I select them but then they don't get listed in the toolbox items...
What am I missing?
I managed to do it by adding the metaclass in the "Profile helper".
Here's the profile diagram view of a custom stereotype:
Related
I am trying to create nested activity diagrams in Papyrus.
My Problem: I don't know how to create a sub-activity-diagram directly from an action of my main activity-diagram. I want also to transfer ports from the action to the sub-diagram. In cameo it works easily as described in MagicGrid Handbook:
create sub-activity-diagram from an action
sub-activity diagram including ports
In Papyrus I can only create a sub-diagram manually and then create a hyperlink to the main diagram. But ports are not transferred in this case.
Any idea? Thanks and BR, Lennox
We use elements with composite diagrams in our models. Usually if such a composite diagram exists, then the element shows a link icon to indicate a double click will open/show the diagram.
But with ArchiMate elements the link icon is not shown unless using the rectangle notation. Is there some workarround or configuration to allways show the icon?
This screenshot illustrates the problem:
Out of the box, there is nothing you can do. There is no setting or configuration that will show the composite diagram indicator on the Archimate elements.
The reason is that the shapescript used for these elements simply doesn't include this indicator.
There are a few options to get this done anyway
1 Send a feature request to Sparx
You can use this link: https://www.sparxsystems.com/support/forms/feature_request.html to send an official feature request to Sparx Systems. They might one day implement this, but there are no guarantees at all.
2 Override the standard the ArchiMate MDG
Steps include
Create your own stereotypes in a profile, redefining the existing ArchiMate stereotypes. See the manual for more details
Include your profile into an MDG
Add your MDG to your model or environment
Set your MDG to Active to actually make the redefines happen.
This might be interesting if you want to add additional properties (tagged values) to the standard ArchiMate stereotypes as well. I'm not so sure if it's worth the trouble just to add the composite indicator.
3 Hack the existing Archimate MDG file
The Archimate MDG is defined in the file C:\Program Files (x86)\Sparx Systems\EA\MDGTechnologies\ArchiMate3.xml. This is an XML file that you can open with any text editor. The shapescripts are included in binary form like this
<Image type="EAShapeScript 1.0" xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64">
UEsDBBQAAAAIAGaEbU+CvMH4PQIAADAKAAAHABEAc3RyLmRhdFVUDQAH1zDMXdcwzF3XMMxd
zVVJTsNAEOyrkfhDFC6OlAP7IsSRF/AAlMSJY5FNjgMKiL9T1Z3B9tiJAxKLLI9nqamumV68
lLH0ZCFDackUvURmcigH8qZtIBPMrWUuK8nwrBV5J23pYy6VCKMUo9sNeobZpTJG6L0AmWF9
BZRDWJvISELFLcGYAkveVC2E4EsxGmDUA2MMDUNl5jjD3jlGbeniPcbbwWOsTnOgukbgTuQV
vVDO5AL4K+A7n0oCrJORVhfKPAayuD6E5Qk4FkCS5RT7u/pea3vm8VFltIVrBB6y8USRWuap
n7CnHj/F6jNWM3xDqK+zR20zD+OfsYw5UQzbMqrO2m6mm72YzB75mpjKmPfNlx7g3Tf51zh8
xdUoChWXK687AWOXHlohxi2WGZuMSnqKa1QfbyKQkbjf7hn6U/Rt30AYLZlY/hQZ3Dff3fIs
O0R+H4FmEe+EfOxF2D0EPsY3Qx4ydnMb7n7rrTmldXbG8ohVejAGjpWgfJLcRqA1YgIl1Srg
FPM8md7O0afVI+8+nFb7Wsu3qJh51RdGC1ec3u32GVOMPiqIVQU1LFGx6B2LEafBdvx0xdrv
Nvw7YB4M9By5nRb6VMLZ4m3Yac1XOZoeZC7mnvuN8zbl91crMyuj+Y01oCvnXk7vqszfq8W+
hf9fi+3vtbsW23+trhY3xRxnprg//v8TYTUgtjn2HuS+EHt/G3VN1hPMV89pFl2FKdotV04/
Zl0UufbS80x1BxEO7f5f1V1lr1tm+F73/W5Z46PqKu8HUEsBAhcLFAAAAAgAZoRtT4K8wfg9
AgAAMAoAAAcACQAAAAAAAAAAAACAAAAAAHN0ci5kYXRVVAUAB9cwzF1QSwUGAAAAAAEAAQA+
AAAAcwIAAAAA
</Image>
If you replace that section with a shapescript of your own, it will happily accept that. You can create this format by creating your own profile in EA and then exporting the package as a UML profile. EA will then convert your shapescript into this binary format.
I one published the shapescript for most of the MDG's, including ArchiMate3 on github. That might give you a head start when developing your own.
How can I create a custom wizard in TCA so that, I can click on add button to create a particluar specific plugin on a page? my TYPO3 Version is 7.6.
click on the image. There is a add button
You can make a custom wizard on your own or use an existing one. Here you can find examples of existing ones and an example to create a custom one: https://docs.typo3.org/typo3cms/TCAReference/7.6/AdditionalFeatures/WizardsConfiguration/Index.html#user-defined-wizard-processing-with-php-function
Note this code area has been rewritten with core v8 - much more powerful 'wizards' are possible, called 'node expansion' and they come with a better API. For details see https://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/FormEngine/Rendering/Index.html#node-expansion and the according sections from TCA Reference for details.
Is there a way to hide or remove the various base_Class properties that appear together with the properties defined for a stereotype? I am close to deploy a profile and I am pretty sure this will generate some confusion among the users.
Actually you really don't want to remove the 'base_*' properties as these indicate the meta class that your stereotypes extend. When a user goes to apply your profile, the meta class extension allows the UML editor e.g. Papyrus to display appropriate stereotypes for the target UML element. So if a user wants to apply your profile to a UML Class element, without the 'base_Class' property, nothing will show up. These extensions are linked to other elements within your profile so just removing them will cause your profile to "break" elsewhere. Other typical meta class extensions might be Property i.e. a 'base_Property' will show up. There are many others.
Oh ok cool. So when your users apply the profile to a model this takes place, as you know, primarily under the Profile->Applied stereotypes area of the Properties editor. The meta class extension properties are definitely not visible there, at least on my Papyrus version. Using Modeling Luna 4.4.0
I'm updating the existing documentation of a project I've done. In short, I have to add a new library to communicate the application with a new hardware the client wants to use. So far so good.
So in EA I went to the existing diagram and added a new component. I have a class that acts as controller for the actions this new hardware is going to do, so in the new implementation of the system, this class depends on the new component.
I tried to create a new dependency relationship between them, but when I release the mouse, a popup appears telling me that the connector used between origin and destination elements is not permitted. It prompts me with valid relationships between a class and a component. In that list I can see the dependency relationship, which is the one I'm trying to set up.
This is the popup:
Any ideas of what am I doing wrong?
Thank you in advance.
To me, it looks like some other Model validation is in place. What MDG Technologies do you have enabled? Which Toolbox / diagram are you using.
Go to Settings -> MDG Technologies and try to unselect the ones that are not standard with EA and try again, it must work.
PS - Works fine for me.