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

Pages: 1 [2] 3 4
Bugs and Issues / order of elements in documentation generator
« on: March 03, 2015, 06:19:37 am »
The default Order for Packages, Elements and Diagrams in the Generate Document/Options is set to Tree Order/Ascending.

Using the above defaults, why when I include the elements of a diagram in the template (Sections/Package/Diagram/Element), they are always always sorted by Name?

v12. 1207

Bugs and Issues / Red Exclamation in Project Browser
« on: February 25, 2015, 02:07:54 am »
I am working on an eap project file on my pc, thus I am the only user.
In the project browser on just one of many packages, I see a red exclamation icon in between the package icon and name.
Other posts state that this indicates the package is locked by another user.  How can that be when I am the only user accessing the eap project?
Is there another reason that triggers the red exclamation?

Restarting EA clears the red exclamation.

(Note: never saw this before r12).

Bugs and Issues / Import DB via ODBC and multiple schemas/owners
« on: December 12, 2014, 06:41:54 am »
Just FYI.

If you create a data model via the Import DB schema from ODBC tool and the MS SQL database that you are accessing actually has multiple schemas (owners), EA may not correctly create the associations between the obects. (tables or views).
This occurs when the same name is used for multiple objects. Seems EA does not take into account the schema (owner) of the objects when drawing the connection on the diagram.
For example, given:
Database has 3 schemas, "S1", "S2" and "S3".

Each of the 3 schemas have the same objects:
  "T1" - table
  "T2" - table
     ("T2" has a FK association to PK of "T1")
  "T1" - view, which basically defines T1 table as a view, thus is associated with the T1 table.
  "T2" - view, which basically defines T2 table as a view, thus is associated with the T2 table.

When EA creates the diagram via the Import schema, it correctly creates the tables and views with the name of the schema set as the OWNER tag.  (FYI: setting "Show Data Model Owner" under the Element menu tag of the diagram's properties will display the owner name with the object name).
However, in my experience it does not correctly draw the associations.

For the views, it not only shows the association between the view and the table within the each schema, it erroneously shows additional associations between the view and the tables/views in the other schemas that have the same name.

As for the FK association between the tables, it sometimes will draw the association connection to a view instead of the table of the same name.


Bugs and Issues / Page order in custom toolbox
« on: October 24, 2014, 07:23:54 am »
I save my toolbox profile via the diagram, not the package.  In the EA User Guide for "Create Toolbox Profiles" there is a note that states:

"Diagram, the Toolbox page sequence is determined by the Z-order of the Stereotype elements on the diagram - the higher the Z-order number of the Stereotype element, the further down the Toolbox its Toolbox page is placed"

Perhaps I am reading it incorrectly, but I think the order is exactly opposite to what the User Guide states.

In my diagram, when I click "Modify Element Z-order...", I see:
ZOrder    Name
1            PaggA
2            PageB
3            PageC

When the toolbox is generated, the order of the displayed pages is:


Is that not the opposite of what the user Guide states?

Bugs and Issues / Tracing communication path assoications
« on: September 05, 2014, 02:49:43 am »
When viewing the traceability, links such as associations can be included using the "Other Links" , however communication path connections, which is a specialized association relationship are not listed in the trace.


I think this is a bug unless there is away to include communication path association relationships in the trace.


Bugs and Issues / port classifier label placement
« on: August 19, 2014, 06:32:53 am »
Something apparently changed (I think in this latest 1110 build) with how EA handles the physical placement of the classifier label on a port. I no longer can control the placement of the classified label in respect to the port., thus I can no longer create a nice looking diagram.

More detail:
On a diagram I have nodes stereotyped as network devices, such as switches which have defined ports. When displaing the port, I use the Advanced/Port Size customizable function so that I can enlarge the port so that I can place the port name inside the port rectangle. When I create a connection, representing a physical connections between ports, I use the target and source classifier to indicate the speed of the port interface. Seems like I was always able to control the placement of the label box for the classifier, but moving the placement of the connection point on the port. EA would place the classifier label box  centered on the connection point, but not overlapping the port box.  

Now when I position the connection point on the port, most of the time the classifier label box will be place to one side of the port box, rather than at the connection point.  This has messed up all my network diagrams, causing overlapping of the classifier label with adjacent port boxes and in some cases, even overlays its own port box.  

I need consistent and accurate control of the labels.

Bugs and Issues / FlushRtfLine(B) Ran out of memory
« on: June 18, 2014, 06:57:01 am »
Is it just me or is v11 throwing more out of memory errors than v9 or v10?

Quite possible it is just me as I am going through my templates and modifying them to take advantage of v11 generate documentation enhancements.

For example I have a package with one diagram. The diagram defines 71 small screens using simpleDialog. On an average each screen has 5 simple controls. The diagram also has links to 19 database tables where I have created realization relationships between the UI Control and its source database table and column via link to element function.

Using the stock Diagram Report template with no TOC, Stylesheet of Cover Page, the Generate Documentation throws the FlushRtfLine(B) Ran out of memory error while still Analyzing the model structure.  When you click OK, the progress quickly runs through the elements and then states "Document successfully created", but it has no diagram.

I am running on a PC with 16 GB RAM and system information shows 11 GB RAM still available when the error is thrown.  I am assuming this is more complicated than just a physical RAM issue.

Other diagrams will also run out of memory but cannot received causing Windows to terminate EA.

I noticed some previous posting (I think over a year ago) regarding the out of memory error where SPARX was working with the third part that wrote the Generate Document function for a solution. Is this the same problem or is this new?

Bugs and Issues / EA style sheets creeate erroneous Heading 1 in TOC
« on: June 17, 2014, 01:05:32 am »
When creating a Word document using the EA provided Print Small style sheet (and I assume all the other style sheets), the style defined for Diagram Label and Table Label apparently have an Outline 1 level set, like Heading 1 style.  When one updates the generated table of contents in Word, they appear as a TOC 1 as if they are a Heading 1 style.

To re-create issue:
1) Open the Print Small style
2) Create a new template (do not copy any existing template, thus should be based solely on normal.rtf.
3) copy text from Print Small style sheet and paste into the new template.
4) save the new template as XXX
5) Select a package and click F8 to initiate the Generate Documentation window.
6) Select XXX as template
7) Select Print Small as style template
8) Select Portrait for Table of Contents
9) Select Portrait for Cover Page
10 Select DOCX as Output Format
11) Generate the document.

12) View the generated document in Word. Note that the Table of Contents does NOT include the Figure and Table references.
13) Now while still in Word, click in the table of contents and click F9 to update the TOC.  Select option to update the entire table.
14) Note now that the Table 1 and Figure 1 are picked up in the TOC as if they where Heading 1.

Bugs and Issues / Data Model-Multiple table relationships
« on: April 29, 2014, 01:22:06 am »
I assume this is a bug.
1) Create a new data model package and diagram, then Import DB Schema from ODBC. Viewed the results in the diagram.
2) Without making any changes in diagram, re-execute the Import DB Schema from ODBC.  Expected to not see any changes. For most relationships that was true, but for a few, there was a second relationship created between the two tables, thus creating a false duplicate relationship.
3) Again, without making any changes in diagram, re-execute the Import DB Schema from ODBC. Again, most relationships remain the same, but for the few that had the duplicate relationship created, either a third relationship was added or the duplicate was removed.
4)If you keep re-executing the Import DB Schema from ODBC, the relationships with the above issues would either just keep adding additional relationships or would toggle deleting and adding the additional relationship.    

Has anyone seen this and if so can explain what is going on?

In my case the database being modeled is an MS SQL 2008 R2.

Bugs and Issues / Import DB schema not syching well-Display changes
« on: April 23, 2014, 03:06:30 am »
Several weeks ago I created new data models for 5 SQL 2008 databases via Import DB Schema from ODBC.  All went well, except I do not like the display it automatically creates.

I changed all of the connections to direct and repositioned the objects to enable easier viewing of relationship and even pinned the end points of the connection (something I typically do not do)

Today I tried to obtain any updates be re importing.  This has work many time in the past for me with the same EA build, however in these cases, EA is changing all of the connections back to custom and re-arranging all the objects, this messing up all the work I did it re-arranging the display.  It did keep by end points pinned.

Any clues on why this is happening?
The only differences between these imports and others I have done is that in these cases I am importing Stored Procedure, User Functions and User Sequences whereas I typically only import the tables and views.  

Here are details:
Using EA 1010.
Settings on the Import DB Schema from ODBC source window:
  Schema/Owner:  blank   (will except all that are found)
  Include System Objects: No
  Include User Packages (Oracle): No
  Include User Views: Yes
  Include Length Semantics (Oracle): Yes
  Include Triggers: Yes
  Include Default Constraints (SQL Server): Yes
  Include User Stored Procedures: Yes   Import as class operations  
  Include User Function: Yes   Import as class operations
  Include User Sequences: Yes   Import as class operations
  Overwrite Table/Column Comments: No
  Overwrite Column Default Values: Yes
  Overwrite Check Constraints: Yes
  Import as New objects: No
Import To:
  Diagram and Package

Bugs and Issues / Connection Names not sticking where repositioned
« on: October 02, 2013, 12:45:57 am »
I am creating a data dictionary, of sorts. I create a package with a diagram for each application screen where I define the appl screen using UI controls on the first page  and then I drag down links from the underlying data model to any tables that the screen references on the second page. I then create a realization connection from the table to the UI control on the screen and then on the table side I use the  Link to Element Feature to change the connection to the associated column in  the table. Finally I name the connection the same as the column name with parenthesis around it.  When you name a connection, EA defaults the placement of the name in the middle of the connection. For the realization connection between table column and screen ui control, I like to place the name of the connection (whcih is the column name), next to the UI control.
EA is not always remembering the EXACT position of the connection name. It will be close by, but not exactly wher I placed it, thus messing up the visual look of the screen. If I correct the position several times  and save the diagram, it sometimes gets better. Even if I reposition the name and then view a different part of the diagram such as the tables and then return to view the UI control, the name will be moved.  Basically EA is SOMETIMES not remembering the exact diagram placement of the connection name.
Anyone else experience this? any thoughts on how to make EA keep the desired name connection diagram location?

Bugs and Issues / Import MS SQL Views - Create not displayed
« on: September 04, 2013, 01:38:05 am »
I am using Import ODBC feature to create data models for our production databases. Some are still MS SQL 2000, but most are MS SQL 2008.
My question has to do with the imported views. For MS SQL 2000 databases, the imported view displays the Create statement whereas the views for MS SQL 2008 do not. Any clues why?

Also I noticed that MOST of the tables/views used within the view have a generalization association created, but sometimes a table/view is missing. Any clues why?

Bugs and Issues / Alternate images: tag list widths  and notes
« on: January 03, 2013, 04:27:26 am »
Does anyone have a workaround? (I am assuming no).

In a diagram using objects with alternate images, I have the Feature and Compartment Visibiliy options set to display tags and notes.

First issue: the Notes are not displayed.

I then resize the width of the displayed tags so that there is no wrapping of tag/value, save and close the diagram, thus making it easier to read and reducing the heigth of the list.

2nd Issue: When re-opening the diagram, EA resets the width, thus ignoring the custom width.

This becomes important when one is trying to create daigrams (and save them) for executive presentations.


Bugs and Issues / Stereotype bug? using same name stereotypes
« on: December 06, 2012, 03:07:26 am »
Can I define a stereotype with the same name as an EA defined stereotype?  For example, EA has a node stereotype for "router".  In my MDG I have a node stereotype called "Router".  I think EA is getting them confused (see detail below).

If the answer is that there can only be one stereotype of the same name, case insensitive, then can I somehow selectively disable the EA stereotypes causing the confliction?  
(Note that some MDGs delivered with EA also duplicate stereotype names and thus may have the same issues. For example, server and unit).

  (using EA 935)

I have a node metaclass and extended from it, several network device stereotypes defined, including:

Name: Server
   StereoType: stereotype
   Attributes include:
        _metatype  string  Server
        _image   string  <Image type="EAShapeScript 1.0" xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64">UEsDBB...
        icon   string   C:\...\Icons\Server_16.png
   Default Appearance has background color of blue.
Name Router
   StereoType: stereotype
   Attributes include:
        _metatype  string  Router
        _image   string  <Image type="EAShapeScript 1.0" xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64">UEsDBBQA...
        icon   string   C:\...\Icons\Router_16.png
   Default Appearance has background color of green.

Both are referenced in a toolbox profile in identical format and appear in the toolbox with their associated icon.

All seems well within the MDG.

As you can see the definition of the stereotypes are nearly identical, yet EA is treating them differently when creating elements in a project.

When I drag the Server element from MDG toolbox onto a diagram, EA draws the rectangle with the correct blue fill color, displays the server icon and the displayed name includes the "<<Server>>" stereotype. The element in the project browser has the correct icon. Likewise when I drag the Router from toolbox onto a diagram, EA draws the rectangle with the correct green fill color, displays the server icon and the displayed name includes the "<<Router>>" stereotype.  Both look as expected.

I now create an instance of a Server by dragging the Server element created above from the project browser onto a diagram and selecting to create an instance. Likewise I create a Router instance. This is where EA treats them different.

For the Server, EA draws the rectancle with the correct fill color, icon, but does not display the stereotype name above the name. In the project browser the stereotype is "<<server>>", not "<<Server>>". (note the small case on "server" as if it is picking up the EA defined stereotype.

For the Router, EA draws the rectancle with the correct fill color, but does NOT display the icon,  but does display the stereotype name above the name, but its value is "<<router>>, not "<<Router>>". In the project browser the stereotype is also "<<router>>".

I am guessing that when EA looksup the stereotype for an element, some logic is getting confused between its own defined stereotype "<<router>>" and my MDG defined stereotype "<<Router>>" when they have the same name (with exception of the case).

This speculation is further supported when one tries to change the stereoype of an element in the project browser (for either the inital element or an instance). Although I see my MDG defined stereotypes in the dropdown selection (as determined by the Title case used),  if I select my "Router" strereotype, it always deploys the EA "router" stereotype name and no icon. Even if I use the ... lookup and uncheck "router" and then select the "Router" under my MDG, EA deploys the "router" stereotype.


Bugs and Issues / Stereotype background default color and instances
« on: October 12, 2012, 03:52:55 am »
Believe this is a bug.

When converting a node to an instance, the instance should pick up the attributes of the node, including color.

I have a node stereotype defined in a profile for "Router" where I have set its default appearance for its background color to blue. When I create a Router on a diagram from the Router element in my toolbox the background is correctly filled with the default blue background. When I change the element to be an instance, the instance's background reverts back to the EA default tan color. It should still be blue.  

This works in other areas such as dragging the Router stereotype from the project browser. If you select creating an instance or link, the resulting background color is the correct default of blue.


Pages: 1 [2] 3 4