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 - chris pearce

Pages: [1] 2
Bugs and Issues / Re: Basic Import to sysML blocks
« on: November 24, 2017, 11:25:19 pm »
This DOES work if i use the correct stereotype "ahem"  :-[

Code: [Select]
Fully Qualified Stereotype Name Notes Alias Type GUID Profile Metatype
block SysML1.3::block TestBlock50 Class SysML1.3::block
block SysML1.3::block TestBlock51 Class SysML1.3::block
block SysML1.3::block TestBlock52 Class SysML1.3::block
block SysML1.3::block TestBlock53 Class SysML1.3::block
block SysML1.3::block TestBlock54 Class SysML1.3::block
block SysML1.3::block TestBlock55 Class SysML1.3::block

The answer : SysML1.3::block  as fully qualified Stereotype and profile meta data does work and attaches the MDG functionality correctly :-)

Thanks Geert  ...

Bugs and Issues / Re: Basic Import to sysML blocks
« on: November 24, 2017, 03:36:43 am »
thanks Geert,

I tried an import with the following test file

Code: [Select]
Stereotype,Fully Qualified Stereotype,Name,Notes,Alias,Type,GUID,Profile Metatype

And although it appears to make sysML 1.3 blocks  the behaviour of the MDG plugin in the back ground ignores the aggregations made in the a diagram to automatically create the "parts" in the parent and show the properties fields in the <<block>> :-[

Dont know if you can post images but a picture would paint a thousand words...

Bugs and Issues / Re: Basic Import to sysML blocks
« on: November 23, 2017, 11:25:48 pm »

So to summarise :

What fields in an EA import do i have to set to automatically create / update an element such that it is handled as a sysML 1.3 <<block>>, and retains all associations of the MDG ?

(Then other stereotypes but lets answer this one first)

Bugs and Issues / Basic Import to sysML blocks
« on: November 23, 2017, 10:33:29 pm »
I have a number of system elements in a separate requirements database tool and want to import them to EA using eadocx or the Native import tool.  If you do this the association with the MDG plugin is lost and the "magic" of the plugin to render the properties, parts and references is also lost.   I want to be able to use eadocx as a sync tool between the 2 platforms but i think the problem lays within EA in how it associates a basic "class" element with its MDG plug in and this gets lost in the translation.

EA V13 systems engineering edition, V13 Corporate edition + sysML MDG plugin 

Any ideas on the basics ?  I'm moderately familiar with the t_object table and decreasingly so therein!

Thanks for any insights...


Bugs and Issues / Re: HTML Report Compatibility in Chrome and Sharep
« on: July 31, 2013, 12:55:17 am »
 >:( >:( >:( >:( >:(

Utterly failed to get Sharepoint to display an HTML report in a webpart.  The browser reports

SCRIPT5: Access is denied.
displayToc.js, line 312 character 3

which is still the       changeCSS('#Preload','height',top.document.body.clientHeight-67+'px','this'); line which causes chrome to hang if run locally.

Im guessing that this is trying to fiddle with the layout of the browser frames which Sharepoint is laying out?? ( Although im surprised that its container does not appear as an entire browser to it)

So im officially stuck....  EA HTML outputs are not compatible with Microsoft Sharepoint.... really? Progress eh ... :'(

Bugs and Issues / Re: HTML Report Compatibility in Chrome and Sharep
« on: July 22, 2013, 06:21:37 pm »
Thanks Skiwi i now feel empowered with secret knowledge  ;)

Bugs and Issues / Re: HTML Report Compatibility in Chrome and Sharep
« on: July 19, 2013, 06:21:00 pm »
BTW i did search the forum for "chrome" and i get no hits (still don't) except this thread ????

Bugs and Issues / Re: HTML Report Compatibility in Chrome and Sharep
« on: July 19, 2013, 06:16:45 pm »
Ah  :) :) :) :) served it and it works.... (in Chrome) I will report back once we confirm that the Sharepoint web part is also fixed but i'm quietly confident...

Thanks for the help

Bugs and Issues / HTML Report Compatibility in Chrome and Sharepoint
« on: July 18, 2013, 07:24:24 pm »
We are trying to output HTML reports to a file server such that SharePoint can display them in a web part component as part of an overall project documentation repository.  We have hit a problem and also noticed that also Google Chrome suffers.  I have not specifically determined that the cause is the same but the symptoms are.

The symptom is that on load the the table of contents left hand pane crashes out with the web page just showing loading....

In chrome i have diagnosed this to the toc.js function ChangeCSS the css object has not been correctly initialised and the references to "rules" and "CSSrules" within the "target" object are both NULL, and hence the script borks and thats the end of it.   Stepped through the same process in Explorer and its fine...  I also checked the CSS on the W3C css validator and there is only one error and this i dont believe it the problem.

I am hoping that if i can get Chrome can read the css and display the page then Sharepoint will also behave, although that remains to be seen.  

Tested with Chrome Version 28.0.1500.72 m, EA V9.0

we have tested HTML output from 2 different projects on EA V8 and V9 and neither work with Chrome...

Any pointers greatly appreciated...

Yes Geert i asked sparx directly and they also pointed me to that whitepaper, although i haven't yet had time to try it properly.  The problem stems from the licence activation with EA being tied to the id of the thing that starts it, when system starts it it has no Key info registered and hangs on the keystore window interaction.  You need to create a service which starts EA in the system context once setup the keystore licence stuff for SYSTEM, then it should work.  Thats my reading of the method anyway....

Ah hmmm, thats odd because im getting the same problem when i run the    standalone non service version if i run it as a scheduled task.  I cannot access the server and have to invoke everything via remote desktop, this automatically logs off after 24hrs of inactivity so i need to run the automation SOMEHOW on the server.... unattended.

Do you understand what the actual problem is qwerty? or if there's a work around? or a "normal" way of doing this ?

I also have encountered this problem when trying to run a c# automation .exe to export the database to HTML.  I find that I only get the exception when the system is running as a scheduled task, I even wrote a service to wrap up the export in, however the same issue occurs.

EA starts in task manager opens then get lost in it own little world never to return @ 0% CPU load.   When the task is terminated control returns and the exception is thrown although I expect the exception has more to do with the ungraceful exit of the thread that anything else.

HOWEVER if I run the exe as a USER from the desktop this problem does not occur.  I have tried all possible combinations of run-as-user x etc as well as a scheduled task or a service.  It doesn't seem to want to work unless manually executed?

How  :-? can we progress this thawny issue ?   :'( :'( :'(

Top marks chaps right in both cases this :
Code: [Select]
           for (int i = 0; i < 10; i++)
                var new_item = package.Elements.AddNew("foo"+i.ToString(),"Requirement");
                new_item.notes = "blah blah blah";
Does much more like i what I was expecting...  Thanks guys :)

Automation Interface, Add-Ins and Tools / Automated requirements import
« on: October 18, 2014, 12:27:50 am »
I am wanting to import requirements from another tool from XML into EA using an standalone automation script I have come up with the following which looks like it should work but the eap file doesn't show the added requirements in the specified package... However the items are added somewhere as i can read them out again.....(multiple versions of the same thing as ive run it lots of times)..

Code: [Select]
           EA.Repository repo = new EA.Repository();
            EA.Package package = null;

            package = repo.GetPackageByGuid("{735D3E44-8417-4601-93D5-B7F6630CA782}");

            for (int i = 0; i < 10; i++)
                var new_item = package.Element.Requirements.AddNew("foo"+i.ToString(),"requirement");
                new_item.notes = "blah blah blah";

            foreach (dynamic req_items in package.Element.Requirements)


Is this method a non starter or should i persevere or should i find an alternative..  I found a few threads on this but not much in terms of automation....
Ultimately i want to check for existing items  / avoid duplicates update existing etc in a daily batch.

Any help much appreciated....

thanks for your patience, that looks a good read... It may have helped if i wasn't just searching the last weeks posts !

Pages: [1] 2