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.
Related
I'm looking for a way to link several items with each other in the Sparx Enterprise Architect Glossary. Is this a possibility?
Example
Term
Definition
Links to
Fact
Something that happend
Follow-upRegistration
Follow-up
Action following a fact
Result
Registration
Writing the fact down
-
Result
The effect of the follow-up
-
I'm looking for a way to register the third column making it easier to have a traceability within the glossary.
You can't do that with the standard glossary, but you can with the new glossary modes (since v15)
See the manual for more info.
This new method allows you to create elements for glossary items. And since they are elements, you can link them to other elements.
You can even use the classes of your existing data model. Just add them to a glossary diagram, and they are included in the glossary.
We are on AEM 6.5.3. I have an experience fragment in the "en" language. And I want to create a live copy of this XF in the es languages. When I select experience fragment and click on create, I see an option to create variation-as live copy, but that creates the live copy in the same hierarchy. But my requirement is to create the live copy under “es” language. I don’t want to use the language copy option because there will not be any relationship b/w en XF and es XF. I want the live copy relation b/w the two (as we maintain the relationship in content pages). This is doable on content pages but not an experience fragment. I mean under content, I can create one page under en, and live copy config can roll out the same page in es language. How to achieve similar functionality in XF.
Another thing is when we use the XF component on the en content page, MSM creates the live copy in es language, But experience fragment path is not translated to match relative to es language. Basically, the inclusion of the experience fragment on the page does not update to match the language of the page.
How do we achieve the above two functionalities?
Using the MSM for Experience Fragments (XPF) is not supported by AEM. This is because AEM uses MSM relationships for XPF variations. So this doesn’t support your (and many others) requirements. You cannot have the same hierarchy of live- and language-copies, as for the normal content. And you cannot have XPF references, that are automatically adjusted during rollout or translation of the normal content.
The alternative is to implement an old-fashioned content library:
Inside your sites structure (in each branch), you create a special folder “Content Library”
There you create pages with “Content Snippets” or “Content Fragments”
You create a custom “Reference” component, that just contains a reference (path) to an content snippet, and renders it (instead of itself)
In detail the problems with OOTB implementation of XPF are:
You cannot have Livecopies of livecopies. So you could not use XPF variation
But Adobe forbid this explicitly by enforcing a fixed path structure, based on sling:folder's
/content/experience-fragments(/[sling:folder])*/[Generic XPF Page]/master
/variation1
/variation2
The AEM UI explicitly looks for the sling:folder – otherwise it doesn’t offer any menu actions. But the sling:folder is not supported by MSM. So you cannot fake a MSM hierarchy and get a working XPF.
It was not built for your scenario.
This is a bit of a hack solution, but XF variations do support the move function. You can create one XF under you language masters and another where you expect to create your published XFs - both using the same XF template. With this set up, you can create a variation-as-live-copy in your language master and then move it to the other XF template instance. It will retain the live copy connection to the language master and you'll be able to roll out as expected. To make this solution work, avoid using the default variant named "master" - it is required and so cannot be easily moved.
More details can be found here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/live-copies-of-experience-fragment-aem-6-5/qaq-p/365482
I need help with mouse over content of the HTML export from Enterprise Architect. I would like the HTML output from Enterprise Architect to also contain the 'Notes' of the element when I mouse over them. Currently this is not possible with the standard HTML export from Enterprise Architect.
Actually there is no way to see the contents and tags of the element if it has a composite child structure except for you have to find it in the side window like project browser and then click the individual object from there.
Please let me know if there are some ways I can achieve these.
Cheers!
Neha
I don't think the mouseover option is possible since the actual clickable areas are not related to the elements, they just redirect to the elements page.
But when clicking on an element on the HTML model, it should show you its details :notes, attributes, diagram, etc...(If it shows you the diagram, rest of the content should be below it)
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 have a Wizard with two pages: pageone extending WizardNewProjectCreationPage, and pagetwo is extending WizardPage. I want the user to be able to create the project first, and then add files to the project on the second page.
For the latter I want to use a SWT Table (?) like when you pick an interface in the Java Class Wizard in Eclipse IDE (cf. picture here). Also the "Add" button next to it.
How can I achieve this? Do I have to use Eclipse Forms API for this? Or simply add a SWT Table? I have used the Plug-In Spy but the source code given in NewClassWizardPage and NewTypeWizardPage seems to be very specific to this example and I cannot make sense of it.
I've also had a look at vogella's tutorial for JFace table, but I can't get my head around it.
Just some basic steps would be great, or maybe somebody has done this before?
I can easily understand why you're confused... there are indeed many ways to do this. You even left out Data Binding which provides you with yet another way to populate and decorate the table in question.
To sum up the usage of the different APIs:
SWT provides the basic widgets and controls. Often these have a rather irregular low-level interface - especially compared with Swing - but you need to access the SWT controls to lay them out (an exercise that can be complicated in itself). Also many of the listeners are on the controls.
JFace provides a set of viewers on top of the corresponding structured SWT controls - e.g. TableViewer on top of Table. These viewers provides a high-level interface to the functionality of the underlying control - e.g. with models, label providers, sorting, filtering and more. (The viewers can easily be compared with the Swing counterparts...)
Eclipse Forms provides a (relatively) simple way to create views, dialogs, etc that looks like web pages. Examples of this are the various PDE editors.
Data Binding provides a (somewhat complicated) way to bind controls (including Tables) to a data structure (Bean, EMF or POJO based).
So... you have to decide on whether to use the model facet of JFace and Data Binding, but the rest of the APIs are often combined in the same view or dialog.
NewClassWizardPage and NewTypeWizardPage are both particular complicated examples of wizards - don't base your own work on these!
For your particular case - as I understand it - I would use a simple JFace TableViewer to hold the list of interfaces... (I use a TableViewer rather than a ListViewer as the later cannot have an image as part of the label provider.) The "Add" and "Remove" buttons will manipulate the model of the viewer and then update the viewer. You don't need Eclipse Forms as the wizards usually don't look like web pages. And Data Binding is also an overkill here given the very, very simple data for the wizard.
Please note that the function of a wizard is only performed after all the wizard pages has been shown and the "Finish" button is pressed.