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

Pages: [1] 2
1
Bugs and Issues / Re: Missing Column Metaclass?
« on: February 19, 2022, 01:33:09 am »
Hi Paolo,

Thanks, I can see what you mean. For example "table" appears in the list of stereotypes for EAUML. However, still no sign of "column" as either a metaclass or a stereotype...

Regards,

Tony

2
Bugs and Issues / Missing Column Metaclass?
« on: February 18, 2022, 08:41:26 pm »
In my MDG Technology I wish to add a stereotype that extends the Column Metaclass... except there isn't a Column Metaclass to pick.

I have tried extending the Attribute Metaclass in the hope that Column was itself an extension of Attribute, but to no avail.

The Column properties window is quite different in look, feel, and function to the other Properties windows such as Class and Attribute and Table. Is this because Column is not a UML element type?

Any way around this? Ideas welcome.

Thanks,

Tony

3
I solved it, but in a slightly strange way.

I logged on as Administrator. Disabled security (which took 20 mins!) then re-enabled it, making sure both processes completely successfully. I think that I lost connection to my server repository part way through the process of locking a large number of elements, which caused the corruption, so had to ensure I went completely round the loop again to remove the inconsistency. I can now create classes again! :)

4
Bugs and Issues / Re: How do I Export Class Attributes in a .csv file?
« on: February 09, 2022, 09:56:52 pm »
You can create an SQL search an then export the results to CSV:

Geert

Many thanks Geert, this is precisely what I required and your SQL worked a treat.
Regards,
Tony

5
Bugs and Issues / Re: Template appearance for connectors not picked up?
« on: February 04, 2022, 11:09:18 pm »
That's good news that the same metatype is used. Did you code the shapescript to react to the values of multiplicity or is that "built in" to EA?

6
Bugs and Issues / Re: Template appearance for connectors not picked up?
« on: February 04, 2022, 08:17:54 pm »
Hi Paolo,

Many thanks for the offer of assistance. Now I know that the templates for arcs do not flow through, I have baselined it for now, as I have other priorities, but will pick up later when I can schedule it in.

Initial thoughts are that as we are mandated to use the Information Engineering (Crowsfoot) notation, I will need separate stereotypes (subtyped from the Association metaclass) with shapescripts for every combo of relationship (0:1, 1:1 ,1:many ,0:many ,many:many, etc) and that therefore these will have to be different connector types in my toolbox. Sounds a bit clunky, I'm sure you know of a better way...

Tony

7
Very many thanks q, you were absolutely right.

I have done:
toolbox tab -> choose any stereotype -> click Synchronize Stereotype > OK
and this has updated a number of instances of my stereotype which when I go and look at the pull down lists that were displaying strangely, they are all updated and correct (and the previously picked values are preserved).

I can now see the power of this as I had envisaged that if we added a tagged value or changed an enumerated value list sometime in the future that we would have to manually add this to all previously created instances of the stereotype. Now I can see that this function brings them all up-to-date with the latest version of the MDG Technology all in one go.

What a shame such an important function is so buried in a right click menu (although I can't think where else it could/should be). I guess it's one of those things that you just have to know, and now I know it.

Thanks again,

Tony

8
Bugs and Issues / Re: Template appearance for connectors not picked up?
« on: February 03, 2022, 08:55:25 pm »
Hi Paolo,

Many thanks. I didn't really think I would be the first to have come across this, but maybe the more requests from users the more likely Sparx are to carry out the enhancement.

I note your comment regarding shapescripts for relationships. I do have a my own MDG Technology so will look to enhance that as you suggest.

Thanks again.

Tony

9
Bugs and Issues / Performance Speed Issues
« on: February 03, 2022, 04:41:58 am »
We're seeing a number of performance speed issues when connected to our networked repositories. Creating diagrams and creating elements on diagrams etc can take between 2 and 25 seconds. We see the busy cursor a lot.

Our set up is remote clients with SQL Server driver, through a dedicated VPN and firewall, to the Azure SQL Server licence database and repository databases.

We don't have Pro Cloud Server installed so we use "Connect to Server" rather than "Connect to Cloud". Would having Pro Cloud Server likely resolve the performance speed issues?

Any general thoughts and ideas would be welcomed. I've raised this with Sparx but am putting it out to the wider forum as well in the hope we can get to a resolution.

Regards,

Tony

10
Thanks q for the recommendation re taking regular snapshots and working on a central DB with "require user lock to edit" being the best way to collaborate. We haven't gone down the version control route, hence why I was trying to work out the best alternative. Thanks again.

Tony

11
Bugs and Issues / How do I Export Class Attributes in a .csv file?
« on: February 03, 2022, 04:28:31 am »
I can successfully export a package which includes all the element types on the diagrams by using the Export csv function and creating a specification. When I leave the Types field blank, all element types down to Classes are exported.

However, what I need is an export that goes one step deeper. I would like to list all the attributes in every class in a csv so I can import into Excel the list of attributes by class name. Is there a way to do this? Any help would be gratefully received

12
Bugs and Issues / MDG Technology Enumerated list appears to be corrupted
« on: February 03, 2022, 03:46:07 am »
I have created my own MDG Technology and successfully deployed it to both local and networked repositories. On a new local repository all is fine. On one of our more established networked repositories I see some corruption.

The enumerated type is a simple list with values "(Unset),0%,25%,50%,75%,100%". When the tagged value pull down is pulled down, all is well to the 75% value, but the 100% value has ""Default: (Unset)Description: As per DAMA core data quality dimensions" added and there is also an additional value on the end of the enumerated list entitled "Accuracy" which is the name of the tagged value. It seems like the last value in the enumerated list has been corrupted.

The XML file used in the MDG Technology has the standard list of values "(Unset),0%,25%,50%,75%,100%". The dubious text seen is elsewhere in the xml in description fields but seems to have got corrupted within the target repository.

I have deleted the MDG Technology and reimported it - no change. I have run the consistency check - no change. Does the repository need to be compacted or repaired? I don't want to do this if I don't have to, but if you think it would fix this issue then I'm prepared to give it a go. Any other thoughts. Thanks and regards, Tony

13
Bugs and Issues / Re: Template appearance for connectors not picked up?
« on: February 02, 2022, 08:22:27 pm »
Hi Paolo,

Many thanks for clarifying this. At least it is not that I have done something wrong. It's a shame because my users are impressed with the appearance of the shapes from my template, but then are equally disappointed by the appearance of the relationships!

I will raise an enhancement request with Sparx.

Regards,

Tony

14
Many thanks Geert, I will leave the Manage Technologies dialog alone for now. I appreciate that restricting technologies can be achieved by restricting perspectives. I will concentrate on ensuring that my user groups are set up with restricted perspective sets (or a single set with only the technologies we use, as you suggest).

Regards,

Tony

15
Is there a way to automate the setting of the different technologies on the Manage Technologies dialog? I want to make it really really easy for my user community to be defaulted to a much smaller subset of all the available technologies without them having to go through the dialog and set manually the ones that I want them to have / not have. Currently, it appears that the Manage Technologies is specific to user but applies across all repositories. Is there not a way for the administrator to set this up on everyone's behalf?

Pages: [1] 2