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 - Ian Mitchell

Pages: 1 ... 14 15 [16] 17
Not sure about RTF, but with eaDocX you can create LOADS of hyperlinks within your document.
We think it makes big documents much more readable. You can make documents which have a smaller 'main' part - which you really want the reader to look at - and lots of appendices, linked from the 'main' bit with  hyperlinks, which your readers MIGHT want to read.

The way to get this to work with eaDocX would be to give a different stereotype to the 'title' package then give it its own Profile.

Automation Interface, Add-Ins and Tools / Re: SynchTaggedValues
« on: August 06, 2013, 05:21:30 pm »
...and having those guys grinning at me isn't helping either...:-)

Automation Interface, Add-Ins and Tools / Re: SynchTaggedValues
« on: August 06, 2013, 05:20:16 pm »
I realise I'm a bit late into this discussion, and thanks Simon for the answer to my question: I was stuck on the basic adding of a new BPMN element.
It seems odd that we need to create a new element of type 'BPMN20.::Gateway', rather than one of type 'BPMN2.0::Decision' with a stereotype="Gateway", which is what I was expecting.
It seems that this MDG has effectively defined some new "types" rather than stereotypes of existing ones.
My question is therefore where are these new types listed? The BPMN help  explains very well what they are from the user's point of view e.g"Data Object", "End Event" etc, but is there somewhere where we can find the new type names which the API understands ? For example, do we:
addNew("something","BPMN2.0::Data Object") or
addnew("something","BPMN2.0::DataObject") etc

Also, is it just me who gets confused about what's a type, what's a stereotype, and what one of these new 'special types', which look like type+stereotype in the database, but which EA treats like first-class types when listing available types ? Are there some rules here which might merit a bit more explanation ?

So here's the data, done the hard way:

  • Resources      srchID={02707522-DB58-4db2-82A9-E987764859EB};
  • Method Details      srchID={FEDECDF1-720B-4fae-B36B-08AC1C35E18D};
  • Recently Modified Diagrams      srchID={EBF4F7B8-6188-4f32-B22A-3C7403EA6A95};
  • Recently Modified Elements      srchID={208FA579-C35F-436b-A557-83046DAF8F4E};
  • Failed Internal Tests      srchID={4D1F04A1-1762-4e3e-90AE-5CA86CBAC90E};
  • Find Orphans      srchID={0CA24A24-EFDA-436f-8E47-4D385118E214};
  • Attribute Details      srchID={A5481563-8672-454d-B038-927430FA86B1};
  • Simple      srchID={DEEA1BE3-4565-428b-B746-83403E071FE6}
  • Extended      srchID={FC9FB0D7-76F9-4db2-8635-5AE8172CF732};
  • Find Bookmarked Elements      srchID={4ECCA3E7-1674-43dc-900E-8A61D51C0441};
  • My Checked Out Packages      srchID={D3825173-0DAC-4bbb-874F-FCF1D445B1AF};
  • Simple Issues Search      srchID={DEEA1BE3-4565-428b-B746-83403E071FE6}
  • Requirements      srchID={67003A6F-D6F4-46d7-828E-66D55A3CF2AA};
  • Responsibility      srchID={A9EAC1EE-536B-45db-96C2-B49B4C1A0EAF};
  • Element Name      srchID={F5B9369D-F986-42ed-829C-EB4FA1072CD5};

Thanks gentlemen.
FYI - the EA-supplied, built-in searches are NOT in the /AppData/.../EA_Search.XML - these are only the user-defined ones.

As usual :-) Geert has the best suggestion: I'll just have to pick the built-in searches one at a time, and make a note of the GUIDs, then hard-code it into eaDocX.
@Sparx: this doesn't seem a very polite solution: any chance of a bit of help? Perhaps you might save me the trouble, and post the Name/GUID pairs ?
Pretty please :-)

In the definition of a ModelView, the name of  search is defined by its GUID.
But to run the search using repository.getElementsByQuery, we need the name of the search.
Does anyone know how to do a lookup on the search GUID to get its name ?

eaDocX can do this!
Just create an eaDocX 'section' in your Word document, and put a diagram in it. In the background, eaDocX remembers the GUID of the diagram, no matter where you move it to.

@Geert - I really liked that post - have you put it on the Community site? We should get some T Shirts made up for it!

Automation Interface, Add-Ins and Tools / Re: RunModelSearch
« on: May 25, 2013, 09:51:10 pm »
I think there may be a bit of confusion here.
There are two RunModelSearch methods: one in Repository, one in ProjectInterface.

ProjectInterface.RunModelSearch one has the one which just runs the search and allows for the showInEA option. Which seems to work just fine, but doesn't return the results.

Repository.RunModelSearch also runs, but the API documentation says it returns a string with the results.
Has anyone made this work? I can run it, and the search runs OK (but it also displays the results in the EA User Interface, which I don't want) but I can't get it to return any results.
In order to test it, i'm not passing any search criteria:


..but strXML is empty. The strReportName is OK, because the seach runs.

Is this a bug, or am I doing in wrong?

If you would like to be able to use the Stereotype of your Requirements in a Relationship Matrix, EA currently doesn't support it (as of V10).
BUT, if you generate documents using eaDocX, it allows you to choose the  Type AND Stereotype of items to appear in the matrix, as well as display the stereotype name (an other stuff) as additional rows/columns.
It only supports the 'main' stereotype - the one which is shown in the package browser: any other stereotypes are ignored.

I need to get back the contents of a diagram. Diagram.diagramObjects does this perfectly, but what about when the user has applied a Diagram Filter. Great feature, but how can I get the sub-set of diagramObjects from the diagram with the filter applied?
Looking at the format of the filter definition in t_xrefsystem (found that thanks to its really complicated, so no chance to do the filtering myself.
Any ideas ?

Automation Interface, Add-Ins and Tools / Re: storing (meta)data ?
« on: February 11, 2013, 11:04:43 pm »
Assuming that you don't want it to be a simple TaggedValue (which WOULD be visible in UI) then I guess all you can do is to use one of the existing columns in t_object. This would be dangerous, as Sparx might overwrite your data from somewhere else in the UI.
One approach might be to create a property of the element (in t_objectProperties) and put your data in there? Best to wait for the definitive solution from QUERTY...

If you use eaDocX to document your model, and not RTF, then you can create a diagram which shows just the methods/attributes you want, then document the diagram contents.

If you need highly-formatted document, have you looked at eaDocX?

Pages: 1 ... 14 15 [16] 17