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 - Nizam

Pages: [1] 2 3 ... 20
Bugs and Issues / Re: Generate Documentation - Images too small
« on: July 20, 2018, 09:16:13 pm »
You might have to enable page border and check if the diagram fits fill size in the A4 page. EA would only render the actual size (relative to page), so if you make it fully scaled in the diagram, you must be seeing a bigger image

Do you know any feature or plugin that allows, given a class model (classes with attributes and relationships), convert it to a database model of classes (classes stereotyped as <<table>> with columns and foreign keys)?

We don't have a ERD model, but a simple class model.

You can use DDL or write a script to stereotype the objects, attributes, and connectors

General Board / Re: Visio import: Element text invisible
« on: July 20, 2018, 02:27:16 pm »
Seems to work okay for me.
My systems spec
EA 13
Visio 2016
EA Visio MDG Link

IMported Image

I chose 'Activity' when EA prompted for default conversion.

PS - I have to drag and drop objects to a diagram to create this diagram.

Bugs and Issues / Re: Generate Documentation - Images too small
« on: July 19, 2018, 01:01:06 pm »
It may be worth to Check your Page settings in EA and the page size to which you are printing your document.
Also, try''Divide diagram into multiple pages' option to see if that makes any difference.

General Board / Re: Visio import: Element text invisible
« on: July 19, 2018, 12:57:02 pm »
I tested again, and my visio imports brings in connectors, are you able to share an excerpt of your actual Visio.

General Board / Re: Default Attribute Value
« on: July 19, 2018, 02:59:01 am »
Try adding 'None' as a data type for your default Language  You can do that from 'Code Engineering Datatypes'

then you'll see None in your list of types to choose for Default Attribute Type

General Board / Re: Default Attribute Value
« on: July 18, 2018, 08:15:30 pm »
Are you referring to default Attribute Type being set as 'int'? you can change that under Preferences -> Language specific page under Source Code Engineering -> Default Attribute type.

Or If you are looking at setting the 'Initial Value', you have to consider Template Packages.

Does the EA only allow the user to perform "Elements Filter" from search builted through the "Query Builder"???

YOu have to creat a new search of type 'SQL Editor' and then type your query in the 'Query Builder'.

All other steps that Arshad has mentioned are to just create a new search in your machine.
FWIW - the searches are stored in  %appdata%\Sparx Systems\EA\Search Data\EA_Search.xml

General Board / Re: Block Filtering by Tagged Values for reporting
« on: July 16, 2018, 01:29:38 pm »
Consider Sharing an image of what you've tried in the template and your model.

Suggestions and Requests / Re: Archimate connector stereotype labels
« on: July 13, 2018, 01:30:34 pm »
Further to qwerty's comment and your posts, you can consider modifying the shapescripts in the MDG.
Removing middlebottomlabel this (and updating the default MDG) should restore your expected behavior.

Actual Shapescript from ArchiMate (refer Geerts
Code: [Select]
shape main

label middlebottomlabel

General Board / Re: Visio import: Element text invisible
« on: July 11, 2018, 07:40:22 am »
OK, here's some more information. I set a baseline then, using EA, I clicked on one element and deleted the stereotype of "rectangle" by backspacing the text and then clicking out of the field in the Element Properties window.

Now I ran a Baseline Compare. I wish I could post an image here but cannot. Well, the comparison said three items had changed:
- The value of stereotype in the element went from "rectangle" to null. (No surprise there)
- There was a tagged value with Name "fill" that was false in the baseline. This tagged value was deleted.
- There was a tagged value with Name "nameVisible" that was also false in the baseline. This tagged value had also been deleted.

Knowing this, I executed SQL to do make the exact same changes to another element. The result in the appearance of the diagram was no change. The stereotype for the element I tried to change using SQL still said "rectangle", so clearly the field t_object.stereotype is not the authority for this property. Where is this data hidden?

Quite a puzzle.


I'd again suggest trying using a script to modifying a few elements, and see if that helps. There are items in StyleEx field, PData, XRef, object properties  and many other places that EA could use to infer appearance

You don't seem to have a very unusual reporting requirement
Use a template with 'Sub Packages' enabled and just have the name and notes of Element under package
Refer image below

however if you want a report of all elements alphabetically , one way to achieve will be to use a Model Document, write a query to fetch all the elements and have that as the input to that Model document (use the same template)

General Board / Re: Visio import: Element text invisible
« on: July 10, 2018, 10:19:40 am »
For item 2, I did some checking inside the database as I have SQL access. I ran this query (after identifying package_id 305 as the import):
select * from t_connector where start_object_id in (select object_id from t_object where package_id = 305) or end_object_id in (select object_id from t_object where package_id = 305)
Whats your Visio version? can you try saving the file in the older format (.vsd) and importing again.

(From the post i infer that your Visio diagrams uses the generic shapes stencil (rather than UML or BPMN, etc.)  Visio import works better if one of the standard stencils is used.)

For item 3, I found that each element was of type Rectangle and stereotype rectangle. I found that if I null the stereotype, the Element Name text suddenly appears. I attempted to make the change using an SQL update to a different element:
update t_object set stereotype = null where object_id = 9717
EA stores Stereotype information in multiple tables (t_xref has the FQ Streotype details), best to use scripts to iterate and clear the stereotypeex field of the objects.

General Board / Re: Default element size
« on: July 09, 2018, 11:38:06 am »
No, I believe that Cornelian is saying that Ctrl+Z puts elements at their default size, but where does the user define what the default size is?

Ah!, makes sense, however Alt+Z is the best size (rather than default size), I think its case by case basis (depending on whats displayed). and its best handled by the system.

Setting a default size for an element is either a Template package (relatively easy) or Shapescript.

General Board / Re: Default element size
« on: July 09, 2018, 08:18:32 am »
How can i set default element size( used with Alt-Z) ?

Template package helps  to influence the size.

However, you are saying the 'Alt + z' is not working or you aren't able to find it?

Pages: [1] 2 3 ... 20