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.


Topics - sousac

Pages: [1]
1
One of our team members is making use of the structured scenario result and state attributes within a use case.

These need to be included in the Use Case Details document but are not rendering when added to the template.

What I did was simply start with the standard Use Case Details document template and save it as a custom template. I then added the attributes within the existing structured scenario tags.  The content of the "result" simply won't render.

So the template has something like:

Quote
structured scenarios >
         {Scenario_Structured.Step}.{Scenario_Structured.Action}
               Uses:
                {Scenario_Structured.Uses}

               Result:
                {Scenario_Structured.Result}

< structured scenarios

Can't see any filters or other reasons the content would not be output in the template. Bug?

2
We have a model that we manage translations for in two languages but we have a requirement to provide the diagrams of our content in both languages to our audience.

In Sparx EA 15.2 and Prolaborate 4.x there doesn't seem to be language context capabilities for diagram content (i.e., show a specific language or allow a toggle when viewing a diagram) so I thought I would check with the community to see if I am missing something or this feature has not yet arrived.  The document generation also seems deficient when it comes to diagram content and multi-lingual capabilities.

We can accomplish, partially, what we need by maintaining two diagrams and - via scripting - conveying the second language in the alias of the elements/connectors (and then using the "show alias if available") but this limits our use of the alias for other purposes (e.g., abbreviations).

3
Suggestions and Requests / Always open diagram as relation matrix
« on: June 23, 2020, 01:41:34 pm »
The relation matrix is an excellent addition to the diagram view and, unlike the general model relationship matrix, is nicely confined (with ease) to the diagram.

It would be great if (a) the settings of the matrix that were altered were persisted (they reset upon each toggle) and (b) we could default the view of the diagram to this view.

4
I have written a script that creates a collection of child Archimate elements (nested) for the selected element, complete with tagged values, as well as relationships. The script performs as designed without any issues.

<Existing Element>
     3 x New Child Element (with tagged values and a relationship to its parent)
          6 x Sub-Child Elements for each (with tagged values and relationship to its parent)

Performance
On a local EAPX, the scrip runs in about 5 seconds or less (what I would expect). Over a wide area network to a repository via cloud connection, the same script takes about a minute to run (a factor of 12x slower).

The slowness seems to be due to the number of addNew and Update methods I am calling in the script (one can literally observe the items being created in the project browser at a snails pace).

General question, is there any general strategy to observe to limit the number of "save trips" back to the repository when creating a structure like the one depicted (ie., similar to the concept of a commit wrapper....create a bunch of data....commit once?)

5
We are working with databases that are not natively supported in Sparx 14 (e.g., SAP Hana).  A current shortcoming is that the "data type mapping" feature (to express equivalency of data types from one platform to another) does not work with databases that you have added yourself.  I've confirmed this "bug" with Sparx Support. 

Currently when you change the "database" of a table element from one platform to your own custom version, Sparx either maps everything to "varchar" or in the case of going from one custom DB to another custom DB, you lose the datatype and length/precision specifications.

To compensate, I wanted to write my own script to "convert table from database platform x to database platform y", however, I can't seem to find where the "Database" property is exposed in the EA Object Model.


Does anyone have a sample script to manipulate the extended properties associated with EA's data modeling extension (e.g., Database Platform)?

6
My model includes a RefGUID tagged value to establish a relationship between columns (attributes) for source->target specification.  The RefGUID works well in the model, however, it does not present a fully qualified name when shown in the UI or included in documentation.

I'd like to show the parent class (table) for the referenced attribute to offer a fully qualified name.

e.g., if my RefGUID tag references an attribute within Class1 called "FirstName", I want to convey (in documentation) that the referenced attribute is Class1.FirstName

After including the tags collection in a document template, there doesn't seem to be any properties I can work with.

I would likely have access to the referenced object in a script.
Is scripting to an output file the only option or am I missing something in the document generator.

7
Many of my customers who use Archimate 2.0 will be moving to Archimate 3.0 as EA 13 is formally released.

Is anyone aware of a way (script or other utility) to move existing model assets from one version of an MDG to another?  I can readily prepare a script to perform the conversion but thought I would check with the community first.

Pages: [1]